[DISPATCH-2002] Adaptor flow control does not work across multi-router networks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.15.0
• Fix Version/s: 1.16.0
• Component/s: Protocol Adaptors
• Assignee: Unassigned
• Reporter: Charles E. Rolke
• Created: 15/Mar/21 22:02
• Updated: 14/May/21 14:10
• Resolved: 26/Mar/21 20:57

Description

From TCP Adaptor perspective:

• Single-router flow control works just fine
• Multi-router flow control presents unlimited buffering to the ingress TCP connection

In a two-router test case with TCP Adaptor tunneling iperf3 between the routers the ingress router memory grows to 4Gb in one minute.

This happens with or without DISPATCH-2001 streaming link priority setting.

Streaming links tunneling TCP traffic need to provide back pressure to the ingress raw connection.

Issue Links

• depends upon: DISPATCH-2006 Set stricter default maxSessionFrames to avoid router OOM under load
• duplicates: DISPATCH-2006 Set stricter default maxSessionFrames to avoid router OOM under load