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

Luke Cwik updated BEAM-4149:
----------------------------
    Description: 
The SDK harness currently does nothing to populate control plane headers with 
the harness worker id. This id is necessary in order to identify harnesses when 
multiple are run from the same runner server.

Note that this affects the _Java_ harness specifically (e.g., when running a 
local process or in-memory harness). When the harness launched within the 
docker container, the go boot code takes care of setting this: 
https://github.com/apache/beam/blob/dffe50924f34d3cc994008703f01e802c99913d2/sdks/java/container/boot.go#L70

  was:
The Java SDK harness currently does nothing to populate control plane headers 
with the harness worker id. This id is necessary in order to identify harnesses 
when multiple are run from the same runner control server.

Note that this affects the _Java_ harness specifically (e.g., when running a 
local process or in-memory harness). When the harness launched within the 
docker container, the go boot code takes care of setting this: 
https://github.com/apache/beam/blob/dffe50924f34d3cc994008703f01e802c99913d2/sdks/java/container/boot.go#L70


> SDK Harness should populate worker id in RPC headers
> ----------------------------------------------------
>
>                 Key: BEAM-4149
>                 URL: https://issues.apache.org/jira/browse/BEAM-4149
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-harness
>            Reporter: Ben Sidhom
>            Assignee: Robert Bradshaw
>            Priority: Minor
>             Fix For: Not applicable
>
>
> The SDK harness currently does nothing to populate control plane headers with 
> the harness worker id. This id is necessary in order to identify harnesses 
> when multiple are run from the same runner server.
> Note that this affects the _Java_ harness specifically (e.g., when running a 
> local process or in-memory harness). When the harness launched within the 
> docker container, the go boot code takes care of setting this: 
> https://github.com/apache/beam/blob/dffe50924f34d3cc994008703f01e802c99913d2/sdks/java/container/boot.go#L70



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

Reply via email to