[SERVER-35006] Do not reset KeysCollectionManager Created: 15/May/18 Updated: 29/Oct/23 Resolved: 17/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.6, 4.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Misha Tyulenev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | bkp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.6
|
||||||||
| Sprint: | Sharding 2018-05-21 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 4 | ||||||||
| Description |
|
KeysCollectionManager may be referenced after it was reset when a node is transitioning to arbiter but processing older requests. There is no need to reset it because the arbiter nodes can not transition to a non arbiters. |
| Comments |
| Comment by Githook User [ 01/Jun/18 ] |
|
Author: {'username': 'mikety', 'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com'}Message: (cherry picked from commit 24a6081a3f7a0c4eaa9d765ef453bcda64f4288e) |
| Comment by Githook User [ 17/May/18 ] |
|
Author: {'email': 'misha@mongodb.com', 'username': 'mikety', 'name': 'Misha Tyulenev'}Message: |