[SERVER-47435] Incrementing topologyVersion for FCV change does not update awaitingTopologyChanges Created: 09/Apr/20  Updated: 29/Oct/23  Resolved: 13/Apr/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.3.6
Fix Version/s: 4.4.0-rc2, 4.7.0

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

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Repl 2020-04-20
Participants:

 Description   

When we increment the topologyVersion for featureCompatibilityVersion change here, this does not reset the awaitingTopologyChanges serverStatus metric.



 Comments   
Comment by Githook User [ 15/Apr/20 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-47435 Incrementing topologyVersion for FCV change must update awaitingTopologyChanges

(cherry picked from commit ab61e34c1ad83290e7bbf5a902f09042d80ec493)
Branch: v4.4
https://github.com/mongodb/mongo/commit/f1daa511e366f79cf95e301e03441b931299c2f1

Comment by Githook User [ 10/Apr/20 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-47435 Incrementing topologyVersion for FCV change must update awaitingTopologyChanges
Branch: master
https://github.com/mongodb/mongo/commit/ab61e34c1ad83290e7bbf5a902f09042d80ec493

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