Unable to set min-clients-per-thread from keydb.conf

[javedsha]

trafficstars

Describe the bug

When setting min-clients-per-thread in keydb.conf, after deployment, the value is set to some random value. For e.g., when I set it to 4, after deployment, when I login to the VM, connect to keydb via keydb-cli, I can see the value set to 28. Not sure why :)

I am able to set this value by directly running config set min-clients-per-thread 4 directly with the keydb-cli, but I have to do this for every master/replica.

[javedsha]

@msotheeswaran-sc what does priority 2 means? Can someone have a look at this? Is this a bug or some mistake from my side?

[msotheeswaran-sc]

Could be either, if it is a bug then it is marked as Priority 2 since it doesn't have a significant negative impact on KeyDB's usability. To understand if it is some mistake from your side I would need more context as to how your deployment is setup.

[javedsha]

This is our keydb.conf (main parts):

port 0 cluster-enabled yes server-threads 4 server-thread-affinity true min-clients-per-thread 4

When we deploy using this config, and check 'min-clients-per-thread' value it is set to 28. Which is a problem, as the multi threading doesn't really kicks in for us, as we less number of clients.

We can still set te value to 4, by running the command config set min-clients-per-thread 4 in each primary node.

[msotheeswaran-sc]

@javedsha works fine for me with server-threads 4 server-thread-affinity true min-clients-per-thread 4

can you provide more specific repro instructions, I can't fix this if I can't reproduce it