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

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/06/26 14:49:00 UTC

[jira] [Closed] (FLINK-12993) Rework forceReleaseOnConsumptionFlag to be JM internal concept

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

Chesnay Schepler closed FLINK-12993.
------------------------------------
    Resolution: Fixed

master: d2247598897b273dbadfda0ab4c05e3678807ff5

> Rework forceReleaseOnConsumptionFlag to be JM internal concept
> --------------------------------------------------------------
>
>                 Key: FLINK-12993
>                 URL: https://issues.apache.org/jira/browse/FLINK-12993
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Network
>    Affects Versions: 1.9.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The forceReleaseOnConsumption flag is currently evaluated on the TM side deep in the netty shuffle environment.
> We can rework this to be evaluated on the JM side, by setting the releasedOnConsumption flag in the ResultPartitionDeploymentDescriptor appropriately.
> This consolidates the setting of releasedOnConsumption on the JM, and also allows this to be used with other shuffle service implementations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)