Lindorm Tunnel Service (LTS) migrates data from ApsaraDB for HBase clusters. LTS supports full historical data migration and incremental real-time synchronization.
Prerequisites
Before you begin, make sure that you have:
-
An Alibaba Cloud account with access to the ApsaraDB for HBase console
Purchase an LTS cluster
-
Log on to the ApsaraDB for HBase console.
-
In the left-side navigation pane, click Clusters. On the page that appears, click Create BDS Cluster.
-
Configure the following parameters.
Parameter
Description
Product Type
Select a product type. Four options are available: HBase Cluster Subscription, HBase Cluster PAYG, HBase Single Subscription, and HBase Single PAYG. Select a pay-as-you-go type for one-time migration tasks. Select a subscription type for long-term real-time synchronization tasks.
Service
Select BDS to purchase an LTS cluster. Other options include HBase (Standard, HBaseUE(Lindorm), Serverless) and Spark.
Version
Optional.
Cluster Name
Enter a custom name for the cluster.
Region
Select the region where you want to deploy the instance.
Zone
Select a zone. A zone is an independent physical location within a region.
Network Type
Select a network type. A virtual private cloud (VPC) provides higher security and better performance than a classic network. We recommend that you select VPC. If you select classic network, you must configure security groups or whitelist policies to block unauthorized access.
vpcId
Select the VPC ID.
vswitchID
Select the vSwitch ID.
Core Node Specification
Select the core node specification.
Core Nodes
Specify the number of core nodes. See Recommended cluster size for guidance.
Whether to Use Cold Storage
Select Yes or No. Cold storage provides separate storage media for data archiving and less frequently accessed historical data. If you select Yes, set the cold storage capacity.
Resource Group
Select an existing resource group or create a new one.
-
Click Buy Now. The Confirm Order page appears.
Recommended cluster size
Select the number of data sync nodes based on the total data volume to migrate.
|
Data volume |
Node specification |
Number of data sync nodes |
|
Less than 1 TB |
4 cores 8G |
1 |
|
1 TB to 10 TB |
4 cores 8G |
2 to 5 |
|
More than 10 TB |
4 cores 8G |
More than 5 |
Migration performance per node
Each data sync node uses a 4-core 8 GB specification. The maximum migration rate per node ranges from 50 MB/s to 100 MB/s. The following table describes the throughput capacity per node.
|
Migration type |
Threads per node |
Throughput per node |
|
Historical data (full migration) |
5 concurrent threads for replicating HBase files |
50 MB/s to 100 MB/s |
|
Incremental synchronization (log replication) |
5 logs concurrently processed |
50 MB/s to 60 MB/s |