[
https://issues.apache.org/jira/browse/HBASE-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529880#comment-13529880
]
Hudson commented on HBASE-5258:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #293 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/293/])
HBASE-5258 Move coprocessors set out of RegionLoad - Addendum (Sergey)
(Revision 1420521)
Result = FAILURE
tedyu :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
> Move coprocessors set out of RegionLoad
> ---------------------------------------
>
> Key: HBASE-5258
> URL: https://issues.apache.org/jira/browse/HBASE-5258
> Project: HBase
> Issue Type: Task
> Reporter: Ted Yu
> Assignee: Sergey Shelukhin
> Priority: Critical
> Fix For: 0.96.0, 0.94.4
>
> Attachments: HBASE-5258-094.patch, HBASE-5258-fix-on-top-of-v1.patch,
> HBASE-5258-v0.patch, HBASE-5258-v1.patch
>
>
> When I worked on HBASE-5256, I revisited the code related to Ser/De of
> coprocessors set in RegionLoad.
> I think the rationale for embedding coprocessors set is for maximum
> flexibility where each region can load different coprocessors.
> This flexibility is causing extra cost in the region server to Master
> communication and increasing the footprint of Master heap.
> Would HServerLoad be a better place for this set ?
> If required, region server should calculate disparity of loaded coprocessors
> among regions and send report through HServerLoad
--
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
