[
https://issues.apache.org/jira/browse/HDFS-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035529#comment-13035529
]
Hudson commented on HDFS-1927:
------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #666 (See
[https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/666/])
HDFS-1927. Fix a bug which causes ip=null in NameNode audit log.
Contributed by John George
szetszwo :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1124349
Files :
*
/hadoop/hdfs/trunk/src/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* /hadoop/hdfs/trunk/CHANGES.txt
> 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
