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

Hadoop QA commented on HDFS-1927:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12478979/HDFS-1927.patch
  against trunk revision 1102153.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    -1 javac.  The patch appears to cause tar ant target to fail.

    -1 findbugs.  The patch appears to cause Findbugs (version 1.3.9) to fail.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    -1 core tests.  The patch failed these core unit tests:


    -1 contrib tests.  The patch failed contrib unit tests.

    -1 system test framework.  The patch failed system test framework compile.

Test results: 
https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/500//testReport/
Console output: 
https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/500//console

This message is automatically generated.

> 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

Reply via email to