Details
-
Bug
-
Resolution: Not a Bug
-
Minor
-
None
-
6.5.1
-
None
-
Triaged
-
Ubuntu 64-bit
-
1
-
Yes
Description
In couchbase4, we could change connection limit (to sustain small connections spikes) using this command:
curl u [admin]:[}}{{password}}{{] -X POST http://localhost:8091/pools/default/settings/memcached/global -data maxconn=60000
Now in Coucbase 6 (Community Edition 6.5.1 build 6299), we are unable to change this value, the URL above do not work anymore.
Checking the source, looks like the value is now hardcoded:
https://github.com/couchbase/ns_server/blob/master/src/ns_config_default.erl
We need this capability as when we have big campaigns, we can sometimes have a huge increase in users, so new sessions and cache access and overload the couchbase. Due to the way the cluster works, adding more nodes not always spread the connections, some keys are more accessed than others, so a few nodes usually have more connections than others. So as horizontal scale do not solve the problem, we need a vertical scale (not hardware resources, but just the connection limit)
Without this capability to finetune the connection limit, the cluster will start giving errors. Worse, with the connection limit reached, other cluster nodes marked one node as failed and quickly overload the remaining, ending in a cluster crash. So without this feature, we are unable to use couchbase 6 as we risk cluster failure with little workarounds to avoid it.
In couchbase 4 we increased that limit to 60k and then 80k.
In couchbase 6 we were unable to increase the limit and had to revert back to couchbase4 to avoid new cluster failures.
Attachments
Issue Links
- relates to
-
DOC-7795 Document connection management settings
- Closed