[
https://issues.apache.org/jira/browse/KYLIN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851618#comment-16851618
]
PENG Zhengshuai commented on KYLIN-3994:
----------------------------------------
Reload cube list is a solution. But I think a more safety solution is to add
NEW-BORN resource protection everywhere. That means when getting the candidates
to delete, filter them if they are NEW-BORN resources (just generated very
recently)
> StorageCleanupJob may delete cube id data of new built segment because of
> cube cache in CubeManager
> ---------------------------------------------------------------------------------------------------
>
> Key: KYLIN-3994
> URL: https://issues.apache.org/jira/browse/KYLIN-3994
> Project: Kylin
> Issue Type: Bug
> Affects Versions: v2.5.2
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Major
>
> In our production cluster, we found that the cube id data of a new-built
> segment is deleted by the StorageCleanupJob.
> After checking the code of cleanUnusedHdfsFiles in StorageCleanupJob, we
> found that there is a bug here: CubeManager read all cube meta in
> initiation and cache it for later
> listAllCubes operations, the metadata will be out of data after listing the
> hdfs working dir.
> So the working directory of a finished job may be deleted unexpectedly.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
