[MB-5282] Rebooting a node, marks all its replica vbuckets to dead, due to firewall Created: 10/May/12 Updated: 09/Jan/13 Resolved: 10/May/12
|Reporter:||Karan Kumar (Inactive)||Assignee:||Aleksey Kondratenko|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Attachments:||10.1.3.114-8091-diag.txt.gz 10.1.3.115-8091-diag.txt.gz 10.1.3.116-8091-diag.txt.gz 10.1.3.117-8091-diag.txt.gz 10.1.3.118-8091-diag.txt.gz|
1) Load some items
2) Rebooted node .15. (Firewall get turned now now)
3) Node 15 comes back up..
vb_replica_curr_items = 0 as all vbuckets are marked as dead.
During this time, ns_server does not detect that the node is unreachable or anything. Until we disable the firewall.
Disable the firewall, all replica vbuckets are set back correctly.
|Comment by Aleksey Kondratenko [ 10/May/12 ]|
There's bug somewhere already that states this behavior is confusing. It's there for reason. I.e. janitor (piece of code that sets vbucket states) needs to be sure everything is healthy and warmed up before doing anything. I.e. it's conservative.|
Main problem (not mentioned in this ticket) is everything is marked as green but there's not indication that janitor actually needs other nodes to be up and warmed up.