turb opened a new issue, #30482: URL: https://github.com/apache/beam/issues/30482
### What happened? With Beam 0.54.0 Google Dataflow runner v2 has been enabled by default. While it works for us on jobs with little data size, when we launch on larger volumes, it fails with: ``` The job failed because a work item has failed 4 times. Look in previous log entries for the cause of each one of the 4 failures. If the logs only contain generic timeout errors related to accessing external resources, such as MongoDB, verify that the worker service account has permission to access the resource's subnetwork. For more information, see https://cloud.google.com/dataflow/docs/guides/common-errors. The work item was attempted on these workers: Root cause: Timed out waiting for an update from the worker. For more information, see https://cloud.google.com/dataflow/docs/guides/common-errors#worker-lost-contact. Worker ID: <SNIP>, <REPEATED> ``` Looking on worker logs, it seems something is wrong connecting/binding to a localhost port: ``` Failed to process element for bundle "process_bundle-<SNIP>" Exception while trying to handle InstructionRequest process_bundle-<SNIP> Failed to handle for url: "localhost:12371" <REPEATED> ``` Specifying `--experiments=disable_runner_v2` makes it work back. This is the same with all the jobs manipulating large data that we tested. ### 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 - [ ] 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 - [X] 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]
