Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-10776

All members in replica set went to STARTUP2 state and remains there.

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.4.1
    • Component/s: Replication
    • Environment:
      Linux (CentOs 5.8)
    • Fully Compatible

      Hi,
      I am facing an issue with one of replica-set members which I created in my environment.
      I created replica-set has 5 members, out of 5 one is arbiter and two of the members have priority is 2. Each member is running in individual Linux machine.
      All members are running well before shutting down the members. After I bring up one by one member arbiter came up properly as it arbiter state and reaming members of the replica-set are remains at STARTUP2 state.

      How can i bring up the members who are all in STARTUP2 to the running state like PRIMARY with SECONDARY states?

      Could you please suggest?

      Note: All members are running with --nojournal
      Attached mongodb logs for your reference

      Thanks & Regards
      Krishnachaitanya

        1. Replica_set startup2 member logs.rar
          10 kB

            Assignee:
            Unassigned Unassigned
            Reporter:
            kthummur Krishnachaitanya Thummuru
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: