[SERVER-65012] Avoid invariant when converting write-blocked shard to replicaSet Created: 29/Mar/22 Updated: 29/Oct/23 Resolved: 30/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-04-04 |
| Participants: |
| Description |
|
When user write blocking is enabled on a shardsvr, the associated critical section document has blockNewUserShardedDDL set to true. If now we convert this shardsvr back to replSet (which is a use case we account for), the replSet is hitting this invariant on startup due to seeing blockNewUserShardedDDL=true. Since it is not actually a problem that blockNewUserShardedDDL is true on a replSet (it is just ignored), we should remove this invariant. |
| Comments |
| Comment by Githook User [ 30/Mar/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |