Repository navigation
Conversation
The agent removes the instance's ephemeral access config, then polls that operation with zoneOperations.wait on the pooled HTTP/2 connection to the Compute API. That connection was opened while the instance still egressed through the ephemeral address, so it stops carrying traffic as soon as the address is gone, without any error. The Google API client only probes a silent connection after 31 s (transport/http ReadIdleTimeout), so every node start spent ~31 s idle before the existing retry re-issued the request on a fresh connection, while the operation itself completed in 6-8 s. Build the Compute client on a transport with aggressive HTTP/2 health checks (PING after 2 s of silence, 2 s to answer) so a dead connection is dropped in about 4 s and the operation wait retries right away. Log the transport retry at debug level so the delay is visible. Fixes doitintl#180
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The agent removes the instance's ephemeral access config, then polls that operation with zoneOperations.wait on the pooled HTTP/2 connection to the Compute API. That connection was opened while the instance still egressed through the ephemeral address, so it stops carrying traffic as soon as the address is gone, without any error. The Google API client only probes a silent connection after 31 s (transport/http ReadIdleTimeout), so every node start spent ~31 s idle before the existing retry re-issued the request on a fresh connection, while the operation itself completed in 6-8 s.
Build the Compute client on a transport with aggressive HTTP/2 health checks (PING after 2 s of silence, 2 s to answer) so a dead connection is dropped in about 4 s and the operation wait retries right away. Log the transport retry at debug level so the delay is visible.
Fixes #180