You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2012/05/17 04:52:06 UTC

[jira] [Updated] (HBASE-6030) Log AccessDeniedExceptions at INFO level

     [ https://issues.apache.org/jira/browse/HBASE-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-6030:
----------------------------------

    Component/s: coprocessors
       Assignee: Andrew Purtell
    
> Log AccessDeniedExceptions at INFO level
> ----------------------------------------
>
>                 Key: HBASE-6030
>                 URL: https://issues.apache.org/jira/browse/HBASE-6030
>             Project: HBase
>          Issue Type: Improvement
>          Components: coprocessors, security
>    Affects Versions: 0.92.2, 0.96.0, 0.94.1
>         Environment: AccessController coprocessor
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Minor
>
> The HBase AccessController can emit a detailed trace of every action, and whether it succeeded or failed, but this is expected to be used only for debugging an application in a staging environment. In production a RegionServer may have thousands of requests per second, logging the audit trace just isn't viable. However, we might want to log the AccessDeniedExceptions which result from access failures in the daemon logs like Hadoop does, e.g. the NameNode log.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira