[SERVER-28578] When doing an upgrade from PV0 to PV1, we should not return from the reconfigure until the lastVote document is written. Created: 31/Mar/17  Updated: 06/Dec/22  Resolved: 28/Jun/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.2.13, 3.4.4
Fix Version/s: 3.2.15, 3.2.16, 3.4.6

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Backlog - Replication Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-28865 Replace ReplicationExecutor with Thre... Closed
Related
is related to SERVER-28624 Replace references to ReplicationExec... Closed
is related to SERVER-28244 replSetReconfig command during an ele... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4, v3.2, v3.0
Participants:
Linked BF Score: 0

 Description   

The protocol_version_upgrade_downgrade test expects a lastVote document to be written on upgrade from PV0 to PV1. This document is written asynchronously, so there may be a race between the upgrade and the document appearing. We should delay signalling the reconfigure as complete until the lastVote document is written.



 Comments   
Comment by Githook User [ 28/Jun/17 ]

Author:

{u'username': u'mtrussotto', u'name': u'Matthew Russotto', u'email': u'matthew.russotto@10gen.com'}

Message: SERVER-28578 When doing an upgrade from PV0 to PV1, we should not return from the reconfigure until the lastVote document is written.

(cherry picked from commit 62f52d2eba138a8729ac31b589d87bde6f1b5cf5)
Branch: v3.2
https://github.com/mongodb/mongo/commit/c9b99e6c1f23e6db4937db041dbba1b247c9e45f

Comment by Githook User [ 27/Jun/17 ]

Author:

{u'username': u'mtrussotto', u'name': u'Matthew Russotto', u'email': u'matthew.russotto@10gen.com'}

Message: SERVER-28578 When doing an upgrade from PV0 to PV1, we should not return from the reconfigure until the lastVote document is written.
Branch: v3.4
https://github.com/mongodb/mongo/commit/62f52d2eba138a8729ac31b589d87bde6f1b5cf5

Comment by Spencer Brody (Inactive) [ 13/Jun/17 ]

This is causing build failures on 3.4 and 3.2, so probably worth considering fixing for those branches if its not too much work

Comment by Matthew Russotto [ 19/May/17 ]

The removal of replication executor in SERVER-28865 fixes this bug. If we backport it, it will need to be done differently.

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