You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Dmytro Sen <ds...@hortonworks.com> on 2015/02/28 17:49:42 UTC
Review Request 31583: .log Files are not placed in the changed
directory in Ambari 1.6 and 1.7
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31583/
-----------------------------------------------------------
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
-----
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/templates/storm.yaml.j2 db476f4
Diff: https://reviews.apache.org/r/31583/diff/
Testing
-------
Only jinja template chaged, tested manually
Thanks,
Dmytro Sen
Re: Review Request 31583: .log Files are not placed in the changed
directory in Ambari 1.6 and 1.7
Posted by Myroslav Papirkovskyy <mp...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31583/#review74681
-----------------------------------------------------------
Ship it!
Ship It!
- Myroslav Papirkovskyy
On Лют. 28, 2015, 6:49 після полудня, Dmytro Sen wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/31583/
> -----------------------------------------------------------
>
> (Updated Лют. 28, 2015, 6:49 після полудня)
>
>
> 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
> -----
>
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/templates/storm.yaml.j2 db476f4
>
> Diff: https://reviews.apache.org/r/31583/diff/
>
>
> Testing
> -------
>
> Only jinja template chaged, tested manually
>
>
> Thanks,
>
> Dmytro Sen
>
>
Re: Review Request 31583: .log Files are not placed in the changed
directory in Ambari 1.6 and 1.7
Posted by Myroslav Papirkovskyy <mp...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31583/#review78521
-----------------------------------------------------------
Ship it!
Ship It!
- Myroslav Papirkovskyy
On Квітень 1, 2015, 5:26 після полудня, Dmytro Sen wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/31583/
> -----------------------------------------------------------
>
> (Updated Квітень 1, 2015, 5: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
> -----
>
> 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
>
>
Re: Review Request 31583: .log Files are not placed in the changed
directory in Ambari 1.6 and 1.7
Posted by Dmytro Sen <ds...@hortonworks.com>.
-----------------------------------------------------------
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