ambari-dev 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-7761) stale_configs parameter works incorrectly for Flume
Date Mon, 13 Oct 2014 18:45:35 GMT

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

Hadoop QA commented on AMBARI-7761:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12674548/AMBARI-7761.patch.1
  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 7 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/179//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/179//console

This message is automatically generated.

> stale_configs parameter works incorrectly for Flume
> ---------------------------------------------------
>
>                 Key: AMBARI-7761
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7761
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>         Environment: 3-node CentOS 6.4
> HDP 2.1
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7761.patch, AMBARI-7761.patch.1, AMBARI-7761_branch-1.7.0.patch
>
>
> *STR:*
> # Deployed cluster with Flume but without Flume Agents
> # Added Flume agent component on each host.
> # Crated config groups for Flume: _group1_(assigned host _c6401_) and _group2_(assigned
host _c6402_). Note that host _c6403_ is in _Flume Default_ group.
> # Overrided flume.conf for _group1_ and _group2_ with custom values.
> # Restarted all components for Flume (there are no restart indicators after restart).
> # Setted flume.conf for _Flume Default_ group with custom value. (_Flume Default_ had
only c6403).
> # Clicked 'Save'.
> *Result:* Appeared restart indicators for Flume agents on all hosts, including hosts,
which are memberships of _group1_ and _group2_ (but configs were changed only for Flume agent
in _Flume Default_ group).



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

Mime
View raw message