[SERVER-80259] Add logging for stepping up services from ReplicaSetAwareServiceRegistry Created: 18/Aug/23 Updated: 29/Oct/23 Resolved: 06/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Sean Zimmerman | Assignee: | Sean Zimmerman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2023-09-04, Repl 2023-09-18 |
| Participants: |
| Description |
|
While looking at BF-29617 I noticed a gap in logging we have in our stepup path which could help improve debugging in the future. In ReplicaSetAwareServiceRegistry::onStepUpComplete we rely on the individual services to log their status. If one of these services hung during stepup it would be very difficult to debug what was happening since most do not log any in onStepUpComplete. I propose we add 2 logs here, an info level log at the beginning of the function and a debug level log before we call onStepUpComplete on each service. This would be similar to killOpsForStorageEngineChange |
| Comments |
| Comment by Githook User [ 05/Sep/23 ] |
|
Author: {'name': 'seanzimm', 'email': 'sean.zimmerman@mongodb.com', 'username': 'seanzimm'}Message: |