ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15133) Functionality to purge operational logs from the ambari database
Date Wed, 02 Mar 2016 08:15:18 GMT

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

Yusaku Sako commented on AMBARI-15133:
--------------------------------------

It was failing on ambari-server/test.result.  Looks like you've already taken care this with
267d60778fab840d3c2d629313810c30342d8fec.



> Functionality to purge operational logs from the ambari database
> ----------------------------------------------------------------
>
>                 Key: AMBARI-15133
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15133
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server
>    Affects Versions: 2.2.1
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>              Labels: features
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15133.v12.patch, AMBARI-15133.v2.2.1.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Ambari operational data may significantly grow over time and as a result the database
operations may degrade.
> This feature is about allowing operators to purge related tables based on configurable
cleaning policies. (As a first step only time based cleanup is to be supported)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message