[
https://issues.apache.org/jira/browse/HADOOP-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated HADOOP-5054:
------------------------------
Description:
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.
was:
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.
Summary: Chukwa database partitions does not create/expire
automatically (was: Chukwa database partitions does not get created
automatically)
> 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.
