Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Content-Type: multipart/alternative;
 boundary="===============0289022277150248077=="
MIME-Version: 1.0
Subject: Re: Review Request 31583: .log Files are not placed in the changed
 directory in Ambari 1.6 and 1.7
From: "Dmytro Sen" <dsen@hortonworks.com>
To: "Myroslav Papirkovskyy" <mpapyrkovskyy@hortonworks.com>
Cc: "Dmytro Sen" <dsen@hortonworks.com>, "Ambari" <dev@ambari.apache.org>
Date: Wed, 01 Apr 2015 14:26:03 -0000
Message-ID: <20150401142603.16791.24977@reviews.apache.org>
Auto-Submitted: auto-generated
Sender: "Dmytro Sen" <noreply@reviews.apache.org>
References: <20150228164942.1420.45060@reviews.apache.org>
In-Reply-To: <20150228164942.1420.45060@reviews.apache.org>
Reply-To: "Dmytro Sen" <dsen@hortonworks.com>

--===============0289022277150248077==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31583/
-----------------------------------------------------------

(Updated Апрель 1, 2015, 2:26 п.п.)


Review request for Ambari and Myroslav Papirkovskyy.


Bugs: AMBARI-9849
    https://issues.apache.org/jira/browse/AMBARI-9849


Repository: ambari


Description
-------

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).


Diffs (updated)
-----

  ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-env.xml c663116 
  ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-site.xml 5e96fb1 
  ambari-server/src/main/resources/stacks/HDP/2.2/services/STORM/configuration/storm-site.xml c933099 

Diff: https://reviews.apache.org/r/31583/diff/


Testing
-------

Only jinja template chaged, tested manually


Thanks,

Dmytro Sen


--===============0289022277150248077==--