Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 17 May 2011 22:50:47 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1572017771.20926.1305672647508.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <169268315.6832.1305210587479.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1927) audit logs could ignore certain
 xsactions and also could contain "ip=null"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsz Wo (Nicholas), SZE commented on HDFS-1927:
----------------------------------------------

John, could you also update the javadoc of the method?

> 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
>    Affects Versions: 0.23.0
>            Reporter: John George
>            Assignee: John George
>         Attachments: 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