[
https://issues.apache.org/jira/browse/BEAM-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459052#comment-16459052
]
Ben Sidhom commented on BEAM-4149:
----------------------------------
The workaround is technically fine for now, but it will break as soon as we
have multiple concurrent environments and need to run test cases for this. More
importantly, having an empty worker id makes it harder to debug test and
runtime failures due to SDK/runner communication issues.
> Java SDK Harness should populate worker id in control plane 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: Luke Cwik
> Priority: Minor
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
