KeyDB | A Multithreaded Fork of Redis | Performance Testing library

There are many example present over the internet. But, I would refer the official docs always.

Refer docs here : https://github.com/robaho/keydb and https://pkg.go.dev/github.com/robaho/keydb

How to use :

This command will import all certs contained in the p12 file to the kdb.

KeyDB, in fact, only runs the IO operations and Redis protocol parsing operations in parallel. It processes the commands in serial, i.e. process commands one-by-one, and working threads are synced with a spin lock.

That's why those simple set/get commands are blocked by a slow command. So even with KeyDB, you should NOT run slow command either and, the multiple threading won't help.

UPDATE

KeyDB can have multiple threads listen on the same IP:port, so that it can accept multiple connections in parallel, i.e. SO_REUSEPORT. Also it reads (including parsing received data into commands with redis protocol, i.e. RESP) and writes socket in parallel.

While Redis only have a single thread, i.e. main thread, listen on the IP:port. By default, Redis reads and writes socket in a single thread. Since Redis 6.0, you can enable io-threads to make it write socket in parallel. Also, if you enable io-threads-do-reads, Redis will also reading and protocol parsing in parallel.

The Go text/template range operator rebinds the . special variable, in this case to be the loop index. In your top-level template you have:

If you specify DATABASE=... in the connection string, the you must use a real database name , not an alias.

If you want to use an alias , then instead use DSN=... (and omit DATABASE=...).

Additionally, your connection string should contain HOSTNAME=... for best results.

Note also that if you only have a single certificate file then you can avoid the bother of creating a dedicated keystore on the client side by simply using the SSLServerCertificate=... keyword with a value being the fully qualified pathname to the certificate file.

Additionally, to externalise all the connection attributes from your C++ source code, you could simply use DSN=...;UID=...;PWD=...; and define the DSN attributes (including SSL attributes) in the db2dsdriver.cfg xml file. Your choice.

Your other errors such as the SQL1224N and SQL30040N are configuration specific, and your question omits the facts of your client and server configs. But fix the connection string first and these errors may disappear.

For the Node.js side you need to know which npm modules are being used to determine which settings to use. The ibmmq node library calls the C MQI API, which also takes care of TLS, so a NODE_DEBUG option is not going to help.

Going through the library it looks like you might be able to dynamically switch on logging by calling

One way to temporarily handle this situation is to modify: /database/config/db2inst1/sqllib/profile.env and in that text file alter the setting for the DB2COMM variable from 'TCPIP' to 'TCPIP,SSL' (or whatever you need).

However, this will only persist while the container exists .

So if you remove the container you will need to redo.

If you simply stop and start the container, the change will persist.

To make the change persist permanently, you would need to alter the image (or make a new image) so that file has the values you need. There may be more elegant solutions. To modify the image look at the instructions here in the Build your own section.

As no one wrote an answer at the end of bounty. I am writing my experience on solving the issue for the people who will get this error later.

Please note that this is not a canonical answer. But It is rather a workaround

I am starting with sharing what was happening.

We were trying to migrate from a Redis server hosting nearly 600 000 keys. Standard migration process was taking a lot of time for transfer that amount of keys from Redis to keyDB. So I came across a different solution.

Our KeyDB works on 2 Active-Active replica servers. I will provide the link to those are wondering how this system works.

https://medium.com/faun/failover-redis-like-cluster-from-two-masters-with-keydb-9ab8e806b66c

The solution was re-building up our Redis data using some MongoDB database aggregation and doing some batch operations on KeyDB.

Here is a simulation(Not exact as source. Also I did not tested for syntax errors)

Scheduling errors can often occur when affinity conditions are not met. Should you be using pod affinity rather than antiaffinity? Or even node affinity instead? Maybe try schedule with node affinity, or simpler affinity rules to try rule out affinity as a cause first.

See here for examples on affinity.