[SERVER-45484] Blacklist rollback_after_enabling_majority_reads.js from multiversion suite Created: 10/Jan/20 Updated: 29/Oct/23 Resolved: 11/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| 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: | Repl 2020-01-13 | ||||
| Participants: | |||||
| Linked BF Score: | 50 | ||||
| Description |
|
If a node was primary in 4.3 but restarted with a 4.2 binary after an unclean shutdown. The fastcount of oplogTruncateAfterPoint could be wrong. This is related to We do not even support a crashed v4.3 binary being restarted with a v4.2 binary. So putting the requires_fcv_44 tag to the test. |
| Comments |
| Comment by Githook User [ 11/Jan/20 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |