[SERVER-20855] Don't replace the ShardRegistry with older information than it already knows about Created: 09/Oct/15 Updated: 25/Jan/17 Resolved: 12/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding B (10/30/15) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
If two calls to ShardRegistry::reload() overlap, it's possible for one that started sooner and targeted a staler node to finish after one that started later. This means that the ShardRegistry could already have been loaded with newer data, but then throw it out and replace it with older data when the slower reload finishes. |
| Comments |
| Comment by Githook User [ 12/Oct/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 12/Oct/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 12/Oct/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |