flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-5073) ZooKeeperCompleteCheckpointStore executes blocking delete operation in ZooKeeper client thread
Date Tue, 22 Nov 2016 22:11:58 GMT

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

Till Rohrmann closed FLINK-5073.
--------------------------------
    Resolution: Fixed

Fixed in 1.2 via 3fb92d8687f03c1fac8b87396b2b5a7ff29f6dd6
Fixed in 1.1.4 via f2e4c193e1fb6b0cf26861bc01c2f3d6bcd4d8f6

> ZooKeeperCompleteCheckpointStore executes blocking delete operation in ZooKeeper client
thread
> ----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-5073
>                 URL: https://issues.apache.org/jira/browse/FLINK-5073
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination
>    Affects Versions: 1.2.0, 1.1.3
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>             Fix For: 1.2.0, 1.1.4
>
>
> When deleting completed checkpoints from the {{ZooKeeperCompletedCheckpointStore}}, one
first tries to delete the meta state handle from ZooKeeper and then deletes the actual checkpoint
in a callback from the delete operation. This callback is executed by the ZooKeeper client's
main thread which is problematic, because it blocks the ZooKeeper client. If a delete operation
takes longer than it takes to complete a checkpoint, then it might even happen that delete
operations of outdated checkpoints are piling up because they are effectively executed sequentially.
> I propose to execute the delete operations by a dedicated {{Executor}} so that we keep
the client's main thread free to do ZooKeeper related work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message