[SERVER-71819] Broadcast collMod command to all shards Created: 03/Dec/22 Updated: 29/Oct/23 Resolved: 12/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.1, 7.2.0-rc0, 7.0.3, 6.0.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Pol Pinol |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v7.1, v7.0, v6.0
|
||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18 | ||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
When we run collMod on a collection in a sharded cluster, the CollModCoordinator runs collMod only on shards that own a chunk. This makes it possible to bypass the effects of collMod under certain conditions. For example, let's take a two shard set up, only one node in each shard and in the config server. Shard shard-rs0 is the primary shard for the collection we use below. Run the following commands on mongos:
In the above example the final statement bypassed the schema validation, which shouldn't happen. I have not investigated how other collMod behaviors (such as to convert indexes to unique) are affected and if other DDL coordinators have the same problem. |
| Comments |
| Comment by Githook User [ 17/Oct/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: (cherry picked from commit eec54ec63e557e18f0e8361335b9a39887572b4d)
(cherry picked from commit 76ef13cd2ef0798606f8387a088a1edff1093d9a) |
| Comment by Githook User [ 04/Oct/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: (cherry picked from commit eec54ec63e557e18f0e8361335b9a39887572b4d)
(cherry picked from commit 76ef13cd2ef0798606f8387a088a1edff1093d9a) |
| Comment by Githook User [ 04/Oct/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: (cherry picked from commit eec54ec63e557e18f0e8361335b9a39887572b4d)
(cherry picked from commit 76ef13cd2ef0798606f8387a088a1edff1093d9a) |
| Comment by Githook User [ 12/Sep/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |
| Comment by Vishnu Kaushik [ 05/Dec/22 ] |
|
I'm not sure if other backports to 5.0 and lower are required. I'll defer that to the sharding team. Thanks! |
| Comment by Vishnu Kaushik [ 03/Dec/22 ] |