[SERVER-36760] shard_existing_coll_chunk_count.js should use more relaxed conditions for chunk count Created: 20/Aug/18 Updated: 29/Oct/23 Resolved: 27/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (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 2018-09-10 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 13 | ||||||||
| Description |
|
Currently shard_existing_coll_chunk_count.js checks for exact equality on chunk count, but if the timing of inserts is slightly off, the test will fail because there will be too few chunks even though everything is working properly. The easiest workaround for this is to use a more relaxed condition and assert that the number of chunks created is greater than or equal to some minimum amount. |
| Comments |
| Comment by Githook User [ 27/Aug/18 ] |
|
Author: {'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com', 'username': 'saltzm'}Message: |