[SERVER-56165] Updating config.shards can lose information Created: 19/Apr/21 Updated: 27/Oct/23 Resolved: 09/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lamont Nelson | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Operating System: | ALL |
| Participants: |
| Description |
|
The ShardingReplicaSetChangeListener writes to config.shards from multiple nodes without synchronization or version information: https://github.com/mongodb/mongo/blob/c6c9c62b8abe5ca36ec65320c813eaf81735f02a/src/mongo/s/mongos_main.cpp#L547. This can result in newer updates being replaced by older information. |
| Comments |
| Comment by Connie Chen [ 09/Jul/21 ] |
|
This only exists in 4.4 and so we are not going to address unless there are major customer concerns raised. |
| Comment by Lamont Nelson [ 29/Apr/21 ] |
|
Yes, I've been meaning to contact you about this. The bug that I was originally thinking about was before the refactoring that Kevin had did a few months ago. When I sat down to look at the code to enter the details I realized that the Shard Registry was basically re-written. I'll reach out to you today on slack. This may not be a problem anymore. |
| Comment by Kaloian Manassiev [ 29/Apr/21 ] |
|
lamont.nelson, can you add a bit more context to this ticket? |