Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0E3FF10952 for ; Thu, 12 Dec 2013 07:34:38 +0000 (UTC) Received: (qmail 75704 invoked by uid 500); 12 Dec 2013 07:34:36 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 75668 invoked by uid 500); 12 Dec 2013 07:34:36 -0000 Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.incubator.apache.org Delivered-To: mailing list dev@tajo.incubator.apache.org Received: (qmail 75608 invoked by uid 99); 12 Dec 2013 07:34:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Dec 2013 07:34:35 +0000 X-ASF-Spam-Status: No, hits=-2000.1 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 12 Dec 2013 07:34:33 +0000 Received: (qmail 75182 invoked by uid 99); 12 Dec 2013 07:34:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Dec 2013 07:34:09 +0000 Date: Thu, 12 Dec 2013 07:34:09 +0000 (UTC) From: "Jihoon Son (JIRA)" To: dev@tajo.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (TAJO-333) Add metric system to Tajo MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/TAJO-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846120#comment-13846120 ] Jihoon Son edited comment on TAJO-333 at 12/12/13 7:33 AM: ----------------------------------------------------------- The Ganglia reporter looks really great! But, I have a question for the console reporter. I configured logj4.properties as in this patch. {noformat} log4j.rootLogger=info,stdout,EventCounter log4j.threshhold=ALL log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%d{ISO8601} %-5p %c{2} (%F:%M(%L)) - %m%n log4j.logger.org.apache.hadoop=WARN log4j.logger.org.apache.hadoop.conf=ERROR log4j.appender.EventCounter=org.apache.tajo.util.metrics.TajoLogEventCounter {noformat} I run a query of "select count( * ) from lineitem" for a 1GB table on a single machine cluster. The console reports seems to be written to the query master log, but I can't find it anywhere. Would you tell me how I can see the console report? was (Author: jihoonson): The Ganglia reporter looks really great! But, I have a question for the console reporter. I configured logj4.properties as in this patch. {noformat} log4j.rootLogger=info,stdout,EventCounter log4j.threshhold=ALL log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%d{ISO8601} %-5p %c{2} (%F:%M(%L)) - %m%n log4j.logger.org.apache.hadoop=WARN log4j.logger.org.apache.hadoop.conf=ERROR log4j.appender.EventCounter=org.apache.tajo.util.metrics.TajoLogEventCounter {noformat} I run a query of "select count(*) from lineitem" for a 1GB table on a single machine cluster. The console reports seems to be written to the query master log, but I can't find it anywhere. Would you tell me how I can see the console report? > Add metric system to Tajo > ------------------------- > > Key: TAJO-333 > URL: https://issues.apache.org/jira/browse/TAJO-333 > Project: Tajo > Issue Type: New Feature > Reporter: Hyunsik Choi > Assignee: hyoungjunkim > Labels: metrics > Fix For: 0.8-incubating > > Attachments: TAJO-333.patch, TAJO-333_2.patch, tajo-ganglia-01.png, tajo-ganglia-02.png > > > Currently, there is no way to measure and observe Tajo's internal operations. As a Hadoop job, Tajo also should measure and record a lot of operational works. > I would like to propose the use of Metrics (http://metrics.codahale.com/). It is well known as a stable and efficient metric library. -- This message was sent by Atlassian JIRA (v6.1.4#6159)