[SERVER-48623] chunk_history_window.js must be robust to stepdowns Created: 05/Jun/20  Updated: 29/Oct/23  Resolved: 10/Jun/20

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: sharding-csrs-stepdown-upkeep
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-06-15
Participants:
Linked BF Score: 17

 Description   

The queries to the config server to get history must ensure they are getting fresh data. This means either doing a majority read (though that will not work with EMRC=false), or awaiting replication on the config servers.



 Comments   
Comment by Githook User [ 10/Jun/20 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-48623: chunk_history_window.js must be robust to stepdowns
Branch: master
https://github.com/mongodb/mongo/commit/16008228ec1ce35dc7979c4ccc0af6dc9b375988

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