[
https://issues.apache.org/jira/browse/HBASE-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398282#comment-13398282
]
nkeywal commented on HBASE-6058:
--------------------------------
All the tests I made with multi were successful. But they were only tests :-).
Note it's not totally trivial to use it in bulk assignment, because we have two
levels of asynchronous calls (the callback calls another asynchronous
function). So supporting both ZK version (with & without multi) would be
looking for issue imho.
And fixing ZOOKEEPER-1381 would help on deployment, today we hang if we call
multi on a 3.3 ZK server...
Anyway, I will redo some perfo tests to see where we are now with the current
implementation.
> Use ZK 3.4 API 'multi' in bulk assignment
> -----------------------------------------
>
> Key: HBASE-6058
> URL: https://issues.apache.org/jira/browse/HBASE-6058
> Project: HBase
> Issue Type: Improvement
> Components: master, zookeeper
> Affects Versions: 0.96.0
> Reporter: nkeywal
> Assignee: nkeywal
> Priority: Minor
>
> We use async API today. This is already much much faster than the sync API.
> Still, it makes sense to use the 'multi' function: this will decrease the
> network & zookeeper load at startup/rolling restart.
> On a 500 nodes cluster, we see 3 that 3 seconds are spent on updating ZK per
> bulk assignment. This should cut it in half (+ the benefits on the network/zk
> load).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
