[
https://issues.apache.org/jira/browse/AMBARI-24855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232563#comment-17232563
]
akiyamaneko commented on AMBARI-24855:
--------------------------------------
[~itskrishspace]
hi,guys, I tried to reproduce this problem following your steps in Ambari
2.7.4. and Ambari worked as expected . Can you try again with the higher
version of Ambari?
> Ambari does not prompt History Server restart upon modification in
> "yarn.log-aggregation.retain-seconds"
> --------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-24855
> URL: https://issues.apache.org/jira/browse/AMBARI-24855
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.1
> Reporter: Krishnama Raju K
> Priority: Critical
>
> Currently aggregated log cleaner service runs in MR Job History Server as
> "_AggregatedLogDeletionService_". Hence, any change in
> "yarn.log-aggregation.retain-seconds" in yarn-site.xml should enforce a
> restart of MR Job histotry server. However, we see only YARN service restarts
> to be prompted. So, there should be another restart icon that should pop up
> for MapReduce service for Job history server.
>
> Ref: YARN Log aggregation behavior is explained
> [here|https://hortonworks.com/blog/simplifying-user-logs-management-and-access-in-yarn/]
>
> Steps to Reproduce
> ===============
> # Make sure there are no stale configs (prompting restarts) in YARN or MR
> service page
> # In YARN config page change "yarn.log-aggregation.retain-seconds" from
> default 30 days (in seconds) to any other value.
> # Save and observe the restart icon appear on just YARN service in Ambari
> UI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
