This topic describes how to connect different network environments when you use ApsaraDB for HBase.
Source cluster network | Destination cluster network | Supported by Lindorm Tunnel Service (LTS) | How to connect networks |
---|---|---|---|
VPC | Same virtual private cloud (VPC) network | Yes | Associate your LTS cluster with the source and destination HBase clusters in the LTS console. |
VPC | Different VPC network | Yes |
|
Classic network | Same classic network | No |
|
Classic network | VPC | Yes |
|
Classic network | Classic network for ApsaraDB for HBase | No |
|
Classic network for ApsaraDB for HBase | VPC | No |
|
Notes
You are subject to some limits when you establish connections based on Express Connect or ClassicLink.
Ports for migration
Type | Default port | Description |
---|---|---|
fs.default.name | 8020 | The port for NameNode RPC interaction |
dfs.http.address | 50070 | The port for NameNode management over HTTP |
dfs.datanode.ipc.address | 50020 | The port of the DataNode RPC server |
dfs.datanode.address | 50010 | The port used for DataNode management |
zookeeper.property.clientPort | 2181 | The ZooKeeper port |
hbase.regionserver.port | 16020 | The port bound to the HBase RegionServer |
hbase.master.port | 16000 | The port bound to the HBase Master |