[SERVER-68156] Do not run ShardMerge protocol on tenant_migration_timeseries_retryable_write_retry_on_recipient.js Created: 19/Jul/22 Updated: 29/Oct/23 Resolved: 25/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | Mathis Bessa |
| 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: | Server Serverless 2022-07-25, Server Serverless 2022-08-08 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 149 | ||||||||||||
| Description |
|
The test tenant_migration_timeseries_retryable_write_retry_on_recipient.js is based off tenant_migration_retryable_write_retry_on_recipient.js which does not run the shard merge protocol due to the stepup in the test. We should therefor apply that same logic (or use the incompatible_with_shard_merge tag) to not run a shard merge on this test as a temporary solution until we can provide a proper fix. |
| Comments |
| Comment by Githook User [ 25/Jul/22 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |