scwhittle opened a new issue, #29661: URL: https://github.com/apache/beam/issues/29661
### What happened? There is a connection timeout set for the read from the metadata server in this function. However there is not a read timeout set. https://blog.cloudflare.com/when-tcp-sockets-refuse-to-die/ indicates that this can result in ~15 minutes of delay. Beyond setting this timeout we could also perhaps just read this data from the gce metadata server once and cache it. ### Issue Priority Priority: 2 (default / most bugs should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [X] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
