Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D6FCA18999 for ; Wed, 2 Mar 2016 08:01:18 +0000 (UTC) Received: (qmail 82526 invoked by uid 500); 2 Mar 2016 08:01:18 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 82458 invoked by uid 500); 2 Mar 2016 08:01:18 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 82186 invoked by uid 99); 2 Mar 2016 08:01:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2016 08:01:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1F5C22C1F5C for ; Wed, 2 Mar 2016 08:01:18 +0000 (UTC) Date: Wed, 2 Mar 2016 08:01:18 +0000 (UTC) From: "Hudson (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-15133) Functionality to purge operational logs from the ambari database MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175235#comment-15175235 ] Hudson commented on AMBARI-15133: --------------------------------- FAILURE: Integrated in Ambari-trunk-Commit #4421 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4421/]) Revert "AMBARI-15133. Functionality to purge operational logs from the (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cc4c739845f587cbbe8b746f537ba1a149270da5]) * ambari-server/pom.xml * ambari-server/src/main/java/org/apache/ambari/server/cleanup/TimeBasedCleanupPolicy.java * ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertCurrentEntity.java * ambari-server/src/main/java/org/apache/ambari/server/cleanup/PurgePolicy.java * ambari-server/src/test/java/org/apache/ambari/server/cleanup/CleanupServiceImplTest.java * ambari-server/src/main/python/ambari_server/setupActions.py * ambari-server/src/main/python/ambari-server.py * ambari-server/src/main/java/org/apache/ambari/server/cleanup/CleanupServiceImpl.java * ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertNoticeEntity.java * ambari-server/src/main/java/org/apache/ambari/server/cleanup/ClasspathScannerUtils.java * ambari-server/src/main/python/ambari_server/dbCleanup.py * ambari-server/src/main/java/org/apache/ambari/server/cleanup/CleanupModule.java * ambari-server/src/main/java/org/apache/ambari/server/cleanup/CleanupService.java * ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertHistoryEntity.java * ambari-server/src/test/resources/ddl-func-test/ddl-cleanup-test-data.sql * ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertsDAO.java * ambari-server/src/test/java/org/apache/ambari/server/cleanup/CleanupServiceFunctionalTest.java * ambari-server/sbin/ambari-server * ambari-server/src/main/java/org/apache/ambari/server/orm/dao/Cleanable.java * ambari-server/src/main/java/org/apache/ambari/server/cleanup/CleanupDriver.java > 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)