You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Zhong Yanghong (JIRA)" <ji...@apache.org> on 2016/04/12 08:20:25 UTC
[jira] [Commented] (KYLIN-1458) Checking the consistency of cube
segment host with the environment after cube migration
[ https://issues.apache.org/jira/browse/KYLIN-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236666#comment-15236666 ]
Zhong Yanghong commented on KYLIN-1458:
---------------------------------------
In the previous version, when running tool "CubeMigrationCLI" with parameter "realExecute" set to false, at the end of this process, "CubeMigrationCheckCLI" will throw out an exception:
Exception in thread "main" java.lang.NullPointerException
at org.apache.kylin.storage.hbase.util.CubeMigrationCheckCLI.addHTableNamesForCube(CubeMigrationCheckCLI.java:141)
at org.apache.kylin.storage.hbase.util.CubeMigrationCheckCLI.checkCube(CubeMigrationCheckCLI.java:124)
at org.apache.kylin.storage.hbase.util.CubeMigrationCheckCLI.execute(CubeMigrationCheckCLI.java:103)
at org.apache.kylin.storage.hbase.util.CubeMigrationCLI.checkMigrationSuccess(CubeMigrationCLI.java:157)
at org.apache.kylin.storage.hbase.util.CubeMigrationCLI.moveCube(CubeMigrationCLI.java:147)
at org.apache.kylin.storage.hbase.util.CubeMigrationCLI.moveCube(CubeMigrationCLI.java:152)
at org.apache.kylin.storage.hbase.util.CubeMigrationCLI.main(CubeMigrationCLI.java:91)
due to the cube has't been migrated to the destination.
Thus the tool "CubeMigrationCheckCLI" should be used under the condition with the parameter "realExecute" set to true
> Checking the consistency of cube segment host with the environment after cube migration
> ---------------------------------------------------------------------------------------
>
> Key: KYLIN-1458
> URL: https://issues.apache.org/jira/browse/KYLIN-1458
> Project: Kylin
> Issue Type: New Feature
> Components: General
> Reporter: Zhong Yanghong
> Assignee: hongbin ma
> Fix For: v1.5.0, v1.4.0
>
> Attachments: add_cube_migration_check.patch
>
>
> Some segments be deleted unexpectedly during StorageCleanupJob. The cause is during cube migration, the segment related htable's host didn't be changed successfully. To avoid this, after cube migration, a tool to check whether exists the inconsistency between the migrated segments and new environment is needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)