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

MongoDB Replica set is not joining after changing the containers in Docker.

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.9
    • Component/s: None
    • Labels:
      None
    • Environment:
      Docker container
    • Linux

      2019-04-24T09:51:43.453-0500 I REPL [initandlisten] Recovering from stable timestamp: Timestamp(1556117443, 1) (top of oplog: { ts: Timestamp(1556117485, 1), t: 43 }, appliedThrough: { ts: Timestamp(0, 0), t: -1 }, TruncateAfter: Timestamp(0, 0))
      2019-04-24T09:51:43.453-0500 I REPL [initandlisten] Starting recovery oplog application at the stable timestamp: Timestamp(1556117443, 1)
      2019-04-24T09:51:43.453-0500 I REPL [initandlisten] Replaying stored operations from { : Timestamp(1556117443, 1) } (exclusive) to { : Timestamp(1556117485, 1) } (inclusive).
      2019-04-24T09:51:43.455-0500 I CONTROL [LogicalSessionCacheRefresh] Sessions collection is not set up; waiting until next sessions refresh interval: Replication has not yet been configured
      2019-04-24T09:51:43.455-0500 I NETWORK [initandlisten] waiting for connections on port 27017
      2019-04-24T09:51:43.459-0500 W NETWORK [replexec-0] getaddrinfo("mongodb2") failed: Temporary failure in name resolution
      2019-04-24T09:51:43.464-0500 W REPL [replexec-0] Locally stored replica set configuration does not have a valid entry for the current node; waiting for reconfig or remote heartbeat; Got "NodeNotFound: No host described in new configuration 93501 for replica set ecf-replicas-set maps to this node" while validating { _id: "ecf-replicas-set", version: 93501, protocolVersion: 1, writeConcernMajorityJournalDefault: true, members: [ { _id: 1, host: "mongodb1:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 2, host: "mongodb2:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 3, host: "mongodb3:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, catchUpTimeoutMillis: -1, catchUpTakeoverDelayMillis: 30000, getLastErrorModes: {}, getLastErrorDefaults: { w: "majority", wtimeout: 30000 }, replicaSetId: ObjectId('5bda38cf657acc2a8da906e1') } }
      2019-04-24T09:51:43.464-0500 I REPL [replexec-0] New replica set config in use: { _id: "ecf-replicas-set", version: 93501, protocolVersion: 1, writeConcernMajorityJournalDefault: true, members: [ { _id: 1, host: "mongodb1:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 2, host: "mongodb2:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 3, host: "mongodb3:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, catchUpTimeoutMillis: -1, catchUpTakeoverDelayMillis: 30000, getLastErrorModes: {}, getLastErrorDefaults: { w: "majority", wtimeout: 30000 }, replicaSetId: ObjectId('5bda38cf657acc2a8da906e1') } }
      2019-04-24T09:51:43.464-0500 I REPL [replexec-0] This node is not a member of the config
      2019-04-24T09:51:43.464-0500 I REPL [replexec-0] transition to REMOVED from STARTUP
      2019-04-24T09:51:43.464-0500 I REPL [replexec-0] Starting replication storage threads
      2019-04-24T09:51:43.464-0500 I REPL [replexec-0] Starting replication fetcher thread
      2019-04-24T09:51:43.464-0500 I REPL [replexec-0] Starting replication applier thread
      2019-04-24T09:51:43.464-0500 I REPL [replexec-0] Starting replication reporter thread
      2019-04-24T09:51:43.464-0500 I REPL [rsSync-0] Starting oplog application

            Assignee:
            daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
            Reporter:
            harsha7282 harshavardhan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: