[
https://issues.apache.org/jira/browse/BEAM-6754?focusedWorklogId=209672&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-209672
]
ASF GitHub Bot logged work on BEAM-6754:
----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Mar/19 17:09
Start Date: 07/Mar/19 17:09
Worklog Time Spent: 10m
Work Description: robertwb commented on issue #7984: [BEAM-6754] Use
subprocess instead of threads in loopback environment
URL: https://github.com/apache/beam/pull/7984#issuecomment-470611499
Fair enough.
I still think it should be opt-in, as the primary advantage of loopback is
that it's as lightweight as possible.
On Wed, Mar 6, 2019 at 10:04 PM Ankur <[email protected]> wrote:
> 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.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/beam/pull/7984#issuecomment-470275831>, or mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AAdqgef2o35zqdMrZ2iPwnoafiylf8a4ks5vUC1egaJpZM4bdR-U>
> .
>
----------------------------------------------------------------
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: 209672)
Time Spent: 2h 40m (was: 2.5h)
> 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: 2h 40m
> 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)
