[
https://issues.apache.org/jira/browse/AMBARI-13800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997433#comment-14997433
]
Hadoop QA commented on AMBARI-13800:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12771397/AMBARI-13800.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 3 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-metrics/ambari-metrics-timelineservice ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4225//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4225//console
This message is automatically generated.
> It is not possible to change "Metrics Collector log dir"
> --------------------------------------------------------
>
> Key: AMBARI-13800
> URL: https://issues.apache.org/jira/browse/AMBARI-13800
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.1.3
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: AMBARI-13800.patch
>
>
> Steps:
> - Was deployed cluster.
> - Try to change "Metrics Collector log dir" property.
> - Save changes.
> - Start AMS
> Result - start fails by 1200 secs timeout
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
