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 2018/03/30 10:28:00 UTC

[jira] [Commented] (KYLIN-3326) Better way to update migration target cluster's metadata after cube migration

    [ https://issues.apache.org/jira/browse/KYLIN-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420355#comment-16420355 ] 

Zhong Yanghong commented on KYLIN-3326:
---------------------------------------

Currently when call {{updateMeta}} in {{CubeMigrationCLI}}, it gets all the target cluster's rest servers and then call rest to update the metadata for each server. This may lead to an issue in case of that the target cluster expose only a vip to others. We can not expect that all the nodes in the source cluster can successfully connect to all the nodes in the target cluster. Therefore, I think it's better to expose only a interface to others like {{announceWipeCache}} in {{CacheController}}.

> Better way to update migration target cluster's metadata after cube migration
> -----------------------------------------------------------------------------
>
>                 Key: KYLIN-3326
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3326
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Tools, Build and Test
>            Reporter: Zhong Yanghong
>            Assignee: Zhong Yanghong
>            Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)