ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16958) Prefix component log lines in agent log
Date Tue, 31 May 2016 08:15:12 GMT

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

Hadoop QA commented on AMBARI-16958:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12807045/AMBARI-16958.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7064//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7064//console

This message is automatically generated.

> Prefix component log lines in agent log
> ---------------------------------------
>
>                 Key: AMBARI-16958
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16958
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.4.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16958.patch
>
>
> If parallel execution is enabled, log lines of different components may interfere, especially
if they are split in more lines, a prefix for each log containing component ROLE, task ID
would be useful to be able to co-relate these.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message