You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "YeT (Jira)" <ji...@apache.org> on 2022/01/21 23:55:00 UTC
[jira] [Commented] (BEAM-9082) "Socket closed" Spurious GRPC errors in Flink/Spark runner log output
[ https://issues.apache.org/jira/browse/BEAM-9082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480299#comment-17480299 ]
YeT commented on BEAM-9082:
---------------------------
I've seen this issue when running beam flink runner in k8s. It's not at the end of job but in the middle, causing job to fail early.
Sample log
{code:java}
2022-01-21 22:54:30,637 ERROR /usr/local/lib/python3.8/site-packages/apache_beam/runners/worker/sdk_worker_main.py:156 [] - Python sdk harness failed: Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/apache_beam/runners/worker/sdk_worker_main.py", line 153, in main sdk_harness.run() File "/usr/local/lib/python3.8/site-packages/apache_beam/runners/worker/sdk_worker.py", line 234, in run for work_request in self._control_stub.Control(get_responses()): File "/usr/local/lib/python3.8/site-packages/grpc/_channel.py", line 426, in __next__ return self._next() File "/usr/local/lib/python3.8/site-packages/grpc/_channel.py", line 826, in _next raise selfgrpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with: status = StatusCode.UNAVAILABLE details = "Socket closed" debug_error_string = "{"created":"@1642805670.633834025","description":"Error received from peer ipv4:127.0.0.1:35271","file":"src/core/lib/surface/call.cc","file_line":1074,"grpc_message":"Socket closed","grpc_status":14}" {code}
> "Socket closed" Spurious GRPC errors in Flink/Spark runner log output
> ---------------------------------------------------------------------
>
> Key: BEAM-9082
> URL: https://issues.apache.org/jira/browse/BEAM-9082
> Project: Beam
> Issue Type: Sub-task
> Components: runner-flink, runner-spark
> Reporter: Kyle Weaver
> Priority: P3
> Labels: portability-flink, portability-spark
>
> We often see "Socket closed" errors on job shutdown, even though the pipeline has finished successfully. They are misleading and especially annoying at scale.
> ERROR:root:Failed to read inputs in the data plane.
> ...
> grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
> status = StatusCode.UNAVAILABLE
> details = "Socket closed"
> debug_error_string = "{"created":"@1578597616.309419460","description":"Error received from peer ipv6:[::1]:37211","file":"src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Socket closed","grpc_status":14}"
--
This message was sent by Atlassian Jira
(v8.20.1#820001)