You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/11/15 19:59:58 UTC

[jira] [Created] (FLINK-5073) ZooKeeperCompleteCheckpointStore executes blocking delete operation in ZooKeeper client thread

Till Rohrmann created FLINK-5073:
------------------------------------

             Summary: 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.1.3, 1.2.0
            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)