[SERVER-71263] Create RTAB at the start of the merge using the tenant info stored in the state doc Created: 10/Nov/22 Updated: 29/Oct/23 Resolved: 22/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Didier Nadeau |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | shard-merge-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Server Serverless 2022-12-26 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Remove installing recipient access blocker on-fly during file-copy based cloning & oplog application phase, instead create recipient access blocker when shard merge starts ( similar to how MTM installs recipient access blocker upfront) . We can also do a similar implementation like |
| Comments |
| Comment by Githook User [ 22/Dec/22 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |