[SERVER-66996] Add warnings to ReplicaSetAwareServiceRegistry for services that block drain mode Created: 03/Jun/22 Updated: 29/Oct/23 Resolved: 22/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaitlin Mahar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2023-03-06, Repl 2023-03-20, Repl 2023-04-03 |
| Participants: |
| Description |
|
ReplicaSetAwareService implementations have the ability to run in drain mode and some of the ones that we have take advantage of that. We should add some logic in the ReplicaSetAwareServiceRegistry which keeps a tally of how much time each service spends in drain mode and then logs a warning if:
If there are other events on the RSAS that have the potential of causing unavailability if they take too much time, we should add warnings for them as well. |
| Comments |
| Comment by Githook User [ 22/Mar/23 ] |
|
Author: {'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'}Message: |