Skip to content

[8.17] Mention zero-window state in networking docs (#124969) #124971

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 16, 2025
Merged

[8.17] Mention zero-window state in networking docs (#124969) #124971

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/reference/modules/transport.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,6 +195,15 @@ setting `transport.ping_schedule` if keepalives cannot be configured. Devices
which drop connections when they reach a certain age are a common source of
problems to {es} clusters, and must not be used.

If an {es} node is temporarily unable to handle network traffic it may stop
reading data from the network and advertise a zero-length TCP window to its
peers so that they pause the transmission of data to the unavailable node. This
is the standard backpressure mechanism built into TCP. When the node becomes
available again, it will resume reading from the network. Configure your
network to permit TCP connections to exist in this paused state without
disruption. Do not impose any limit on the length of time that a connection may
remain in this paused state.

For information about troubleshooting unexpected network disconnections, see
<<troubleshooting-unstable-cluster-network>>.

Expand Down