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 2018/03/21 22:41:00 UTC

[jira] [Updated] (FLINK-8984) Disabling credit based flow control deadlocks Flink on checkpoint

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

Chesnay Schepler updated FLINK-8984:
------------------------------------
    Component/s: Configuration

> Disabling credit based flow control deadlocks Flink on checkpoint
> -----------------------------------------------------------------
>
>                 Key: FLINK-8984
>                 URL: https://issues.apache.org/jira/browse/FLINK-8984
>             Project: Flink
>          Issue Type: Bug
>          Components: Configuration, Network
>    Affects Versions: 1.5.0
>            Reporter: Piotr Nowojski
>            Assignee: Piotr Nowojski
>            Priority: Blocker
>             Fix For: 1.5.0
>
>
> This is configuration issue. There are two options: 
> taskmanager.network.credit-based-flow-control.enabled
> and
> taskmanager.exactly-once.blocking.data.enabled
> If we disable first one, but remain default value for the second one deadlocks will occur. I think we can safely drop the second config value altogether and always use blocking BarrierBuffer for credit based flow control and spilling BarrierBuffer for non credit based flow control.
> cc [~zjwang]



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