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-5520) Flink runner per operator SDK harness option
Date Sun, 30 Sep 2018 23:39:00 GMT

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

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

                Author: ASF GitHub Bot
            Created on: 30/Sep/18 23:38
            Start Date: 30/Sep/18 23:38
    Worklog Time Spent: 10m 
      Work Description: tweise commented on issue #6524:  [BEAM-5520] Flink pipeline option
to run SDK harness per subtask.
URL: https://github.com/apache/beam/pull/6524#issuecomment-425761022
 
 
   @mxm this will also take care of https://issues.apache.org/jira/browse/BEAM-5516

----------------------------------------------------------------
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: 149870)
    Time Spent: 40m  (was: 0.5h)

> Flink runner per operator SDK harness option
> --------------------------------------------
>
>                 Key: BEAM-5520
>                 URL: https://issues.apache.org/jira/browse/BEAM-5520
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
>            Priority: Major
>              Labels: portability, portability-flink
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> For streaming pipelines, the runner currently uses a single SDK harness process for all
subtasks of a job that get deployed on the same task manager. In common deployments with 16
or more tasks slots, many executable stage operators all use the same SDK harness process.
To scale, we need an option to run separate harness processes per subtask.
>    



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message