[jira] [Work logged] (BEAM-5520) Flink runner per operator SDK harness option

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 01/Oct/18 13:53
            Start Date: 01/Oct/18 13:53
    Worklog Time Spent: 10m 
      Work Description: mxm commented on a change in pull request #6524:  [BEAM-5520] Flink pipeline option to run SDK harness per subtask.
URL: https://github.com/apache/beam/pull/6524#discussion_r221614851
 
 

 ##########
 File path: runners/flink/src/main/java/org/apache/beam/runners/flink/translation/functions/FlinkExecutableStageFunction.java
 ##########
 @@ -141,8 +144,17 @@ public void mapPartition(
 
   @Override
   public void close() throws Exception {
-    try (AutoCloseable bundleFactoryCloser = stageBundleFactory) {}
-    try (AutoCloseable closable = stageContext) {}
+    // close may be called multiple times when an exception is thrown
 
 Review comment:
   Should we synchronize close then? The calls could be interleaved.

----------------------------------------------------------------
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: 150042)
    Time Spent: 1h 20m  (was: 1h 10m)

> 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: 1h 20m
>  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)