[
https://issues.apache.org/jira/browse/BEAM-6754?focusedWorklogId=209153&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-209153
]
ASF GitHub Bot logged work on BEAM-6754:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Mar/19 21:04
Start Date: 06/Mar/19 21:04
Worklog Time Spent: 10m
Work Description: angoenka commented on issue #7984: [BEAM-6754] Use
subprocess instead of threads in loopback environment
URL: https://github.com/apache/beam/pull/7984#issuecomment-470275831
> I don't think the default should be subprocess. More futureproof might be
to have a separate numprocesses setting which if 1 would use a threadpool and
for > 1 use subprocess.
Interesting idea. I think that changing the behavior based on number of
process (1 and >1) might be bit unintuitive for the user. Also even with 1
process, multiple threads will be created if runner request for multiple
SDKHarness.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 209153)
Time Spent: 2.5h (was: 2h 20m)
> Support multi core machines for python pipeline on flink for loopback
> environment
> ---------------------------------------------------------------------------------
>
> Key: BEAM-6754
> URL: https://issues.apache.org/jira/browse/BEAM-6754
> Project: Beam
> Issue Type: Task
> Components: runner-core, runner-flink
> Reporter: Ankur Goenka
> Assignee: Ankur Goenka
> Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Loopbck worker is shared across multiple taskmanagers on a single machine. We
> should support starting multiple process in loopback worker based on number
> of cores.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
