-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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.
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
Beam Core IO: WriteFiles stuck #21492
Comments
I believe this is google/conscrypt#864 and will be addressed once GoogleCloudDataproc/hadoop-connectors#865 is in a 2.2.x release and beam depedencies are so google_cloud_bigdataoss_version includes this version. In the meantime this can be avoided by disabling conscrypt |
The fix should be in the 2.2.8 hadoop-connectors release, no ETA yet |
.take-issue |
Hello @scwhittle . We have released GCS connector 2.2.8 containing the fix for Conscrypt socket hangs. https://mvnrepository.com/artifact/com.google.cloud.bigdataoss/gcs-connector/hadoop3-2.2.8 |
Thanks Chris! #23300 to update Beam |
.reopen-issue |
The reason for rollbacks here ( |
This should be fixed by upgrade to 2.2.16 or higher above |
In our pipeline, workers are sometimes stuck at step WriteShardsIntoTempFiles. We believe this happens when GCS fails to respond for more than 10 minutes and Google's VPC cuts the connection. The Java code will just hang forever because it's waiting on FIN or RST from the peer.
Environment: Java 8, Beam 2.34/2.35, Dataflow runner.
See below for relevant information from logs, threads, netstat.
Log snippet:
Threads snippet:
Netstat snippet:
Imported from Jira BEAM-14067. Original Jira may contain additional context.
Reported by: yianni.
The text was updated successfully, but these errors were encountered: