MongoDB复制集

时间 2020-01-02

原文原文链接

概述：

MongoDB复制集是将数据同步在多个服务器的过程。复制集提升了数据的可用性，并能够保证数据的安全性。复制集是额外的数据副本，是跨多个服务器同步数据的过程，复制集提供了冗余并增长了数据可用性，经过复制集能够对硬件故障和中断的服务进行恢复。
mongodb

复制集的优点以下：
1.让数据更安全
2.高数据可用性（24*7）
3.灾难恢复
4.无停机维护（如备份、索引重建、故障转移）
5.读缩放（额外的副本读取）
6.副本集对应用程序是透明。数据库

MongoDB复制集的工做原理：

1.mongodb的复制集至少须要两个节点。其中一个是主节点，负责处理客户端请求，其他的都是从节点，负责复制主节点上的数据。
2.mongodb各个节点常见的搭配方式为：一主一从、一主多从。
3.主节点记录在其上的全部操做oplog，从节点按期轮询主节点获取这些操做，而后对本身的数据副本执行这些操做，从而保证从节点的数据与主节点一致。

复制集的特色：
1.N 个节点的集群
2.任何节点可做为主节点
3.全部写入操做都在主节点上
4.自动故障转移
5.自动恢复vim

部署MongoDB复制集：

咱们在同一台服务器上建立MongoDB的多实例，来作MongoDB主从的实验。
咱们这里建立四个实例：mongdb一、mongdb二、mongdb三、mongdb4；接下来开始配置复制集：安全

1.首先在已经安装好的这一台MongoDB服务器上，建立4个实例：
mkdir -p /data/mongodb/mongodb{1,2,3,4} //建立各实例的数据目录
mkdir -p /data/conf/ //建立实例配置目录
mkdir -p /data/logs/ //建立实例的日志目录
touch /data/logs/mongodb{1,2,3,4}.log //建立各实例的日志文件
chmod 777 /data/logs/*.log //赋予日志文件权限777
服务器

2.编辑mongodb1.conf配置文件，开启复制集功能并配置replSetName参数
vim /data/mongodb/mongodb1.conf
修改以下：
#mongod.conf
#for documentation of all options, see:
#http://docs.mongodb.org/manual/reference/configuration-options/
#where to write logging data.
systemLog:
destination: file
logAppend: true
path: /data/logs/mongodb1.log //mongodb1的日志文件路径
#Where and how to store data.
storage:
dbPath: /data/mongodb/mongodb1/ //mongodb1的数据文件路径
journal:
enabled: true
#engine:
#mmapv1:
#wiredTiger:
#how the process runs
processManagement:
fork: true # fork and run in background
pidFilePath: /data/mongodb/mongodb1/mongod.pid # location of pidfile
timeZoneInfo: /usr/share/zoneinfo
#network interfaces
net:
port: 27017 //mongodb1的进程号
bindIp: 0.0.0.0 # Listen to local interface only, comment to listen on all interfaces.
#security:
#operationProfiling:
replication: //删除“#”，开启复制集功能
replSetName: test-rc //名称为test-rc
#sharding:
##Enterprise-Only Options
#auditLog:
#snmp:
app

3.复制默认mongodb1.conf配置文件，生成另外三份实例的配置文件
cp -p /data/mongodb/mongodb1.conf /data/conf/mongodb2.conf
cp -p /data/mongodb/mongodb1.conf /data/conf/mongodb3.conf
cp -p /data/mongodb/mongodb1.conf /data/conf/mongodb4.conf
ide

4.分别修改mongodb2.conf、mongodb3.conf、mongodb4.conf配置文件，以下所示：
vim /data/conf/mongodb2.conf修改以下：
#mongod.conf
#for documentation of all options, see:
#http://docs.mongodb.org/manual/reference/configuration-options/
#where to write logging data.
systemLog:
destination: file
logAppend: true
path: /data/logs/mongodb2.log //mongodb2的日志文件路径
#Where and how to store data.
storage:
dbPath: /data/mongodb/mongodb2/ //mongodb2的数据文件路径
journal:
enabled: true
#engine:
#mmapv1:
#wiredTiger:
#how the process runs
processManagement:
fork: true # fork and run in background
pidFilePath: /data/mongodb/mongodb1/mongod.pid # location of pidfile
timeZoneInfo: /usr/share/zoneinfo
#network interfaces
net:
port: 27018 //mongodb2的进程号
bindIp: 0.0.0.0 # Listen to local interface only, comment to listen on all interfaces.
#security:
#operationProfiling:
replication: //删除“#”，开启复制集功能
replSetName: test-rc #名称为test-rc
#sharding:
##Enterprise-Only Options
#auditLog:
#snmp:

vim /data/conf/mongodb3.conf修改以下：
#mongod.conf
#for documentation of all options, see:
#http://docs.mongodb.org/manual/reference/configuration-options/
#where to write logging data.
systemLog:
destination: file
logAppend: true
path: /data/logs/mongodb3.log //mongodb3的日志文件路径
#Where and how to store data.
storage:
dbPath: /data/mongodb/mongodb3/ //mongodb3的数据文件路径
journal:
enabled: true
#engine:
#mmapv1:
#wiredTiger:
#how the process runs
processManagement:
fork: true # fork and run in background
pidFilePath: /data/mongodb/mongodb1/mongod.pid # location of pidfile
timeZoneInfo: /usr/share/zoneinfo
#network interfaces
net:
port: 27019 //mongodb3的进程号
bindIp: 0.0.0.0 # Listen to local interface only, comment to listen on all interfaces.
#security:
#operationProfiling:
replication: //删除“#”，开启复制集功能
replSetName: test-rc #名称为test-rc
#sharding:
##Enterprise-Only Options
#auditLog:
#snmp:

vim /data/conf/mongodb4.conf修改以下：
#mongod.conf
#for documentation of all options, see:
#http://docs.mongodb.org/manual/reference/configuration-options/
#where to write logging data.
systemLog:
destination: file
logAppend: true
path: /data/logs/mongodb4.log //mongodb4的日志文件路径
#Where and how to store data.
storage:
dbPath: /data/mongodb/mongodb4/ //mongodb4的数据文件路径
journal:
enabled: true
#engine:
#mmapv1:
#wiredTiger:
#how the process runs
processManagement:
fork: true # fork and run in background
pidFilePath: /data/mongodb/mongodb1/mongod.pid # location of pidfile
timeZoneInfo: /usr/share/zoneinfo
#network interfaces
net:
port: 27020 //mongodb4的进程号
bindIp: 0.0.0.0 # Listen to local interface only, comment to listen on all interfaces.
#security:
#operationProfiling:
replication: //删除“#”，开启复制集功能
replSetName: test-rc //名称为test-rc
#sharding:
##Enterprise-Only Options
#auditLog:
#snmp:
3d

5.依次启动mongodb四个实例:
mongod -f /data/conf/mongodb1.conf
mongod -f /data/conf/mongodb2.conf
mongod -f /data/conf/mongodb3.conf
mongod -f /data/conf/mongod4.conf

netstat -tunlp | grep mongod //查看端口监听：
日志

6.接下来配置三个节点的复制集：
mongo //登陆默认数据库
rs.status() //查看默认端口号27017的复制集状态
blog

7.定义cfg初始化参数(先加入三台，另外一台后面实现添加节点功能)
cfg={"_id":"test-rc","members":[{"_id":0,"host":"192.168.48.149:27017"},{"_id":1,"host":"192.168.48.149:27018"},{"_id":2,"host":"192.168.48.149:27019"}]}

8. 启动复制集功能
rs.initiate(cfg)

#注：初始化配置时保证从节点没有数据

9.查看复制集的状态信息
test-rc:PRIMARY> rs.status() //查看已知主节点在192.168.100.100:27017节点上
{
"set" : "test-rc",
"date" : ISODate("2018-09-14T01:59:21.162Z"),
"myState" : 1,
"term" : NumberLong(1),
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"heartbeatIntervalMillis" : NumberLong(2000),
"optimes" : {
"lastCommittedOpTime" : {
"ts" : Timestamp(1536890351, 1),
"t" : NumberLong(1)
},
"readConcernMajorityOpTime" : {
"ts" : Timestamp(1536890351, 1),
"t" : NumberLong(1)
},
"appliedOpTime" : {
"ts" : Timestamp(1536890351, 1),
"t" : NumberLong(1)
},
"durableOpTime" : {
"ts" : Timestamp(1536890351, 1),
"t" : NumberLong(1)
}
},
"lastStableCheckpointTimestamp" : Timestamp(1536890321, 1),
"members" : [
{
"_id" : 0,
"name" : "192.168.48.149:27017",
"health" : 1, //健康值为1 是健康状态
"state" : 1, //1：为主节点； 2：为从节点
"stateStr" : "PRIMARY", //"PRIMARY"主节点
"uptime" : 2263,
"optime" : {
"ts" : Timestamp(1536890351, 1),
"t" : NumberLong(1)
},
"optimeDate" : ISODate("2018-09-14T01:59:11Z"),
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"infoMessage" : "",
"electionTime" : Timestamp(1536890079, 1),
"electionDate" : ISODate("2018-09-14T01:54:39Z"),
"configVersion" : 1,
"self" : true,
"lastHeartbeatMessage" : ""
},
{
"_id" : 1,
"name" : "192.168.48.149:27018",
"health" : 1,
"state" : 2
"stateStr" : "SECONDARY", //SECONDARY从节点
"uptime" : 291,
"optime" : {
"ts" : Timestamp(1536890351, 1),
"t" : NumberLong(1)
},
"optimeDurable" : {
"ts" : Timestamp(1536890351, 1),
"t" : NumberLong(1)
},
"optimeDate" : ISODate("2018-09-14T01:59:11Z"),
"optimeDurableDate" : ISODate("2018-09-14T01:59:11Z"),
"lastHeartbeat" : ISODate("2018-09-14T01:59:20.380Z"),
"lastHeartbeatRecv" : ISODate("2018-09-14T01:59:20.895Z"),
"pingMs" : NumberLong(0),
"lastHeartbeatMessage" : "",
"syncingTo" : "192.168.48.149:27017",
"syncSourceHost" : "192.168.48.149:27017",
"syncSourceId" : 0,
"infoMessage" : "",
"configVersion" : 1
},
{
"_id" : 2,
"name" : "192.168.48.149:27019",
"health" : 1,
"state" : 2,
"stateStr" : "SECONDARY",
"uptime" : 291,
"optime" : {
"ts" : Timestamp(1536890351, 1),
"t" : NumberLong(1)
},
"optimeDurable" : {
"ts" : Timestamp(1536890351, 1),
"t" : NumberLong(1)
},
"optimeDate" : ISODate("2018-09-14T01:59:11Z"),
"optimeDurableDate" : ISODate("2018-09-14T01:59:11Z"),
"lastHeartbeat" : ISODate("2018-09-14T01:59:20.380Z"),
"lastHeartbeatRecv" : ISODate("2018-09-14T01:59:20.923Z"),
"pingMs" : NumberLong(0),
"lastHeartbeatMessage" : "",
"syncingTo" : "192.168.48.149:27017",
"syncSourceHost" : "192.168.48.149:27017",
"syncSourceId" : 0,
"infoMessage" : "",
"configVersion" : 1
}
],
"ok" : 1,
"operationTime" : Timestamp(1536890351, 1),
"$clusterTime" : {
"clusterTime" : Timestamp(1536890351, 1),
"signature" : {
"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
"keyId" : NumberLong(0)
}
}
}

10.添加节点并查看复制集的状态信息
rs.add("192.168.48.149:27020")

rs.status()

11.删除端口号为27018的从节点，而后查看复制集
rs.remove("192.168.48.149:27018")

rs.status()

12.故障转移切换

先退出mogodb，查看一下四个实例的进程信息：

2.关闭主节点端口号为27017的进程，检查是否可以自动切换：

3.登陆MongoDB端口号为27019的实例，而后查看复制集的状态：
[root@localhost mongodb]# mongo --port 27019 //登陆MongoDB端口号为27019的实例
test-rc:SECONDARY> rs.status() //查看复制集的状态
查看结果以下：原来的主节点27017进程已被杀掉。端口号27020已经抢占主节点。
{
"_id" : 2,
"name" : "192.168.48.149:27019",
"health" : 1,
"state" : 2,
"stateStr" : "SECONDARY",
"uptime" : 5203,
"optime" : {
"ts" : Timestamp(1536893313, 1),
"t" : NumberLong(2)
},
"optimeDate" : ISODate("2018-09-14T02:48:33Z"),
"syncingTo" : "192.168.48.149:27020",
"syncSourceHost" : "192.168.48.149:27020",
"syncSourceId" : 3,
"infoMessage" : "",
"configVersion" : 3,
"self" : true,
"lastHeartbeatMessage" : ""
},
{
"_id" : 3,
"name" : "192.168.48.149:27020",
"health" : 1,
"state" : 1,
"stateStr" : "PRIMARY",
"uptime" : 1569,
"optime" : {
"ts" : Timestamp(1536893313, 1),
"t" : NumberLong(2)
},
"optimeDurable" : {
"ts" : Timestamp(1536893313, 1),
"t" : NumberLong(2)
},
"optimeDate" : ISODate("2018-09-14T02:48:33Z"),
"optimeDurableDate" : ISODate("2018-09-14T02:48:33Z"),
"lastHeartbeat" : ISODate("2018-09-14T02:48:36.644Z"),
"lastHeartbeatRecv" : ISODate("2018-09-14T02:48:36.935Z"),
"pingMs" : NumberLong(0),
"lastHeartbeatMessage" : "",
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"infoMessage" : "",
"electionTime" : Timestamp(1536892762, 1),
"electionDate" : ISODate("2018-09-14T02:39:22Z"),
"configVersion" : 3
}

13.接下来手动切换主节点

rs.freeze(30) //设置暂停30秒不参与选举

2.rs.stepDown(60,30)//让出主节点位置，维持从节点状态很多于60秒，等待30秒使主节点和从节点日志同步

3.查看复制集的状态信息
test-rc:SECONDARY> rs.status()//此刻主节点已经在192.168.48.149:27019节点上
{
"set" : "test-rc",
"date" : ISODate("2018-09-14T03:01:48.447Z"),
"myState" : 2,
"term" : NumberLong(3),
"syncingTo" : "192.168.48.149:27019",
"syncSourceHost" : "192.168.48.149:27019",
"syncSourceId" : 2,
"heartbeatIntervalMillis" : NumberLong(2000),
"optimes" : {
"lastCommittedOpTime" : {
"ts" : Timestamp(1536894107, 1),
"t" : NumberLong(3)
},
"readConcernMajorityOpTime" : {
"ts" : Timestamp(1536894107, 1),
"t" : NumberLong(3)
},
"appliedOpTime" : {
"ts" : Timestamp(1536894107, 1),
"t" : NumberLong(3)
},
"durableOpTime" : {
"ts" : Timestamp(1536894107, 1),
"t" : NumberLong(3)
}
},
"lastStableCheckpointTimestamp" : Timestamp(1536894097, 1),
"members" : [
{
"_id" : 0,
"name" : "192.168.48.149:27017",
"health" : 0,
"state" : 8,
"stateStr" : "(not reachable/healthy)",
"uptime" : 0,
"optime" : {
"ts" : Timestamp(0, 0),
"t" : NumberLong(-1)
},
"optimeDurable" : {
"ts" : Timestamp(0, 0),
"t" : NumberLong(-1)
},
"optimeDate" : ISODate("1970-01-01T00:00:00Z"),
"optimeDurableDate" : ISODate("1970-01-01T00:00:00Z"),
"lastHeartbeat" : ISODate("2018-09-14T03:01:47.657Z"),
"lastHeartbeatRecv" : ISODate("2018-09-14T02:39:11.212Z"),
"pingMs" : NumberLong(0),
"lastHeartbeatMessage" : "Error connecting to 192.168.48.149:27017 :: caused by :: Connection refused",
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"infoMessage" : "",
"configVersion" : -1
},
{
"_id" : 2,
"name" : "192.168.48.149:27019",
"health" : 1,
"state" : 1,
"stateStr" : "PRIMARY",
"uptime" : 2359,
"optime" : {
"ts" : Timestamp(1536894097, 1),
"t" : NumberLong(3)
},
"optimeDurable" : {
"ts" : Timestamp(1536894097, 1),
"t" : NumberLong(3)
},
"optimeDate" : ISODate("2018-09-14T03:01:37Z"),
"optimeDurableDate" : ISODate("2018-09-14T03:01:37Z"),
"lastHeartbeat" : ISODate("2018-09-14T03:01:47.181Z"),
"lastHeartbeatRecv" : ISODate("2018-09-14T03:01:48.314Z"),
"pingMs" : NumberLong(0),
"lastHeartbeatMessage" : "",
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"infoMessage" : "",
"electionTime" : Timestamp(1536894006, 1),
"electionDate" : ISODate("2018-09-14T03:00:06Z"),
"configVersion" : 3
},
{
"_id" : 3,
"name" : "192.168.48.149:27020",
"health" : 1,
"state" : 2,
"stateStr" : "SECONDARY",
"uptime" : 5985,
"optime" : {
"ts" : Timestamp(1536894107, 1),
"t" : NumberLong(3)
},
"optimeDate" : ISODate("2018-09-14T03:01:47Z"),
"syncingTo" : "192.168.48.149:27019",
"syncSourceHost" : "192.168.48.149:27019",
"syncSourceId" : 2,
"infoMessage" : "",
"configVersion" : 3,
"self" : true,
"lastHeartbeatMessage" : ""
}
],
"ok" : 1,
"operationTime" : Timestamp(1536894107, 1),
"$clusterTime" : {
"clusterTime" : Timestamp(1536894107, 1),
"signature" : {
"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
"keyId" : NumberLong(0)
}
}
}

本章总结：

1.mongodb复制集（Replica Sets）是额外的数据副本，复制集提供了冗余和增长数据可用性。2.mongodb的复制集至少须要两个节点。其中主节点负责处理客户端请求，从节点负责复制主节点上的数据。3.mongodb复制集能够实现群集的高可用，当主节点出现故障时会自动切换到其余节点。管理员也能够手动进行复制集的主从切换。4.复制是基于操做日志oplog，至关于MySQL中的二进制日志，只记录发生改变的记录。复制是将主节点的oplog日志同步并应用到其余从节点的过程。5.节点类型分为标准节点、被动节点和仲裁节点。只有标准节点可能被选举为活跃（主）节点。6.尽可能保证主节点的oplog足够大，可以存放至关长时间的操做记录。