[ 
https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665329#comment-15665329
 ] 

Hadoop QA commented on AMBARI-18866:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12838857/AMBARI-18866.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelperTest
                  
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9264//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9264//console

This message is automatically generated.

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

Reply via email to