[DOCS-15223] [Server] Confusing Flow Control Description Created: 08/Apr/22 Updated: 22/Jan/24 |
|
| Status: | Backlog |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Przemek Malkowski | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | backlog, proactive, replication, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 43 weeks, 5 days ago |
| Epic Link: | DOCSP-11702 |
| Description |
|
In the documentation: https://www.mongodb.com/docs/manual/tutorial/troubleshoot-replica-sets/#flow-control we can read:
However, flow control goal is to really throttle writes when there is certain replication lag. Also, in https://www.mongodb.com/docs/manual/reference/parameters/#mongodb-parameter-param.flowControlTargetLagSeconds we can read:
So I think it is clear that it is about write concern and not read concern? Besides, before version 4.4 it was even impossible to set read concern globally: https://www.mongodb.com/docs/manual/reference/read-concern/
|