You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Dian Fu (Jira)" <ji...@apache.org> on 2020/08/12 11:40:00 UTC

[jira] [Comment Edited] (FLINK-18738) Revisit resource management model for python processes.

    [ https://issues.apache.org/jira/browse/FLINK-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176272#comment-17176272 ] 

Dian Fu edited comment on FLINK-18738 at 8/12/20, 11:39 AM:
------------------------------------------------------------

Thanks [~sewen] for the information. I think this is a good solution and it should work. My previous concern that we'd better not move the logic of launching Python Process to the runtime module will also not be a problem any more.


was (Author: dian.fu):
Thanks [~sewen] for the information. I think this is a good solution and it should work.

> 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)