[
https://issues.apache.org/jira/browse/HBASE-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484419#comment-13484419
]
Hudson commented on HBASE-6977:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #236 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/236/])
HBASE-6977 Multithread processing ZK assignment events (Revision 1402226)
Result = FAILURE
jxiang :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/HRegionInfo.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/OfflineCallback.java
> Multithread processing ZK assignment events
> -------------------------------------------
>
> Key: HBASE-6977
> URL: https://issues.apache.org/jira/browse/HBASE-6977
> Project: HBase
> Issue Type: Improvement
> Components: Region Assignment
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: trunk-6977_v1.patch, trunk-6977_v2-1.patch,
> trunk-6977_v3.patch
>
>
> Related to HBASE-6976 and HBASE-6611. ZK events processing is a bottle neck
> for assignments, since there is only one ZK event thread. If we can use
> multiple threads, it should be better.
> With multiple threads, the order of events could be messed up. However, if we
> pass all events related to one region always to the same worker thread, the
> order should be kept.
> We need to play with it and find out how much performance imrovement we can
> get.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
