mongodb 副本集的维护(1)

简介:

一、修改副本集中各成员的优先级:

shard1:PRIMARY> conf=rs.conf()

{

"_id" : "shard1",

"version" : 3,

"protocolVersion" : NumberLong(1),

"members" : [

{

"_id" : 0,

"host" : "mongo01-jp:27027",

"arbiterOnly" : false,

"buildIndexes" : true,

"hidden" : false,

"priority" : 1,

"tags" : {


},

"slaveDelay" : NumberLong(0),

"votes" : 1

},

{

"_id" : 1,

"host" : "mongo02-jp:27027",

"arbiterOnly" : false,

"buildIndexes" : true,

"hidden" : false,

"priority" : 1,

"tags" : {


},

"slaveDelay" : NumberLong(0),

"votes" : 1

},

{

"_id" : 2,

"host" : "mongo03-jp:27027",

"arbiterOnly" : true,

"buildIndexes" : true,

"hidden" : false,

"priority" : 1,

"tags" : {


},

"slaveDelay" : NumberLong(0),

"votes" : 1

}

],

"settings" : {

"chainingAllowed" : true,

"heartbeatIntervalMillis" : 2000,

"heartbeatTimeoutSecs" : 10,

"electionTimeoutMillis" : 10000,

"catchUpTimeoutMillis" : 2000,

"getLastErrorModes" : {


},

"getLastErrorDefaults" : {

"w" : 1,

"wtimeout" : 0

},

"replicaSetId" : ObjectId("5850deb0205cd94104cd9a38")

}

}

shard1:PRIMARY> conf.members[0].priority=100

100

shard1:PRIMARY> conf.members[1].priority=90

90

shard1:PRIMARY> rs.reconfig(conf)

{ "ok" : 1 }

shard1:PRIMARY> rs.conf()

{

"_id" : "shard1",

"version" : 4,

"protocolVersion" : NumberLong(1),

"members" : [

{

"_id" : 0,

"host" : "mongo01-jp:27027",

"arbiterOnly" : false,

"buildIndexes" : true,

"hidden" : false,

"priority" : 100,

"tags" : {


},

"slaveDelay" : NumberLong(0),

"votes" : 1

},

{

"_id" : 1,

"host" : "mongo02-jp:27027",

"arbiterOnly" : false,

"buildIndexes" : true,

"hidden" : false,

"priority" : 90,

"tags" : {


},

"slaveDelay" : NumberLong(0),

"votes" : 1

},

{

"_id" : 2,

"host" : "mongo03-jp:27027",

"arbiterOnly" : true,

"buildIndexes" : true,

"hidden" : false,

"priority" : 1,

"tags" : {


},

"slaveDelay" : NumberLong(0),

"votes" : 1

}

],

"settings" : {

"chainingAllowed" : true,

"heartbeatIntervalMillis" : 2000,

"heartbeatTimeoutSecs" : 10,

"electionTimeoutMillis" : 10000,

"catchUpTimeoutMillis" : 2000,

"getLastErrorModes" : {


},

"getLastErrorDefaults" : {

"w" : 1,

"wtimeout" : 0

},

"replicaSetId" : ObjectId("5850deb0205cd94104cd9a38")

}

}

shard1:PRIMARY>

关于优先级范围从0 至 1000 (3.2以上版本) ,优先级越大,越可能成为primary;若优先级为0,则该节点无资格参与primary的选举。

如果希望某节点不参与primary的选举有两种方法: 1、将该节点优先级设置为0;2、rs.freeze(30) 在cluster选举primary时,将该节点暂时冻结30S。

如果希望将本primary节点降为secondary状态,可以执行 rs.stepDown() 。


二、在副本集中删除成员、重新添加成员

shard2:PRIMARY> rs.status()

{

"set" : "shard2",

"date" : ISODate("2016-12-14T06:12:11.986Z"),

"myState" : 1,

"term" : NumberLong(1),

"heartbeatIntervalMillis" : NumberLong(2000),

"optimes" : {

"lastCommittedOpTime" : {

"ts" : Timestamp(1481695926, 1),

"t" : NumberLong(1)

},

"appliedOpTime" : {

"ts" : Timestamp(1481695926, 1),

"t" : NumberLong(1)

},

"durableOpTime" : {

"ts" : Timestamp(1481695926, 1),

"t" : NumberLong(1)

}

},

"members" : [

{

"_id" : 0,

"name" : "mongo02-jp:27028",

"health" : 1,

"state" : 1,

"stateStr" : "PRIMARY",

"uptime" : 1128,

"optime" : {

"ts" : Timestamp(1481695926, 1),

"t" : NumberLong(1)

},

"optimeDate" : ISODate("2016-12-14T06:12:06Z"),

"electionTime" : Timestamp(1481695445, 2),

"electionDate" : ISODate("2016-12-14T06:04:05Z"),

"configVersion" : 4,

"self" : true

},

{

"_id" : 1,

"name" : "mongo01-jp:27028",

"health" : 1,

"state" : 2,

"stateStr" : "SECONDARY",

"uptime" : 464,

"optime" : {

"ts" : Timestamp(1481695926, 1),

"t" : NumberLong(1)

},

"optimeDurable" : {

"ts" : Timestamp(1481695926, 1),

"t" : NumberLong(1)

},

"optimeDate" : ISODate("2016-12-14T06:12:06Z"),

"optimeDurableDate" : ISODate("2016-12-14T06:12:06Z"),

"lastHeartbeat" : ISODate("2016-12-14T06:12:10.206Z"),

"lastHeartbeatRecv" : ISODate("2016-12-14T06:12:11.202Z"),

"pingMs" : NumberLong(0),

"syncingTo" : "mongo02-jp:27028",

"configVersion" : 4

},

{

"_id" : 2,

"name" : "mongo03-jp:27028",

"health" : 1,

"state" : 7,

"stateStr" : "ARBITER",

"uptime" : 439,

"lastHeartbeat" : ISODate("2016-12-14T06:12:10.205Z"),

"lastHeartbeatRecv" : ISODate("2016-12-14T06:12:10.125Z"),

"pingMs" : NumberLong(0),

"configVersion" : 4

}

],

"ok" : 1

}

shard2:PRIMARY> rs.remove("mongo01-jp:27028")

{ "ok" : 1 }

shard2:PRIMARY> rs.remove("mongo03-jp:27028")

{ "ok" : 1 }

shard2:PRIMARY> rs.status()

{

"set" : "shard2",

"date" : ISODate("2016-12-14T06:13:18.227Z"),

"myState" : 1,

"term" : NumberLong(1),

"heartbeatIntervalMillis" : NumberLong(2000),

"optimes" : {

"lastCommittedOpTime" : {

"ts" : Timestamp(1481695994, 1),

"t" : NumberLong(1)

},

"appliedOpTime" : {

"ts" : Timestamp(1481695994, 1),

"t" : NumberLong(1)

},

"durableOpTime" : {

"ts" : Timestamp(1481695994, 1),

"t" : NumberLong(1)

}

},

"members" : [

{

"_id" : 0,

"name" : "mongo02-jp:27028",

"health" : 1,

"state" : 1,

"stateStr" : "PRIMARY",

"uptime" : 1195,

"optime" : {

"ts" : Timestamp(1481695994, 1),

"t" : NumberLong(1)

},

"optimeDate" : ISODate("2016-12-14T06:13:14Z"),

"electionTime" : Timestamp(1481695445, 2),

"electionDate" : ISODate("2016-12-14T06:04:05Z"),

"configVersion" : 6,

"self" : true

}

],

"ok" : 1

}

shard2:PRIMARY> rs.add("mongo03-jp:27028")

{ "ok" : 1 }

shard2:PRIMARY> rs.addArb("mongo01-jp:27028")

{ "ok" : 1 }

shard2:PRIMARY> rs.status()

{

"set" : "shard2",

"date" : ISODate("2016-12-14T06:39:40.718Z"),

"myState" : 1,

"term" : NumberLong(1),

"heartbeatIntervalMillis" : NumberLong(2000),

"optimes" : {

"lastCommittedOpTime" : {

"ts" : Timestamp(1481697576, 1),

"t" : NumberLong(1)

},

"appliedOpTime" : {

"ts" : Timestamp(1481697576, 1),

"t" : NumberLong(1)

},

"durableOpTime" : {

"ts" : Timestamp(1481697576, 1),

"t" : NumberLong(1)

}

},

"members" : [

{

"_id" : 0,

"name" : "mongo02-jp:27028",

"health" : 1,

"state" : 1,

"stateStr" : "PRIMARY",

"uptime" : 2777,

"optime" : {

"ts" : Timestamp(1481697576, 1),

"t" : NumberLong(1)

},

"optimeDate" : ISODate("2016-12-14T06:39:36Z"),

"electionTime" : Timestamp(1481695445, 2),

"electionDate" : ISODate("2016-12-14T06:04:05Z"),

"configVersion" : 9,

"self" : true

},

{

"_id" : 1,

"name" : "mongo03-jp:27028",

"health" : 1,

"state" : 2,

"stateStr" : "SECONDARY",

"uptime" : 1034,

"optime" : {

"ts" : Timestamp(1481697576, 1),

"t" : NumberLong(1)

},

"optimeDurable" : {

"ts" : Timestamp(1481697576, 1),

"t" : NumberLong(1)

},

"optimeDate" : ISODate("2016-12-14T06:39:36Z"),

"optimeDurableDate" : ISODate("2016-12-14T06:39:36Z"),

"lastHeartbeat" : ISODate("2016-12-14T06:39:38.838Z"),

"lastHeartbeatRecv" : ISODate("2016-12-14T06:39:39.594Z"),

"pingMs" : NumberLong(0),

"syncingTo" : "mongo02-jp:27028",

"configVersion" : 9

},

{

"_id" : 2,

"name" : "mongo01-jp:27028",

"health" : 1,

"state" : 7,

"stateStr" : "ARBITER",

"uptime" : 1128,

"lastHeartbeat" : ISODate("2016-12-14T06:39:39.053Z"),

"lastHeartbeatRecv" : ISODate("2016-12-14T06:39:36.708Z"),

"pingMs" : NumberLong(0),

"configVersion" : 9

}

],

"ok" : 1

}










本文转自 meteor_hy 51CTO博客,原文链接:http://blog.51cto.com/caiyuanji/1882646,如需转载请自行联系原作者
目录
相关文章
|
存储 NoSQL MongoDB
MongoDB 复制(副本集)
10月更文挑战第17天
223 2
MongoDB 复制(副本集)
|
NoSQL 容灾 MongoDB
MongoDB主备副本集方案:两台服务器使用非对称部署的方式实现高可用与容灾备份
在资源受限的情况下,为了实现MongoDB的高可用性,本文探讨了两种在两台服务器上部署MongoDB的方案。方案一是通过主备身份轮换,即一台服务器作为主节点,另一台同时部署备节点和仲裁节点;方案二是利用`priority`设置实现自动主备切换。两者相比,方案二自动化程度更高,适合追求快速故障恢复的场景,而方案一则提供了更多的手动控制选项。文章最后对比了这两种方案与标准三节点副本集的优缺点,指出三节点方案在高可用性和数据一致性方面表现更佳。
1256 5
|
存储 NoSQL Shell
MongoDB复制(副本集)总结
这篇文章是关于MongoDB副本集的总结,包括复制原理、设置副本集、案例分析等内容。
371 1
|
NoSQL MongoDB
MongoDB分片+副本集高可用集群的启停步骤
MongoDB分片+副本集高可用集群的启停步骤
585 0
|
NoSQL MongoDB 数据库
国内唯一 阿里云荣膺MongoDB“2024年度DBaaS认证合作伙伴奖”
阿里云连续第五年斩获MongoDB合作伙伴奖项,也是唯一获此殊荣的中国云厂商。一起学习MongoDB副本集的选举机制以及可能会出现的特殊情况。
国内唯一 阿里云荣膺MongoDB“2024年度DBaaS认证合作伙伴奖”
|
监控 NoSQL MongoDB
【MongoDB 专栏】MongoDB 的副本集故障转移与恢复
【5月更文挑战第11天】MongoDB的副本集是高可用性关键,提供数据冗余和自动故障转移。由主节点和从节点组成,主节点处理写操作,从节点同步数据。当主节点故障,副本集通过选举产生新主节点,确保服务不间断。故障转移涉及节点优先级和数据同步状态的考量。恢复阶段解决数据不一致,重点包括节点部署监控、数据同步策略、选举机制和备份恢复计划。网络延迟和大规模数据可能带来挑战,需优化网络、性能调优和定期演练。随着技术进步,副本集的故障转移与恢复将更高效、智能,保障数据安全,支撑业务系统的稳定运行。
740 3
【MongoDB 专栏】MongoDB 的副本集故障转移与恢复
|
存储 NoSQL 前端开发
MongoDB——副本集与分片
 MongoDB复制是将数据同步在多个服务器的过程。
1213 0
MongoDB——副本集与分片
|
NoSQL MongoDB Windows
MongoDB 读写分离——Windows MongoDB 副本集配置
MongoDB 读写分离——Windows MongoDB 副本集配置
419 0
|
监控 NoSQL 算法
【MongoDB】 MongoDB的副本集是什么?
【4月更文挑战第1天】【MongoDB】 MongoDB的副本集是什么?
|
存储 监控 NoSQL
MongoDB 副本集:构建可靠的数据备份与高可用性系统
MongoDB 副本集:构建可靠的数据备份与高可用性系统
288 0

推荐镜像

更多