Specify the instance series
Lindorm is available in the following series to meet different business requirements: Lindorm, Lindorm New Edition, and LTS.
Lindorm: Instances of this series are individually deployed as individual clusters and provide the following engines: wide table engine, time series engine, search engine, file engine, compute engine, and streaming engine. This series is applicable to the production scenarios of large enterprises, such as Internet of Vehicles (IoV), Internet of Things (IoT), Industrial Internet of Things (IIoT), risk control, billing, advertising, feeds, and data dashboard. Lindorm instances can be deployed in a single zone or multiple zones to meet different levels of disaster recovery requirements.
Lindorm New Edition: Instances of this series supports the wide table engine, time series engine, and LTS. This series is suitable for large- and medium-sized enterprises that use Lindorm for production, individual developers who want to learn the features of Lindorm, and small enterprises that use Lindorm for feature verification, development, and testing.
LTS: Instances of this series provide features such as data migration, change tracking, and data backup and restoration.
For more information about Lindorm series, see Series.
Create a Lindorm instance
Create a Lindorm New Edition instance that is suitable for production, testing, and learning
In the Product Type section of the buy page, select Lindorm New Edition Available for Purchase.
Set the Billing Method parameter to Subscription or Pay-as-you-go.
Subscription: If you purchase a subscription instance, you must pay an upfront fee for the instance. For long-term usage, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You are provided with larger discounts for longer subscription periods.
Pay-as-you-go: You are charged for your instance based on the instance specification. Bills are generated on an hourly basis. Fees are automatically deducted from your account. For short-term use, we recommend that you select the pay-as-you-go billing method. If you no longer need a pay-as-you-go instance, you can release the instance to reduce costs.
Note You can change the billing method of an instance after it is created. For more information, see Billing methods.
Set the Edition parameter to Production or Test and the Deployment Method parameter to Single-zone Deployment.
Note We recommend that you select an edition based on your business requirements. For more information about the application scenarios for production and test instances, see Series.
Configure the region, zone, and VPC of the Lindorm New Edition instance.
Parameter | Description |
Region | Specify the region where you want to deploy the instance. We recommend that you note the following items when you select the region: Select the region of the instance based on the location where your business is deployed. An instance in a region that is closer to the location of your business can provide lower data transmission latency. If you purchase multiple Alibaba Cloud services and want to connect the services over VPCs, select the region in which your other Alibaba Cloud services are deployed.
For more information, see Select a region.
Important The region of an instance cannot be changed after the instance is created. |
Zone | Specify the zone where you want to deploy the instance.
Note Alibaba Cloud services deployed in different zones of the same region can communicate with each other over VPCs. |
Network Type | Specify the type of network where you want to deploy the instance. This parameter can be set only to VPC. |
VPC | Specify the ID of the VPC where you want to deploy the instance. If you purchase multiple Alibaba Cloud services, such as ECS, and want to connect the services over VPCs, select the VPC in which your other Alibaba Cloud services are deployed. Otherwise, the Lindorm instance cannot communicate with other services over the VPC.
Important If no VPC is displayed on the buy page, perform the following operations: Check whether a VPC is created in the selected region. If you create the instance as a RAM user, check whether the RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. You can select VPCs on the buy page after the two permissions are granted to the RAM user.
|
vSwitch | Specify the ID of the vSwitch to which you want the instance to connect.
Important If no vSwitch is displayed on the buy page, perform the following operations: Check whether a vSwitch is created in the selected zone. If you create the instance as a RAM user, check whether the RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. You can select vSwitches on the buy page after the two permissions are granted to the RAM user.
|
Instance Name | Specify the name used to identify and manage the instance. |
Configure the Instance Configuration parameter.
Select one or more engines based on your business requirements. If you do not need to purchase an engine, skip this parameter. For more information about the Lindorm engines, see Series. For more information about the engines and their application scenarios, see Engines and Overview.
After you select an engine, you can click the 
icon in the upper-right corner of the engine card to configure the number and specification of nodes, whether to attach disks, the type of disks to attach, and the capacity of the disks to attach.
Important The engines displayed in the Instance Configuration section are only the required engines when you purchase the instance. You can activate other supported engines that are not displayed in this section after the instance is created.
You cannot downgrade the specifications or reduce the number of nodes of a Lindorm New Edition instance. Select the specifications and number of nodes based on your business requirements to avoid unnecessary costs.
Disks cannot be attached to LTS engine nodes.
If you select the subscription billing method, specify the subscription duration of the instance and whether to enable auto-renewal.
To prevent your instance from being released after it expires, we recommend that you enable automatic renewal for the instance. For more information about the impact of instance expiration and how to renew an instance, see Expiration and overdue payments and Enable auto-renewal.
Important If you create the Lindorm instance as a RAM user, the RAM user must have the AliyunBSSOrderAccess permission to pay for the order of a subscription instance. If you create a pay-as-you-go instance, this permission is not required.
Specify the resource group of the instance.
You can manage resources, grant permissions on resources, and allocate resources costs based on resource groups. For more information, see What is Resource Group?.
Complete the payment according to the instructions on the buy page.
Create a single-zone Lindorm instance that supports all engines and is suitable for disaster recovery within a single data center
In the Product Type section of the buy page, select Lindorm.
Set the Billing Method parameter to Subscription or Pay-as-you-go.
Subscription: If you purchase a subscription instance, you must pay an upfront fee for the instance. For long-term usage, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You are provided with larger discounts for longer subscription periods.
Pay-as-you-go: You are charged for your instance based on the instance specification. Bills are generated on an hourly basis. Fees are automatically deducted from your account. For short-term use, we recommend that you select the pay-as-you-go billing method. If you no longer need a pay-as-you-go instance, you can release the instance to reduce costs.
Note You can change the billing method of an instance after it is created. For more information, see Billing methods.
Set the Deployment Method parameter to Single-zone Deployment.
Parameter | Description |
Deployment Method | Select Single-zone Deployment. The primary and secondary nodes of a single-zone Lindorm instance are deployed in the same zone. This deployment method can provide single-data center disaster recovery. |
Region | Specify the region where you want to deploy the instance. We recommend that you note the following items when you select the region: Select the region of the instance based on the location where your business is deployed. An instance in a region that is closer to the location of your business can provide lower data transmission latency. If you purchase multiple Alibaba Cloud services and want to connect the services over VPCs, select the region in which your other Alibaba Cloud services are deployed.
For more information, see Select a region.
Important The region of an instance cannot be changed after the instance is created. |
Zone | Specify the zone where you want to deploy the instance.
Note Alibaba Cloud services deployed in different zones of the same region can communicate with each other over VPCs. |
Network Type | Specify the type of network where you want to deploy the instance. This parameter can be set only to VPC. |
VPC | Specify the ID of the VPC where you want to deploy the instance. If you purchase multiple Alibaba Cloud services, such as ECS, and want to connect the services over VPCs, select the VPC in which your other Alibaba Cloud services are deployed. Otherwise, the Lindorm instance cannot communicate with other services over the VPC.
Important If no VPC is displayed on the buy page, perform the following operations: Check whether a VPC is created in the selected region. If you create the instance as a RAM user, check whether the RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. You can select VPCs on the buy page after the two permissions are granted to the RAM user.
|
vSwitch | Specify the ID of the vSwitch to which you want the instance to connect.
Important If no vSwitch is displayed on the buy page, perform the following operations: Check whether a vSwitch is created in the selected zone. If you create the instance as a RAM user, check whether the RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. You can select vSwitches on the buy page after the two permissions are granted to the RAM user.
|
Cluster Name | Specify the name used to identify and manage the instance. |
Configure the Storage Type parameter. You can select the storage type of the instance based on access latency, scenarios, supported engines, and prices. For more information, see Storage types.
Important The storage type of an instance cannot be changed after the instance is created.
Select the specification and number of nodes for Lindorm engines.
Select one or more engine based on your business requirements. For more information about the Lindorm engines, see Engines.
A Lindorm instance is deployed as a distributed cluster. Each engine must be deployed on at least two individual nodes to run tasks in a distributed manner.
If you do not need to purchase an engine, set the number of nodes for the engine to 0.
Important After the instance is created, you can change the number and specification of engine nodes, activate engines that are not purchased when you create the instance. However, you cannot deactivate engines that have been activated.
Specify the storage capacity of the instance. The storage capacity determines how much data that you can store in the instance. The method used to configure storage capacity varies with the storage type that you select.
Specify the capacity of Standard, Performance, or Capacity storage
Specify the value of Storage Space.
The storage capacity that you specify for this parameter is the actual capacity that you can use to store data.
For example, you purchase 200 GB of storage for the instance and want to store 100 GB of data in the instance. If the data size is compressed into 50 GB, only 50 GB of storage is used and 150 GB of free storage capacity is available.
You can scale up or down the storage capacity without the need to manually migrate data after the instance is created.
Specify a value for Purchase Cold Storage.
The Capacity type of storage is used to store historical data (cold data) that is infrequently accessed to reduce storage costs. For more information about Capacity storage, see Capacity storage.
You can purchase Capacity storage when you create the instance or enable Capacity storage after the instance is created.
Note If you set the Storage Type parameter to Capacity, this parameter is unavailable.
Specify the capacity of Local SSD or Local HDD
View the value of Disk Capacity of Each Node.
The value of Disk Capacity of Each Node indicates the storage capacity of the local disk for a single node. This value is determined based on the specification and number of nodes and cannot be specified. If the storage capacity specified by Disk Capacity of Each Node cannot meet your requirements, you can purchase cloud disks and use cloud disks together with local SSDs.
Lindorm instances that use local disks are deployed in a triple-replica architecture. The available storage capacity is one-third of the disk capacity that is displayed in the console.
For example, you purchase an instance that uses local SSDs and set the number of engine nodes to 3, the value of Disk Capacity of Each Node parameter is 894 GB on the buy page. After the instance is created, the total storage capacity of the instance is 2682 GiB in the console. However, the actual storage capacity that you can use is 894 GB (2682 × 1/3).
To improve the storage utilization of your instance, enable erasure coding to reduce the redundancy of data replicas in the instance. For more information, see Storage types.
Specify a value for Purchase Cold Storage.
Capacity storage is used to store historical data (cold data) that is infrequently accessed to reduce storage costs. For more information about Capacity storage, see Capacity storage.
You can purchase Capacity storage when you create the instance or enable Capacity storage after the instance is created.
Specify a value for Attach Disk.
If the storage capacity of local disks cannot meet your requirements and you do not want to purchase additional nodes, you can attach cloud disks to the instance and use cloud disks together with local disks.
Attached cloud disks use the same triple-replica architecture as local disks. The available storage capacity is one-third of the cloud disk capacity that is displayed in the console.
Note Capacity storage and cloud disks are not supported by instances that use Local HDDs for storage.
If you select the subscription billing method, specify the subscription duration of the instance and whether to enable auto-renewal.
To prevent your instance from being released after it expires, we recommend that you enable automatic renewal for the instance. For more information about the impact of instance expiration and how to renew an instance, see Expiration and overdue payments and Enable auto-renewal.
Important If you create the Lindorm instance as a RAM user, the RAM user must have the AliyunBSSOrderAccess permission to pay for the order of a subscription instance. If you create a pay-as-you-go instance, this permission is not required.
Specify the resource group of the instance.
You can manage resources, grant permissions on resources, and allocate resources costs based on resource groups. For more information, see What is Resource Group?.
Complete the payment according to the instructions on the buy page.
Create a multi-zone Lindorm (Basic Edition) instance that supports all engines and zone-disaster recovery within a period of time
In the Product Type section of the buy page, select Lindorm or Lindorm New Edition Available for Purchase.
Set the Billing Method parameter based on the product type:
Select Subscription if the Product Type parameter is set to Lindorm.
Select Subscription or Pay-as-you-go if the Product Type parameter is set to Lindorm New Edition Available for Purchase.
Note Subscription: If you purchase a subscription instance, you must pay an upfront fee for the instance. For long-term usage, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You are provided with larger discounts for longer subscription periods.
Pay-as-you-go: You are charged for your instance based on the instance specification. Bills are generated on an hourly basis. Fees are automatically deducted from your account. For short-term use, we recommend that you select the pay-as-you-go billing method. If you no longer need a pay-as-you-go instance, you can release the instance to reduce costs.
You can change the billing method of an instance after it is created. For more information, see Billing methods.
Set the Deployment Method parameter to Multi-zone Basic Edition.
Parameter | Description |
Deployment Method | Select Multi-zone Basic Edition. In a multi-zone instance, each region of a wide table has an individual replica in all zones. The data of replicas is synchronized by using the replica consensus protocol. Multi-zone instances are suitable for zone-disaster recovery. |
Region | Specify the region where you want to deploy the instance. We recommend that you take note of the following items when you select the region: Select the region of the instance based on the location where your business is deployed. An instance in a region that is closer to the location of your business can provide lower data transmission latency. If you purchase multiple Alibaba Cloud services and want to connect the services over VPCs, select the region in which your other Alibaba Cloud services are deployed.
|
Multi-zone Deployment | Select a combination of zones in which you want to deploy the instance. |
Network Type | Specify the type of network where you want to deploy the instance. This parameter can be set only to VPC. |
VPC | Specify the ID of the VPC where you want to deploy the instance. If you purchase multiple Alibaba Cloud services, such as ECS, and want to connect the services over VPCs, select the VPC in which your other Alibaba Cloud services are deployed. Otherwise, the Lindorm instance cannot communicate with other services over the VPC.
Important If no VPC is displayed on the buy page, perform the following operations: Check whether a VPC is created in the selected region. If you create the instance as a RAM user, check whether the RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. You can select VPCs on the buy page after the two permissions are granted to the RAM user.
|
Primary Zone | Select the primary zone in which the region replica of wide tables is deployed. |
vSwitch for Primary Zone | Select the vSwitch of the primary zone. |
Secondary Zone | Select the secondary zone in which another region replica of wide tables is deployed. The replicas in the primary zone and secondary zone are synchronized by using the replica consensus protocol. |
vSwitch for Secondary Zone | Select the vSwitch of the secondary zone. |
Coordinator Node Zone | Select the zone in which the coordinator node is deployed. The log node is also deployed in this zone. |
vSwitch | Select the vSwitch of the coordinator node zone. |
Cluster Name | Specify the name used to identify and manage the instance. |
Configure the Storage Type parameter. You can select the storage type of the instance based on access latency, scenarios, and prices. For more information, see Storage types.
Important The storage type of an instance cannot be changed after the instance is created.
Select the specification and number of nodes for Lindorm engines. If you do not need a specific engine, set the value to 0.
Lindorm
Select one or more engines based on your business requirements. For more information about descriptions and use cases of each engine type, see Engines.
Select the desired engine.
Click the 
icon to configure the engine information such as node specifications, quantity, whether to attach cloud disks, cloud disk type, and capacity per node.
Lindorm New Edition Available for Purchase
Select one or more engines based on your business requirements. For more information about descriptions and use cases of each engine type, see Engines.
Lindorm adopts a distributed cluster architecture where all engines run on independent nodes. To implement distributed processing capabilities, each engine must run on at least 2 nodes (at least 3 nodes when local disks are used).
Specify the storage capacity of the instance. The method used to configure storage capacity varies with the storage type that you select.
Note The Select Storage Type parameter is not displayed if you set the Product Type to Lindorm New Edition Available for Purchase.
Specify the capacity of Standard, Performance, or Capacity storage
Specify the value of Storage Space.
The storage capacity that you specify for this parameter is the actual capacity that you can use to store data.
For example, you purchase 200 GB of storage for the instance and want to store 100 GB of data in the instance. If the data size is compressed into 50 GB, only 50 GB of storage is used and 150 GB of free storage capacity is available.
You can scale up or down the storage capacity without the need to manually migrate data after the instance is created.
Specify a value for Purchase Cold Storage.
The Capacity type of storage is used to store historical data (cold data) that is infrequently accessed to reduce storage costs. For more information about Capacity storage, see Capacity storage.
You can purchase Capacity storage when you create the instance or enable Capacity storage after the instance is created.
Note If you set the Storage Type parameter to Capacity, this parameter is unavailable.
Specify the capacity of Local SSD or Local HDD
View the value of Disk Capacity of Each Node.
The value of Disk Capacity of Each Node indicates the storage capacity of the local disk for a single node. This value is determined based on the specification and number of nodes and cannot be specified. If the storage capacity specified by Disk Capacity of Each Node cannot meet your requirements, you can purchase cloud disks and use cloud disks together with local SSDs.
Lindorm instances that use local disks are deployed in a triple-replica architecture. The available storage capacity is one-third of the disk capacity that is displayed in the console.
For example, you purchase an instance that uses local SSDs and set the number of engine nodes to 3, the value of Disk Capacity of Each Node parameter is 894 GB on the buy page. After the instance is created, the total storage capacity of the instance is 2682 GiB in the console. However, the actual storage capacity that you can use is 894 GB (2682 × 1/3).
To improve the storage utilization of your instance, enable erasure coding to reduce the redundancy of data replicas in the instance. For more information, see Storage types.
Specify a value for Purchase Cold Storage.
Capacity storage is used to store historical data (cold data) that is infrequently accessed to reduce storage costs. For more information about Capacity storage, see Capacity storage.
You can purchase Capacity storage when you create the instance or enable Capacity storage after the instance is created.
Specify a value for Attach Disk.
If the storage capacity of local disks cannot meet your requirements and you do not want to purchase additional nodes, you can attach cloud disks to the instance and use cloud disks together with local disks.
Attached cloud disks use the same triple-replica architecture as local disks. The available storage capacity is one-third of the cloud disk capacity that is displayed in the console.
Note Capacity storage and cloud disks are not supported by instances that use local HDDs for storage.
If you select the subscription billing method, specify the subscription duration of the instance and whether to enable auto-renewal.
To prevent your instance from being released after it expires, we recommend that you enable automatic renewal for the instance. For more information about the impact of instance expiration and how to renew an instance, see Expiration and overdue payments and Enable auto-renewal.
Important If you create the Lindorm instance as a RAM user, the RAM user must have the AliyunBSSOrderAccess permission to pay for the order of a subscription instance. If you create a pay-as-you-go instance, this permission is not required.
Specify the resource group of the instance.
You can manage resources, grant permissions on resources, and allocate resources costs based on resource groups. For more information, see What is Resource Group?.
Complete the payment according to the instructions on the buy page.
Create a multi-zone Lindorm (High-availability Edition) instance that supports only the wide table engine and is suitable for zone-disaster recovery
Note Multi-zone Lindorm instances support only the wide table engine. If you need to use other engines, create a single-zone instance.
In the Product Type section of the buy page, select Lindorm.
Set the Billing Method parameter to Subscription or Pay-as-you-go.
Subscription: If you purchase a subscription instance, you must pay an upfront fee for the instance. For long-term usage, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You are provided with larger discounts for longer subscription periods.
Pay-as-you-go: You are charged for your instance based on the instance specification. Bills are generated on an hourly basis. Fees are automatically deducted from your account. For short-term use, we recommend that you select the pay-as-you-go billing method. If you no longer need a pay-as-you-go instance, you can release the instance to reduce costs.
Note You can change the billing method of an instance after it is created. For more information, see Billing methods.
Set the Deployment Method parameter to Multi-zone Deployment.
Parameter | Description |
Deployment Method | Select Multi-zone Deployment. In a multi-zone instance, each region of a wide table has an individual replica in all zones. The data of replicas is synchronized by using the replica consensus protocol. Multi-zone instances are suitable for zone-disaster recovery. |
Region | Specify the region where you want to deploy the instance. We recommend that you take note of the following items when you select the region: Select the region of the instance based on the location where your business is deployed. An instance in a region that is closer to the location of your business can provide lower data transmission latency. If you purchase multiple Alibaba Cloud services and want to connect the services over VPCs, select the region in which your other Alibaba Cloud services are deployed.
|
Multi-zone Deployment | Select a combination of zones in which you want to deploy the instance. |
Network Type | Specify the type of network where you want to deploy the instance. This parameter can be set only to VPC. |
VPC | Specify the ID of the VPC where you want to deploy the instance. If you purchase multiple Alibaba Cloud services, such as ECS, and want to connect the services over VPCs, select the VPC in which your other Alibaba Cloud services are deployed. Otherwise, the Lindorm instance cannot communicate with other services over the VPC.
Important If no VPC is displayed on the buy page, perform the following operations: Check whether a VPC is created in the selected region. If you create the instance as a RAM user, check whether the RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. You can select VPCs on the buy page after the two permissions are granted to the RAM user.
|
Primary Zone | Select the primary zone in which the region replica of wide tables is deployed. |
vSwitch for Primary Zone | Select the vSwitch of the primary zone. |
Secondary Zone | Select the secondary zone in which another region replica of wide tables is deployed. The replicas in the primary zone and secondary zone are synchronized by using the replica consensus protocol. |
vSwitch for Secondary Zone | Select the vSwitch of the secondary zone. |
Coordinator Node Zone | Select the zone in which the coordinator node is deployed. The log node is also deployed in this zone. |
vSwitch | Select the vSwitch of the coordinator node zone. |
Cluster Name | Specify the name used to identify and manage the instance. |
Configure the Storage Type parameter. You can select the storage type of the instance based on access latency, scenarios, and prices. For more information, see Storage types.
Important The storage type of an instance cannot be changed after the instance is created.
Select the specification and number of nodes for Lindorm engines.
Specify the specification and number of nodes of instances that use the Standard or Performance storage
Select a value for Node Spec of Wide Table Engine and Wide Table Nodes.
Select the specification based on the number of requests and regions for your business. For more information, see Select the number and specification of nodes.
The nodes of the wide table engine are deployed across the primary and secondary zones. Therefore, the number of wide table nodes must be a multiple of two. You must specify at least two wide table engine nodes in each zone.
Select a value for Log Node Specifications and Log Nodes.
Log nodes store the recorded WAL logs. The WAL logs of tables whose consistency level is strong are backed up to log nodes. Log nodes cannot be directly read or written by users. Therefore, we recommend that you keep the default values for the specification and number of log nodes. If large amounts of data is stored in your instance, contact technical support.
Specify the specification and number of nodes of instances that use the local SSD or local HDD
Select a value for Node Spec of Local Disk and Wide Table Nodes.
The wide table engine is deployed on the specified nodes that use local disks.
Select a value for Log Node Specifications and Log Nodes.
Log nodes store the recorded WAL logs. The WAL logs of tables whose consistency level is strong are backed up to log nodes. Log nodes cannot be directly read or written by users. Therefore, we recommend that you keep the default values for the specification and number of log nodes. If large amounts of data is stored in your instance, contact technical support.
Specify the storage capacity of the instance. The method used to configure storage capacity varies with the storage type that you select.
Specify the capacity of Standard or Performance storage
Select a value for Storage per Core Node.
The available storage capacity of the instance is half of the capacity that is specified for this parameter.
For example, if you set the value of this parameter to 400 GB and the number of wide table nodes to 4, the available storage capacity of the instance is 800 GB.
You can scale up or down the disk capacity based on your requirements after the instance is created.
Select a value for Log Node Disk Type and Storage per Log Node.
Select a disk type for log nodes based on your business requirements. Valid values:
The storage capacity that you specify for Log Node Capacity is the actual capacity that you can use to store logs.
Capacity storage is not supported by multi-zone Lindorm instances.
Note You can change the values of Storage per Core Node and Storage per Log Node to scale the storage capacity .
Specify the capacity of local SSD or local HDD
Select a value for Log Node Disk Type and Storage per Log Node.
Select a disk type for log nodes based on your business requirements. Valid values:
The storage capacity that you specify for Log Node Capacity is the actual capacity that you can use to store logs.
View the value of Disk Capacity of Each Node.
The value of Disk Capacity of Each Node indicates the storage capacity of the local disk for a single node. This value is determined based on the specification and number of nodes and cannot be specified. If the storage capacity specified by Disk Capacity of Each Node cannot meet your requirements, you can purchase cloud disks and use cloud disks together with local SSDs.
Lindorm instances that use local disks are deployed in a triple-replica architecture. The available storage capacity is one-third of the disk capacity that is displayed in the console.
For example, you purchase an instance that uses local SSDs and set the number of engine nodes to 3, the value of Disk Capacity of Each Node parameter is 894 GB on the buy page. After the instance is created, the total storage capacity of the instance is 2682 GiB in the console. However, the actual storage capacity that you can use is 894 GB (2682 × 1/3).
To improve the storage utilization of your instance, enable erasure coding to reduce the redundancy of data replicas in the instance. For more information, see Storage types.
Capacity storage is not supported by multi-zone Lindorm instances.
If you select the subscription billing method, specify the subscription duration of the instance and whether to enable auto-renewal.
To prevent your instance from being released after it expires, we recommend that you enable automatic renewal for the instance. For more information about the impact of instance expiration and how to renew an instance, see Expiration and overdue payments and Enable auto-renewal.
Important If you create the Lindorm instance as a RAM user, the RAM user must have the AliyunBSSOrderAccess permission to pay for the order of a subscription instance. If you create a pay-as-you-go instance, this permission is not required.
Specify the resource group of the instance.
You can manage resources, grant permissions on resources, and allocate resources costs based on resource groups. For more information, see What is Resource Group?.
Complete the payment according to the instructions on the buy page.
Create an LTS instance that is suitable for data migration and synchronization
In the Product Type section of the buy page, select Lindorm Tunnel Service.
Set the Billing Method parameter to Subscription or Pay-as-you-go.
Subscription: If you purchase a subscription instance, you must pay an upfront fee for the instance. For long-term usage, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You are provided with larger discounts for longer subscription periods.
Pay-as-you-go: You are charged for your instance based on the instance specification. Bills are generated on an hourly basis. Fees are automatically deducted from your account. For short-term use, we recommend that you select the pay-as-you-go billing method. If you no longer need a pay-as-you-go instance, you can release the instance to reduce costs.
Note You can change the billing method of an instance after it is created. For more information, see Billing methods.
Select the region, zone, and VPC in which you want to create the LTS instance.
Parameter | Description |
Region | Specify the region where you want to deploy the instance. We recommend that you note the following items when you select the region: Select the region of the instance based on the location where your business is deployed. An instance in a region that is closer to the location of your business can provide lower data transmission latency. If you purchase multiple Alibaba Cloud services and want to connect the services over VPCs, select the region in which your other Alibaba Cloud services are deployed.
For more information, see Select a region.
Important The region of an instance cannot be changed after the instance is created. |
Zone | Specify the zone where you want to deploy the instance.
Note An ECS instance and a Lindorm instance can communicate with each other even if they are deployed in different zones. However, if your application is deployed on an ECS instance, we recommend that you deploy the Lindorm instance in the same zone as the ECS instance to reduce network latency. However, a Lindorm instance and an ECS instance can still communicate with each other even if they are deployed in different zones. |
Network Type | Specify the type of network where you want to deploy the instance. This parameter can be set only to VPC. |
VPC | Specify the ID of the VPC where you want to deploy the instance. If you purchase multiple Alibaba Cloud services, such as ECS, and want to connect the services over VPCs, select the VPC in which your other Alibaba Cloud services are deployed. Otherwise, the Lindorm instance cannot communicate with other services over the VPC.
Important If no VPC is displayed on the buy page, perform the following operations: Check whether a VPC is created in the selected region. If you create the instance as a RAM user, check whether the RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. You can select VPCs on the buy page after the two permissions are granted to the RAM user.
|
vSwitch | Specify the ID of the vSwitch to which you want the instance to connect.
Important If no vSwitch is displayed on the buy page, perform the following operations: Check whether a vSwitch is created in the selected zone. If you create the instance as a RAM user, check whether the RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. You can select vSwitches on the buy page after the two permissions are granted to the RAM user.
|
Cluster Name | Specify the name used to identify and manage the instance. |
Select the specification and number of nodes for the instance.
If you select the subscription billing method, specify the subscription duration of the instance and whether to enable auto-renewal.
To prevent your instance from being released after it expires, we recommend that you enable automatic renewal for the instance. For more information about the impact of instance expiration and how to renew an instance, see Expiration and overdue payments and Enable auto-renewal.
Important If you create the Lindorm instance as a RAM user, the RAM user must have the AliyunBSSOrderAccess permission to pay for the order of a subscription instance. If you create a pay-as-you-go instance, this permission is not required.
Specify the resource group of the instance.
You can manage resources, grant permissions on resources, and allocate resources costs based on resource groups. For more information, see What is Resource Group?.
Complete the payment according to the instructions on the buy page.
FAQ
What do I do if a message is displayed on the buy page to indicate that the inventory resources are insufficient?
This message is displayed because resources in the selected zone are insufficient. Create the instance in another zone.
What do I do if a message is displayed on the buy page to indicate that the authentication fails?
If you create a Lindorm instance as a Resource Access Management (RAM) user, make sure that the RAM user has the following permissions:
Lindorm and Lindorm New Edition
The permissions required by a RAM user to create an instance vary with the billing method of the instance.
Subscription: AliyunLindormFullAccess, AliyunHBaseReadOnlyAccess, AliyunBSSOrderAccess.
Pay-as-you-go: AliyunLindormFullAccess, AliyunHBaseReadOnlyAccess.
For more information about how to view the permissions of a RAM user, see View the information about a RAM user.
If your RAM user does not have required permissions, contact the owner of the Alibaba Cloud account to grant permissions to the RAM user. For more information, see Grant permissions to a RAM user.
Why cannot I select VPCs and vSwitches?
In most cases, this issue occurs for the following reasons:
No VPC or vSwitch is created in the selected region and zone. Make sure that VPCs and vSwitches are created in the selected region and zone.
The RAM user that is used to create the instance does not have the required permissions. Make sure that the RAM user has the AliyunLindormFullAccess and AliyunHBaseReadOnlyAccess permissions. You can select VPCs and vSwitches after the two permissions are granted to the RAM user.
Why cannot I view the instance I just purchased in the console?
The Lindorm instance becomes available about 20 minutes after you purchase it. If the instance is still not displayed in the console 20 minutes after you purchase it, go to the Order Management page to check whether the instance is refunded. If you receive a refund, the instance failed to be created. You can create the instance again. If the issue persists, submit a ticket.
Am I charged fees when I use the instance that I create?
You are charged the following fees when you use a Lindorm instance:
Enable billed features. For example, you are charged fees when you enable the backup feature of the wide table engine or activate the compute engine. You are prompted before you enable a billed feature. You can decide whether to enable the feature. For more information about the billable items of Lindorm, see Overview.
Upgrade the configuration of instances or scale up instances. For example, you are charged fees when you add nodes for an instance, change the node specification of an instance, or scale up the storage capacity of an instance. You are prompted before you perform configuration upgrade and scaling operations. For more information, see Billing of configuration changes.
Can I release an instance? Am I charged fees for a released instance?
If you no longer need the Lindorm, Lindorm New Edition, or LTS instance, you can release the instance.
You are no longer charged fees for the instance after the instance is released.