ambari-dev mailing list archives

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


Yusaku Sako commented on AMBARI-15133:

Looks like this was committed to trunk and branch-2.2.
Is there a ReviewBoard for this?  If so, please link it from this JIRA.
Also, I reverted the changes from branch-2.2, because it was causing a rat failure (mvn clean
apache-rat:check failed).

> Functionality to purge operational logs from the ambari database
> ----------------------------------------------------------------
>                 Key: AMBARI-15133
>                 URL:
>             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

View raw message