[SERVER-52681] Scanning RSM should log when a reply is considered stale by the config version or election id Created: 07/Nov/20  Updated: 18/Nov/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: 4.2.9
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Lamont Nelson Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: bkp, sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Cluster Scalability
Backport Requested:
v5.0
Participants:
Case:
Story Points: 1

 Description   

In HELP-19787 the customer could not reach the primary of it's replica set due to following a subset of the instructions here. This was due to the election id staleness checks here. We can log this information to prevent confusion in the future.

In versions 4.4+, this affects the scanning_replica_set_monitor.cpp instead of replica_set_monitor.cpp.


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