[
https://issues.apache.org/jira/browse/HBASE-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511077#comment-13511077
]
Andrew Purtell commented on HBASE-5258:
---------------------------------------
bq. I don't see getting coprocessors from RegionLoad actually being used
anywhere.
+1
I searched for users of RegionLoad#getCoprocessors and didn't find any either.
Originally we put this in so the loaded coprocessors on a region would show up
next to other region information in the master UI. Unfortunately the result was
not that useful, just clutter.
> 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
> Priority: Critical
>
> 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
