You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2018/05/04 12:25:00 UTC

[jira] [Updated] (IGNITE-8421) ZkDistributedCollectDataFuture fails to delete future data in case of concurrent deletion

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

Dmitriy Pavlov updated IGNITE-8421:
-----------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> ZkDistributedCollectDataFuture fails to delete future data in case of concurrent deletion
> -----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8421
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8421
>             Project: Ignite
>          Issue Type: Bug
>          Components: zookeeper
>    Affects Versions: 2.5
>            Reporter: Sergey Chugunov
>            Assignee: Sergey Chugunov
>            Priority: Critical
>             Fix For: 2.6
>
>
> In *ZkDistributedCollectDataFuture#deleteFutureData* method KeeperException.NoNodeException may be thrown but the exception isn't critical in this context and doesn't require special handling (just logging is enough).
> However *deleteFutureData* relies on *ZookeeperClient#getChildren* which reacts on any exception (including NoNodeException) by killing current Ignite node.
> Another implementation of *ZookeeperClient#getChildren* is needed which tolerates NoNodeException.



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