-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
I ran rs.status() and it scared the everliving bejeezus out of me. It said that my newly brought up secondary was syncing to my primary and overwriting the data there. Then I realized that this is just a horrible message and it really meant it's syncing from the primary not to it.
{ "_id" : 15, "name" : "128.138.202.153:27017", "health" : 1, "state" : 5, "stateStr" : "STARTUP2", "uptime" : 4373, "optime" : Timestamp(1373384104, 1), "optimeDate" : ISODate("2013-07-09T15:35:04Z"), "lastHeartbeat" : ISODate("2013-07-09T19:21:31Z"), "lastHeartbeatRecv" : ISODate("1970-01-01T00:00:00Z"), "pingMs" : 7, "syncingTo" : "128.138.202.152:27017" }
,
- duplicates
-
SERVER-5461 Add syncSourceHost field to replSetGetStatus output
- Closed