【MongoDB】一主两从的副本集配置

最新推荐文章于 2024-11-04 18:02:08 发布
最新推荐文章于 2024-11-04 18:02:08 发布
阅读量182 收藏
点赞数 2
分类专栏： 数据库运维-MongoDB 文章标签： mongodb 数据库
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_43346403/article/details/139654204
版权

1.开启三个节点

mongod --dbpath /mongodb/db1 --port 27017 --bind_ip 192.168.75.56 -replSet myrelset/192.168.75.56:27017 &
mongod --dbpath /mongodb/db2 --port 27018 --bind_ip 192.168.75.56 -replSet myrelset/192.168.75.56:27018 &
mongod --dbpath /mongodb/db3 --port 27019 --bind_ip 192.168.75.56 -replSet myrelset/192.168.75.56:27019 &

2.查看进程 

--2.查看进程 

mongod    22567   3684  1 14:38 pts/1    00:00:02 mongod --dbpath /mongodb/db1 --port 27017 --bind_ip 192.168.75.56 -replSet myrelset/192.168.75.56:27017
mongod    22655   3684  1 14:39 pts/1    00:00:01 mongod --dbpath /mongodb/db2 --port 27018 --bind_ip 192.168.75.56 -replSet myrelset/192.168.75.56:27018
mongod    22794   3889  1 14:40 pts/2    00:00:00 mongod --dbpath /mongodb/db3 --port 27019 --bind_ip 192.168.75.56 -replSet myrelset/192.168.75.56:27019

3.初始化副本集 

mongo 192.168.75.56 --port 27017
sql>use admin
sql>cfg={_id:'myrelset',members:[{_id:0,host:'192.168.75.56:27017'},{_id:1,host:'192.168.75.56:27018'},{_id:2,host:'192.168.75.56:27019',priority:0}]}
> cfg={_id:'myrelset',members:[{_id:0,host:'192.168.75.56:27017'},{_id:1,host:'192.168.75.56:27018'},{_id:2,host:'192.168.75.56:27019',priority:0}]}
{
	"_id" : "myrelset",
	"members" : [
		{
			"_id" : 0,
			"host" : "192.168.75.56:27017"
		},
		{
			"_id" : 1,
			"host" : "192.168.75.56:27018"
		},
		{
			"_id" : 2,
			"host" : "192.168.75.56:27019",
			"priority" : 0
		}
	]
}


sql>rs.initiate(cfg)   --初始化。
{
	"ok" : 1,
	"operationTime" : Timestamp(1633606554, 1),
	"$clusterTime" : {
		"clusterTime" : Timestamp(1633606554, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

4.集群状态查看 

rs.status() 

myrelset:SECONDARY> rs.status()
{
	"set" : "myrelset",
	"date" : ISODate("2024-06-14T06:46:36.431Z"),
	"myState" : 2,
	"term" : NumberLong(2),
	"syncingTo" : "192.168.75.56:27018",
	"syncSourceHost" : "192.168.75.56:27018",
	"syncSourceId" : 1,
	"heartbeatIntervalMillis" : NumberLong(2000),
	"optimes" : {
		"lastCommittedOpTime" : {
			"ts" : Timestamp(1718347593, 1),
			"t" : NumberLong(2)
		},
		"readConcernMajorityOpTime" : {
			"ts" : Timestamp(1718347593, 1),
			"t" : NumberLong(2)
		},
		"appliedOpTime" : {
			"ts" : Timestamp(1718347593, 1),
			"t" : NumberLong(2)
		},
		"durableOpTime" : {
			"ts" : Timestamp(1718347593, 1),
			"t" : NumberLong(2)
		}
	},
	"lastStableCheckpointTimestamp" : Timestamp(1718347583, 1),
	"members" : [
		{
			"_id" : 0,
			"name" : "192.168.75.56:27017",
			"health" : 1,
			"state" : 2,
			"stateStr" : "SECONDARY",
			"uptime" : 71,
			"optime" : {
				"ts" : Timestamp(1718347593, 1),
				"t" : NumberLong(2)
			},
			"optimeDate" : ISODate("2024-06-14T06:46:33Z"),
			"syncingTo" : "192.168.75.56:27018",
			"syncSourceHost" : "192.168.75.56:27018",
			"syncSourceId" : 1,
			"infoMessage" : "",
			"configVersion" : 1,
			"self" : true,
			"lastHeartbeatMessage" : ""
		},
		{
			"_id" : 1,
			"name" : "192.168.75.56:27018",
			"health" : 1,
			"state" : 1,
			"stateStr" : "PRIMARY",
			"uptime" : 70,
			"optime" : {
				"ts" : Timestamp(1718347593, 1),
				"t" : NumberLong(2)
			},
			"optimeDurable" : {
				"ts" : Timestamp(1718347593, 1),
				"t" : NumberLong(2)
			},
			"optimeDate" : ISODate("2024-06-14T06:46:33Z"),
			"optimeDurableDate" : ISODate("2024-06-14T06:46:33Z"),
			"lastHeartbeat" : ISODate("2024-06-14T06:46:35.422Z"),
			"lastHeartbeatRecv" : ISODate("2024-06-14T06:46:35.035Z"),
			"pingMs" : NumberLong(0),
			"lastHeartbeatMessage" : "",
			"syncingTo" : "",
			"syncSourceHost" : "",
			"syncSourceId" : -1,
			"infoMessage" : "",
			"electionTime" : Timestamp(1718347432, 1),
			"electionDate" : ISODate("2024-06-14T06:43:52Z"),
			"configVersion" : 1
		},
		{
			"_id" : 2,
			"name" : "192.168.75.56:27019",
			"health" : 1,
			"state" : 2,
			"stateStr" : "SECONDARY",
			"uptime" : 70,
			"optime" : {
				"ts" : Timestamp(1718347593, 1),
				"t" : NumberLong(2)
			},
			"optimeDurable" : {
				"ts" : Timestamp(1718347593, 1),
				"t" : NumberLong(2)
			},
			"optimeDate" : ISODate("2024-06-14T06:46:33Z"),
			"optimeDurableDate" : ISODate("2024-06-14T06:46:33Z"),
			"lastHeartbeat" : ISODate("2024-06-14T06:46:35.421Z"),
			"lastHeartbeatRecv" : ISODate("2024-06-14T06:46:35.117Z"),
			"pingMs" : NumberLong(0),
			"lastHeartbeatMessage" : "",
			"syncingTo" : "192.168.75.56:27018",
			"syncSourceHost" : "192.168.75.56:27018",
			"syncSourceId" : 1,
			"infoMessage" : "",
			"configVersion" : 1
		}
	],
	"ok" : 1,
	"operationTime" : Timestamp(1718347593, 1),
	"$clusterTime" : {
		"clusterTime" : Timestamp(1718347593, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

当前:

192.168.75.56:27017 Secondary角色

192.168.75.56:27018 Primary角色

192.168.75.56:27019 Secondary角色

且监控状态都是1；

5.使用各个端口登录检查自己是否master; 

myrelset:SECONDARY> db.isMaster()
{
	"hosts" : [
		"192.168.75.56:27017",
		"192.168.75.56:27018"
	],
	"passives" : [
		"192.168.75.56:27019"
	],
	"setName" : "myrelset",
	"setVersion" : 1,
	"ismaster" : false,
	"secondary" : true,
	"primary" : "192.168.75.56:27018",
	"me" : "192.168.75.56:27017",
	"lastWrite" : {
		"opTime" : {
			"ts" : Timestamp(1718347963, 1),
			"t" : NumberLong(2)
		},
		"lastWriteDate" : ISODate("2024-06-14T06:52:43Z"),
		"majorityOpTime" : {
			"ts" : Timestamp(1718347963, 1),
			"t" : NumberLong(2)
		},
		"majorityWriteDate" : ISODate("2024-06-14T06:52:43Z")
	},
	"maxBsonObjectSize" : 16777216,
	"maxMessageSizeBytes" : 48000000,
	"maxWriteBatchSize" : 100000,
	"localTime" : ISODate("2024-06-14T06:52:51.850Z"),
	"logicalSessionTimeoutMinutes" : 30,
	"minWireVersion" : 0,
	"maxWireVersion" : 7,
	"readOnly" : false,
	"ok" : 1,
	"operationTime" : Timestamp(1718347963, 1),
	"$clusterTime" : {
		"clusterTime" : Timestamp(1718347963, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

主节点是27018，自己是27017 


--现在使用27018登录。
myrelset:PRIMARY> rs.isMaster()
{
	"hosts" : [
		"192.168.75.56:27017",
		"192.168.75.56:27018"
	],
	"passives" : [
		"192.168.75.56:27019"
	],
	"setName" : "myrelset",
	"setVersion" : 1,
	"ismaster" : true,
	"secondary" : false,
	"primary" : "192.168.75.56:27018",
	"me" : "192.168.75.56:27018",
	"electionId" : ObjectId("7fffffff0000000000000002"),
	"lastWrite" : {
		"opTime" : {
			"ts" : Timestamp(1718348061, 1),
			"t" : NumberLong(2)
		},
		"lastWriteDate" : ISODate("2024-06-14T06:54:21Z"),
		"majorityOpTime" : {
			"ts" : Timestamp(1718348061, 1),
			"t" : NumberLong(2)
		},
		"majorityWriteDate" : ISODate("2024-06-14T06:54:21Z")
	},
	"maxBsonObjectSize" : 16777216,
	"maxMessageSizeBytes" : 48000000,
	"maxWriteBatchSize" : 100000,
	"localTime" : ISODate("2024-06-14T06:54:33.569Z"),
	"logicalSessionTimeoutMinutes" : 30,
	"minWireVersion" : 0,
	"maxWireVersion" : 7,
	"readOnly" : false,
	"ok" : 1,
	"operationTime" : Timestamp(1718348061, 1),
	"$clusterTime" : {
		"clusterTime" : Timestamp(1718348061, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

--发现自己是主节点。

--现在使用27019登录。
--自己是从节点。
myrelset:SECONDARY> rs.isMaster()
{
	"hosts" : [
		"192.168.75.56:27017",
		"192.168.75.56:27018"
	],
	"passives" : [
		"192.168.75.56:27019"
	],
	"setName" : "myrelset",
	"setVersion" : 1,
	"ismaster" : false,
	"secondary" : true,
	"primary" : "192.168.75.56:27018",
	"passive" : true,
	"me" : "192.168.75.56:27019",
	"lastWrite" : {
		"opTime" : {
			"ts" : Timestamp(1718348113, 1),
			"t" : NumberLong(2)
		},
		"lastWriteDate" : ISODate("2024-06-14T06:55:13Z"),
		"majorityOpTime" : {
			"ts" : Timestamp(1718348113, 1),
			"t" : NumberLong(2)
		},
		"majorityWriteDate" : ISODate("2024-06-14T06:55:13Z")
	},
	"maxBsonObjectSize" : 16777216,
	"maxMessageSizeBytes" : 48000000,
	"maxWriteBatchSize" : 100000,
	"localTime" : ISODate("2024-06-14T06:55:19.452Z"),
	"logicalSessionTimeoutMinutes" : 30,
	"minWireVersion" : 0,
	"maxWireVersion" : 7,
	"readOnly" : false,
	"ok" : 1,
	"operationTime" : Timestamp(1718348113, 1),
	"$clusterTime" : {
		"clusterTime" : Timestamp(1718348113, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

复本集的名称myreplset 是自定义的。

6.关闭主节点观察主从切换情况

当前主节点是:27018,关闭主节点。

myrelset:PRIMARY> use admin 
switched to db admin
myrelset:PRIMARY> db.shutdownServer()
2024-06-14T15:02:44.182+0800 E QUERY    [js] Error: shutdownServer failed: {
	"operationTime" : Timestamp(1718348563, 1),
	"ok" : 0,
	"errmsg" : "shutdown must run from localhost when running db without auth",
	"code" : 13,
	"codeName" : "Unauthorized",
	"$clusterTime" : {
		"clusterTime" : Timestamp(1718348563, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
} :
_getErrorWithCode@src/mongo/shell/utils.js:25:13
DB.prototype.shutdownServer@src/mongo/shell/db.js:453:1
@(shell):1:1

关闭服务器必须是本地节点。所以现在关闭重启，并写上本地节点启动。

kill -9 xxx 杀掉集群 

重启 

mongod --dbpath /mongodb/db1 --port 27017 --bind_ip 192.168.75.56,127.0.0.1 -replSet testset/192.168.75.56:27017 &
mongod --dbpath /mongodb/db2 --port 27018 --bind_ip 192.168.75.56,127.0.0.1 -replSet testset/192.168.75.56:27018 &
mongod --dbpath /mongodb/db3 --port 27019 --bind_ip 192.168.75.56,127.0.0.1 -replSet testset/192.168.75.56:27019 &

关闭主节点。

当前主节点:27017,从节点是:27018,27019;

[mongod@mysql57 mongodb]$ mongo --host 127.0.0.1 --port 27017
MongoDB shell version v4.0.2
connecting to: mongodb://127.0.0.1:27017/
MongoDB server version: 4.0.2
Server has startup warnings: 
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] 
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] 
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] 
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] 
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] 
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] ** WARNING: soft rlimits too low. rlimits set to 4096 processes, 524288 files. Number of processes should be at least 262144 : 0.5 times number of files.
2024-06-14T15:59:22.683+0800 I CONTROL  [initandlisten] 
---
Enable MongoDB's free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).

The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.

To enable free monitoring, run the following command: db.enableFreeMonitoring()
To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
---

myrelset:PRIMARY> use admin 
switched to db admin
myrelset:PRIMARY> db.shutdownServer()
server should be down...
2024-06-14T16:02:51.805+0800 I NETWORK  [js] trying reconnect to 127.0.0.1:27017 failed
2024-06-14T16:02:51.980+0800 I NETWORK  [js] reconnect 127.0.0.1:27017 failed failed 
2024-06-14T16:02:51.983+0800 I NETWORK  [js] trying reconnect to 127.0.0.1:27017 failed
2024-06-14T16:02:51.983+0800 I NETWORK  [js] reconnect 127.0.0.1:27017 failed failed

此时可以看到:27018,变成主节点，27019变成从节点。27017节点状态不健康。

myrelset:PRIMARY> rs.status()
{
	"set" : "myrelset",
	"date" : ISODate("2024-06-14T08:03:26.630Z"),
	"myState" : 1,
	"term" : NumberLong(4),
	"syncingTo" : "",
	"syncSourceHost" : "",
	"syncSourceId" : -1,
	"heartbeatIntervalMillis" : NumberLong(2000),
	"optimes" : {
		"lastCommittedOpTime" : {
			"ts" : Timestamp(1718352202, 1),
			"t" : NumberLong(4)
		},
		"readConcernMajorityOpTime" : {
			"ts" : Timestamp(1718352202, 1),
			"t" : NumberLong(4)
		},
		"appliedOpTime" : {
			"ts" : Timestamp(1718352202, 1),
			"t" : NumberLong(4)
		},
		"durableOpTime" : {
			"ts" : Timestamp(1718352202, 1),
			"t" : NumberLong(4)
		}
	},
	"lastStableCheckpointTimestamp" : Timestamp(1718352172, 1),
	"members" : [
		{
			"_id" : 0,
			"name" : "192.168.75.56: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("2024-06-14T08:03:26.037Z"),
			"lastHeartbeatRecv" : ISODate("2024-06-14T08:02:51.111Z"),
			"pingMs" : NumberLong(0),
			"lastHeartbeatMessage" : "Error connecting to 192.168.75.56:27017 :: caused by :: Connection refused",
			"syncingTo" : "",
			"syncSourceHost" : "",
			"syncSourceId" : -1,
			"infoMessage" : "",
			"configVersion" : -1
		},
		{
			"_id" : 1,
			"name" : "192.168.75.56:27018",
			"health" : 1,
			"state" : 1,
			"stateStr" : "PRIMARY",
			"uptime" : 209,
			"optime" : {
				"ts" : Timestamp(1718352202, 1),
				"t" : NumberLong(4)
			},
			"optimeDate" : ISODate("2024-06-14T08:03:22Z"),
			"syncingTo" : "",
			"syncSourceHost" : "",
			"syncSourceId" : -1,
			"infoMessage" : "could not find member to sync from",
			"electionTime" : Timestamp(1718352171, 1),
			"electionDate" : ISODate("2024-06-14T08:02:51Z"),
			"configVersion" : 1,
			"self" : true,
			"lastHeartbeatMessage" : ""
		},
		{
			"_id" : 2,
			"name" : "192.168.75.56:27019",
			"health" : 1,
			"state" : 2,
			"stateStr" : "SECONDARY",
			"uptime" : 166,
			"optime" : {
				"ts" : Timestamp(1718352202, 1),
				"t" : NumberLong(4)
			},
			"optimeDurable" : {
				"ts" : Timestamp(1718352202, 1),
				"t" : NumberLong(4)
			},
			"optimeDate" : ISODate("2024-06-14T08:03:22Z"),
			"optimeDurableDate" : ISODate("2024-06-14T08:03:22Z"),
			"lastHeartbeat" : ISODate("2024-06-14T08:03:25.827Z"),
			"lastHeartbeatRecv" : ISODate("2024-06-14T08:03:25.816Z"),
			"pingMs" : NumberLong(0),
			"lastHeartbeatMessage" : "",
			"syncingTo" : "192.168.75.56:27018",
			"syncSourceHost" : "192.168.75.56:27018",
			"syncSourceId" : 1,
			"infoMessage" : "",
			"configVersion" : 1
		}
	],
	"ok" : 1,
	"operationTime" : Timestamp(1718352202, 1),
	"$clusterTime" : {
		"clusterTime" : Timestamp(1718352202, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

7.从新启动27017，看看什么情况。

myrelset:SECONDARY> rs.status()
{
	"set" : "myrelset",
	"date" : ISODate("2024-06-14T08:07:30.052Z"),
	"myState" : 2,
	"term" : NumberLong(4),
	"syncingTo" : "192.168.75.56:27019",
	"syncSourceHost" : "192.168.75.56:27019",
	"syncSourceId" : 2,
	"heartbeatIntervalMillis" : NumberLong(2000),
	"optimes" : {
		"lastCommittedOpTime" : {
			"ts" : Timestamp(1718352442, 1),
			"t" : NumberLong(4)
		},
		"readConcernMajorityOpTime" : {
			"ts" : Timestamp(1718352442, 1),
			"t" : NumberLong(4)
		},
		"appliedOpTime" : {
			"ts" : Timestamp(1718352442, 1),
			"t" : NumberLong(4)
		},
		"durableOpTime" : {
			"ts" : Timestamp(1718352442, 1),
			"t" : NumberLong(4)
		}
	},
	"lastStableCheckpointTimestamp" : Timestamp(1718352442, 1),
	"members" : [
		{
			"_id" : 0,
			"name" : "192.168.75.56:27017",
			"health" : 1,
			"state" : 2,
			"stateStr" : "SECONDARY",
			"uptime" : 124,
			"optime" : {
				"ts" : Timestamp(1718352442, 1),
				"t" : NumberLong(4)
			},
			"optimeDate" : ISODate("2024-06-14T08:07:22Z"),
			"syncingTo" : "192.168.75.56:27019",
			"syncSourceHost" : "192.168.75.56:27019",
			"syncSourceId" : 2,
			"infoMessage" : "",
			"configVersion" : 1,
			"self" : true,
			"lastHeartbeatMessage" : ""
		},
		{
			"_id" : 1,
			"name" : "192.168.75.56:27018",
			"health" : 1,
			"state" : 1,
			"stateStr" : "PRIMARY",
			"uptime" : 123,
			"optime" : {
				"ts" : Timestamp(1718352442, 1),
				"t" : NumberLong(4)
			},
			"optimeDurable" : {
				"ts" : Timestamp(1718352442, 1),
				"t" : NumberLong(4)
			},
			"optimeDate" : ISODate("2024-06-14T08:07:22Z"),
			"optimeDurableDate" : ISODate("2024-06-14T08:07:22Z"),
			"lastHeartbeat" : ISODate("2024-06-14T08:07:29.800Z"),
			"lastHeartbeatRecv" : ISODate("2024-06-14T08:07:28.363Z"),
			"pingMs" : NumberLong(1),
			"lastHeartbeatMessage" : "",
			"syncingTo" : "",
			"syncSourceHost" : "",
			"syncSourceId" : -1,
			"infoMessage" : "",
			"electionTime" : Timestamp(1718352171, 1),
			"electionDate" : ISODate("2024-06-14T08:02:51Z"),
			"configVersion" : 1
		},
		{
			"_id" : 2,
			"name" : "192.168.75.56:27019",
			"health" : 1,
			"state" : 2,
			"stateStr" : "SECONDARY",
			"uptime" : 123,
			"optime" : {
				"ts" : Timestamp(1718352442, 1),
				"t" : NumberLong(4)
			},
			"optimeDurable" : {
				"ts" : Timestamp(1718352442, 1),
				"t" : NumberLong(4)
			},
			"optimeDate" : ISODate("2024-06-14T08:07:22Z"),
			"optimeDurableDate" : ISODate("2024-06-14T08:07:22Z"),
			"lastHeartbeat" : ISODate("2024-06-14T08:07:29.800Z"),
			"lastHeartbeatRecv" : ISODate("2024-06-14T08:07:28.273Z"),
			"pingMs" : NumberLong(0),
			"lastHeartbeatMessage" : "",
			"syncingTo" : "192.168.75.56:27018",
			"syncSourceHost" : "192.168.75.56:27018",
			"syncSourceId" : 1,
			"infoMessage" : "",
			"configVersion" : 1
		}
	],
	"ok" : 1,
	"operationTime" : Timestamp(1718352442, 1),
	"$clusterTime" : {
		"clusterTime" : Timestamp(1718352442, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

原来的主节点重启后变成了从节点。由此可见mongodb的副本集还是非常强大的。维护简单。

8.数据库查看 

myrelset:PRIMARY> show tables; 
myrelset:PRIMARY> show dbs; 
admin   0.000GB
config  0.000GB
local   0.000GB
myrelset:PRIMARY> use admin 
switched to db admin
myrelset:PRIMARY> show tables; 
myrelset:PRIMARY> show collections; 
myrelset:PRIMARY> use config
switched to db config
myrelset:PRIMARY> show tables; 
transactions
myrelset:PRIMARY> show collections; 
transactions
myrelset:PRIMARY> use local 
switched to db local
myrelset:PRIMARY> show tables 
oplog.rs
replset.election
replset.minvalid
replset.oplogTruncateAfterPoint
startup_log
myrelset:PRIMARY> show dbs;
admin   0.000GB
config  0.000GB
local   0.000GB

mongodb副本集搭建
09-08
进入主节点的 MongoDB 客户端，配置集群信息，包括副本集的名称、成员信息等。 三、集群添加认证 1. 修改配置文件 在三个节点上都需要修改配置文件，添加认证相关的配置，包括启用认证和密钥文件路径等。 2. ...
MongoDB副本集(一主两从)读写分离、故障转移功能环境部署记录
weixin_30919571的博客
02-26 468
Mongodb是一种非关系数据库(NoSQL)，非关系型数据库的产生就是为了解决大数据量、高扩展性、高性能、灵活数据模型、高可用性。MongoDB官方已经不建议使用主从模式了，替代方案是采用副本集的模式。主从模式其实就是一个单副本的应用，没有很好的扩展性和容错性，而Mongodb副本集具有多个副本保证了容错性，就算一个副本挂掉了还有很多副本存在，主节点挂掉后，整个集群内会实现自动切...
centos7.9 mongodb 5.0.7 集群（一主两从 副本集 开启Keyfile）
m0_62999427的博客
01-26 419
1.提前准备好mongodb-linux-x86_64-rhel70-5.0.7.tgz。
mongodb集群安装，一主二从，replica_set
码厦（微信号）
03-28 1290
下载mongodb-linux-x86_64-rhel62-3.2.0.tar.gz，将该压缩文件上传到三台服务器上， 将该文件可以放入到如下地址： /Data/mongodb-linux-x86_64-rhel62-3.2.0进入到bin目录下   touch mongo.conf 打开该mongo.conf文件写入以下配置信息。 logpath=/Data/mongodb/logs
使用docker-compose部署mongodb集群（一主两从的副本集模式）
天草二十六
05-04 2539
进入主节点，初始化副本集，把其他两个从节点加入到集群中。新增admin用户，密码为admin。主节点暴露端口号，见下映射关系。默认是不用账户和密码的授权。部署成功，容器列表见下。
Mongodb数据库之主从复制配置实战
jks212454的博客
12-14 2235
Mongodb数据库之主从复制配置实战
MongoDb双机主从同步（不是副本集）
qq_39944052的博客
08-03 2853
mongodb的主从同步（不是副本集
mongodb集群的搭建（1主2从，或1主3从，一个从隐身）--03
欢迎查阅
11-24 1446
集群的搭建1. 环境描述与准备（多实例的实现方式）2. 主从复制的配置2.1 1主2从，从库普通配置2.2 1主1从1个arditer2.3 集群的管理操作2.4 特殊的从节点2.5 设置副本（从）节点可读 基本构成是1主2从的结构，自带互相监控投票机制（Raft（MongoDB） Paxos（mysql MGR 用的是变种）） 如果发生主库宕机，复制集内部会进行投票选举， 选择一个新的主库替代原有主库对外提供服务。 同时复制集会自动通知客户端程序，主库已经发生切换了。应用就会连接到新的主库。 1. 环境
ClickHouse基础知识（六）：ClickHouse的副本配置
zuodingquan666的博客
12-29 1232
副本的目的主要是保障数据的高可用性，即使一台 ClickHouse 节点宕机，那么也可以 从其他服务器获得相同的数据。
mongodb3.6.2 linux安装 副本集配置 详细步骤
02-07
该步骤是根据mongodb3.6.2版本配置，从安装到认证模式到测试副本集，步骤清楚详细，有疑问评论 给你们一一解答
MongoDB副本集配置和数据迁移实战
12-29
由于 MongoDB 的主从复制功能不支持高可用，所以从 3.2 版本开始已经被废弃了，转而用副本集来代替实现数据复制的功能。一个副本集总会有一个活跃节点（Primary）和若干个备份节点（Secondary），还有一个可选的一个...
MongoDB 主从复制，副本集分布式存储
09-18
**副本集**则是一种更高级的复制机制，它由多个服务器组成，包括一个主节点和多个从节点。主节点负责接受所有写操作，而从节点则用于读取操作和提供冗余备份。副本集不仅提供了高可用性，还能够实现故障转移和自动...
MongoDB 复制（副本集）学习笔记
09-09
下面将详细介绍MongoDB复制（副本集）的原理、配置以及使用方法。 ### 原理 MongoDB复制的基本原理是通过将数据写入主节点（Primary），然后由主节点同步到其他从节点（Secondary）。这种同步通常是实时的，确保...
mongodb的副本集搭建(主从)
橙子的随笔集
12-11 1377
mongodb副本集的搭建，验证和选举过程。
基于docker创建mongodb副本集（1主2从）
单俞浩的博客
06-03 2545
docker下创建mongodb副本集
mongodb实现一主两从一个仲裁者
curiouswen的博客
10-12 5119
4台机器安装mongodb后，把4台机器的mongod启动，然后通过mongo连接你要做主机的mongo。 如以192.168.10.111:27017为主节点 master.conf配置 processManagement:    fork: true net:    bindIp: 127.0.0.1,192.168.10.110,10.9.0.1,14.17.97.2
MongoDB配置复制集（一主两从一仲裁）
星矢的博客
06-12 1423
一、准备工作 1.安装MongoDB 4.0 2.win10 64位系统 二、安装MongoDB 1.具体安装mongoDB步骤 2.配置环境变量 三、配置复制集 复制集主节点端口号为27100，从节点1为27101，从节点2为27102，仲裁节点为27103（端口号可以自行决定） 1.在data文件夹中新建四个文件夹，分别为primary（主服务器）、secondary1（从服务器1）、sec...
在同一台服务器上部署MongoDB一主多从
最爱嫣夜来
11-23 2588
1.登录服务器主机，创建主节点和从节点的数据存储目录 命令：mkdir -rp /rds/mongos/db1 命令：mkdir -rp /rds/mongos/db1 2.打开两个终端页面，运行mongodb数据库 命令：mongod -bind_ip 192.168.0.254 -port 27018 -dbpath /rds/mongos/db1 -replSet rs0 命令：mong...
MongoDB
最新发布
刘皇叔说Java的博客
11-04 1068
mongodbMongoDB 是一种基于文档的 NoSQL 数据库，使用 BSON（Binary JSON）格式来存储数据。与传统的关系型数据库相比，MongoDB 提供了更灵活的结构、可扩展性和高性能。以下是对 MongoDB 的详细介绍，包括基本概念、数据模型、操作、特性、优缺点以及应用场景。MongoDB 是一种灵活且高效的 NoSQL 数据库，适合需要快速开发和动态变化的数据应用。理解其基本概念和操作方式，可以帮助开发人员在项目中更好地利用 MongoDB 的特性。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值