It seems that MOXI lazily creates downstream connections, which causes problems when running in stand alone because my application thinks the server is dead until the connections are all loaded. Is this true? Is there a work around?
It is somewhat true, but that shouldn't be at all exposed to the application. What error message are you getting at the client level?
Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.Consider purchasing enterprise-level support from Couchbase: http://www.couchbase.com/products-and-services/overviewCall or email "sales -at- couchbase-dot- com" today!
Timeout. Server marked as dead.
And I presume that during this time, the actual server is still alive and responsive?
Moxi shouldn't be having any impact here...unless perhaps you're running well beyond the number of concurrent requests it can handle (~1k by default).
When this happens, can you telnet into Moxi and get the output of 'stats proxy' so we can see what Moxi thinks is going on?
© 2013 COUCHBASE All rights reserved.