[SERVER-63724] ShardingDDLCoordinators should forward the WriteBlockBypass flag when running commands on participant shards Created: 16/Feb/22 Updated: 29/Oct/23 Resolved: 23/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04 | ||||||||
| Participants: | |||||||||
| Description |
|
Sharded DDL that is started by a client that has the WriteBlockBypass flag attached should be able to proceed. To do so, ShardingDDLCoordinators will need to forward this flag in the requests it makes to participant shards. The status of the bypass flag should be stored onĀ ShardingDDLCoordinatorMetadata and attached on the opCtx in ForwardableOperationMetadata::setOn so that it is forwarded when making requests to the shards. |
| Comments |
| Comment by Githook User [ 22/Mar/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |