[
https://issues.apache.org/jira/browse/IGNITE-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582154#comment-16582154
]
Amelchev Nikita commented on IGNITE-8189:
-----------------------------------------
I have implemented improving batching in *deleteFutureData* and
*cleanupPreviousClusterData* methods.
See more detail in [PR description|https://github.com/apache/ignite/pull/4537].
[Tests|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&tab=projectOverview&branch_IgniteTests24Java8=pull%2F4537%2Fhead]
[ l|http://example.com]l/]ook good.
[~Jokser] or [~sergey-chugunov] could you review, please?
> 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
> Fix For: 2.7
>
>
> 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)
