目录
2、MongoDB主从数据库,配置MongoDB 集群名称为 rs
介绍
MongoDB:一个基于分布式文件存储的数据库。由C++语言编写。旨在为WEB应用提供可扩展的高性能数据存储解决方案。
了解
主从模式主要是为了实现数据的备份与高可用性而产生的,它最早应用在数据库系统中。在传统的数据库中,主从复制是通过在主数据库上捕捉事务并将其记录在二进制日志中,然后将这些日志文件发送到从数据库。从数据库则应用这些日志,以确保从数据库中的数据与主数据库一致。这样做的好处是可以通过增加从数据库来扩展读取性能,同时也可以提供高可用性,因为即使主数据库宕机,从数据库也可以立即接管服务。随着分布式系统的兴起,该模式也被应用到了分布式系统中。在分布式系统中,主从模式通常是指有一个主节点和多个从节点,主节点负责处理所有的请求,而从节点只是接收主节点的复制数据以便备份和容灾。
基本信息
操作系统:Linux
MongoDB版本:v3.4.24
主库:192.168.100.99:27017
从库:192.168.100.100:27017
1、前期配置
#两台主机前期配置操作
#关闭防火墙
systemctl stop firewalld
systemctl disable firewalld
#关闭SElinux
vi /etc/selinux/config
SELINUX=disabled #修改
配置yum源
cat /etc/yum.repos.d/mongodb-org.repo
[mongodb-org]
name=MongoDB Repository
baseurl=http://mirrors.aliyun.com/mongodb/yum/redhat/7Server/mongodb-org/3.4/x86_64/
gpgcheck=0
enabled=1
#安装
yum install -y mongodb
#开启、开机自启、查看状态操作
[root@sql-1 ~]# systemctl start mongod
[root@sql-1 ~]# systemctl enable mongod
[root@sql-1 ~]# systemctl status mongod
2、MongoDB主从数据库,配置MongoDB 集群名称为 rs
#修改MongoDB配置文件mongod.conf
主
[root@sql-1 ~]# vi /etc/mongod.conf
net:
port: 27017
bindIp: 0.0.0.0 #修改
replication:
replSetName: rs #添加
#保存后重启服务
[root@sql-1 ~]# systemctl restart mongod
从
[root@sql-2 ~]# vi /etc/mongod.conf
net:
port: 27017
bindIp: 0.0.0.0 #修改
replication:
replSetName: rs #添加
#保存后重启服务
[root@sql-2 ~]# systemctl restart mongod
#进入数据库配置主从关系(当然进入的方式有很多,我这里是直接进入,也可以使用 mongo --host ip地址 --port 端口号 进入,还可以mongo 127.0.0.1:端口号 进入)
[root@sql-1 ~]# mongo
MongoDB shell version v3.4.24
connecting to: mongodb://127.0.0.1:27017
MongoDB server version: 3.4.24
#切换到管理员
> use admin
#这里采用定义一个主从同步的变量config
#也可以不定义,直接输入进行初始化 rs.initiate({_id:"rs",members:[{_id:0,host:"192.168.100.99:27017"},{_id:1,host:"192.168.100.100:27017"}]})
> config={_id:"rs",members:[{_id:0,host:"192.168.100.99:27017"},{_id:1,host:"192.168.100.100:27017"}]}
{
"_id" : "rs",
"members" : [
{
"_id" : 0,
"host" : "192.168.100.99:27017"
},
{
"_id" : 1,
"host" : "192.168.100.100:27017"
}
]
}
#初始化数据库主从绑定
> rs.initiate(config)
{ "ok" : 1 } #显示 OK 1 说明绑定成功
设置主从变量
3、初始化报错解决
#这里在初始化中会出现报错,大致报错内容是(has data already, cannot initiate set)意思就是已有数据,无法初始化设置,不过已经解决
#这里提示大家遇到问题不要慌!学会自主去分析解决问题才是关键!!!
#我的解决办法是:
1、编辑从节点配置文件,将刚刚配置的主从配置注释掉
[root@sql-2 ~]# vi /etc/mongod.conf
#replication:
# replSetName: rs
2、保存文件然后重启服务
[root@sql-2 ~]# systemctl restart mongod
3、进入数据库后执行db.dropDatabase(),清空所有的数据库,然后使用show dbs查看为空则完成清除
[root@sql-2 ~]# mongo 127.0.0.1:27017
> db.dropDatabase()
{ "ok" : 1 }
> use admin
switched to db admin
> db.dropDatabase()
{ "dropped" : "admin", "ok" : 1 }
#查看发现还有一个,继续删除
> show dbs
local 0.000GB
> use local
switched to db local
> db.dropDatabase()
{ "dropped" : "local", "ok" : 1 }
#查看清空数据后,退出
> show dbs
> exit
bye
4、此时如果直接主节点直接初始化,还是会报错(errmsg" : "replSetInitiate quorum check failed because not all proposed set members responded affirmatively: 192.168.100.100:27017 failed with not running with --replSet",
),报错内容大概是因为没有运行——replSet,192.168.100.100:27107并不是集群成员,无法响应。所以现在就应该把第一步的注释去掉就可以了
[root@sql-2 ~]# vi /etc/mongod.conf
replication:
replSetName: rs
5、再次主节点初始化,执行命令执行rs.initiate(config),发现已经没问题啦!!!完美解决!!!
[root@sql-1 ~]# mongo
> config={_id:"rs",members:[{_id:0,host:"192.168.100.99:27017"},{_id:1,host:"192.168.100.100:27017"}]}
> rs.initiate(config)
{ "ok" : 1 }
初始化报错图
解决图
4、查看状态
#mongo进入数据库,查看状态
主节点查看
rs:OTHER> rs.status()
{
"set" : "rs",
"date" : ISODate("2023-11-30T11:38:15.270Z"),
"myState" : 1,
"term" : NumberLong(1),
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"heartbeatIntervalMillis" : NumberLong(2000),
"optimes" : {
"lastCommittedOpTime" : {
"ts" : Timestamp(1701344292, 1),
"t" : NumberLong(1)
},
"appliedOpTime" : {
"ts" : Timestamp(1701344292, 1),
"t" : NumberLong(1)
},
"durableOpTime" : {
"ts" : Timestamp(1701344292, 1),
"t" : NumberLong(1)
}
},
"members" : [
{
"_id" : 0,
"name" : "192.168.100.99:27017",
"health" : 1,
"state" : 1,
"stateStr" : "PRIMARY",
"uptime" : 2207,
"optime" : {
"ts" : Timestamp(1701344292, 1),
"t" : NumberLong(1)
},
"optimeDate" : ISODate("2023-11-30T11:38:12Z"),
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"infoMessage" : "",
"electionTime" : Timestamp(1701343720, 1),
"electionDate" : ISODate("2023-11-30T11:28:40Z"),
"configVersion" : 1,
"self" : true,
"lastHeartbeatMessage" : ""
},
{
"_id" : 1,
"name" : "192.168.100.100:27017",
"health" : 1,
"state" : 2,
"stateStr" : "SECONDARY",
"uptime" : 585,
"optime" : {
"ts" : Timestamp(1701344292, 1),
"t" : NumberLong(1)
},
"optimeDurable" : {
"ts" : Timestamp(1701344292, 1),
"t" : NumberLong(1)
},
"optimeDate" : ISODate("2023-11-30T11:38:12Z"),
"optimeDurableDate" : ISODate("2023-11-30T11:38:12Z"),
"lastHeartbeat" : ISODate("2023-11-30T11:38:14.733Z"),
"lastHeartbeatRecv" : ISODate("2023-11-30T11:38:13.341Z"),
"pingMs" : NumberLong(0),
"lastHeartbeatMessage" : "",
"syncingTo" : "192.168.100.99:27017",
"syncSourceHost" : "192.168.100.99:27017",
"syncSourceId" : 0,
"infoMessage" : "",
"configVersion" : 1
}
],
"ok" : 1
}
rs:PRIMARY>
从节点查看
rs:SECONDARY> rs.status()
{
"set" : "rs",
"date" : ISODate("2023-11-30T12:38:31.592Z"),
"myState" : 2,
"term" : NumberLong(1),
"syncingTo" : "192.168.100.99:27017",
"syncSourceHost" : "192.168.100.99:27017",
"syncSourceId" : 0,
"heartbeatIntervalMillis" : NumberLong(2000),
"optimes" : {
"lastCommittedOpTime" : {
"ts" : Timestamp(1701347902, 1),
"t" : NumberLong(1)
},
"appliedOpTime" : {
"ts" : Timestamp(1701347902, 1),
"t" : NumberLong(1)
},
"durableOpTime" : {
"ts" : Timestamp(1701347902, 1),
"t" : NumberLong(1)
}
},
"members" : [
{
"_id" : 0,
"name" : "192.168.100.99:27017",
"health" : 1,
"state" : 1,
"stateStr" : "PRIMARY",
"uptime" : 4199,
"optime" : {
"ts" : Timestamp(1701347902, 1),
"t" : NumberLong(1)
},
"optimeDurable" : {
"ts" : Timestamp(1701347902, 1),
"t" : NumberLong(1)
},
"optimeDate" : ISODate("2023-11-30T12:38:22Z"),
"optimeDurableDate" : ISODate("2023-11-30T12:38:22Z"),
"lastHeartbeat" : ISODate("2023-11-30T12:38:31.590Z"),
"lastHeartbeatRecv" : ISODate("2023-11-30T12:38:31.070Z"),
"pingMs" : NumberLong(0),
"lastHeartbeatMessage" : "",
"syncingTo" : "",
"syncSourceHost" : "",
"syncSourceId" : -1,
"infoMessage" : "",
"electionTime" : Timestamp(1701343720, 1),
"electionDate" : ISODate("2023-11-30T11:28:40Z"),
"configVersion" : 1
},
{
"_id" : 1,
"name" : "192.168.100.100:27017",
"health" : 1,
"state" : 2,
"stateStr" : "SECONDARY",
"uptime" : 4206,
"optime" : {
"ts" : Timestamp(1701347902, 1),
"t" : NumberLong(1)
},
"optimeDate" : ISODate("2023-11-30T12:38:22Z"),
"syncingTo" : "192.168.100.99:27017",
"syncSourceHost" : "192.168.100.99:27017",
"syncSourceId" : 0,
"infoMessage" : "",
"configVersion" : 1,
"self" : true,
"lastHeartbeatMessage" : ""
}
],
"ok" : 1
}
rs:SECONDARY>
5、创建集合,验证主从是否同步
#验证主从
1、在主节点数据库上,进行创建集合
rs:PRIMARY> use admin
rs:PRIMARY> db.createCollection("mymongodb")
{ "ok" : 1 }
rs:PRIMARY> show dbs
admin 0.000GB
local 0.000GB
test 0.000GB
rs:PRIMARY> show collections
mymongodb
2、进入从节点数据库上,查看在主库上创建的结果是否出现在从节点数据库上
rs:SECONDARY> use admin
#输入show dbs查询的操作发现又报错,这个小问题不用害怕!这是因为在配置了MongoDB的主从同步后,在MongoDB的从节点库上,没有读和写的权限,所以导致无法查看数据
rs:SECONDARY> show dbs
2023-11-30T07:45:48.407-0500 E QUERY [thread1] Error: listDatabases failed:{
"ok" : 0,
"errmsg" : "not master and slaveOk=false",
"code" : 13435,
"codeName" : "NotMasterNoSlaveOk"
} :
_getErrorWithCode@src/mongo/shell/utils.js:25:13
Mongo.prototype.getDBs@src/mongo/shell/mongo.js:62:1
shellHelper.show@src/mongo/shell/utils.js:814:19
shellHelper@src/mongo/shell/utils.js:704:15
@(shellhelp2):1:1
#设置从节点数据库可读
rs:SECONDARY> rs.slaveOk()
或
rs:SECONDARY> db.getMongo().setSlaveOk()
3、再次查看,没问题,发现从节点数据库数据已经同步
rs:SECONDARY> rs.slaveOk()
rs:SECONDARY> show dbs
admin 0.000GB
local 0.000GB
test 0.000GB
rs:SECONDARY> show collections
mymongodb
从节点数据库报错解决图
删除集合
#主节点数据库,删除集合
rs:PRIMARY> db.mymongodb.drop()
true
rs:PRIMARY> show collections
rs:PRIMARY>
#从节点数据库查看
rs:SECONDARY> show collections
rs:SECONDARY>
#需要注意的是创建在哪个数据库中就使用use命令选定数据库,进行对应操作
#当然大家也可以用其他方式进行主从库的测试验证
至此,配置MongoDB的主从数据库完美完成!!!