[
https://issues.apache.org/jira/browse/IGNITE-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579725#comment-16579725
]
ASF GitHub Bot commented on IGNITE-8189:
----------------------------------------
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/4537
IGNITE-8189
Improve batching deleteAll operations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite ignite-8189
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4537.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4537
----
commit 422102ce298733bde2f10af26a4020c2710347e6
Author: NSAmelchev <nsamelchev@...>
Date: 2018-08-14T12:16:19Z
Draft implementation
----
> Improve ZkDistributedCollectDataFuture#deleteFutureData implementation
> ----------------------------------------------------------------------
>
> Key: IGNITE-8189
> URL: https://issues.apache.org/jira/browse/IGNITE-8189
> Project: Ignite
> Issue Type: Improvement
> Components: zookeeper
> Reporter: Sergey Chugunov
> Assignee: Amelchev Nikita
> Priority: Major
>
> Three issues need to be improved in implementation:
> * two more deleteIfExists methods within the *deleteFutureData* to be
> included in batching *deleteAll* operation;
> * if request exceeds ZooKeeper max size limit fallback to one-by-one deletion
> should be used (related ticket IGNITE-8188);
> * ZookeeperClient#deleteAll implementation may throw NoNodeException is case
> of concurrent operation removing the same nodes, in this case fallback to
> one-by-one deletion should be used too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
