You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Daniel Gomes (Jira)" <ji...@apache.org> on 2020/05/28 13:48: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=17118690#comment-17118690 ]
Daniel Gomes commented on BEAM-9082:
------------------------------------
Seeing message 1. using Google Dataflow and everything also seems to work fine. Using apache-beam[gcp]==2.21.0
> "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
> Assignee: Kyle Weaver
> Priority: P2
> 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.3.4#803005)