[ https://issues.apache.org/jira/browse/FLINK-8984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-8984. ----------------------------------- Resolution: Fixed master: 91707e35d39a1b9c11448f21eafc27f0fd949370 1.5: 23005ee1f653a3fcddac0f710d56f3e0d6157a48 > 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)