5.mongodb误删除文件,无法启动

最新推荐文章于 2024-06-18 16:03:51 发布

戒掉贪嗔痴

最新推荐文章于 2024-06-18 16:03:51 发布

阅读量862

点赞数 8

CC 4.0 BY-SA版权

分类专栏：数据库运维-MongoDB 文章标签： mongodb 数据库

本文链接：https://blog.youkuaiyun.com/weixin_43346403/article/details/135407445

数据库运维-MongoDB 专栏收录该内容

59 篇文章

订阅专栏

文章讲述了在MongoDB中由于误删除单个数据文件导致服务无法启动的情况，详细描述了通过禁用fork选项、执行`mongod--repair`命令以及修复过程中的日志分析。最后强调了定期备份的重要性以防止数据丢失。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

1.场景

mongodb数据目录下误删除个别数据文件，导致mongodb无法启动。

2.修复方法

(1)注释fork;
vi mongod.conf 
processManagement:
#    fork: true

--执行修复命令
--如下命令未修复成功。
--/mysqlbackup/mongodb/bin/mongod --dbpath /mysqlbackup/mongosc --port 27018  --oplogSize 512  \
----bind_ip 0.0.0.0 --logpath /var/log/mongodb/mongodb.log \
----logappend --journal --directoryperdb --profile=1 --repair



(2)修复数据库。
/mysqlbackup/mongodb/bin/mongod -f /mysqlbackup/mongodb/mongod.conf  --repair & 

(3)观察日志输出。
tail -100f /var/log/mongodb/mongod.conf 
2024-01-04T17:57:48.041+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 86400
2024-01-04T17:57:48.465+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 86500
2024-01-04T17:57:48.928+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 86600
2024-01-04T17:57:49.349+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 86700
2024-01-04T17:57:49.826+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 86800
2024-01-04T17:57:50.282+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 86900
2024-01-04T17:57:50.755+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 87000
2024-01-04T17:57:51.239+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 87100
2024-01-04T17:57:51.750+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 87200
2024-01-04T17:57:52.232+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 87300
2024-01-04T17:57:52.727+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 87400
2024-01-04T17:57:53.205+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 87500
2024-01-04T17:57:53.695+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 87600
2024-01-04T17:57:54.222+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 87700
2024-01-04T17:57:54.742+0800 I  STORAGE  [initandlisten] WiredTiger progress WT_SESSION.verify 87800
..................................................................................................
2024-01-04T20:22:52.898+0800 W  STORAGE  [initandlisten] WARNING: Repair may have modified replicated data. This node will no longer be able to join a replica set without a full re-sync
2024-01-04T20:22:52.901+0800 I  STORAGE  [initandlisten] Flow Control is enabled on this deployment.
2024-01-04T20:22:52.901+0800 I  STORAGE  [initandlisten] finished checking dbs  (修复完成)
2024-01-04T20:22:52.901+0800 I  -        [initandlisten] Stopping further Flow Control ticket acquisitions.
2024-01-04T20:22:52.901+0800 I  STORAGE  [initandlisten] Deregistering all the collections
2024-01-04T20:22:52.901+0800 I  STORAGE  [WTOplogJournalThread] Oplog journal thread loop shutting down
2024-01-04T20:22:52.901+0800 I  STORAGE  [initandlisten] Timestamp monitor shutting down
2024-01-04T20:22:52.902+0800 I  STORAGE  [initandlisten] WiredTigerKVEngine shutting down
2024-01-04T20:22:52.905+0800 I  STORAGE  [initandlisten] Shutting down session sweeper thread
2024-01-04T20:22:52.905+0800 I  STORAGE  [initandlisten] Finished shutting down session sweeper thread
2024-01-04T20:22:52.905+0800 I  STORAGE  [initandlisten] Shutting down journal flusher thread
2024-01-04T20:22:52.948+0800 I  STORAGE  [initandlisten] Finished shutting down journal flusher thread
2024-01-04T20:22:52.948+0800 I  STORAGE  [initandlisten] Shutting down checkpoint thread
2024-01-04T20:22:52.948+0800 I  STORAGE  [initandlisten] Finished shutting down checkpoint thread
2024-01-04T20:22:53.056+0800 I  STORAGE  [initandlisten] shutdown: removing fs lock...
2024-01-04T20:22:53.057+0800 I  CONTROL  [initandlisten] now exiting
2024-01-04T20:22:53.057+0800 I  CONTROL  [initandlisten] shutting down with code:0

(4)修复结束后启动数据库
--启动
/mysqlbackup/mongodb/bin/mongod   -f /mysqlbackup/mongodb/mongod.conf &

--登录:
/mysqlbackup/mongodb/bin/mongo --host 10.1.1.1 --port=27018

>use admin 
>db.auth("admin","admin");   --密码认证登录。
(5)查看数据库和集合
> show dbs;
admin         0.000GB
config        0.000GB
edocuments  947.649GB
local         0.000GB
> use edocuments;
switched to db edocuments
> show collections;
base_interface_record
base_interface_record_20231024
car_pics_interface_record

我的参数文件如下:

vi mongod.conf 
systemLog:
    destination: file
    logAppend: true
    path: /var/log/mongodb/mongodb.log
storage:
    dbPath: /mysqlbackup/mongosc
    journal:
        enabled: true
processManagement:
#    fork: true
    pidFilePath: /mysqlbackup/mongosc/mongodb.pid
    timeZoneInfo: /usr/share/zoneinfo
net:
    port: 27018
    bindIp: 0.0.0.0

security:
    keyFile: "/mysqlbackup/mongosc/mongodb_keyfile"
    clusterAuthMode: "keyFile"
    authorization: "enabled"

3.总结

由此可见，即使mongodb的个别数据文件 collection-13-7183433419409953098.wt 文件被误删除后，其他正常的文件，还是可以通过repair命令进行修复。只不过丢失的数据就无法找回了。所以做好备份是非常重要的。