[SERVER-59483] tenant_migration_collection_ttl.js must account for race between recipient cloner and donor TTL sweep Created: 20/Aug/21 Updated: 29/Oct/23 Resolved: 21/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.4, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Vishnu Kaushik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 18 | ||||||||
| Description |
|
The donor TTL may run before the recipient has had a chance to clone documents, after starting the migration. That would mean the recipient would not clone any documents. Therefore, this test, in which we expect recipient-side TTL to be suspended, may not function as intended, because this assertion (that there are documents on the recipient, owing to the recipient TTL being suspended) would fail. We should implement some synchronization to mitigate this race, or maybe just a check that observes the race and accordingly skips the test, such as the one implemented in the second half of the test. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 29/Sep/21 ] |
|
Author: {'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |
| Comment by Githook User [ 21/Aug/21 ] |
|
Author: {'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |