[SERVER-32209] Reset the in-memory optimes on PV downgrade and upgrade Created: 07/Dec/17  Updated: 30/Oct/23  Resolved: 01/Feb/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.3

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Siyuan Zhou
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-11242 After protocol version downgrade, wai... Closed
Duplicate
Problem/Incident
Related
is related to SERVER-31004 persist term and initialize to it on ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6, v3.4
Sprint: Repl 2018-01-15, Repl 2018-01-29, Repl 2018-02-12
Participants:
Linked BF Score: 0

 Description   

We assume terms only increase, but on downgrade they can decrease. Resetting the in-memory terms to 0 should fix this. Which OpTimes need to be reset requires more investigation. The lastCommittedOpTime certainly does.



 Comments   
Comment by Githook User [ 01/Feb/18 ]

Author:

{'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou', 'username': 'visualzhou'}

Message: SERVER-32209 Don't drop snapshots for all reconfig, only on PV change.
Branch: v3.6
https://github.com/mongodb/mongo/commit/0de3f450c0cd14b90d6c670c7019fe28d9c2b61c

Comment by Githook User [ 29/Jan/18 ]

Author:

{'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou', 'username': 'visualzhou'}

Message: SERVER-32209 Reset the in-memory optimes on PV downgrade and upgrade
Branch: v3.6
https://github.com/mongodb/mongo/commit/ad7cc696e84390604bc6cfd7563abebe9c122ab3

Comment by Siyuan Zhou [ 24/Jan/18 ]

spencer, DOCS-11242 is created for this.

Comment by Siyuan Zhou [ 12/Jan/18 ]

Removed "3.7 Required" from Fix Versions because PV0 is going to be removed in 3.8 and this fix only applies to 3.6 (and 3.4).

Comment by Siyuan Zhou [ 12/Jan/18 ]

Blacklisted this test in v3.6 for now. The fix will enable it again.

Comment by Githook User [ 12/Jan/18 ]

Author:

{'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou', 'username': 'visualzhou'}

Message: SERVER-32209 Disable min_valid_on_pv_change.js temporarily on 3.6
Branch: v3.6
https://github.com/mongodb/mongo/commit/844c4d6e8ee461303a5d2d664896709c1c97d9e1

Comment by Judah Schvimer [ 04/Jan/18 ]

As a quick fix to stop the BFs, let's blacklist the test on 3.6 and then unblacklist it when this is completed.

Generated at Thu Feb 08 04:29:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.