[SERVER-42419] Ban whole_cluster_metadata_notifications test from running with majority read concern off Created: 25/Jul/19 Updated: 29/Oct/23 Resolved: 30/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Davis Haupt (Inactive) | Assignee: | Davis Haupt (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 12 | ||||||||
| Description |
|
When running in a sharded multi-statement transaction passthrough on the majority read concern off variant, if two databases used in whole_cluster_metadata_notifications are on different shards, the test will fail. This is due to |
| Comments |
| Comment by Githook User [ 14/Aug/19 ] |
|
Author: {'username': 'davish', 'email': 'davis.haupt@mongodb.com', 'name': 'Davis Haupt'}Message: (cherry picked from commit a220e3043fbfe5c300048364fe062a4864dc5182) |
| Comment by Githook User [ 30/Jul/19 ] |
|
Author: {'name': 'Davis Haupt', 'email': 'davis.haupt@mongodb.com', 'username': 'davish'}Message: |
| Comment by Davis Haupt (Inactive) [ 26/Jul/19 ] |
|
Code review URL: https://mongodbcr.appspot.com/504140053 |