replSetGetStatus¶

On this page

Definition
Example
Output

Definition¶

replSetGetStatus¶

The replSetGetStatus command returns the status of the replica set from the point of view of the current server. You must run the command against the admin database. The command has the following prototype format:

copy

{ replSetGetStatus: 1 }

The value specified does not affect the output of the command. Data provided by this command derives from data included in heartbeats sent to the current instance by other members of the replica set. Because of the frequency of heartbeats, these data can be several seconds out of date.

You can also access this functionality through the rs.status() helper in the mongo shell.

The mongod must have replication enabled and be a member of a replica set for the for replSetGetStatus to return successfully.

Example¶

The following example runs the replSetGetStatus command on the admin database of the replica set primary:

copy

use admin
db.runCommand( { replSetGetStatus : 1 } )

Consider the following example output:

copy

{
    "set" : "replset",
    "date" : ISODate("2014-05-01T14:44:03Z"),
    "myState" : 1,
    "members" : [
        {
            "_id" : 0,
            "name" : "m1.example.net:27017",
            "health" : 1,
            "state" : 1,
            "stateStr" : "PRIMARY",
            "uptime" : 269,
            "optime" : Timestamp(1404225575, 11),
            "optimeDate" : ISODate("2014-05-01T14:39:35Z"),
            "self" : true
        },
        {
            "_id" : 1,
            "name" : "m2.example.net:27017",
            "health" : 1,
            "state" : 2,
            "stateStr" : "SECONDARY",
            "uptime" : 265,
            "optime" : Timestamp(1404225575, 11),
            "optimeDate" : ISODate("2014-05-01T14:39:35Z"),
            "lastHeartbeat" : ISODate("2014-05-01T14:44:03Z"),
            "lastHeartbeatRecv" : ISODate("2014-05-01T14:44:02Z"),
            "pingMs" : 0,
            "syncingTo" : "m1.example.net:27017"
        },
        {
            "_id" : 2,
            "name" : "m3.example.net:27017",
            "health" : 1,
            "state" : 2,
            "stateStr" : "SECONDARY",
            "uptime" : 265,
            "optime" : Timestamp(1404225575, 11),
            "optimeDate" : ISODate("2014-05-01T14:39:35Z"),
            "lastHeartbeat" : ISODate("2014-05-01T14:44:02Z"),
            "lastHeartbeatRecv" : ISODate("2014-05-01T14:44:02Z"),
            "pingMs" : 0,
            "syncingTo" : "m1.example.net:27017"
        }
    ],
    "ok" : 1
}

Output¶

The replSetGetStatus command returns a document with the following fields:

replSetGetStatus.set¶: The set value is the name of the replica set, configured in the replSet setting. This is the same value as _id in rs.conf().

replSetGetStatus.date¶: The value of the date field is an ISODate of the current time, according to the current server. Compare this to the value of the lastHeartbeat to find the operational lag between the current host and the other hosts in the set.

replSetGetStatus.myState¶: The value of myState is an integer between 0 and 10 that represents the replica state of the current member.

replSetGetStatus.members¶

The members field holds an array that contains a document for every member in the replica set.

replSetGetStatus.members.name¶: The name field holds the name of the server.

replSetGetStatus.members.self¶: The self field is only included in the document for the current mongod instance in the members array. It’s value is true.

replSetGetStatus.members.errmsg¶: This field contains the most recent error or status message received from the member. This field may be empty (e.g. "") in some cases.

replSetGetStatus.members.health¶: The health value is only present for the other members of the replica set (i.e. not the member that returns rs.status.) This field conveys if the member is up (i.e. 1) or down (i.e. 0.)

replSetGetStatus.members.state¶: The value of state is an integer between 0 and 10 that represents the replica state of the member.

replSetGetStatus.members.stateStr¶: A string that describes state.

replSetGetStatus.members.uptime¶

The uptime field holds a value that reflects the number of seconds that this member has been online.

This value does not appear for the member that returns the rs.status() data.

replSetGetStatus.members.optime¶

Information regarding the last operation from the operation log that this member has applied.

replSetGetStatus.members.optime.t¶: A 32-bit timestamp of the last operation applied to this member of the replica set from the oplog.

replSetGetStatus.members.optime.i¶: An incremented field, which reflects the number of operations in since the last time stamp. This value only increases if there is more than one operation per second.

replSetGetStatus.members.optimeDate¶: An ISODate formatted date string that reflects the last entry from the oplog that this member applied. If this differs significantly from lastHeartbeat this member is either experiencing “replication lag” or there have not been any new operations since the last update. Compare members.optimeDate between all of the members of the set.

replSetGetStatus.members.self¶: Indicates which replica set member processed the replSetGetStatus command.

replSetGetStatus.members.lastHeartbeat¶

The lastHeartbeat value provides an ISODate formatted date and time of the transmission time of last heartbeat received from this member. Compare this value to the value of the date and lastHeartBeatRecv field to track latency between these members.

This value does not appear for the member that returns the rs.status() data.

replSetGetStatus.members.lastHeartbeatRecv¶: The lastHeartbeat value provides an ISODate formatted date and time that the last heartbeat was received from this member. Compare this value to the value of the date and lastHeartBeat field to track latency between these members.

replSetGetStatus.members.lastHeartbeatMessage¶: When the last heartbeat included an extra message, the lastHeartbeatMessage contains a string representation of that message.

replSetGetStatus.members.pingMs¶

The pingMs represents the number of milliseconds (ms) that a round-trip packet takes to travel between the remote member and the local instance.

This value does not appear for the member that returns the rs.status() data.

replSetGetStatus.syncingTo¶: The syncingTo field is only present on the output of rs.status() on secondary and recovering members, and holds the hostname of the member from which this instance is syncing.

← replSetFreeze replSetInitiate →