小丸子学MongoDB系列之——副本集Auto-Failover

最新推荐文章于 2020-05-07 14:44:33 发布
最新推荐文章于 2020-05-07 14:44:33 发布
阅读量151 收藏
点赞数
文章标签： 数据库 shell 网络
    MongoDB副本集是通过自动故障切换特性来提供的高可用功能，当主节点成员不可用时从节点成员会自动变成主节点来继续对外提供服务，下面为大家演示两种副本集架构下的自动故障切换。
一.Auto-Failover（一主俩从架构）
1.查看副本集状态
[mgousr01@vm1 ~]$ mongo 192.168.157.128:47017
MongoDB shell version: 3.0.3
connecting to: 192.168.157.128:47017/test
rstl:PRIMARY> rs.status()
{
        "set" : "rstl",
        "date" : ISODate("2015-12-07T07:47:14.958Z"),
        "myState" : 1,
        "members" : [
                {
                        "_id" : 0,
                        "name" : "192.168.157.128:47017",
                        "health" : 1,
                        "state" : 1,
                        "stateStr" : "PRIMARY",
                        "uptime" : 258664,
                        "optime" : Timestamp(1449459199, 2),
                        "optimeDate" : ISODate("2015-12-07T03:33:19Z"),
                        "electionTime" : Timestamp(1449458787, 1),
                        "electionDate" : ISODate("2015-12-07T03:26:27Z"),
                        "configVersion" : 1,
                        "self" : true
                },
                {
                        "_id" : 1,
                        "name" : "192.168.157.128:47027",
                        "health" : 1,
                        "state" : 2,
                        "stateStr" : "SECONDARY",
                        "uptime" : 15651,
                        "optime" : Timestamp(1449459199, 2),
                        "optimeDate" : ISODate("2015-12-07T03:33:19Z"),
                        "lastHeartbeat" : ISODate("2015-12-07T07:47:14.804Z"),
                        "lastHeartbeatRecv" : ISODate("2015-12-07T07:47:14.212Z"),
                        "pingMs" : 0,
                        "syncingTo" : "192.168.157.128:47017",
                        "configVersion" : 1
                },
                {
                        "_id" : 2,
                        "name" : "192.168.157.128:47037",
                        "health" : 1,
                        "state" : 2,
                        "stateStr" : "SECONDARY",
                        "uptime" : 15651,
                        "optime" : Timestamp(1449459199, 2),
                        "optimeDate" : ISODate("2015-12-07T03:33:19Z"),
                        "lastHeartbeat" : ISODate("2015-12-07T07:47:14.696Z"),
                        "lastHeartbeatRecv" : ISODate("2015-12-07T07:47:14.509Z"),
                        "pingMs" : 0,
                        "syncingTo" : "192.168.157.128:47017",
                        "configVersion" : 1
                }
        ],
        "ok" : 1
}


2.模拟主节点成员故障
[mgousr01@vm1 ~]$ netstat -ntpl|grep 47017
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 192.168.157.128:47017       0.0.0.0:*                   LISTEN      26892/mongod       
     
[mgousr01@vm1 ~]$ kill -9 26892
[mgousr01@vm1 ~]$ mongo 192.168.157.128:47017
MongoDB shell version: 3.0.3
connecting to: 192.168.157.128:47017/test
2015-12-04T14:44:59.102+0800 W NETWORK  Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-04T14:44:59.103+0800 E QUERY    Error: couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
    at connect (src/mongo/shell/mongo.js:181:14)
    at (connect):1:6 at src/mongo/shell/mongo.js:181
exception: connect failed

[mgousr01@vm1 ~]$ mongo 192.168.157.128:47027
MongoDB shell version: 3.0.3
connecting to: 192.168.157.128:47027/test
rstl:PRIMARY> rs.status();
{
        "set" : "rstl",
        "date" : ISODate("2015-12-04T06:45:46.896Z"),
        "myState" : 1,
        "members" : [
                {
                        "_id" : 0,
                        "name" : "192.168.157.128:47017",
                        "health" : 0,
                        "state" : 8,
                        "stateStr" : "(not reachable/healthy)",
                        "uptime" : 0,
                        "optime" : Timestamp(0, 0),
                        "optimeDate" : ISODate("1970-01-01T00:00:00Z"),
                        "lastHeartbeat" : ISODate("2015-12-04T06:45:46.244Z"),
                        "lastHeartbeatRecv" : ISODate("2015-12-04T06:44:17.958Z"),
                        "pingMs" : 0,
                        "lastHeartbeatMessage" : "Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed",
                        "configVersion" : -1
                },
                {
                        "_id" : 1,
                        "name" : "192.168.157.128:47027",
                        "health" : 1,
                        "state" : 1,
                        "stateStr" : "PRIMARY",
                        "uptime" : 653,
                        "optime" : Timestamp(1449210941, 1),
                        "optimeDate" : ISODate("2015-12-04T06:35:41Z"),
                        "electionTime" : Timestamp(1449211460, 1),
                        "electionDate" : ISODate("2015-12-04T06:44:20Z"),
                        "configVersion" : 1,
                        "self" : true
                },
                {
                        "_id" : 2,
                        "name" : "192.168.157.128:47037",
                        "health" : 1,
                        "state" : 2,
                        "stateStr" : "SECONDARY",
                        "uptime" : 603,
                        "optime" : Timestamp(1449210941, 1),
                        "optimeDate" : ISODate("2015-12-04T06:35:41Z"),
                        "lastHeartbeat" : ISODate("2015-12-04T06:45:46.031Z"),
                        "lastHeartbeatRecv" : ISODate("2015-12-04T06:45:46.031Z"),
                        "pingMs" : 0,
                        "configVersion" : 1
                }
        ],
        "ok" : 1
}


3.观察一主俩从架构的Auto-Failover
成员mg27的日志：
2015-12-04T14:44:19.979+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location10276 DBClientBase::findN: transport error: 192.168.157.128:47017 ns: admin.$cmd query: { replSetHeartbeat: "rstl", pv: 1, v: 1, from: "192.168.157.128:47027", fromId: 1, checkEmpty: false }
2015-12-04T14:44:19.985+0800 I REPL     [ReplicationExecutor] Standing for election
2015-12-04T14:44:19.985+0800 I REPL     [ReplicationExecutor] replSet possible election tie; sleeping 665ms until 2015-12-04T14:44:20.650+0800
2015-12-04T14:44:19.986+0800 W NETWORK  [ReplExecNetThread-3] Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-04T14:44:19.986+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location18915 Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
2015-12-04T14:44:19.987+0800 W NETWORK  [ReplExecNetThread-0] Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-04T14:44:19.987+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location18915 Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
2015-12-04T14:44:20.651+0800 I REPL     [ReplicationExecutor] Standing for election
2015-12-04T14:44:20.651+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2015-12-04T14:44:20.653+0800 I REPL     [ReplicationExecutor] replSet election succeeded, assuming primary role
2015-12-04T14:44:20.653+0800 I REPL     [ReplicationExecutor] transition to PRIMARY
2015-12-04T14:44:21.094+0800 I REPL     [rsSync] transition to primary complete; database writes are now permitted

成员mg37的日志：
2015-12-04T14:44:19.980+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location10276 DBClientBase::findN: transport error: 192.168.157.128:47017 ns: admin.$cmd query: { replSetHeartbeat: "rstl", pv: 1, v: 1, from: "192.168.157.128:47037", fromId: 2, checkEmpty: false }
2015-12-04T14:44:19.985+0800 I REPL     [ReplicationExecutor] Standing for election
2015-12-04T14:44:19.985+0800 W NETWORK  [ReplExecNetThread-1] Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-04T14:44:19.986+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location18915 Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
2015-12-04T14:44:19.986+0800 I REPL     [ReplicationExecutor] replSet possible election tie; sleeping 666ms until 2015-12-04T14:44:20.652+0800
2015-12-04T14:44:19.986+0800 W NETWORK  [ReplExecNetThread-1] Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-04T14:44:19.986+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location18915 Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
2015-12-04T14:44:20.652+0800 I REPL     [ReplicationExecutor] replSetElect voting yea for 192.168.157.128:47027 (1)
2015-12-04T14:44:21.963+0800 I REPL     [ReplicationExecutor] Member 192.168.157.128:47027 is now in state PRIMARY
注：从上述日志可以发现两个从节点成员通过心跳机制都无法向主节点发起请求，于是开始进行选举，由于两个候选成员都有可能成为 主节点，所以选举可能会出现打平的现象，最终成员mg27成为主节点成员。


4.验证新的副本集数据同步是否正常
[mgousr01@vm1 ~]$ mongo 192.168.157.128:47027
MongoDB shell version: 3.0.3
connecting to: 192.168.157.128:47027/test
rstl:PRIMARY> use soho
switched to db soho
rstl:PRIMARY> db.food.find()
{ "_id" : ObjectId("5664fdfe1830846a3331ce02"), "name" : "egg", "price" : 38 }
rstl:PRIMARY> db.food.insert({name:"cake",price:100});
WriteResult({ "nInserted" : 1 })
rstl:PRIMARY> db.food.find()
{ "_id" : ObjectId("5664fdfe1830846a3331ce02"), "name" : "egg", "price" : 38 }
{ "_id" : ObjectId("56653f83e9fccdbf504e8548"), "name" : "cake", "price" : 100 }

[mgousr01@vm1 ~]$ mongo 192.168.157.128:47037
MongoDB shell version: 3.0.3
connecting to: 192.168.157.128:47037/test
rstl:SECONDARY> rs.slaveOk()
rstl:SECONDARY> show dbs;
local  0.203GB
soho   0.078GB
rstl:SECONDARY> use soho
switched to db soho
rstl:SECONDARY> show tables;
food
system.indexes
rstl:SECONDARY> db.food.find();
{ "_id" : ObjectId("5664fdfe1830846a3331ce02"), "name" : "egg", "price" : 38 }
{ "_id" : ObjectId("56653f83e9fccdbf504e8548"), "name" : "cake", "price" : 100 }
注：从上面的输出发现新的副本集没有问题


二.Auto-Failover（一主一从一仲裁架构）
1.初始化副本集并查看状态
[mgousr01@vm1 ~]$ mongo 192.168.157.128:47017
MongoDB shell version: 3.0.3
connecting to: 192.168.157.128:47017/test
> cfg=
{
    "_id" : "rstl",
    "version" : 1,
    "members" : [
         {
            "_id" : 0,
            "host" : "192.168.157.128:47017"
         },
         {
            "_id" : 1,
            "host" : "192.168.157.128:47027"
         },
         {
            "_id" : 2,
            "host" : "192.168.157.128:47037",
            "arbiterOnly":true 
         }
     ]
}
 
> rs.initiate(cfg)
{ "ok" : 1 }

rstl:OTHER> rs.status()
{
        "set" : "rstl",
        "date" : ISODate("2015-12-07T08:30:04.224Z"),
        "myState" : 1,
        "members" : [
                {
                        "_id" : 0,
                        "name" : "192.168.157.128:47017",
                        "health" : 1,
                        "state" : 1,
                        "stateStr" : "PRIMARY",
                        "uptime" : 657,
                        "optime" : Timestamp(1449476903, 1),
                        "optimeDate" : ISODate("2015-12-07T08:28:23Z"),
                        "electionTime" : Timestamp(1449476907, 1),
                        "electionDate" : ISODate("2015-12-07T08:28:27Z"),
                        "configVersion" : 1,
                        "self" : true
                },
                {
                        "_id" : 1,
                        "name" : "192.168.157.128:47027",
                        "health" : 1,
                        "state" : 2,
                        "stateStr" : "SECONDARY",
                        "uptime" : 100,
                        "optime" : Timestamp(1449476903, 1),
                        "optimeDate" : ISODate("2015-12-07T08:28:23Z"),
                        "lastHeartbeat" : ISODate("2015-12-07T08:30:03.484Z"),
                        "lastHeartbeatRecv" : ISODate("2015-12-07T08:30:03.518Z"),
                        "pingMs" : 0,
                        "configVersion" : 1
                },
                {
                        "_id" : 2,
                        "name" : "192.168.157.128:47037",
                        "health" : 1,
                        "state" : 7,
                        "stateStr" : "ARBITER",
                        "uptime" : 100,
                        "lastHeartbeat" : ISODate("2015-12-07T08:30:03.523Z"),
                        "lastHeartbeatRecv" : ISODate("2015-12-07T08:30:03.523Z"),
                        "pingMs" : 0,
                        "configVersion" : 1
                }
        ],
        "ok" : 1
}


2.模拟主节点成员故障
[mgousr01@vm1 ~]$ netstat -ntpl|grep 47017
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 192.168.157.128:47017       0.0.0.0:*                   LISTEN      36268/mongod     
     
[mgousr01@vm1 ~]$ kill -9 36268
[mgousr01@vm1 ~]$ mongo 192.168.157.128:47017
MongoDB shell version: 3.0.3
connecting to: 192.168.157.128:47017/test
2015-12-07T16:42:46.486+0800 W NETWORK  Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-07T16:42:46.488+0800 E QUERY    Error: couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
    at connect (src/mongo/shell/mongo.js:181:14)
    at (connect):1:6 at src/mongo/shell/mongo.js:181
exception: connect failed

[mgousr01@vm1 ~]$ mongo 192.168.157.128:47027
MongoDB shell version: 3.0.3
connecting to: 192.168.157.128:47027/test
rstl:PRIMARY> rs.status()
{
        "set" : "rstl",
        "date" : ISODate("2015-12-07T08:43:02.047Z"),
        "myState" : 1,
        "members" : [
                {
                        "_id" : 0,
                        "name" : "192.168.157.128:47017",
                        "health" : 0,
                        "state" : 8,
                        "stateStr" : "(not reachable/healthy)",
                        "uptime" : 0,
                        "optime" : Timestamp(0, 0),
                        "optimeDate" : ISODate("1970-01-01T00:00:00Z"),
                        "lastHeartbeat" : ISODate("2015-12-07T08:43:00.318Z"),
                        "lastHeartbeatRecv" : ISODate("2015-12-07T08:42:06.201Z"),
                        "pingMs" : 0,
                        "lastHeartbeatMessage" : "Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed",
                        "configVersion" : -1
                },
                {
                        "_id" : 1,
                        "name" : "192.168.157.128:47027",
                        "health" : 1,
                        "state" : 1,
                        "stateStr" : "PRIMARY",
                        "uptime" : 1336,
                        "optime" : Timestamp(1449476903, 1),
                        "optimeDate" : ISODate("2015-12-07T08:28:23Z"),
                        "electionTime" : Timestamp(1449477728, 1),
                        "electionDate" : ISODate("2015-12-07T08:42:08Z"),
                        "configVersion" : 1,
                        "self" : true
                },
                {
                        "_id" : 2,
                        "name" : "192.168.157.128:47037",
                        "health" : 1,
                        "state" : 7,
                        "stateStr" : "ARBITER",
                        "uptime" : 878,
                        "lastHeartbeat" : ISODate("2015-12-07T08:43:00.267Z"),
                        "lastHeartbeatRecv" : ISODate("2015-12-07T08:43:00.264Z"),
                        "pingMs" : 0,
                        "configVersion" : 1
                }
        ],
        "ok" : 1
}


3.观察一主一从一仲裁架构的Auto-Failover
成员mg27的日志：
2015-12-07T16:42:08.218+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location10276 DBClientBase::findN: transport error: 192.168.157.128:47017 ns: admin.$cmd query: { replSetHeartbeat: "rstl", pv: 1, v: 1, from: "192.168.157.128:47027", fromId: 1, checkEmpty: false }
2015-12-07T16:42:08.218+0800 I REPL     [ReplicationExecutor] Standing for election
2015-12-07T16:42:08.219+0800 W NETWORK  [ReplExecNetThread-0] Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-07T16:42:08.220+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location18915 Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
2015-12-07T16:42:08.220+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2015-12-07T16:42:08.220+0800 W NETWORK  [ReplExecNetThread-0] Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-07T16:42:08.220+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location18915 Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
2015-12-07T16:42:08.220+0800 I REPL     [ReplicationExecutor] replSet election succeeded, assuming primary role
2015-12-07T16:42:08.220+0800 I REPL     [ReplicationExecutor] transition to PRIMARY
2015-12-07T16:42:08.525+0800 I REPL     [rsSync] transition to primary complete; database writes are now permitted

成员mg37的日志：
2015-12-07T16:42:08.217+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location10276 DBClientBase::findN: transport error: 192.168.157.128:47017 ns: admin.$cmd query: { replSetHeartbeat: "rstl", pv: 1, v: 1, from: "192.168.157.128:47037", fromId: 2, checkEmpty: false }
2015-12-07T16:42:08.218+0800 W NETWORK  [ReplExecNetThread-4] Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-07T16:42:08.218+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location18915 Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
2015-12-07T16:42:08.219+0800 W NETWORK  [ReplExecNetThread-4] Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-07T16:42:08.219+0800 I NETWORK  [initandlisten] connection accepted from 192.168.157.128:39452 #59 (2 connections now open)
2015-12-07T16:42:08.219+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to 192.168.157.128:47017; Location18915 Failed attempt to connect to 192.168.157.128:47017; couldn't connect to server 192.168.157.128:47017 (192.168.157.128), connection attempt failed
2015-12-07T16:42:08.220+0800 I REPL     [ReplicationExecutor] replSetElect voting yea for 192.168.157.128:47027 (1)
2015-12-07T16:42:10.220+0800 W NETWORK  [ReplExecNetThread-0] Failed to connect to 192.168.157.128:47017, reason: errno:111 Connection refused
2015-12-07T16:42:10.220+0800 I REPL     [ReplicationExecutor] Member 192.168.157.128:47027 is now in state PRIMARY
注：从上述日志可以发现两个从节点成员通过心跳机制都无法向主节点发起请求，于是开始进行选举，从成员mg27的日志并没有发现一主两从架构中的选举争用信息， 最终成员mg27成为主节点成员，此时成员mg27也获得了数据库写的权限


总结：对于三个节点的副本集成员来说，官方建议选择1主俩从的架构，而仲裁节点一般适应于拥有偶数个副本集成员的情况下，这样可以避免选举打平的现象

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/20801486/viewspace-1867663/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/20801486/viewspace-1867663/

ckml77559
关注
mongodb-windows-x86-64-7.0.5-signed.msi
02-18
mongodb-windows-x86_64-7.0.5-signed.msi 数据库构建工具
MongoDB 4.2副本集自动故障转移（一主一副一仲裁）
aa5181的专栏
03-18 414
一、检查副本集状态 handong1:PRIMARY>rs.status() { "set":"handong1", "date":ISODate("2021-03-18T11:43:08...
MongoDB 关于用户认证
灯火觅阑珊
05-07 391
1.开启用户认证步骤 1.1以非用户认证模式开启实例，如配置文件中注释#auth=true 1.2在admin下创建一个管理用户，至少要有userAdmin或userAdminAnyDatabase权限 use admin db.createUser( { user: "root", pwd: "sam", roles: [ { role: "root", db: "a...
mongodb 新版本高可用解决方案-replica sets副本集部署详细过程
csdn's blog
07-20 1万+
Mongodb副本集： NoSQL的产生就是为了解决大数据量、高扩展性、高性能、灵活数据模型、高可用性。但是光通过主从模式的架构远远达不到上面几点，由此MongoDB设计了副本集和分片的功能，先来用用副本集。 Mongodb副本集的同步机制： 数据复制的目的是使数据得到最大的可用性，避免单点故障引起的整站不能访问的情况的发生，Mongodb的副本集在同一时刻只有一台服务器是可以写...
MongoDB集群-主从复制(副本集)、failover
dianhe6449的博客
02-27 169
1.概念 　　主从复制的目的：数据冗余、备份、读写分离 　　主从方式：一主一从（不推荐，只能实现复制，主节点挂掉且未重新启动的时候，无法提升从节点为master），一主一从一裁判，一主多从 　　复制方式：主节点记录在其上的所有操作oplog，从节点定期轮询主节点获取这些操作，然后对自己的数据副本执行这些操作，从而保证从节点的数据与主节点一致。 　　　　　　复制/同步的是操作日志而...
MongoDB 报错AuthenticationFailed Missing credentials for authenticating as internal user
灯火觅阑珊
05-07 898
复制集开启auth验证后，日志报错： [ReplicationExecutor] Error in heartbeat request to 127.0.0.1:37017; AuthenticationFailed Missing credentials for authenticating as internal user 原因是开启auth之后，需要增加keyFile验证。 创建keyfil...
mongodb-org-server-8.0.3-amd64.deb
最新发布
11-06
mongodb-org-server-8.0.3-amd64.deb
MongoDB Community Server（mongodb-windows-x86_64-5.0.8-signed.msi
05-28
MongoDB Community Server（mongodb-windows-x86_64-5.0.8-signed.msi）适用于RedHat / CentOS 7.0 MongoDB是一个基于分布式文件存储的数据库。由C++语言编写。旨在为WEB应用提供可扩展的高性能数据存储解决方案。 ...
副本集是如何实现自动Failover的
MongoDB中文社区
07-03 380
简介 最近一个 MongoDB 集群环境中的某节点异常下电了，导致业务出现了中断，随即又恢复了正常。 通过ELK 告警也监测到了业务报错日志。 运维部对于节点下电的原因进行了排查，发现仅仅是资源分配上的一个失误导致。 在解决了问题之后，大家也对这次中断的也提出了一些问题： >”当前的 MongoDB集群 采用了分片副本集的架构，其中主节点发生故障会产生多大的影响？” >”Mong...
MongoDB 那些坑(转)
weixin_33881041的博客
11-08 512
MongoDB 是目前炙手可热的 NoSQL 文档型数据库，它提供的一些特性很棒：如自动 failover 机制，自动 sharding，无模式 schemaless，大部分情况下性能也很棒。但是薄荷在深入使用 MongoDB 过程中，遇到了不少问题，下面总结几个我们遇到的坑。特别申明：我们目前用的 MongoDB 版本是 2.4.10，曾经升级到 MongoDB 2.6.0 版本，问题依然存在，...
mongodb的故障转移和数据冗余
Mori技术客栈
07-11 955
Mongodb提供了两种方式的数据冗余方式：    一、复制            1、主从复制                mongodb 允许有一个主节点和多个从节点 从节点从主节点复制同步数据                     主节点会保存一个oplog集合的操作记录，这个集合保存了对数据库的写入操作顺序历史记录。从节点负责从该集合复制数据。由于该集合是固定长度的，所以当从节点的状态...
Mongodb ReplSet 小结
Captains-Felix的专栏
07-15 5678
一、副本集基本概念 副本集（replica set） MongoDB的replica set是一个mongod进程实例簇，数据在这个簇中相互复制，并自动进行故障切换。 MongoDB的数据库复制增加了冗余，确保了高可用性，简化了管理任务如备份，并且增加了读能力。大多数产品部署都使用了复制。MongoDB中primary处理写操作，其它进行复制的成员则是secondaries。
MongoDB - Replication - Auto Failover
chuckchen1222的博客
09-04 130
配置在同一个集群下的member，可以自动切换主备，但是有两个前提 1. priority 不等于 0。 2. 如果设置 priority 不为 0， 那么 votes 也不能为 0。 这样，就可以实现自动切换了。 配置方法 1. 可以在开始配置的时候设置好。 rs.add({ host: "dbw21as.daodao.com", priority: 1, vo...
MongoDB replication, failover, shard (In Process)
12-27 281
<br />MongoDB replication, failover, shard (In Process)
Mongodb故障转移
weixin_34370347的博客
12-31 130
测试环境 四台测试服务器10.151.151.150：27017（主节点），10.151.151.151：27017（从节点），10.151.151.152：27018（从节点），10.151.151.152：27017（仲裁节点），10.151.151.143：30000（mongos），10.151.151.143：10000（configserver） 1.首先建立副本集，按照上边的节点...
mongodb与mysql区别（超详细）
热门推荐
{改变自己}
05-23 6万+
MySQL是关系型数据库。   优势：在不同的引擎上有不同 的存储方式。查询语句是使用传统的sql语句，拥有较为成熟的体系，成熟度很高。开源数据库的份额在不断增加，mysql的份额页在持续增长。   缺点：在海量数据处理的时候效率会显著变慢。Mongodb是非关系型数据库(nosql ),属于文档型数据库。文档是mongoDB中数据的基本单元，类似关系数据库的行，多个键值对有序地放置在一起便是文档...
mongodb高可用Replica Set
yangzhawen
08-06 4167
mongodb高可用Replica Set
mongodb副本集中其中一个节点宕机无法重启的问题
程序员涂小哥的技术博客
02-14 6268
2-8日我还在家中的时候，被告知mongodb副本集中其中一个从节点因未知原因宕机，然后暂时负责代管的同事无论如何就是启动不起来。 当时mongodb的日志信息是这样的： 实际上这里这么长一串最重要的信息应该是在后边几行： 2017-02-08T17:10:28.754+0800 I REPL [rsBackgroundSync] replSet our last op ti
MongoDB副本集：实现高可用集群
"搭建高可用mongodb集群（二）——副本集" MongoDB的副本集是解决其高可用性和扩展性问题的关键技术。在传统的主从模式中，一旦主节点出现问题，需要手动切换，而且主节点承受所有读写压力，无法有效分散负载。此外...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值