[
https://issues.apache.org/jira/browse/HBASE-7066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489646#comment-13489646
]
Francis Liu commented on HBASE-7066:
------------------------------------
Stack, I see what you're trying to get at, we can have AccessController wrap
the exceptions it would have thrown in an AccessDeniedException so it won't get
swallowed in shutdown(). The only potential concern here then is the
CoprocessorHost messing up though in which case it prolly won't be throwing an
IOE so that should acceptable.
Ted, for 0.94 we would have to do some reflection since the Exception is the
security module, or actually move the exception. We can't change the signature
since that would break backward compatilibity.
Have we ever considered making security first class in 0.96 (not a coprocessor,
though still switchable)? More and more it seems to me that security cannot be
treated as a bolt-on extension as we have seen handling failures cannot be
treated the same way as other extensions. We are already considering changing a
public method signature to throw a security exception.
> 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: 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
