[SERVER-15858] Don't block writes in stepDown unless you believe there is at least 1 node within 10 seconds of your optime Created: 29/Oct/14  Updated: 10/Dec/14  Resolved: 29/Oct/14

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

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-14251 Change shutdown/stepdown to block wri... Closed
Participants:

 Comments   
Comment by Spencer Brody (Inactive) [ 29/Oct/14 ]

We decided not to do this as there's no way to really do it cleanly in our current implementation. Instead we're going to make the time we wait for replication to catch up configurable (SERVER-15861) along with making sure that when we're blocking writes to allow secondaries to catch up, we don't accidentally block read access to the oplog.

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