You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:07:08 UTC

[jira] [Commented] (BEAM-10231) Connecting data channel blocks getting ProcessBundleResponse

    [ https://issues.apache.org/jira/browse/BEAM-10231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174481#comment-17174481 ] 

Beam JIRA Bot commented on BEAM-10231:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Connecting data channel blocks getting ProcessBundleResponse
> ------------------------------------------------------------
>
>                 Key: BEAM-10231
>                 URL: https://issues.apache.org/jira/browse/BEAM-10231
>             Project: Beam
>          Issue Type: Bug
>          Components: java-fn-execution
>            Reporter: Boyuan Zhang
>            Priority: P2
>              Labels: stale-P2
>
> In Java runner harness shared library code, the ActivateBundle is returned only when data channel is connected: https://github.com/apache/beam/blob/master/runners/java-fn-execution/src/main/java/org/apache/beam/runners/fnexecution/control/SdkHarnessClient.java#L268-L283. But the SDK can fail the bundle and sent the ProcessBundleResponse with error before registering data channel, e.g, throwing exceptions when creating FnApiDoFnRunner. This results in the runner gets timeout error(https://github.com/apache/beam/blob/master/runners/java-fn-execution/src/main/java/org/apache/beam/runners/fnexecution/data/GrpcDataService.java#L182) and doesn't populate possible error in ProcessBundleResponse. We need to find a way to abort sooner and populate correct error message.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)