[SERVER-52839] [testing] Test that tenant migration donor cleans up index build correctly if it fails to write commitIndexBuild oplog entry due to TenantMigrationConflict or TenantMigrationCommitted Created: 12/Nov/20  Updated: 29/Oct/23  Resolved: 19/Nov/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-C
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-11-30
Participants:

 Description   

Right now we get some test coverage for this from index tests that run in the tenant_migration_jscore_passthrough suite if the background migration happens to conflict with the commitIndexBuild oplog entry but there is no test that explicitly tests for this. The test case for createIndex in tenant_migration_concurrent_writes.js always runs createIndex after the migration has entered the write blocking state so TenantMigrationConflict is thrown when we try to write the startIndexBuild oplog entry as supposed to the commitIndexBuild oplog entry .



 Comments   
Comment by Githook User [ 19/Nov/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-52839 Test that tenant migration donor cleans up index build correctly if it fails to write commitIndexBuild oplog entry due to TenantMigrationConflict or TenantMigrationCommitted
Branch: master
https://github.com/mongodb/mongo/commit/871848e83d1fed19a46e52a475c58d3bf528351a

Generated at Thu Feb 08 05:29:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.