[
https://issues.apache.org/jira/browse/IGNITE-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524943#comment-16524943
]
Sergey Chugunov commented on IGNITE-8188:
-----------------------------------------
[~NSAmelchev],
Both your suggestions make sense to me.
I believe that methods called *deleteAll* or *createAll* should do all
necessary actions to perform requested actions no matters in fast way (using
multi) or by fall-back to one-by-one operations.
Lets try to implement these methods in the following way:
# they should do max size checks for batching operations and split batches into
smaller pieces if necessary;
# if batching operation fails for any reason, fallback to one-by-one mode
should happen right within these methods.
> Batching operations should perform check for ZooKeeper request max size
> -----------------------------------------------------------------------
>
> Key: IGNITE-8188
> URL: https://issues.apache.org/jira/browse/IGNITE-8188
> Project: Ignite
> Issue Type: Improvement
> Components: zookeeper
> Reporter: Sergey Chugunov
> Assignee: Amelchev Nikita
> Priority: Major
>
> As ZooKeeper documentation
> [says|https://zookeeper.apache.org/doc/r3.4.3/api/org/apache/zookeeper/ZooKeeper.html#multi(java.lang.Iterable)]
> batching *multi* operation has a limit for size of a single request.
> ZookeeperClient batching methods *createAll* and *deleteAll* should check
> this limit and fall back to execute operations one by one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
