High tunnel timeout in haproxy may leave connections in FIN_WAIT
Bug #1862684 reported by
Radosław Piliszek
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
Triaged
|
Medium
|
Unassigned | ||
| Rocky |
Triaged
|
Medium
|
Unassigned | ||
| Stein |
Triaged
|
Medium
|
Unassigned | ||
| Train |
Triaged
|
Medium
|
Unassigned | ||
| Ussuri |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Re: https:/
"""
Since [tunnel] timeout is usually used in conjunction with long-lived connections,
it usually is a good idea to also set "timeout client-fin" to handle the
situation where a client suddenly disappears from the net and does not
acknowledge a close, or sends a shutdown and does not acknowledge pending
data anymore. This can happen in lossy networks where firewalls are present,
and is detected by the presence of large amounts of sessions in a FIN_WAIT
state.
"""
To post a comment you must log in.
