ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk" <>
Subject Review Request 33083: 2.0.1 CLONE - .log Files are not placed in the changed directory in Ambari 1.6 and 1.7
Date Fri, 10 Apr 2015 15:13:58 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for Ambari and Vitalyi Brodetskyi.

Bugs: AMBARI-9849

Repository: ambari


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





mvn clean test


Andrew Onischuk

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message