compared with
Current by Matt Ingenthron
on Feb 15, 2013 03:44.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
Under normal operation the cluster should be in a “stable” state and the configuration shouldn't change. If your application is using short lived connections or a lot of connections from the same machine you are constantly requesting the server to give you the current configuration of the server. These are HTTP streaming requests which ns_server isn’t implementing very efficiently (slow to set up and requires a fair amount of resources in ns_server). As an example it takes 18 seconds to connect 1000 clients on the loop back interface on my quad-core AMD machine with 4 GB memory.
Under normal operations the cluster should be in a “stable” state and the configuration shouldn't change. If your application is using short lived connections or a lot of connections from the same machine you are constantly requesting the server to give you the current configuration of the server. These are HTTP streaming requests which, in some realases, the ns_server component of the Couchbase Cluster server software isn’t implementing very efficiently (slow to set up and requires a fair amount of resources in ns_server).

The idea is to use a local cache in the file system on the clients so that the clients don’t talk to ns_server unless there is an actual change in the cluster topology.
To mitigate this error and to be even more efficient, the idea is to use a local _cache_ in the file system on the client side so that the clients don’t talk to ns_server unless there is an actual change in the cluster topology.