[SERVER-52881] Fix initialization of shard cluster type mongod servers Created: 16/Nov/20 Updated: 29/Oct/23 Resolved: 17/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0-alpha0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jaume Moragues (Inactive) | Assignee: | Jaume Moragues (Inactive) |
| Resolution: | Fixed | 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 | ||||
| Steps To Reproduce: | It happens from time to time in case during the time window in which replica set monitor is already initialized and topology change listerners are still not registered a topology change message arrives. |
||||
| Sprint: | Sharding 2020-11-30 | ||||
| Participants: | |||||
| Linked BF Score: | 10 | ||||
| Description |
|
When initializing mongod process of shard cluster type, initialize properly its components so topology change messages do not arrive before all topology listeners have been properly added to the system. A solution is to swap first two instructions in https://github.com/mongodb/mongo/blob/7a6078c14ec31052e5109629a78c988ca417b793/src/mongo/db/s/sharding_initialization_mongod.cpp#L261 |
| Comments |
| Comment by Githook User [ 17/Nov/20 ] |
|
Author: {'name': 'Jaume Moragues', 'email': 'jaume.moragues@mongodb.com'}Message: |