-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
Affects Version/s: mongodb-2.4, mongodb-3.0
-
Labels:None
The rs.status() command sometimes includes a maintenanceMode property. But this property and the possible values is not defined. Apparently, it can take on -1 and -7. There is a relationship to the execution of repair and compact and how this property is set. But, neither the property, it's possible values, and what causes these values to be set so is not documented.
For example from version 2.4:
> rs.status()
{
"set" : "RS1",
"date" : ISODate("2015-08-11T12:35:50Z"),
"myState" : 2,
"syncingTo" : "p-monolith-mongo-rs1-use1d-01.app.hudl.com:27018",
"members" : [
{ "_id" : 25, "name" : "p-monolith-mongo-rs1-use1c-01.app.hudl.com:27018", "health" : 1, "state" : 2, "stateStr" : "SECONDARY", "uptime" : 776682, "optime" : Timestamp(1439296548, 2), "optimeDate" : ISODate("2015-08-11T12:35:48Z"), "lastHeartbeat" : ISODate("2015-08-11T12:35:48Z"), "lastHeartbeatRecv" : ISODate("2015-08-11T12:35:49Z"), "pingMs" : 0, "syncingTo" : "p-monolith-mongo-rs1-use1d-01.app.hudl.com:27018" }
,
{ "_id" : 27, "name" : "p-monolith-mongo-rs1-use1d-01.app.hudl.com:27018", "health" : 1, "state" : 1, "stateStr" : "PRIMARY", "uptime" : 886454, "optime" : Timestamp(1439296549, 19), "optimeDate" : ISODate("2015-08-11T12:35:49Z"), "lastHeartbeat" : ISODate("2015-08-11T12:35:49Z"), "lastHeartbeatRecv" : ISODate("2015-08-11T12:35:48Z"), "pingMs" : 1 }
,
{ "_id" : 29, "name" : "p-monolith-mongo-rs1-use1e-01.app.hudl.com:27018", "health" : 1, "state" : 2, "stateStr" : "SECONDARY", "uptime" : 5673507, "optime" : Timestamp(1439296549, 19), "optimeDate" : ISODate("2015-08-11T12:35:49Z"), "maintenanceMode" : -1, "self" : true }
],
"ok" : 1
}