[
https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669028#comment-15669028
]
Hudson commented on AMBARI-18866:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6021 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6021/])
AMBARI-18866. Stack advisor should limit call history it preserves (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8c3ad1d6469fbe9c095fcc563f1c1a536892a727])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelper.java
> Stack advisor should limit call history it preserves
> ----------------------------------------------------
>
> Key: AMBARI-18866
> URL: https://issues.apache.org/jira/browse/AMBARI-18866
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Madhuvanthi Radhakrishnan
> Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18866.patch
>
>
> Today stack advisor uses a monotonically increasing id for each call when it
> creates a local folder. This is reset only when Ambari Server is restarted.
> For large clusters each call may produce 10-12 MB of files and it will result
> in eventual disk space issue as there is no limit to how long call history is
> preserved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
