[SERVER-50780] Improve cache.collections consistency check in ShardingTest hook Created: 07/Sep/20 Updated: 29/Oct/23 Resolved: 08/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
In checkUUIDsConsistentAcrossCluster it is currently assumed that cache.collections is always containing infos about a specific collection. When such condition is not met, actualConfigMetadata is wrongly set to an undefined value leading to a a cryptic error. It should be checked that the cursor returns exactly one result before actually getting it. |
| Comments |
| Comment by Githook User [ 08/Sep/20 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |