[SERVER-56620] Nodes should explicitly clear arbiter durableOpTimeAndWalltime Created: 04/May/21  Updated: 29/Oct/23  Resolved: 14/Jun/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.8, 5.0.2, 5.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Issue split
split from SERVER-54876 Upgrade mongodb 4.4.4 from 4.2.12 failed Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0, v4.4
Sprint: Repl 2021-06-14, Repl 2021-06-28
Participants:

 Description   

If an arbiter sends a durableOpTimeAndWalltime (e.g due to SERVER-56619), that OpTimeAndWallTime can remain in the system indefinitely, passed around in replSetUpdatePosition commands, even after the arbiter has been corrected. This is because replSetUpdatePosition only advances the optime, and a correct arbiter always has a null optime. Thus for arbiters we should explicitly clear the arbiter's durableOpTimeAndWallTime when we get a heartbeat, to avoid "ghost" optimes staying in the system.

We should also LOG_WARNING if we get a non-null durable optime from an arbiter.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 26/Jul/21 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-56620 Clear any durableOpTimeAndWallTime received from arbiters

(cherry picked from commit a85e78c4fe3734abf38b95348e0aa8d62ebdfdc5)
Branch: v4.4
https://github.com/mongodb/mongo/commit/6bdae3b2899c0123e37172410ebe021e90cd2148

Comment by Githook User [ 26/Jul/21 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-56620 Clear any durableOpTimeAndWallTime received from arbiters

(cherry picked from commit a85e78c4fe3734abf38b95348e0aa8d62ebdfdc5)
Branch: v5.0
https://github.com/mongodb/mongo/commit/2f23a4bc8b8eaa459f4fe04c9789002dc41cc94f

Comment by Githook User [ 16/Jun/21 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-56620 Clear any durableOpTimeAndWallTime received from arbiters
Branch: SERVER-34632
https://github.com/mongodb/mongo/commit/a85e78c4fe3734abf38b95348e0aa8d62ebdfdc5

Comment by Githook User [ 14/Jun/21 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-56620 Clear any durableOpTimeAndWallTime received from arbiters
Branch: master
https://github.com/mongodb/mongo/commit/a85e78c4fe3734abf38b95348e0aa8d62ebdfdc5

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