[
https://issues.apache.org/jira/browse/IGNITE-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550684#comment-16550684
]
Amelchev Nikita commented on IGNITE-8188:
-----------------------------------------
[~sergey-chugunov] I have investigated
_ZookeeperDiscoverySpiTest.testCommunicationFailureResolve_CachesInfo1_ test.
The fail reason is _getChildrenIfPathExists_ method throws NoNode exception.
This is in _deleteFutureData_ method where I have removed catching exception
after review.
I suggest revert it and resolve this problem in IGNITE-8189. I have updated
this PR.
What do you think?
> 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
> Fix For: 2.7
>
>
> 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)
