[
https://issues.apache.org/jira/browse/HBASE-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191589#comment-13191589
]
Andrew Purtell commented on HBASE-5258:
---------------------------------------
bq. This flexibility is causing extra cost in the region server to Master
communication and increasing the footprint of Master heap.
No doubt it is redundant to have each region report a coprocessor given how the
framework currently works: All regions for a table will have an identical set
of coprocessors loaded, or there is something bad happening.
bq. Would HServerLoad be a better place for this set ?
I have no major objection.
However, maybe we want a way to know if something bad happened on a region and
a coprocessor on it went away? One could comb logs but that is hardly a
convenient way to get online state.
> Move coprocessors set out of RegionLoad
> ---------------------------------------
>
> Key: HBASE-5258
> URL: https://issues.apache.org/jira/browse/HBASE-5258
> Project: HBase
> Issue Type: Task
> Reporter: Zhihong Yu
>
> 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 ?
--
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
