http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/MB-3575 Couchbase Server -Configure Moxi with a list of URL&#39;s: <br/> ./moxi <a href="http://node1:8091/pools/default/bucketsStreaming/default,">http://node1:8091/pools/default/bucketsStreaming/default,</a> <a href="http://node2:8091/pools/default/bucketsStreaming/default,">http://node2:8091/pools/default/bucketsStreaming/default,</a> <a href="http://node3:8091/pools/default/bucketsStreaming/default">http://node3:8091/pools/default/bucketsStreaming/default</a> <br/> <br/> -Rebalance node 1 out of the cluster (for maintenance) <br/> -Restart Moxi <br/> -Moxi will continuously spin on node1 with the following errors: <br/> 2011-04-08 15:30:21: (agent_config.c.389) configuration received <br/> 2011-04-08 15:30:21: (agent_config.c.448) ERROR: could not parse JSON from REST server: Requested resource not found. <br/> <br/> Two things need to happen here: <br/> -Moxi&#39;s logging needs to be improved to tell the user which Node it is connecting to and which ones are giving it problems (not just once at the top, but for every log mesage) <br/> -Moxi needs to realize that this node has an invalid config (it knows it got an error at least) and move onto the next. MB-3575

Moxi should automatically skip removed or uninitialized nodes

Bug Major Resolved Fixed Public Steve Yen Perry Krug 1.7.0-release-notes Fri, 8 Apr 2011 14:54:39 -0500 Tue, 10 Apr 2012 10:46:02 -0500 Tue, 10 Apr 2012 10:46:02 -0500 1.6.5.3 1.7 GA moxi 0 1 Workaround is to stop the service on the node that was removed from the cluster. This also happens with fast bucket deletion patches. Steps are: <br/> <br/> * create cluster <br/> * load data <br/> * delete bucket <br/> * create bucket with same name <br/> * try loading data <br/> * moxi fails because it keeps invalid connections in pool <br/> This requires some internal API changes between moxi and libconflate to pass the error knowledge across several function invocations to the right place. Not risky. A Pivotal Tracker story has been created for this Issue: <a href="http://www.pivotaltracker.com/story/show/13245071">http://www.pivotaltracker.com/story/show/13245071</a> Some fixes on the way to the real fix... <br/> <br/> <a href="http://review.membase.org/6338">http://review.membase.org/6338</a> <br/> <a href="http://review.membase.org/6339">http://review.membase.org/6339</a> Unfortunately, the code that discovers a problem is in an asynchronous thread that&#39;s &quot;far away&quot; from the REST HTTP code. <br/> <br/> Will bend code to our will. &nbsp;<a href="http://review.membase.org/6342">http://review.membase.org/6342</a> <br/> &nbsp;<a href="http://review.membase.org/6343">http://review.membase.org/6343</a> Perry Krug deleted the linked story in Pivotal Tracker this test is failing now ( 1.8.1 manifest )<br/> <br/> OK<br/> ./t/issue-<a href="http://www.couchbase.com/issues/browse/MB-3575" title="Moxi should automatically skip removed or uninitialized nodes"><strike>MB-3575</strike></a>.sh: line 212: 19957 Terminated: 15 ./moxi -z <a href="http://127.0.0.1:22100/bad,http://127.0.0.1:4567/pools/default/bucketsStreaming/default,http://127.0.0.1:22101/bad">http://127.0.0.1:22100/bad,http://127.0.0.1:4567/pools/default/bucketsStreaming/default,http://127.0.0.1:22101/bad</a> -Z port_listen=11266,downstream_conn_max=1,downstream_max=0,downstream_timeout=300,wait_queue_timeout=300,downstream_conn_queue_timeout=300,connect_timeout=300,auth_timeout=300 2&gt;&gt; /tmp/issue-<a href="http://www.couchbase.com/issues/browse/MB-3575" title="Moxi should automatically skip removed or uninitialized nodes"><strike>MB-3575</strike></a>.out<br/> No matching processes belonging to you were found<br/> ----------------------<br/> FAIL count expect 0, got 20<br/> make: *** [test] Error 1 never mind .didn&#39;t have gem sinatra installed Date of First Response Fri, 15 Apr 2011 13:11:59 -0500 Flagged Rank 6842 Time In Status