[
https://issues.apache.org/jira/browse/HBASE-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527535#comment-13527535
]
Andrew Purtell commented on HBASE-7310:
---------------------------------------
Maybe this is useful in the general case but the specific reason given here
seems flawed. We should not tolerate ClassNotFoundExceptions. At a minimum the
region should not open. See HBASE-6873.
> Allow region server UI to display critical errors such as those corresponding
> to ClassNotFoundException when loading user coprocessors
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7310
> URL: https://issues.apache.org/jira/browse/HBASE-7310
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
>
> When working on HBASE-7205, I logged the following comment:
> The reason for coprocessor loading to tolerate ClassNotFoundException is that
> the user table region where jar file and classname mismatch can reside on any
> of the region servers in the cluster. If we don't tolerate the mismatch, it
> is possible that all region servers in the cluster abort.
> I think we should allow region server UI to display critical errors such as
> those corresponding to ClassNotFoundException when loading user coprocessors.
> This would help user quickly identify issues without forcing them to scan
> region server log(s).
> Region server can also send such critical errors to master so that master can
> aggregate the errors and give user a central place to check critical errors.
--
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
