[
https://issues.apache.org/jira/browse/HBASE-7066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489939#comment-13489939
]
Lars Hofhansl commented on HBASE-7066:
--------------------------------------
Hmm... I agree that for security related exception is OK (can be considered an
exceptional situation), and also that just return true/false from the coproc
does not provide enough information.
CannotIgnoreException could work for 0.96.
For 0.94 it would break old clients on new servers, right? (the old client
would not know about CannotIgnoreException).
Another option is to catch and log IOException but to rethrow all
HBaseIOExceptions, or maybe just always rethrow DoNotRetryIOException, because
the server should not swallow those anyway.
> Some HMaster coprocessor exceptions are being swallowed in try catch blocks
> ---------------------------------------------------------------------------
>
> Key: HBASE-7066
> URL: https://issues.apache.org/jira/browse/HBASE-7066
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors, security
> Affects Versions: 0.94.2, 0.96.0
> Reporter: Francis Liu
> Assignee: Francis Liu
> Priority: Critical
> Attachments: 7066-addendum.txt, HBASE-7066_94.patch,
> HBASE-7066_trunk.patch, HBASE-7066_trunk.patch
>
>
> This is causing HMaster.shutdown() and HMaster.stopMaster() to succeed even
> when an AccessDeniedException is thrown.
--
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
