[SERVER-67080] PerClusterDataConsistencyHook checks data consistency on same cluster twice Created: 07/Jun/22 Updated: 29/Oct/23 Resolved: 09/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc10, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Vishnu Kaushik |
| 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 | ||||||||
| Backport Requested: |
v6.0
|
||||||||
| Sprint: | Repl 2022-06-13 | ||||||||
| Participants: | |||||||||
| Description |
|
The PerClusterDataConsistencyHook prints out that it is checking data consistency on a cluster, but then uses the fixture that was passed into it. This means that it ends up checking consistency on the same cluster (i.e. the fixture that was passed in) multiple times. |
| Comments |
| Comment by Githook User [ 13/Jun/22 ] |
|
Author: {'name': 'kauboy26', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |
| Comment by Githook User [ 09/Jun/22 ] |
|
Author: {'name': 'kauboy26', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |