Question

在我们的制作环境中，我们有一个mongo副本的奇怪行为，我们的主要总是落后于副词。

的 rs.status（）：的

{
    "set" : "repl01",
    "date" : ISODate("2014-02-20T11:11:28.000Z"),
    "myState" : 2,
    "syncingTo" : "prodsrv04:27018",
    "members" : [ 
        {
            "_id" : 0,
            "name" : "prodsrv02:27018",
            "health" : 1,
            "state" : 2,
            "stateStr" : "SECONDARY",
            "uptime" : 6271,
            "optime" : Timestamp(1392894670, 97),
            "optimeDate" : ISODate("2014-02-20T11:11:10.000Z"),
            "self" : true
        }, 
        {
            "_id" : 1,
            "name" : "prodsrv03:27018",
            "health" : 1,
            "state" : 2,
            "stateStr" : "SECONDARY",
            "uptime" : 6270,
            "optime" : Timestamp(1392894670, 68),
            "optimeDate" : ISODate("2014-02-20T11:11:10.000Z"),
            "lastHeartbeat" : ISODate("2014-02-20T11:11:28.000Z"),
            "lastHeartbeatRecv" : ISODate("1970-01-01T00:00:00.000Z"),
            "pingMs" : 2
        }, 
        {
            "_id" : 2,
            "name" : "prodsrv04:27018",
            "health" : 1,
            "state" : 1,
            "stateStr" : "PRIMARY",
            "uptime" : 6270,
            "optime" : Timestamp(1392894669, 113),
            "optimeDate" : ISODate("2014-02-20T11:11:09.000Z"),
            "lastHeartbeat" : ISODate("2014-02-20T11:11:27.000Z"),
            "lastHeartbeatRecv" : ISODate("2014-02-20T11:11:28.000Z"),
            "pingMs" : 6
        }
    ],
    "ok" : 1
}

主操作时间：时间戳（1392894669,113）;
Slave optime：Timestamp（1392894670,68）;

怎么回事？

为什么这个主要成员在一个mongodb副本集中落后于次要成员

0 个答案: