Couchbase http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 [MB-3158] cluster failover/rebalance expected behavior when one or more nodes are out of disk space http://www.couchbase.com/issues/browse/MB-3158 Couchbase Server On or more nodes running out of disk space cannot take down a cluster. Data already stored on a node should stay accessible, only writes to membase buckets should fail. <br/> <br/> Nodes should still be able to be removed from cluster or failed over. <br/> <br/> Attention also needs to be paid to behaviour of other areas that use disk space, such as logs MB-3158 cluster failover/rebalance expected behavior when one or more nodes are out of disk space Bug Major Resolved Won't Fix Public Dipti Borkar Frank Weigel Fri, 10 Dec 2010 13:27:49 -0600 Fri, 3 Aug 2012 19:00:41 -0500 Fri, 3 Aug 2012 19:00:41 -0500 2.0 couchbase-bucket ns_server 0 1 A Pivotal Tracker story has been created for this Issue: <a href="http://www.pivotaltracker.com/story/show/9305789">http://www.pivotaltracker.com/story/show/9305789</a> try this scenario and update before RC when one node runs out of disk space memcached goes into pending mode ) and the user can rebalance this node out from the cluster. <br/> <br/> <br/> Shutting down bucket &quot;default&quot; on &#39;<a href='mailto:ns_1@172.16.75.128'>ns_1@172.16.75.128</a>&#39; for server shutdown ns_memcached002 <a href='mailto:ns_1@172.16.75.128'>ns_1@172.16.75.128</a> 18:48:24 - Tue May 24, 2011 <br/> Usage of disk &quot;/&quot; on node &quot;172.16.75.128&quot; is over 100% <br/> <br/> if you have two nodes running out of disk space you will not be able to failover those two nodes because failover will timeout. <br/> the workaround is if you have two or more nodes running out of disk space you need to stop membase server on those two nodes and then you can fail over those nodes. Just so long as we understand this this is still a bug. Failover should NEVER time out Farshid, this can be closed right? Duplicate MB-3401 MB-3159 Date of First Response Tue, 24 May 2011 18:07:31 -0500 Flagged Rank 1663 Time In Status