[SERVER-66150] Writer pool and DBClientConnection should be shared across the entire tenant file cloning phase Created: 03/May/22 Updated: 29/Oct/23 Resolved: 26/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Christopher Caplinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | shard-merge-milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-08-08, Server Serverless 2022-08-22, Server Serverless 2022-09-05 |
| Participants: |
| Description |
|
Currently, for each learned file, we create a new DBClientConnection and a writer pool to copy & write the data file from donor to recipient. Since we aren't going to do concurrent copies, we can can reuse the DBClientConnection and writerpool for the entire migration by making the TenantFileImporter service to manage theirs lifetime. |
| Comments |
| Comment by Britt Snyman [ 01/Sep/22 ] |
|
Replacing the 6.1.0-rc1 fixVersion with 6.2.0-rc0 since these tickets had commits to master that were merged after we branched for v6.1. |
| Comment by Githook User [ 26/Aug/22 ] |
|
Author: {'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}Message: |