[SERVER-42499] Temporarily blacklist refine_collection_shard_key jstests from config server stepdown suite Created: 30/Jul/19 Updated: 29/Oct/23 Resolved: 31/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | James Heppenstall (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2019-08-12 | ||||
| Participants: | |||||
| Linked BF Score: | 25 | ||||
| Description |
|
Until refineCollectionShardKey updates metadata using a transaction, the tests that use it can't safely run in the continuous config server stepdown suite. Both refine_collection_shard_key_basic.js and refine_collection_shard_key_jumbo.js should be blacklisted with a TODO comment for |
| Comments |
| Comment by Githook User [ 31/Jul/19 ] |
|
Author: {'name': 'Jamie Heppenstall', 'username': 'JamesHeppenstall', 'email': 'jamie.heppenstall@mongodb.com'}Message: |