In the JSON from the stats API, the “curr_connections” reports something that looks like the total number of connections to the whole cluster, numerous times. In my case, an 8 node cluster with 16,000 connections will report 58 items having 16,000 each. The real number of connections to each node is closer to 2,000. I don’t know what the significance of 58 items might be, but it could be the total number of client hosts.
I see something similar reported via DogStatsD. The metric “couchbase.by_bucket.curr_connections” reports something similar, which makes the monitoring graph fairly misleading, especially taken as a sum.
Is this a bug or is there some logical rationale behind this metric report? What I am expecting is the value from the couchbase console under “Server Resources / connections” which in my case does report 2,000 connections (the number of connections for the node that the console hits.)
This is on Community 2.2.