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

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/06/29 12:48:00 UTC

[jira] [Updated] (FLINK-4430) Prevent BLOCKING partition data loss when task is finished

     [ https://issues.apache.org/jira/browse/FLINK-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-4430:
---------------------------------
    Summary: Prevent BLOCKING partition data loss when task is finished  (was: prevent BLOCKING partition data loss when task is finished)

> Prevent BLOCKING partition data loss when task is finished
> ----------------------------------------------------------
>
>                 Key: FLINK-4430
>                 URL: https://issues.apache.org/jira/browse/FLINK-4430
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Cluster Management
>            Reporter: Kurt Young
>            Assignee: zhuhaifeng
>              Labels: flip-6
>
> When we have a BLOCKING result partition type, the data is actually holded by TaskManager, not the slot. When we finish the produce task, we will mark this task finished and try to release the slot. Under the new architecture, with yarn or mesos mode, releasing slot may trigger releasing the container, so the TaskManager will be terminated, thus the result data is lost. We should introduce some mechanism to prevent this from happening.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)