Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-494

One of the replica set member is always in "RECOVERING" state.

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.0
    • Component/s: None
    • Labels:
    • Environment:
      LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
      Red Hat Enterprise Linux Server release 6.5 (Santiago)

      Hi Team,
      We are using mongodb version of 3.0.4. we had set up Sharding env in two servers. Each shard is a replica set. Each replica set is having one primary, one secondary and one arbiter.

      The issue we are facing is that our replica set member in one of the replica set, got moved to "RECOVERING" state. we tried all the options mentioned in documentation (including intial sync after taking backup), but after restart it is moving to "STARTUP2" and then to "RECOVERING" and is staying on this state for days and not getting changed to "SECONDARY". By checkng on few jira tickets, we thought it is know bug in V3.0.2 and rectified in V3.0.4 (based on release notes).

      Please let us know, still that bug of residing in "RECOVERING" state due to some movechunk problem is there. If not, please help us out in getting rid of this issue. We are facing this often.

            Assignee:
            christkv Christian Amor Kvalheim
            Reporter:
            jebas Kingsly J
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: