You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Laszlo Puskas (JIRA)" <ji...@apache.org> on 2016/02/26 13:23:18 UTC

[jira] [Commented] (AMBARI-15133) Functionality to purge operational logs from the ambari database

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

Laszlo Puskas commented on AMBARI-15133:
----------------------------------------

New patch uploaded.

> 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.v5.patch, AMBARI-15133.v8.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)