You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kylin.apache.org by "Aaron Duan (Jira)" <ji...@apache.org> on 2021/04/24 10:20:00 UTC

[jira] [Created] (KYLIN-4989) Is there anyway to do data migtation from kylin 2.6.2 to the same version across different cluster?

Aaron Duan created KYLIN-4989:
---------------------------------

             Summary: Is there anyway to do data migtation from kylin 2.6.2 to the same version across different cluster?
                 Key: KYLIN-4989
                 URL: https://issues.apache.org/jira/browse/KYLIN-4989
             Project: Kylin
          Issue Type: Task
            Reporter: Aaron Duan


As said in summary, Is there anyway to do data migtation from kylin 2.6.2 to the same version across different cluster?

 

I have tried the CubeMigrationCrossClusterCLI by putting the CubeMigrationCrossClusterCLI  jar file under the path $KYLIN_HOME/tool in the source cluster.

 

The CubeMigrationCrossClusterCLI  jar file is got from kylin 3.1.0 version.

 

But, I got erros like this:

java.net.ConnectException: Connection refused (Connection refused)

 

The commad I use is this:

$KYLIN_HOME/bin/kylin.sh org.apache.kylin.tool.migration.CubeMigrationCrossClusterCLI -kylinUriSrc ADMIN:KYLIN@srcHost:17070 -kylinUriDst ADMIN:KYLIN@destHost:17777 -all -execute true -schemaOnly false -overwrite true

 

Can it work? If not, is there any other way?

 

Thanks for help!

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [jira] [Created] (KYLIN-4989) Is there anyway to do data migtation from kylin 2.6.2 to the same version across different cluster?

Posted by zhengshengjun <sh...@sina.com>.
Hi, '-kylinUriSrc ADMIN:KYLIN@srcHost:17070'  will fetch configuration from source cluster by HTTP request.

‘Connection refused’ is likely due to Kylin Server is not running in ’srcHost’ or the listening port is not 17070 (7070 by default).

If you checked both process and port is fine. Try two alternatives:
  1. Try an offline way:  use 'metastore.sh backup' to export source cluster’s metadata to a directory, and set -kylinUriSrc to exported directory (Read exported metadata from local directory).
  2. Or set -kylinUriSrc to source cluster’s properties file (Read source cluster's metadata storage directly)

If you are going to try Kylin 4, read this article:  https://cwiki.apache.org/confluence/display/KYLIN/How+to+migrate+metadata+to+Kylin+4 <https://cwiki.apache.org/confluence/display/KYLIN/How+to+migrate+metadata+to+Kylin+4>  for reference.




> 2021年4月24日 下午6:20,Aaron Duan (Jira) <ji...@apache.org> 写道:
> 
> -kylinUriSrc ADMIN:KYLIN@srcHost:17070