rs.status()命令用于获取mongodb副本集的状态信息。它提供了关于副本集中各个节点的详细信息,包括节点的健康状况、角色、选举状态等。
以下是查看一个mongo集群状态返回的参数:
rs0:primary> rs.status()
{
"set" : "rs0",
"date" : isodate("2024-09-14t06:44:36.882z"),
"mystate" : 1,
"term" : numberlong(510),
"syncingto" : "",
"syncsourcehost" : "",
"syncsourceid" : -1,
"heartbeatintervalmillis" : numberlong(2000),
"majorityvotecount" : 2,
"writemajoritycount" : 2,
"optimes" : {
"lastcommittedoptime" : {
"ts" : timestamp(0, 0),
"t" : numberlong(-1)
},
"lastcommittedwalltime" : isodate("1970-01-01t00:00:00z"),
"appliedoptime" : {
"ts" : timestamp(1726296270, 1),
"t" : numberlong(510)
},
"durableoptime" : {
"ts" : timestamp(1726296270, 1),
"t" : numberlong(510)
},
"lastappliedwalltime" : isodate("2024-09-14t06:44:30.859z"),
"lastdurablewalltime" : isodate("2024-09-14t06:44:30.859z")
},
"laststablerecoverytimestamp" : timestamp(1725300368, 3),
"laststablecheckpointtimestamp" : timestamp(1725300368, 3),
"electioncandidatemetrics" : {
"lastelectionreason" : "electiontimeout",
"lastelectiondate" : isodate("2024-09-14t06:28:20.630z"),
"electionterm" : numberlong(510),
"lastcommittedoptimeatelection" : {
"ts" : timestamp(0, 0),
"t" : numberlong(-1)
},
"lastseenoptimeatelection" : {
"ts" : timestamp(1726284227, 1),
"t" : numberlong(509)
},
"numvotesneeded" : 2,
"priorityatelection" : 2,
"electiontimeoutmillis" : numberlong(10000),
"numcatchupops" : numberlong(0),
"newtermstartdate" : isodate("2024-09-14t06:28:20.830z")
},
"members" : [
{
"_id" : 0,
"name" : "mongo1:27017",
"health" : 1,
"state" : 9,
"statestr" : "rollback",
"uptime" : 987,
"optime" : {
"ts" : timestamp(1726197065, 1),
"t" : numberlong(505)
},
"optimedurable" : {
"ts" : timestamp(1726197065, 1),
"t" : numberlong(505)
},
"optimedate" : isodate("2024-09-13t03:11:05z"),
"optimedurabledate" : isodate("2024-09-13t03:11:05z"),
"lastheartbeat" : isodate("2024-09-14t06:44:35.841z"),
"lastheartbeatrecv" : isodate("2024-09-14t06:44:36.665z"),
"pingms" : numberlong(0),
"lastheartbeatmessage" : "",
"syncingto" : "mongo2:27017",
"syncsourcehost" : "mongo2:27017",
"syncsourceid" : 1,
"infomessage" : "",
"configversion" : 1950478
},
{
"_id" : 1,
"name" : "mongo2:27017",
"health" : 1,
"state" : 1,
"statestr" : "primary",
"uptime" : 990,
"optime" : {
"ts" : timestamp(1726296270, 1),
"t" : numberlong(510)
},
"optimedate" : isodate("2024-09-14t06:44:30z"),
"syncingto" : "",
"syncsourcehost" : "",
"syncsourceid" : -1,
"infomessage" : "",
"electiontime" : timestamp(1726295300, 1),
"electiondate" : isodate("2024-09-14t06:28:20z"),
"configversion" : 1950478,
"self" : true,
"lastheartbeatmessage" : ""
},
{
"_id" : 2,
"name" : "mongo3:27017",
"health" : 1,
"state" : 2,
"statestr" : "secondary",
"uptime" : 987,
"optime" : {
"ts" : timestamp(1726197065, 1),
"t" : numberlong(505)
},
"optimedurable" : {
"ts" : timestamp(1726197065, 1),
"t" : numberlong(505)
},
"optimedate" : isodate("2024-09-13t03:11:05z"),
"optimedurabledate" : isodate("2024-09-13t03:11:05z"),
"lastheartbeat" : isodate("2024-09-14t06:44:34.930z"),
"lastheartbeatrecv" : isodate("1970-01-01t00:00:00z"),
"pingms" : numberlong(1),
"lastheartbeatmessage" : "",
"syncingto" : "",
"syncsourcehost" : "",
"syncsourceid" : -1,
"infomessage" : "",
"configversion" : 1829326
}
],
"ok" : 1,
"$clustertime" : {
"clustertime" : timestamp(1726296270, 1),
"signature" : {
"hash" : bindata(0,"aaaaaaaaaaaaaaaaaaaaaaaaaaa="),
"keyid" : numberlong(0)
}
},
"operationtime" : timestamp(1726296270, 1)
}
rs0:primary>以下是rs.status()响应字段的意义及其对应值的整理:
| 字段 | 意义 | 示例值 |
|---|---|---|
set | 副本集的名称 | "rs0" |
date | 响应生成的时间 | isodate("2024-09-14t06:44:36z") |
mystate | 当前节点的状态(1: primary, 2: secondary, 3: recovering等): 常见的状态包括:
| 1 |
term | 当前选举周期 | 510 |
lastelectionreason | 最近一次选举的原因 | "electiontimeout" |
members | 副本集成员的详细信息 | 数组,包含各个节点的信息 |
health | 节点的健康状态(1: 健康, 0: 不健康) | 1 |
statestr | 节点的状态描述(如 primary, secondary, rollback等) | "secondary" |
uptime | 节点的运行时间(秒) | 987 |
optime | 最近一次操作的时间戳 | timestamp(1726197065, 1) |
optimedurable | 最近一次持久化操作的时间戳 | timestamp(1726197065, 1) |
optimedate | 最近一次操作的日期 | isodate("2024-09-13t03:11:05z") |
optimedurabledate | 最近一次持久化操作的日期 | isodate("2024-09-13t03:11:05z") |
lastheartbeat | 最近一次心跳信号的时间 | isodate("2024-09-14t06:44:34.930z") |
lastheartbeatrecv | 最近一次接收到心跳信号的时间 | isodate("1970-01-01t00:00:00z") |
pingms | 节点的延迟(毫秒) | numberlong(1) |
lastheartbeatmessage | 最近一次心跳的消息 | "" |
syncingto | 当前节点正在同步的目标节点 | "" |
syncsourcehost | 当前节点的同步源主机 | "" |
syncsourceid | 当前节点的同步源id | -1 |
infomessage | 额外的信息消息 | "" |
configversion | 配置版本号 | 1829326 |
$clustertime | 集群时间信息 | 包含 clustertime 和 signature |
operationtime | 最近一次操作的时间 | timestamp(1726296270, 1) |
使用场景
- 故障排查: 当副本集出现问题时,使用
rs.status()可以快速定位故障节点。 - 性能监控: 定期检查副本集状态,以确保所有节点正常运行并及时发现性能瓶颈。
- 维护操作: 在进行维护或升级操作前,确认副本集的健康状况。
- 选举监控: 监控选举过程,确保主节点的选举和切换正常进行。
到此这篇关于mongodb 中rs.stauts()命令参数解析的文章就介绍到这了,更多相关mongodb rs.stauts()命令参数内容请搜索代码网以前的文章或继续浏览下面的相关文章希望大家以后多多支持代码网!
发表评论