You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Thomas Groh (JIRA)" <ji...@apache.org> on 2018/05/23 18:44:00 UTC

[jira] [Assigned] (BEAM-4145) Java SDK Harness populates control request headers with worker id

     [ https://issues.apache.org/jira/browse/BEAM-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Groh reassigned BEAM-4145:
---------------------------------

    Assignee: Thomas Groh  (was: Luke Cwik)

> Java SDK Harness populates control request headers with worker id
> -----------------------------------------------------------------
>
>                 Key: BEAM-4145
>                 URL: https://issues.apache.org/jira/browse/BEAM-4145
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-harness
>            Reporter: Ben Sidhom
>            Assignee: Thomas Groh
>            Priority: Minor
>
> Runner code needs to be able to identify incoming harness connections by the worker ids that it assigns to them on creation. This is currently done by the go boot code when the harness runs in a docker container. However, in-process harnesses never specify worker ids. This prevents in-process harnesses from being multiplexed by a runner (most likely the ULR and test code).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)