[BEAM-4145] Java SDK Harness populates control request headers with worker id

• Type: New Feature
• Status: Resolved
• Priority: P3
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Component/s: sdk-java-harness
• Labels: Done
• Assignee: Eugene Kirpichov
• Reporter: Ben Sidhom
• Created: 19/Apr/18 21:28
• Updated: 06/Oct/20 21:56
• Resolved: 21/Jun/18 19:39

Description

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).

Issue Links

• is depended upon by: BEAM-3327 Add abstractions to manage Environment Instance lifecycles.
• is duplicated by: BEAM-4149 SDK Harness should populate worker id in RPC headers
• links to: GitHub Pull Request #5456
• links to: GitHub Pull Request #5680