Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <30253424.1148079810583.JavaMail.jira@brutus>
Date: Fri, 19 May 2006 23:03:30 +0000 (GMT+00:00)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-237) Standard set of Performance Metrics
 for Hadoop
In-Reply-To: <14919853.1148078609860.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-237?page=comments#action_12412604 ] 

Doug Cutting commented on HADOOP-237:
-------------------------------------

Here are some quick ideas for what could be interesting statistics to monitor:

Map Input:
  records/second
  bytes/second

Map Output Transferred to Reduce Node;
  records/second
  bytes/second

Reduce Output:
  bytes/second
  records/second

Job Tracker:
  maps tasks launched
  map tasks completed
  reduce tasks launched
  reduce tasks completed

DFS Datanode
  bytes/second written
  bytes/second read
  blocks/second read
  blocks/second written
  blocks replicated
  blocks removed

DFS NameNode
  files created
  files renamed
  files listed
  files opened
  files removed

Is this the sort of thing you had in mind?


> Standard set of Performance Metrics for Hadoop
> ----------------------------------------------
>
>          Key: HADOOP-237
>          URL: http://issues.apache.org/jira/browse/HADOOP-237
>      Project: Hadoop
>         Type: Improvement

>   Components: metrics
>     Versions: 0.3
>  Environment: All
>     Reporter: Milind Bhandarkar
>     Assignee: Milind Bhandarkar

>
> I am starting to use Hadoop's shiny new Metrics API to publish performance (and other) Metrics of running jobs and other daemons.
> Which performance metrics are people interested in seeing ? If possible, please group them according to modules, such as map-reduce, dfs, general-cluster-related etc. I will follow this process:
> 1. collect this list
> 2. assess feasibility of obtaining metric
> 3. assign context/record/metrics names
> 4. seek approval for names
> 5. instrument the code.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira