-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Storage NYC 2019-05-20, Execution Team 2019-06-03
-
0
Correctness testing for the most part does not engage Flow Control throttling behavior because majority committed replication lag is minimal. A new variant should be added where Flow Control is certain to be executed in order to test potential interactions of various write operations with Flow Control.
- depends on
-
SERVER-41345 FlowControlRefresher can be shut down while there are operations needing flow control tickets
- Closed