[SERVER-56222] Startup logging should provide regular status updates for the undergoing recovery Created: 21/Apr/21 Updated: 06/Dec/22 Resolved: 21/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dmitry Ryabtsev | Assignee: | Backlog - Storage Engines Team |
| Resolution: | Done | Votes: | 9 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Engines
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
It has been observed in the most recent versions of MongoDB (4.4.5) that startup recovery of an instance with a large data set can take several hours. This is problematic for TSEs and for the users as the status of the mongod process is not entirely clear. For example:
To illustrate, it's been observed that a mongod spends multiple hours recovering after having a message similar to the following printed in the log with no other clear signs of progress:
|
| Comments |
| Comment by Luke Pearson [ 21/May/21 ] |
|
|
| Comment by Sulabh Mahajan [ 27/Apr/21 ] |
|
daniel.gottlieb, very likely it will be recovery_progress. I will make a note on |
| Comment by Daniel Gottlieb (Inactive) [ 27/Apr/21 ] |
|
sulabh.mahajan, is the logging
If so, your proposal to mark this as blocked makes sense to me. AFAIK, nothing specific about MDB was identified to be improved. |
| Comment by Sulabh Mahajan [ 27/Apr/21 ] |
|
I created |
| Comment by Sulabh Mahajan [ 27/Apr/21 ] |
|
Though |