[
https://issues.apache.org/jira/browse/BEAM-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635934#comment-16635934
]
Thomas Weise commented on BEAM-5520:
------------------------------------
An new portable pipeline option was added to support this.
The default behavior can also be controlled at the job server level. To enable
separate sdk process for each subtask:
{code:java}
java -jar
runners/flink/job-server/build/libs/beam-runners-flink_2.11-job-server-2.8.0-SNAPSHOT.jar
--sdk-worker-parallelism=stage{code}
> 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
> Fix For: 2.8.0
>
> Time Spent: 2.5h
> 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)
