Mailing-List: contact chukwa-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@hadoop.apache.org
Message-ID: <1522330464.1238453990433.JavaMail.jira@brutus>
Date: Mon, 30 Mar 2009 15:59:50 -0700 (PDT)
From: "Eric Yang (JIRA)" <jira@apache.org>
To: chukwa-dev@hadoop.apache.org
Subject: [jira] Updated: (CHUKWA-31) dbAdmin.log should be more informative
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CHUKWA-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated CHUKWA-31:
----------------------------

    Attachment: CHUKWA-31.patch

Log duration of SQL statement execution time.

> dbAdmin.log should be more informative
> --------------------------------------
>
>                 Key: CHUKWA-31
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-31
>             Project: Hadoop Chukwa
>          Issue Type: Improvement
>          Components: Data Processors
>         Environment: Redhat EL 5.1, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>            Priority: Blocker
>         Attachments: CHUKWA-31.patch
>
>
> The log produced from dbAdmin is not very useful for trouble shooting or understanding what the process is doing.
> We can add the following information to dbAdmin log file:
>    * Maximum execution time of the executed queries.
>    * Number of queries executed.
> Additional stats about DataExpiration, TableCreator and Aggregator, would be useful.

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