Return-Path: 
 <core-dev-return-43637-apmail-hadoop-core-dev-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org
Received: (qmail 11449 invoked from network); 14 Jul 2008 17:49:28 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 14 Jul 2008 17:49:28 -0000
Received: (qmail 92123 invoked by uid 500); 14 Jul 2008 17:49:22 -0000
Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org
Received: (qmail 92088 invoked by uid 500); 14 Jul 2008 17:49:22 -0000
Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:core-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:core-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:core-dev@hadoop.apache.org>
List-Id: <core-dev.hadoop.apache.org>
Reply-To: core-dev@hadoop.apache.org
Delivered-To: mailing list core-dev@hadoop.apache.org
Received: (qmail 92077 invoked by uid 99); 14 Jul 2008 17:49:22 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2008 10:49:22 -0700
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2008 17:48:37 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id C7821234C173
	for <core-dev@hadoop.apache.org>; Mon, 14 Jul 2008 10:48:31 -0700 (PDT)
Message-ID: <40724312.1216057711816.JavaMail.jira@brutus>
Date: Mon, 14 Jul 2008 10:48:31 -0700 (PDT)
From: "Lohit Vijayarenu (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3753) metrics: FileContext support
 overwrite mode
In-Reply-To: <127769645.1215967291600.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/HADOOP-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613386#action_12613386 ] 

Lohit Vijayarenu commented on HADOOP-3753:
------------------------------------------

bq. In some scenarios, it would be useful to simply write the current statistics to the file once every period, then overwrite the file for the next period.
Right now FileContext writes metric values every 'period' defined by metricsName.period property. (eg. dfs.period). Your idea about overwriting would be very helpful. How about rollover to new file possibly appended with time stamp. Say, if we roll over every 15 minutes or an hour, then append time stamp. Even better if we could have property something like metricsName.fileRollover=<some value in minutes>. Overwriting will lose the data, cleanup could be done by external application. 

> metrics: FileContext support overwrite mode
> -------------------------------------------
>
>                 Key: HADOOP-3753
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3753
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: metrics
>            Reporter: Craig Macdonald
>            Priority: Minor
>
> FileContext currently continually appends to the metrics log file(s), generating an ever lengthening file.
> In some scenarios, it would be useful to simply write the current statistics to the file once every period, then overwrite the file for the next period.
> For instance, this could be useful if an external application parsed the metrics output - e.g. Cacti to create realtime graphs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.