You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7efbfbd
Browse filesBrowse the repository at this point in the historyBrowse files
Calls to the render service carry nothing on the connection for minutes at
a time while the service works on the answer. Network equipment between the
two drops a connection that quiet and tells neither end, so the answer has
nowhere to go. The client then waits for an answer that cannot arrive, with
no read timeout to end the wait and nothing on the connection to tell it the
other end is gone.
Every request now goes through a session whose connections carry keepalive.
The probes put a packet on the connection often enough to keep it, and they
end the connection when the other end has really gone, which the retry logic
already treats as a network error.
A render of the dashboard waited one hour and fifty-six minutes this way.
The service had answered it with 200 after six and a half minutes.
0 commit comments