[
https://issues.apache.org/jira/browse/BEAM-6754?focusedWorklogId=208174&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-208174
]
ASF GitHub Bot logged work on BEAM-6754:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Mar/19 00:01
Start Date: 06/Mar/19 00:01
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-469909606
> Agree we should use multiprocessing. We should also consider making this
configurable (especially as loopback is used for lightweight testing.)
Multiprocessing doesn't seem to work with grpc.
Making it configurable seems right. Using experimental flag which defaults
to subprocess.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 208174)
Time Spent: 2h 10m (was: 2h)
> 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 10m
> 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)
