You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2012/12/09 14:37:21 UTC

[jira] [Created] (HBASE-7310) Allow region server UI to display critical errors such as those corresponding to ClassNotFoundException when loading user coprocessors

Ted Yu created HBASE-7310:
-----------------------------

             Summary: 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