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

Hadoop QA commented on MAPREDUCE-2655:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12491678/MAPREDUCE-2655-v2.patch
  against trunk revision .

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

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 javadoc.  The javadoc tool appears to have generated 6 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 unit tests:



    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/540//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/540//console

This message is automatically generated.

> MR279: Audit logs for YARN 
> ---------------------------
>
>                 Key: MAPREDUCE-2655
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2655
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2655-v2.patch, MAPREDUCE-2655.patch, 
> nm-audit.log, rm-audit.log
>
>
> We need audit logs for YARN components:
> ResourceManager:
>  - All the refresh* protocol access points - refreshQueues, refreshNodes, 
> refreshProxyUsers,
> refreshUserToGroupMappings.
>  - All app-submissions, app-kills to RM.
>  - Illegal and successful(?) AM registrations.
>  - Illegal container allocations/deallocations from AMs
>  - Successful container allocations/deallocations from AMs too?
> NodeManager:
>  - Illegal container launches from AMs
>  - Successful container launches from AMs too?
> Not sure if we need audit logs from MR AMs.

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

        

Reply via email to