flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8984) Disabling credit based flow control deadlocks Flink on checkpoint
Date Wed, 21 Mar 2018 22:41:00 GMT

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

ASF GitHub Bot commented on FLINK-8984:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/flink/pull/5708


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

Mime
View raw message