[SERVER-61876] Mongo has been in the recovery state after restarting Created: 03/Dec/21 Updated: 08/Mar/22 Resolved: 08/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | 帆 张 | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | recovering | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | restart it |
||||||||
| Participants: | |||||||||
| Description |
|
I have a replica set cluster with 1 member, and when I restart it, it has been in the recovering state。Before I restarted, it was in the primary state。 I intercepted its startup log, hoping to help diagnose the problem。 This confuses me
|
| Comments |
| Comment by Eric Sedor [ 08/Mar/22 ] |
|
Hi, We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, |
| Comment by Eric Sedor [ 31/Jan/22 ] |
|
justonezf@gmail.com, are you able to provide mongod.log files and the $dbpath/diagnostic.data directory for this incident, or a recent occurrence of a similar incident? |
| Comment by Eric Sedor [ 10/Dec/21 ] |
|
Hi justonezf@gmail.com and sorry for the delay, Can you confirm the restart in question was at 2021-12-03T08:22:16.678+00:00? Could you please also archive (tar or zip) the mongod.log file immediately prior to the restart, and the $dbpath/diagnostic.data directory (the contents are described here) and upload them to this support uploader location? Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Gratefully, |