Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
1.8.1
-
None
-
Security Level: Public
-
Moxi
Description
In following URL:
http://www.couchbase.com/docs/moxi-manual-1.8/moxi-performance-conncounts.html
downstream_max should be replaced by downstream_conn_max in 3 instances:
. You might have NUM_MOXI number of standalone moxi processes all feverishly processing requests at their downstream_max limits of concurrency.
. NUM_CONN_FROM_MOXI_TO_MEMBASE = NUM_MOXI_WORKER_THREADS x NUM_BUCKETS x downstream_max
. To simplify, let's say you just have a single bucket (such as the "default" bucket), that downstream_max is 4
I validated with Steve Yen that my suggestion is correct.
Also typo at:
http://www.couchbase.com/docs/moxi-manual-1.8/moxi-internals-thread-communication.html
"Communcation"