[SERVER-58823] [5.0] The refineShardKey command should mark its operation context as interruptible at step down/step up Created: 26/Jul/21 Updated: 29/Oct/23 Resolved: 05/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding EMEA 2021-07-26, Sharding EMEA 2021-08-09 | ||||
| Participants: | |||||
| Linked BF Score: | 167 | ||||
| Description |
|
Otherwise we might end up executing this command on a node that it is not a primary anymore. The change should be done here and here (probably just the second one is enough though). |
| Comments |
| Comment by Githook User [ 05/Aug/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |