[SERVER-29508] Add backoff to key collection manager refresh scheduling Created: 07/Jun/17 Updated: 30/Oct/23 Resolved: 13/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Misha Tyulenev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2017-06-19 |
| Participants: |
| Description |
|
The following executor configuration
this executor when run in resmoke will show too frequent key refresh events in its log. Need to adjust the scheduling in the presence of failures. |
| Comments |
| Comment by Githook User [ 13/Jun/17 ] | |
|
Author: {u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}Message: | |
| Comment by Randolph Tan [ 08/Jun/17 ] | |
|
I was not able to reproduce the "not stopping refresh on shutdown" but I was able to figure out why it was attempting to refresh so often. I found out that there are 2 contributing factors: 1. At the beginning, attempting to read the key will fail with "Read concern majority reads are currently not possible" We can potentially mitigate #1 by adding backoff and #2 can be fixed by changing this line to:
|