You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2009/03/13 16:05:55 UTC

[jira] Commented: (HADOOP-5054) Chukwa database partitions does not create/expire automatically

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

Hudson commented on HADOOP-5054:
--------------------------------

Integrated in Hadoop-trunk #778 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/778/])
    

> 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.