[SERVER-49384] the replset primary crashed without a clear reason Created: 08/Jul/20 Updated: 04/Dec/20 Resolved: 14/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.0.13 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Li | Assignee: | Dmitry Agranat |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
any clear reason can't be found in the log |
| Comments |
| Comment by Michael Li [ 13/Jul/20 ] |
|
Hi Dima, thanks for the help! |
| Comment by Dmitry Agranat [ 12/Jul/20 ] |
|
Thank you for uploading the requested information. The crash that you've reported here is related to Thanks, |
| Comment by Michael Li [ 10/Jul/20 ] |
|
Hi Dima, is there a way to start the replset with index rebuild disabled? (noIdexBuildRetry is not allowed for replset).
The problem is that we have a huge amount of collections (about 200k) (with indexes). The server restarting takes way too long time to build index (still going on). We want the server back online ASAP.
|
| Comment by Michael Li [ 09/Jul/20 ] |
|
Hi Dima, logs(5000 line) and diagnostic.data uploaded |
| Comment by Dmitry Agranat [ 09/Jul/20 ] |
|
Would you please archive (tar or zip) the full mongod.log files and the $dbpath/diagnostic.data directory (the contents are described here) and upload them to this support uploader location? Ideally, we would like to see the requested logs from the time of the startup. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Thanks, |