hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ari Rabkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5054) Chukwa database partitions does not create/expire automatically
Date Tue, 10 Feb 2009 00:39:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672087#action_12672087

Ari Rabkin commented on HADOOP-5054:

Looks okay.  I'm a bit nervous about the lack of tests, though I understand that it's hard
to unit-test this sort of thing. Has it been tried out in production?

> Chukwa database partitions does not create/expire automatically
> ---------------------------------------------------------------
>                 Key: HADOOP-5054
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5054
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/chukwa
>         Environment: Redhat EL 5.1, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>         Attachments: HADOOP-5054.patch
> dbAdmin.sh should create database partitions base on time, but this is not working because
the timestamp variable is not inside the loop for creating database partitions.  When the
script is running, it would create partitions corresponding to the execution time once only.
> The database expiration script need to handle the case where partition number is invalid.

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

View raw message