[SERVER-60053] More info logs during replication startup sequence Created: 17/Sep/21 Updated: 29/Oct/23 Resolved: 20/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Wenbin Zhu | Assignee: | Frederic Vitzikam |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Replication 2021-12-27 | ||||
| Participants: | |||||
| Description |
|
There is very little info level logs during replication startup sequence and reconfigs, which makes it difficult to triage customer issues. There should be some info logs before some major steps in the startup sequence for example when it starts to do recoverFromOplog, or change some import states. |
| Comments |
| Comment by Githook User [ 20/Dec/21 ] |
|
Author: {'name': 'Frederic Vitzikam', 'email': 'frederic.vitzikam@mongodb.com', 'username': 'fredvitz'}Message: |
| Comment by Wenbin Zhu [ 13/Dec/21 ] |
|
This has been mostly done as part of |