hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Srungarapu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-11749) Better error logging when coprocessors loading has failed.
Date Thu, 14 Aug 2014 22:21:18 GMT
Srikanth Srungarapu created HBASE-11749:
-------------------------------------------

             Summary: Better error logging when coprocessors loading has failed.
                 Key: HBASE-11749
                 URL: https://issues.apache.org/jira/browse/HBASE-11749
             Project: HBase
          Issue Type: Improvement
          Components: Coprocessors, Usability
            Reporter: Srikanth Srungarapu
            Assignee: Srikanth Srungarapu
            Priority: Trivial


The following is the error in the log being displayed now, when the wrong coprocessor is specified
in config file.
{code}
378:2014-08-14 15:15:41,773 ERROR [master:172.16.2.118:60000] coprocessor.CoprocessorHost:
The coprocessor org.apache.hadoop.hbase.security.visibility.VisibilityControlle threw an unexpected
exception
{code}
Instead it would be better to have more meaningful exception description like
{code}
525:2014-08-14 15:07:33,682 ERROR [master:172.16.2.118:60000] coprocessor.CoprocessorHost:
The coprocessor org.apache.hadoop.hbase.security.visibility.VisibilityControlle threw java.lang.ClassNotFoundException:
org.apache.hadoop.hbase.security.visibility.VisibilityControlle
{code}




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message