You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sebastian Toader (JIRA)" <ji...@apache.org> on 2017/06/13 04:44:00 UTC

[jira] [Commented] (AMBARI-20749) Ambari data purging

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

Sebastian Toader commented on AMBARI-20749:
-------------------------------------------

Added a couple of  fixes to https://issues.apache.org/jira/browse/AMBARI-20687 and renamed the db-cleanup functionality to db-purge-history

> Ambari data purging
> -------------------
>
>                 Key: AMBARI-20749
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20749
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: amarnath reddy pappu
>            Assignee: Sebastian Toader
>            Priority: Critical
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-20749.b25.v1.patch
>
>
> Currently there is one option to purge the old data in Ambari.
> 1. db-cleanup : this sound like database clean up (or delete) , may be better word like Purge can be used.
> 2. appears like currently it purges only Alert related tables - should also consider of other tables lie host_role_command and execution_commands and if there is any other tables as well.
> 3. I don't find any documentation on this option - some customers are trying to hard delete entries from DB tables and ending up with some other issues. so better documentation would help here.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)