After doing failover,Rebalancing cost so mach time!What happened?
Fri, 05/13/2011 - 02:14
My cluster has two nodes,Node A and Node B.Node B's network interface down.The communication between A and B Failed.So I do failover.After a while,Node B's network interface recovered.Then,I do rebalancing.The action costs so much time.
During the progress,Some errors occured(show from the logs).
Port server vbucketmigrator on node 'ns_1@10.1.1.160' exited with status 78. Restarting. Messages: Connecting to {Sock 10.1.1.22:11210}
Failed to connect to host: Failed to connect to [10.1.1.22:11210]
Those errors look to be related to the network interface going down, basically it is saying that the vbucketmigrator process on .160 could not connect to .22.
What is the state of things now? Is rebalancing going on?
Perry
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/overview
Call or email "sales -at- couchbase-dot- com" today!