hbase-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/HBASE-11749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097830#comment-14097830
] 

Andrew Purtell commented on HBASE-11749:
----------------------------------------

+1

> 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
>         Attachments: HBASE-11749.patch
>
>
> The following is the error in the log files, 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