Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 28 Feb 2015 19:26:05 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12778492.1425141911000.43098.1425151565139@Atlassian.JIRA>
In-Reply-To: <JIRA.12778492.1425141911000@Atlassian.JIRA>
References: <JIRA.12778492.1425141911000@Atlassian.JIRA>
 <JIRA.12778492.1425141911035@arcas>
Subject: [jira] [Commented] (AMBARI-9849) .log Files are not placed in the
 changed directory in Ambari 1.6 and 1.7
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on AMBARI-9849:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #1904 (See [https://builds.apache.org/job/Ambari-trunk-Commit/1904/])
AMBARI-9849 .log Files are not placed in the changed directory in Ambari 1.6 and 1.7 (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=38d805e725858d609f89b9fdc54104f305cdb4e0)
* ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/templates/storm.yaml.j2


> .log Files are not placed in the changed directory in Ambari 1.6 and 1.7
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-9849
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9849
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 1.6.1, 1.7.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9849.patch
>
>
> PROBLEM: When changing the location for storm log file (.log files) in Ambari 1.6/1.7, instead of it placing those files in the specified location, it places those files into the default location of /var/log/storm.
> BUSINESS IMPACT: This bug is preventing the customer from changing the location of their placement for their log files which is impacting their space for their filesystem as well as their business activities. Customer is expecting a quick turn-around on this issue.
> STEPS TO REPRODUCE: Support was able to reproduce this issue as well by going in to Ambari 1.6 and 1.7 to change the location for the storm log directories and these changes failed to go to the newly specified location. The .out files all went to the newly specified location.
> SUPPORT ANALYSIS: After seeing the defect it is obvious that this is a bug pertaining to the .log file directory change in Ambari 1.6 and 1.7 (both were tested).


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