[SERVER-45110] Flow control lag check can report isLagged as false even though lag is large if operations are sparse Created: 12/Dec/19 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
In instances where few operations cause large replication lag (e.g., due to an unresponsive secondary), Flow Control's lag check can report isLagged to be false. This could be due to a bug in _approximateOpsBetween. The work for this ticket should be to investigate the behavior of the isLagged check in this scenario. |
| Comments |
| Comment by Connie Chen [ 01/Feb/21 ] |
|
If there are very few operations then flow control lag may not report reliably. Closing this as "Works as designed." Filed DOCSP-14267 to update documentation accordingly. |