[SERVER-45285] index_operations_abort_concurrent_outgoing_migrations.js shouldn't assert that the recipient doesn't have the index created on the donor Created: 20/Dec/19 Updated: 29/Oct/23 Resolved: 23/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| 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 | ||||
| Sprint: | Sharding 2019-12-30 | ||||
| Participants: | |||||
| Linked BF Score: | 23 | ||||
| Description |
|
If a migration is aborted between _recvChunkStart and _migrateClone , the recipient might end up cloning indexes and options before it finds out that the migration has been aborted. So for the createIndexes tests, we should not assert that the recipient shard doesn't have the index created on the donor shard during migration. |
| Comments |
| Comment by Githook User [ 23/Dec/19 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}Message: |