嘗試設置Mongo復制，但最終有兩個輔助成員，沒有主要成員

Question

我一直在嘗試設置一個簡單的復制系統。 1個主mongo，1個備份和1個仲裁器。

不幸的是，解雇它導致主要被選為SECONDARY，而備份被選為PRIMARY（很好的工作仲裁者）。

Main的優先級為100，備份優先級為0，以及從屬延遲。

我試圖通過以下方式告訴備份：

PRIMARY>   db.runCommand({replSetReconfig: conf})
{
        "assertion" : "initiation and reconfiguration of a replica set must
be sent to a node that can become primary",
        "assertionCode" : 13420,
        "errmsg" : "db assertion failure",
        "ok" : 0
}
PRIMARY> .adminCommand({replSetStepDown:1000000, force:1})
Fri Jan 13 17:27:29 SyntaxError: syntax error (shell):1
PRIMARY> db.adminCommand({replSetStepDown:1000000, force:1})
Fri Jan 13 17:27:36 DBClientCursor::init call() failed
Fri Jan 13 17:27:36 query failed : admin.$cmd { replSetStepDown:
1000000.0, force: 1.0 } to: 127.0.0.1
Fri Jan 13 17:27:36 Error: error doing query: failed shell/
collection.js:151
Fri Jan 13 17:27:36 trying reconnect to 127.0.0.1
Fri Jan 13 17:27:36 reconnect 127.0.0.1 ok
SECONDARY>
SECONDARY>
SECONDARY> db.adminCommand({replSetStepDown:1000000, force:1})
{ "errmsg" : "not primary so can't step down", "ok" : 0 }

哪個有效，但主要還是次要的。

有任何想法嗎？ 謝謝！

配置文件

conf = {
  version: 90002,
  _id : "example",
  members: [
    {
      _id : 1,
      host : "main.example.com:27017",
      priority: 100
    },
    {
      _id : 2,
      host : "backup.example.com:27017",
      priority: 0,
      slaveDelay : 3600
    },
    {
      _id : 3,
      host : "arbiter.example.com:27017",
      priority: 0,
      arbiterOnly: true
    }
  ]
};

rs.status on main（）

{
  "set" : "example",
  "date" : ISODate("2012-01-13T23:29:09Z"),
  "myState" : 2,
  "members" : [
    {
      "_id" : 1,
      "name" : "main.example.com:27017",
      "health" : 1,
      "state" : 2,
      "stateStr" : "SECONDARY",
      "optime" : {
        "t" : 1326496827000,
        "i" : 1
      },
      "optimeDate" : ISODate("2012-01-13T23:20:27Z"),
      "self" : true
    },
    {
      "_id" : 2,
      "name" : "backup.example.com:27017",
      "health" : 1,
      "state" : 2,
      "stateStr" : "SECONDARY",
      "uptime" : 324,
      "optime" : {
        "t" : 1326492641000,
        "i" : 1
      },
      "optimeDate" : ISODate("2012-01-13T22:10:41Z"),
      "lastHeartbeat" : ISODate("2012-01-13T23:29:09Z"),
      "pingMs" : 0
    },
    {
      "_id" : 3,
      "name" : "arbiter.example.com:27017",
      "health" : 1,
      "state" : 7,
      "stateStr" : "ARBITER",
      "uptime" : 324,
      "optime" : {
        "t" : 0,
        "i" : 0
      },
      "optimeDate" : ISODate("1970-01-01T00:00:00Z"),
      "lastHeartbeat" : ISODate("2012-01-13T23:29:09Z"),
      "pingMs" : 0
    }
  ],
  "ok" : 1

}

rs.status（）備份

{
  "set" : "example",
  "date" : ISODate("2012-01-13T23:31:06Z"),
  "myState" : 2,
  "members" : [
    {
      "_id" : 0,
      "name" : "BACKUPVMW02:27017",
      "health" : 1,
      "state" : 2,
      "stateStr" : "SECONDARY",
      "optime" : {
        "t" : 1326492641000,
        "i" : 1
      },
      "optimeDate" : ISODate("2012-01-13T22:10:41Z"),
      "self" : true
    }
  ],
  "ok" : 1

Answer 1

事實證明有一個3節點設置，1個主要，1個從屬，1個仲裁器不能很好地工作。 刪除了從屬延遲，並且優先考慮了優先級（從頭開始重新安裝所有節點並刪除數據目錄）

Answer 2

您可能正在使用舊版本的mongodb - 他們用於投票的字段被稱為“投票”，我認為，不是優先級。 當他們切換到“優先級”字段時，你應該調用rs.reconfig（configfile），我想。