[
https://issues.apache.org/jira/browse/AMBARI-15650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220016#comment-15220016
]
Hadoop QA commented on AMBARI-15650:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12796313/AMBARI-15650.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 2 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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6125//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6125//console
This message is automatically generated.
> Output short logs summary on start/stop failure
> -----------------------------------------------
>
> Key: AMBARI-15650
> URL: https://issues.apache.org/jira/browse/AMBARI-15650
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15650.patch
>
>
> There were tons of situations when we had only output of task failure, when a
> certain service failed to start/stop/restart, but couldn't get the logs of
> services.
> Which makes fixing those bugs pretty problematic or even impossible if no
> reproduce is available.
> This jira aims to output a short tail of service logs on start/stop failures,
> this should cover a big part of such a scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
