hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1927) audit logs could ignore certain xsactions and also could contain "ip=null"
Date Wed, 18 May 2011 17:58:47 GMT

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

Tsz Wo (Nicholas), SZE updated HDFS-1927:

       Resolution: Fixed
    Fix Version/s: 0.23.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I have committed this.  Thanks, John!

> audit logs could ignore certain xsactions and also could contain "ip=null"
> --------------------------------------------------------------------------
>                 Key: HDFS-1927
>                 URL: https://issues.apache.org/jira/browse/HDFS-1927
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: John George
>            Assignee: John George
>             Fix For: 0.23.0
>         Attachments: HDFS-1927-1.patch, HDFS-1927.patch
> Namenode audit logs could be ignoring certain transactions that are successfully completed.
This is because it check if the RemoteIP is null to decide if a transaction is remote or not.
In certain cases, RemoteIP could return null but the xsaction could still be "remote". An
example is a case where a client gets killed while in the middle of the transaction. 

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message