[SERVER-74445] Cluster checkMetadataConsistency fails with catalog shard Created: 28/Feb/23 Updated: 29/Oct/23 Resolved: 14/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0, 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding NYC
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||||||||||
| Sprint: | Sharding NYC 2023-04-17 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 60 | ||||||||||||||||||||
| Description |
|
The cluster version of the checkMetadataConsistency command will make a cursor on each shard and the config server, which get established together via establishCursors. That helper will send the same operationKey with every request, which must be unique per process, but when the config server is also a shard, we send the same operationKey to it twice, which fails the second command to arrive with BadValue. |
| Comments |
| Comment by Githook User [ 17/Apr/23 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 8b08b115667c0b75c569a2da2b0a5d9d166503b7) |
| Comment by Githook User [ 14/Apr/23 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |