beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (BEAM-4145) Java SDK Harness populates control request headers with worker id
Date Thu, 21 Jun 2018 19:40:00 GMT

     [ https://issues.apache.org/jira/browse/BEAM-4145?focusedWorklogId=114435&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-114435
]

ASF GitHub Bot logged work on BEAM-4145:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Jun/18 19:39
            Start Date: 21/Jun/18 19:39
    Worklog Time Spent: 10m 
      Work Description: angoenka commented on issue #5680: [BEAM-4145] Populate the worker_id
metadata in the Java SDK Harness
URL: https://github.com/apache/beam/pull/5680#issuecomment-399219189
 
 
   Thanks!

----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 114435)
    Time Spent: 4h 40m  (was: 4.5h)

> 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: Eugene Kirpichov
>            Priority: Minor
>             Fix For: 2.6.0
>
>          Time Spent: 4h 40m
>  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
(v7.6.3#76005)

Mime
View raw message