beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-4145) Java SDK Harness populates control request headers with worker id
Date Wed, 23 May 2018 18:46:00 GMT


ASF GitHub Bot logged work on BEAM-4145:

                Author: ASF GitHub Bot
            Created on: 23/May/18 18:45
            Start Date: 23/May/18 18:45
    Worklog Time Spent: 10m 
      Work Description: tgroh opened a new pull request #5456: [BEAM-4145] Populate the worker_id
metadata in the Java SDK Harness
   The ID is required for any control service with multiple clients, which is the general
   Enable `ManagedChannelFactory` implementations to register interceptors on all of the
   created channels.
   Add an interceptor which attaches the ID to the metadata. Use this interceptor in the 
   Sdk Harness Control Client.
   Populate the ID passed via the container contract in the boot go code.
   Follow this checklist to help us incorporate your contribution quickly and easily:
    - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`,
where you replace `BEAM-XXX` with the appropriate JIRA issue, if applicable. This will automatically
link the pull request to the issue.
    - [ ] If this contribution is large, please file an Apache [Individual Contributor License
   It will help us expedite review of your Pull Request if you tag someone (e.g. `@username`)
to look at it.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

            Worklog Id:     (was: 105258)
            Time Spent: 10m
    Remaining Estimate: 0h

> Java SDK Harness populates control request headers with worker id
> -----------------------------------------------------------------
>                 Key: BEAM-4145
>                 URL:
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-harness
>            Reporter: Ben Sidhom
>            Assignee: Thomas Groh
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
> 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

View raw message