[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:
Depends
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 SERVER-41391 where we added a function to correct the fastcount. But since 4.2 doesnt have that ability (unless we backport that), restarting a node with a 4.2 binary after an unclean shutdown in 4.3, the fastcount could be wrong.

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: SERVER-45484: Blacklist rollback_after_enabling_majority_reads.js from multiversion suite
Branch: master
https://github.com/mongodb/mongo/commit/157d72e6a3d84735be4dab94149d55a969bd071f

Generated at Thu Feb 08 05:08:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.