Couchbase Server

Rebooting a node, marks all its replica vbuckets to dead, due to firewall

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 1.8.1-release-candidate
  • Fix Version/s: 1.8.1
  • Component/s: moxi
  • Security Level: Public
  • Labels:
    None
  • Environment:
    181-810

Description

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.


vb_dead_num 205


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.
  1. GZip Archive
    10.1.3.114-8091-diag.txt.gz
    10/May/12 5:21 PM
    1.32 MB
    Karan Kumar
  2. GZip Archive
    10.1.3.115-8091-diag.txt.gz
    10/May/12 5:21 PM
    579 kB
    Karan Kumar
  3. GZip Archive
    10.1.3.116-8091-diag.txt.gz
    10/May/12 5:21 PM
    705 kB
    Karan Kumar
  4. GZip Archive
    10.1.3.117-8091-diag.txt.gz
    10/May/12 5:21 PM
    704 kB
    Karan Kumar
  5. GZip Archive
    10.1.3.118-8091-diag.txt.gz
    10/May/12 5:21 PM
    695 kB
    Karan Kumar

Activity

Ascending order - Click to sort in descending order
Karan Kumar made changes -
Field Original Value New Value
Summary Rebooting a node, marks all its replica vbuckets to dead Rebooting a node, marks all its replica vbuckets to dead, due to firewall
Hide
Permalink
Aleksey Kondratenko added a comment -
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.
Show
Aleksey Kondratenko added a comment - 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.
Aleksey Kondratenko made changes -
Status Open [ 1 ] Resolved [ 5 ]
Resolution Duplicate [ 3 ]
Farshid Ghods made changes -
Status Resolved [ 5 ] Closed [ 6 ]

People

  • Assignee:
    Aleksey Kondratenko
    Reporter:
    Karan Kumar
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: