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

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

FAILURE: Integrated in Ambari-trunk-Commit #2169 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/2169/])
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=1eb9315d15fbd97b79b7d58eec2c450b9b6e82ec)
* 
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-site.xml
* 
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-env.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/STORM/configuration/storm-site.xml


> .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, 2.0.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.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)

Reply via email to