Before migrating HBase data with Lindorm Tunnel Service (LTS), connect the networks of your source and destination clusters. The steps depend on the network types involved.
Network compatibility overview
| Source network | Destination network | Supported by LTS | Setup required |
|---|---|---|---|
| Virtual private cloud (VPC) | Same VPC | Yes | Associate the LTS cluster with the source and destination HBase clusters in the LTS console. No additional network configuration is needed. |
| VPC | Different VPC | Yes | See Connect clusters across different VPCs. |
| Classic network | Same classic network | No | See Connect clusters within the same classic network. |
| Classic network | VPC | Yes | See Connect a classic network cluster to a VPC cluster. |
| Classic network | Classic network for ApsaraDB for HBase | No | See Connect a classic network cluster to an ApsaraDB for HBase classic network cluster. |
| Classic network for ApsaraDB for HBase | VPC | No | See Connect an ApsaraDB for HBase classic network cluster to a VPC cluster. |
Express Connect and ClassicLink have usage limits that may affect your connections. Review the relevant product documentation before you begin.
Connect clusters across different VPCs
-
Establish a private network connection between the two VPCs using Express Connect circuits. For details, see Connect to VPCs.
-
Add the IP addresses of both the source and destination HBase clusters to the whitelist of the LTS cluster.
-
Activate Hadoop Distributed File System (HDFS) for both ApsaraDB for HBase clusters.
Connect clusters within the same classic network
LTS does not support direct migration within a classic network. To proceed:
-
Add the IP addresses of both the source and destination HBase clusters to the whitelist of the LTS cluster.
-
Enable the HDFS and HBase ports on both HBase clusters.
Connect a classic network cluster to a VPC cluster
-
Establish a ClassicLink connection for the VPC. Bind the classic network-connected Elastic Compute Service (ECS) instance to the corresponding ClassicLink connection. For details, see Overview.
-
Add the IP addresses of both the source and destination HBase clusters to the whitelist of the LTS cluster.
-
Activate HDFS for both ApsaraDB for HBase clusters.
Connect a classic network cluster to an ApsaraDB for HBase classic network cluster
LTS does not support this network combination directly. Use classic network-connected ECS instances as intermediaries:
-
Purchase several classic network-connected ECS instances.
-
Add the IP addresses of both the source and destination HBase clusters to the whitelist of the LTS cluster.
-
Activate HDFS for both ApsaraDB for HBase clusters.
Connect an ApsaraDB for HBase classic network cluster to a VPC cluster
LTS does not support this network combination directly. Use classic network-connected ECS instances as intermediate instances and release them after migration completes. The ECS instances and the VPC-connected HBase cluster must be in the same region, for example, China (Shanghai) or China (Hangzhou).
-
Purchase classic network-connected ECS instances to use as intermediate instances.
-
Connect the ECS instances to the VPC using ClassicLink.
-
Add the IP addresses of both the source and destination HBase clusters to the whitelist of the LTS cluster.
-
Activate HDFS for both ApsaraDB for HBase clusters.
Ports for migration
Open the following ports on both clusters to allow LTS to transfer data.
| Configuration | Default port | Description |
|---|---|---|
| fs.default.name | 8020 | NameNode RPC |
| dfs.http.address | 50070 | NameNode HTTP management |
| dfs.datanode.ipc.address | 50020 | DataNode RPC server |
| dfs.datanode.address | 50010 | DataNode management |
| zookeeper.property.clientPort | 2181 | ZooKeeper client |
| hbase.regionserver.port | 16020 | HBase RegionServer |
| hbase.master.port | 16000 | HBase Master |