[
https://issues.apache.org/jira/browse/KYLIN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834406#comment-16834406
]
ASF GitHub Bot commented on KYLIN-3994:
---------------------------------------
lshmouse commented on pull request #632: KYLIN-3994: StorageCleanupJob may
delete cube id data of new built segment because of cube cache in CubeManager
URL: https://github.com/apache/kylin/pull/632
See: https://issues.apache.org/jira/browse/KYLIN-3994
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> 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)
