[SERVER-76471] Install a single access blocker during shard split recovery in 7.0 Created: 24/Apr/23 Updated: 29/Oct/23 Resolved: 28/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.0-rc0 |
| Fix Version/s: | 7.0.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Didier Nadeau | Assignee: | Didier Nadeau |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Server Serverless 2023-05-01 |
| Participants: |
| Description |
|
The code to recover access blocker for shard split (https://github.com/10gen/mongo/blob/af171a2a74353693ce811a55577c1aa86ae2cdb4/src/mongo/db/repl/tenant_migration_access_blocker_util.cpp#L600) at the end of a rollback or initial sync install one blocker per tenant. The shard split observer expects one blocker shared by all tenant and will not correctly deal with the access blockers. This will be fixed in master by |
| Comments |
| Comment by Githook User [ 28/Apr/23 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |