[
https://issues.apache.org/jira/browse/FLINK-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176150#comment-17176150
]
Till Rohrmann commented on FLINK-18738:
---------------------------------------
I like the idea of the {{ExternalExecutionBackend}} as it gives us great
flexibility. We could start with a {{PerSlotPythonExecutionBackend}} which
requires Flink managed memory and starts a Python process per slot as you
described it.
If it should become necessary to run the language execution outside of the
Flink process, then one could have an {{ExternalExecutionBackend}} which does
not consume managed memory and delegates the execution to some external service
(potentially co-located to the Flink process or not).
> Revisit resource management model for python processes.
> -------------------------------------------------------
>
> Key: FLINK-18738
> URL: https://issues.apache.org/jira/browse/FLINK-18738
> Project: Flink
> Issue Type: Task
> Components: API / Python, Runtime / Coordination
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Major
> Fix For: 1.12.0
>
>
> This ticket is for tracking the effort towards a proper long-term resource
> management model for python processes.
> In FLINK-17923, we run into problems due to python processes are not well
> integrate with the task manager resource management mechanism. A temporal
> workaround has been merged for release-1.11.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
