MongoDB 副本集分片集群一分片config库主机断电导致该分片config库无法启动
2018-01-22 16:48
961 查看
2018年,1月22日,由于机房意外断电,一分片config服务器断电导致该config库无法启动,相关报错如下:
关键报错信息:
2018-01-22T15:18:43.863+0800 I -[initandlisten] Detected data file in D:\mongodata\cfg created
by the 'wiredTiger' storage
engine,so setting the active storage engine to 'wiredTiger'.
2018-01-22T15:18:43.865+0800 W- [initandlisten] Detected
unclean shutdown -D:\mongodata\cfg\mongod.lock is not empty.
2018-01-22T15:18:43.866+0800 w STORAGE [initandlisten] Recovering data from the last clean
checkpoint.
根据网上查到的处理方法:
1、关闭启动窗口
2、删除D:\mongodata\cfg\mongod.lock,
3、执行修复操作:D:\MongoDB\Server\3.2\bin\mongod
--configsvr --replSet configReplSet --port 27001
--dbpath D:\mongodata\cfg --repair
2018-01-22T15:46:50.530+0800 I STORAGE [initandlisten] Repairing collection loc
al.system.replset
2018-01-22T15:46:50.531+0800 I STORAGE [initandlisten] Verify succeeded on uri
table:collection-4--3441646246172970043. Not salvaging.
2018-01-22T15:46:50.545+0800 I INDEX [initandlisten] build index on: local.sy
stem.replset properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "local.syste
m.replset" }
2018-01-22T15:46:50.545+0800 I INDEX [initandlisten] building index
using bulk method
2018-01-22T15:46:50.569+0800 I STORAGE [initandlisten] finished checking dbs
2018-01-22T15:46:50.569+0800 I CONTROL [initandlisten] now exiting
2018-01-22T15:46:50.569+0800 I NETWORK [initandlisten] shutdown: going to close
listening sockets...
2018-01-22T15:46:50.570+0800 I NETWORK [initandlisten] shutdown: going to flush
diaglog...
2018-01-22T15:46:50.570+0800 I NETWORK [initandlisten] shutdown: going to close
sockets...
2018-01-22T15:46:50.571+0800 I STORAGE [initandlisten] WiredTigerKVEngine shutt
ing down
2018-01-22T15:46:50.769+0800 I STORAGE [initandlisten] shutdown: removing fs lo
ck...
2018-01-22T15:46:50.770+0800 I CONTROL [initandlisten] dbexit: rc: 0
4、修复操作没有明显的报错,重新启动config库,问题依然存在,报错与上述提到的日志一致
由于是副本集分片集群,且该config库只是一个片的config库,该副本集分片集群一共有3台config库,于是决定删除该config库
的data目录D:\mongodata\cfg下的所有数据文件以从集群其他节点重新同步,该config库重新同步数据后恢复正常。
关键报错信息:
2018-01-22T15:18:43.863+0800 I -[initandlisten] Detected data file in D:\mongodata\cfg created
by the 'wiredTiger' storage
engine,so setting the active storage engine to 'wiredTiger'.
2018-01-22T15:18:43.865+0800 W- [initandlisten] Detected
unclean shutdown -D:\mongodata\cfg\mongod.lock is not empty.
2018-01-22T15:18:43.866+0800 w STORAGE [initandlisten] Recovering data from the last clean
checkpoint.
根据网上查到的处理方法:
1、关闭启动窗口
2、删除D:\mongodata\cfg\mongod.lock,
3、执行修复操作:D:\MongoDB\Server\3.2\bin\mongod
--configsvr --replSet configReplSet --port 27001
--dbpath D:\mongodata\cfg --repair
2018-01-22T15:46:50.530+0800 I STORAGE [initandlisten] Repairing collection loc
al.system.replset
2018-01-22T15:46:50.531+0800 I STORAGE [initandlisten] Verify succeeded on uri
table:collection-4--3441646246172970043. Not salvaging.
2018-01-22T15:46:50.545+0800 I INDEX [initandlisten] build index on: local.sy
stem.replset properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "local.syste
m.replset" }
2018-01-22T15:46:50.545+0800 I INDEX [initandlisten] building index
using bulk method
2018-01-22T15:46:50.569+0800 I STORAGE [initandlisten] finished checking dbs
2018-01-22T15:46:50.569+0800 I CONTROL [initandlisten] now exiting
2018-01-22T15:46:50.569+0800 I NETWORK [initandlisten] shutdown: going to close
listening sockets...
2018-01-22T15:46:50.570+0800 I NETWORK [initandlisten] shutdown: going to flush
diaglog...
2018-01-22T15:46:50.570+0800 I NETWORK [initandlisten] shutdown: going to close
sockets...
2018-01-22T15:46:50.571+0800 I STORAGE [initandlisten] WiredTigerKVEngine shutt
ing down
2018-01-22T15:46:50.769+0800 I STORAGE [initandlisten] shutdown: removing fs lo
ck...
2018-01-22T15:46:50.770+0800 I CONTROL [initandlisten] dbexit: rc: 0
4、修复操作没有明显的报错,重新启动config库,问题依然存在,报错与上述提到的日志一致
由于是副本集分片集群,且该config库只是一个片的config库,该副本集分片集群一共有3台config库,于是决定删除该config库
的data目录D:\mongodata\cfg下的所有数据文件以从集群其他节点重新同步,该config库重新同步数据后恢复正常。
相关文章推荐
- mongodb分片集群突然停电造成一些错误,分片无法启动
- mongodb分片集群突然停电造成一些错误,分片无法启动(非正常关闭)
- mongodb分片集群突然停电造成一些错误,分片无法启动
- MongoDB健壮集群——用副本集做分片
- mongodb 集群搭建 分片+副本集
- apache配置虚拟主机,如果该文件配置错误,可能导致apache无法启动
- Linux:记一次异常断电导致的系统无法正常启动(文件系统故障)
- Mongodb 副本集+分片集群搭建
- 基于linux的mongodb3.2副本集+分片集群搭建
- HBase错误日志:集群时钟不同步导致HBase集群无法启动
- MongoDB主机断电后重启出现无法连接数据库的情况
- 搭建IIS服务器80端口却已被占用的问题和用了Sc config http start= disabled命令导致HTTP服务无法启动的解决方案
- mongodb集群分片+副本模式操作+javaCode
- MongoDB 3.2.7 for rhel6.4 副本集-分片集群部署
- mongodb 分片集群切换单个分片副本集primary的正确步骤
- 修改主机名导致oracle实例无法启动暨如何修改hostname
- [Oracle 11g r2(11.2.0.4.0)]案例分析3-由于同一个子网中存在同名集群导致的gpnp 无法启动
- mongodb副本集无法启动的解决方案
- MongoDB 副本集集群从节点控制台报错10061:由于目标计算机积极拒绝,无法连接
- oracle11gr2 netca 无法启动 报错 默认主机名导致