-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.4.8
-
Component/s: None
-
Labels:
-
ALL
-
I have a replica set cluster with 1 member, and when I restart it, it has been in the recovering state。Before I restarted, it was in the primary state。
I intercepted its startup log, hoping to help diagnose the problem。
This confuses me
test-gxm-fa842-replica0:RECOVERING> rs.status()test-gxm-fa842-replica0:RECOVERING> rs.status(){ "set" : "test-gxm-fa842-replica0", "date" : ISODate("2021-12-03T08:22:58.647Z"), "myState" : 3, "term" : NumberLong(10), "syncSourceHost" : "", "syncSourceId" : -1, "heartbeatIntervalMillis" : NumberLong(2000), "majorityVoteCount" : 1, "writeMajorityCount" : 1, "votingMembersCount" : 1, "writableVotingMembersCount" : 1, "optimes" : { "lastCommittedOpTime" : { "ts" : Timestamp(0, 0), "t" : NumberLong(-1) }, "lastCommittedWallTime" : ISODate("1970-01-01T00:00:00Z"), "appliedOpTime" : { "ts" : Timestamp(1638519598, 1), "t" : NumberLong(1) }, "durableOpTime" : { "ts" : Timestamp(1638519598, 1), "t" : NumberLong(1) }, "lastAppliedWallTime" : ISODate("2021-12-03T08:19:58.388Z"), "lastDurableWallTime" : ISODate("2021-12-03T08:19:58.388Z") }, "lastStableRecoveryTimestamp" : Timestamp(1638519548, 1), "members" : [ { "_id" : 0, "name" : "test-gxm-fa842-replica0-0-0.test-gxm-fa842-replica0-headless.qfusion-admin:27017", "health" : 1, "state" : 3, "stateStr" : "RECOVERING", "uptime" : 42, "optime" : { "ts" : Timestamp(1638519598, 1), "t" : NumberLong(1) }, "optimeDate" : ISODate("2021-12-03T08:19:58Z"), "syncSourceHost" : "", "syncSourceId" : -1, "infoMessage" : "Could not find member to sync from", "configVersion" : 1, "configTerm" : 1, "self" : true, "lastHeartbeatMessage" : "" } ], "ok" : 1}
- is duplicated by
-
-
- Closed
-