[SERVER-81559] Fix tests calling enableSharding after implicitly creating a database Created: 29/Sep/23 Updated: 29/Oct/23 Resolved: 29/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | car-71-backport-declined | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2023-10-02 | ||||
| Participants: | |||||
| Linked BF Score: | 160 | ||||
| Description |
|
We have observed some sporadic failures only in multiversion suites with mixed binaries (random binaries versions for each shard). When implicitly creating a database, the least loaded shard is chosen and most probably the issue is due to the fact that shards in older versions create less internal collections. |
| Comments |
| Comment by Githook User [ 29/Sep/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |