[
https://issues.apache.org/jira/browse/KYLIN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852888#comment-16852888
]
ASF subversion and git services commented on KYLIN-3994:
--------------------------------------------------------
Commit cfce8bb628e0e4ade4e03ba9d544096859760907 in kylin's branch
refs/heads/master from Liu Shaohui
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=cfce8bb ]
KYLIN-3994: StorageCleanupJob may delete cube id data of new built segment
because of cube cache in CubeManager (#633)
* KYLIN-3994: StorageCleanupJob may delete cube id data of new built segment
because of cube cache in CubeManager
> StorageCleanupJob may delete data of newly 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
> Fix For: v2.6.3
>
>
> 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)
