[SERVER-49393] KeysCollectionManager should not silently ignore refresh failures Created: 09/Jul/20 Updated: 29/Oct/23 Resolved: 03/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Jason Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.4, v4.2, v4.0, v3.6
|
||||||||||||
| Sprint: | Sharding 2020-09-07 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 25 | ||||||||||||
| Description |
|
The KeysCollectionManager checks for refresh failure, but only handles it by doing backoff for the retries. This means that admins are not aware that refreshing has failed, which is important because persistent refresh failures can prevent the cluster from operating correctly. These failures should be logged at the default level (because they should be rare/infrequent, and even though the first retry is after 200ms, this will increase until they are done every 10 mins). |
| Comments |
| Comment by Githook User [ 08/Sep/20 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com'}Message: |
| Comment by Githook User [ 04/Sep/20 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com'}Message: |