Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
2.0.1
-
Security Level: Public
-
Untriaged
Description
2.0.1-129-rel
steps:
1. cluster with 2 nodes: 10.3.121.112 & 10.3.121.113
2. click Remove for 10.3.121.113
3. stop cb on 10.3.121.113
result:
on UI 10.3.121.113 node is Down, but Rebalance button is enabled
only after cache refresh(F5 or Ctrl+F5) the button becomes disabled.
Alk, and another question related to rebalance with nodes down:
So we can run rebalance( through UI or Rest) when any node is not ready to rebalance( down or warmup). If I run a rebalance I see progress on a minute on UI. Does it make sense to start it at all, if any of the servers is certainly not ready yet?
Because now we can't trigger rebalance on UI after F5) but can via rest ( rebalance failure after 1 min)
Rebalance exited with reason
{not_all_nodes_are_ready_yet,['ns_1@10.3.121.113']} ns_orchestrator002 ns_1@10.3.121.112 14:26:30 - Wed Jan 16, 2013
Shutting down bucket "defaullt" on 'ns_1@10.3.121.113' for server shutdown ns_memcached002 ns_1@10.3.121.113 14:26:09 - Wed Jan 16, 2013
Bucket "defaullt" loaded on node 'ns_1@10.3.121.113' in 0 seconds. ns_memcached001 ns_1@10.3.121.113 14:25:51 - Wed Jan 16, 2013
Couchbase Server has started on web port 8091 on node 'ns_1@10.3.121.113'. menelaus_sup001 ns_1@10.3.121.113 14:25:49 - Wed Jan 16, 2013
Node 'ns_1@10.3.121.113' synchronized otp cookie pozzoodiircndvke from cluster ns_cookie_manager002 ns_1@10.3.121.113 14:25:49 - Wed Jan 16, 2013
Started rebalancing bucket defaullt ns_rebalancer000 ns_1@10.3.121.112 14:25:30 - Wed Jan 16, 2013
Starting rebalance, KeepNodes = ['ns_1@10.3.121.112'], EjectNodes = ['ns_1@10.3.121.113'] ns_orchestrator004 ns_1@10.3.121.112 14:25:30 - Wed Jan 16, 2013