Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1360CD34C for ; Thu, 6 Sep 2012 23:43:08 +0000 (UTC) Received: (qmail 65729 invoked by uid 500); 6 Sep 2012 23:43:07 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 65694 invoked by uid 500); 6 Sep 2012 23:43:07 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 65682 invoked by uid 99); 6 Sep 2012 23:43:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2012 23:43:07 +0000 Date: Fri, 7 Sep 2012 10:43:07 +1100 (NCT) From: "Karthik Kambatla (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <909747974.47377.1346974987849.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (MAPREDUCE-4643) Make job-history cleanup-period configurable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Karthik Kambatla created MAPREDUCE-4643: ------------------------------------------- Summary: Make job-history cleanup-period configurable Key: MAPREDUCE-4643 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4643 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 2.0.0-alpha, 1.0.3 Reporter: Karthik Kambatla Job history cleanup should be made configurable. Currently, it is set to 1 month by default. The DEBUG_MODE (to be removed, see MAPREDUCE-4629) sets it to 20 minutes, but it should be configurable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira