[SERVER-39667] Ensure flow control mechanism only runs when read concern majority is enabled Created: 19/Feb/19  Updated: 29/Oct/23  Resolved: 28/Mar/19

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

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-39494 Clean up chosen Flow Control POC Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-04-08
Participants:

 Description   

Throttling writes on the primary in response to majority committed replication lag poses the risk that PSA replica sets stall writes for extended periods of time if the data-bearing secondary goes down. To cope with this risk, the flow control mechanism should only be enabled when read concern majority is enabled. PSA replica sets with read concern majority enabled are not a supported configuration.



 Comments   
Comment by Githook User [ 28/Mar/19 ]

Author:

{'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}

Message: SERVER-39667: Locally disable flow control when majority reads are off.
Branch: master
https://github.com/mongodb/mongo/commit/f2f422d92b639edba0a10d40a43803723cb15baf

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