MongoDB副本集--管理命令

4910阅读　0评论2017-12-22　zhangshengdong
分类：NOSQL

这篇文档主要介绍MongoDB副本集的日常查看和管理的命令.

1)命令行的查看命令:db.serverCmdLineOpts()

点击(此处)折叠或打开

  1. arps:SECONDARY> db.serverCmdLineOpts()
  2. {
  3.         "argv" : [
  4.                 "/opt/software/mongodb-linux-x86_64-3.0.1/bin/mongod",//启动参数mongod
  5.                 "-f",
  6.                 "/opt/software/mongodb-linux-x86_64-3.0.1/bin/mongodb.conf"  
  7.         ],//参数配置文件
  8.         "parsed" : {
  9.                 "config" : "/opt/software/mongodb-linux-x86_64-3.0.1/bin/mongodb.conf",
  10.                 "net" : {
  11.                         "port" : 27017   //端口
  12.                 },
  13.                 "processManagement" : {
  14.                         "fork" : true,
  15.                         "pidFilePath" : "/opt/data/mongodb/mongodb.pid"  //进程文件
  16.                 },
  17.                 "replication" : {
  18.                         "oplogSizeMB" : 10000,       //oplog日志大小
  19.                         "replSet" : "arps"           //副本集的名称arps
  20.                 },
  21.                 "storage" : {
  22.                         "dbPath" : "/opt/data/mongodb",   //数据存储的位置
  23.                         "directoryPerDB" : true,
  24.                         "mmapv1" : {
  25.                                 "preallocDataFiles" : false
  26.                         }
  27.                 },
  28.                 "systemLog" : {
  29.                         "destination" : "file",
  30.                         "logAppend" : true,
  31.                         "path" : "/opt/data/mongodb/log/mongodb.log"  //系统日志的位置
  32.                 }
  33.         },
  34.         "ok" : 1
  35. }
2）查看副本集状态的命令：rs.status()

点击(此处)折叠或打开

  1. arps:SECONDARY> rs.status()
  2. {
  3.         "set" : "arps",                                //副本集名称
  4.         "date" : ISODate("2017-12-22T06:12:21.904Z"),  //执行时间
  5.         "myState" : 2,                                
  6.         "syncingTo" : "172.17.4.37:27017",             //同步源:172.17.4.37:27017
  7.         "members" : [                                  //成员
  8.                 {
  9.                         "_id" : 0,                    
  10.                         "name" : "172.17.4.37:27017",
  11.                         "health" : 1,                 //健康状态值，1为UP，0为down
  12.                         "state" : 2,                  //成员状态值，2为secondary
  13.                         "stateStr" : "SECONDARY",
  14.                         "uptime" : 12354,
  15.                         "optime" : Timestamp(1513923135, 3),  //最近一次更改数据库的时间。
  16.                         "optimeDate" : ISODate("2017-12-22T06:12:15Z"),
  17.                                                   //最后一个操作发生的时间
  18.                         "lastHeartbeat" : ISODate("2017-12-22T06:12:20.999Z"),
  19.                                                   //最后一次心跳接收的时间值
  20.                         "lastHeartbeatRecv" : ISODate("2017-12-22T06:12:20.999Z"),
  21.                                                   //最近心跳的发送到达的时间值
  22.                         "pingMs" : 0,
  23.                         "syncingTo" : "172.17.4.38:27017",
  24.                         "configVersion" : 1
  25.                 },
  26.                 {
  27.                         "_id" : 1,
  28.                         "name" : "172.17.4.38:27017",
  29.                         "health" : 1,
  30.                         "state" : 1,                  //成员状态值，1位primary
  31.                         "stateStr" : "PRIMARY",
  32.                         "uptime" : 12354,
  33.                         "optime" : Timestamp(1513923135, 3),
  34.                         "optimeDate" : ISODate("2017-12-22T06:12:15Z"),
  35.                         "lastHeartbeat" : ISODate("2017-12-22T06:12:21.805Z"),
  36.                         "lastHeartbeatRecv" : ISODate("2017-12-22T06:12:20.956Z"),
  37.                         "pingMs" : 1,
  38.                         "electionTime" : Timestamp(1506330005, 1),
  39.                         "electionDate" : ISODate("2017-09-25T09:00:05Z"),
  40.                         "configVersion" : 1
  41.                 },
  42.                 {
  43.                         "_id" : 2,
  44.                         "name" : "172.17.4.39:27017",
  45.                         "health" : 1,
  46.                         "state" : 2,
  47.                         "stateStr" : "SECONDARY",
  48.                         "uptime" : 12356,
  49.                         "optime" : Timestamp(1513923135, 3),
  50.                         "optimeDate" : ISODate("2017-12-22T06:12:15Z"),
  51.                         "syncingTo" : "172.17.4.37:27017",
  52.                         "configVersion" : 1,
  53.                         "self" : true
  54.                 }
  55.         ],
  56.         "ok" : 1
  57. }
mongod实例每隔两秒就会向其他成员发送一个心跳包，并且通过rs.status()中返回的成员的health来判断成员的状态。如果primary节点不可用了，那么复制集中的所有secondary节点都会触发一次选举操作。选出新的primary节点。如果secondary节点有多个，则会选举拥有最新oplog时间戳记录的或者有较高权限的节点成为primary

3）添加、删除副本集成员：rs.add，rs.addArb()，rs.remove()，rs.reconfig()

点击(此处)折叠或打开

  1. 1)添加成员
  2. rs.add('172.17.4.39:27017')  //在添加成员之前，需要在目标成员里加上repset参数。

  4. 2)添加选举节点，不会同步数据
  1. rs.add({,"host":"192.168.200.252:27017","arbiterOnly":true}) rs.addArb()

  3. 3）修改配置
  1. 通过rs.reconfig()来实现。

  3. 4）删除成员
  4. rs.remove('172.17.4.39:27017')
4）副本集的配置：rs.config()

点击(此处)折叠或打开

  1. arps:PRIMARY> rs.config()
  2. {
  3.         "_id" : "arps",
  4.         "version" : 3,
  5.         "members" : [
  6.                 {
  7.                         "_id" : 0,
  8.                         "host" : "172.17.4.37:27017",//主机名
  9.                         "arbiterOnly" : false,       //是否为选举节点
  10.                         "buildIndexes" : true,       //是否建立索引
  11.                         "hidden" : false,            //是否隐藏
  12.                         "priority" : 1,              //优先级
  13.                         "tags" : {

  15.                         },
  16.                         "slaveDelay" : 0,
  17.                         "votes" : 1                 
  18.                 },
  19.                 {
  20.                         "_id" : 1,
  21.                         "host" : "172.17.4.38:27017",
  22.                         "arbiterOnly" : false,
  23.                         "buildIndexes" : true,
  24.                         "hidden" : false,
  25.                         "priority" : 1,
  26.                         "tags" : {

  28.                         },
  29.                         "slaveDelay" : 0,
  30.                         "votes" : 1
  31.                 },
  32.                 {
  33.                         "_id" : 2,
  34.                         "host" : "172.17.4.39:27017",
  35.                         "arbiterOnly" : false,
  36.                         "buildIndexes" : true,
  37.                         "hidden" : false,
  38.                         "priority" : 1,
  39.                         "tags" : {

  41.                         },
  42.                         "slaveDelay" : 0,
  43.                         "votes" : 1
  44.                 }
  45.         ],
  46.         "settings" : {
  47.                 "chainingAllowed" : true,                  //自动寻找数据源功能
  48.                 "heartbeatTimeoutSecs" : 10,               //心跳连接超时时间
  49.                 "getLastErrorModes" : {                    

  51.                 },
  52.                 "getLastErrorDefaults" : {                //write concern写入安全机制
  53.                         "w" : 1,                          //1为(应答时写入）
  54.                               //确认写入操作已经发送到指定的单个mongodb实例或者副本集的Primary
  55.                         "wtimeout" : 0                   
  56.                 }
  57.         }
  58. }

5.Secondary进入维护模式：replSetMaintenance

如何让一个成员远落后于Primary的，进入维护模式

点击(此处)折叠或打开

  1. arps:RECOVERING> db.adminCommand({"replSetMaintenance":true})   //进入维护模式

  3. arps:RECOVERING> rs.status().members
  4. [
  5.         {
  6.                 "_id" : 0,
  7.                 "name" : "172.17.4.37:27017",
  8.                 "health" : 1,
  9.                 "state" : 2,
  10.                 "stateStr" : "SECONDARY",
  11.                 "uptime" : 15241,
  12.                 "optime" : Timestamp(1513926020, 4),
  13.                 "optimeDate" : ISODate("2017-12-22T07:00:20Z"),
  14.                 "lastHeartbeat" : ISODate("2017-12-22T07:00:28.772Z"),
  15.                 "lastHeartbeatRecv" : ISODate("2017-12-22T07:00:28.771Z"),
  16.                 "pingMs" : 0,
  17.                 "syncingTo" : "172.17.4.38:27017",
  18.                 "configVersion" : 3
  19.         },
  20.         {
  21.                 "_id" : 1,
  22.                 "name" : "172.17.4.38:27017",
  23.                 "health" : 1,
  24.                 "state" : 1,
  25.                 "stateStr" : "PRIMARY",
  26.                 "uptime" : 15241,
  27.                 "optime" : Timestamp(1513926020, 4),
  28.                 "optimeDate" : ISODate("2017-12-22T07:00:20Z"),
  29.                 "lastHeartbeat" : ISODate("2017-12-22T07:00:28.772Z"),
  30.                 "lastHeartbeatRecv" : ISODate("2017-12-22T07:00:26.849Z"),
  31.                 "pingMs" : 0,
  32.                 "electionTime" : Timestamp(1506330005, 1),
  33.                 "electionDate" : ISODate("2017-09-25T09:00:05Z"),
  34.                 "configVersion" : 3
  35.         },
  36.         {
  37.                 "_id" : 2,
  38.                 "name" : "172.17.4.39:27017",
  39.                 "health" : 1,
  40.                 "state" : 3,
  41.                 "stateStr" : "RECOVERING",   //进入维护模式，会强制进入RECOVERING状态，不提供服务
  42.                 "uptime" : 15243,
  43.                 "optime" : Timestamp(1513926020, 4),
  44.                 "optimeDate" : ISODate("2017-12-22T07:00:20Z"),
  45.                 "syncingTo" : "172.17.4.38:27017",
  46.                 "maintenanceMode" : 1,
  47.                 "configVersion" : 3,
  48.                 "self" : true
  49.         }
  50. ]

  52. arps:RECOVERING> db.adminCommand({"replSetMaintenance":false})  //退出维护模式
6.主节点变成备份节点：rs.stepDown(time)，rs.freeze(time)

rs.stepDown(time)  可以让主节点退成备份节点，timie单位是秒，默认60s。60s内主被副本集的其他成员获得，时间到后，会重新进行选举，一般都会重新成为主（优先级）。

rs.freeze(time)：阻止选举，始终出于备份节点状态。比如主节点需要做一些维护，不希望其他成员选举为主节点，可以在每个备份节点上执行。强制他们出于备份节点状态。

点击(此处)折叠或打开

  1. arps:PRIMARY> rs.stepDown(30) //退出主节点，成为secondary节点
  2. .......
  3. .......
  4. 2017-12-22T15:05:52.110+0800 I NETWORK trying reconnect to 127.0.0.1:27017 (127.0.0.1) failed
  5. 2017-12-22T15:05:52.111+0800 I NETWORK reconnect 127.0.0.1:27017 (127.0.0.1) ok
  6. arps:SECONDARY>

  8. arps:SECONDARY> rs.status().members
  9. [
  10.         {
  11.                 "_id" : 0,
  12.                 "name" : "172.17.4.37:27017",
  13.                 "health" : 1,
  14.                 "state" : 1,
  15.                 "stateStr" : "PRIMARY",  //升级为主节点
  16.                 "uptime" : 15797,
  17.                 "optime" : Timestamp(1513926601, 3),
  18.                 "optimeDate" : ISODate("2017-12-22T07:10:01Z"),
  19.                 "lastHeartbeat" : ISODate("2017-12-22T07:09:43.092Z"),
  20.                 "lastHeartbeatRecv" : ISODate("2017-12-22T07:09:43.130Z"),
  21.                 "pingMs" : 0,
  22.                 "electionTime" : Timestamp(1513926357, 1),
  23.                 "electionDate" : ISODate("2017-12-22T07:05:57Z"),
  24.                 "configVersion" : 3
  25.         },
  26.         {
  27.                 "_id" : 1,
  28.                 "name" : "172.17.4.38:27017",
  29.                 "health" : 1,
  30.                 "state" : 2,
  31.                 "stateStr" : "SECONDARY",  //退位至备份节点
  32.                 "uptime" : 15797,
  33.                 "optime" : Timestamp(1513926601, 3),
  34.                 "optimeDate" : ISODate("2017-12-22T07:10:01Z"),
  35.                 "lastHeartbeat" : ISODate("2017-12-22T07:09:43.092Z"),
  36.                 "lastHeartbeatRecv" : ISODate("2017-12-22T07:09:43.245Z"),
  37.                 "pingMs" : 0,
  38.                 "syncingTo" : "172.17.4.37:27017",
  39.                 "configVersion" : 3
  40.         },
  41.         {
  42.                 "_id" : 2,
  43.                 "name" : "172.17.4.39:27017",
  44.                 "health" : 1,
  45.                 "state" : 2,
  46.                 "stateStr" : "SECONDARY",
  47.                 "uptime" : 15799,
  48.                 "optime" : Timestamp(1513926601, 3),
  49.                 "optimeDate" : ISODate("2017-12-22T07:10:01Z"),
  50.                 "syncingTo" : "172.17.4.37:27017",
  51.                 "configVersion" : 3,
  52.                 "self" : true
  53.         }
  54. ]
7.复制延迟状态查看db.printReplicationInfo()和db.printSlaveReplicationInfo()

点击(此处)折叠或打开

  1. arps:PRIMARY> db.printReplicationInfo()    //主上面执行的复制状态信息
  2. configured oplog size: 10000.003845214844MB
  3. log length start to end: 31637996secs (8788.33hrs)
  4. oplog first event time: Wed Dec 21 2016 10:54:05 GMT+0800 (CST)
  5. oplog last event time: Fri Dec 22 2017 15:14:01 GMT+0800 (CST)
  6. now: Fri Dec 22 2017 15:14:01 GMT+0800 (CST)

  8. arps:SECONDARY> db.printSlaveReplicationInfo()  //从上面执行的复制延迟信息
  9. source: 172.17.4.38:27017
  10.         syncedTo: Fri Dec 22 2017 15:14:01 GMT+0800 (CST)
  11.         0 secs (0 hrs) behind the primary
  12. source: 172.17.4.39:27017
  13.         syncedTo: Fri Dec 22 2017 15:14:01 GMT+0800 (CST)
  14.         0 secs (0 hrs) behind the primary






上一篇：MongoDB副本集--Secondary节点恢复实例
下一篇：Mongodb副本集--切换主从节点