DocsICP FilingConsole
Documentation
Home Page Lindorm Getting Started Create an instance

Create an instance

Updated at:
Copy as MD
Product
My Favorites

You can create a Lindorm instance in the Lindorm console. This topic explains the steps for creating a Lindorm instance and the parameters you configure, including the billing method, region, storage type, and data engines.

Prerequisites

You must have a registered Alibaba Cloud account before you begin.

Free trial

Alibaba Cloud offers a free trial of Lindorm. You can visit Alibaba Cloud Free Trial to apply. Lindorm free trial tutorial.

Network requirements

If your application runs on an ECS instance, ensure the Lindorm and the ECS instance meet the following network requirements. View instance information.

  • Deploy the Lindorm and ECS instances in the same region. We recommend placing them in the same availability zone to reduce network latency.

  • The instances use the same network type.

Note

A VPC provides better security, so we recommend using one. If you use a VPC, make sure the Lindorm and ECS instances are in the same VPC.

Procedure

  1. Log on to the Lindorm console.

  2. On the Instances page, click Create.

    Note

    You can also go to the product details page and click Buy Now to create an instance.

  3. In the Commodity Type section, select the product type that best suits your business needs: Lindorm V1, Lindorm, or LindormTunnel channel service.

    Note

    Learn about product types in Product series.

  4. In the Billing Method section, select Subscription or Pay-as-you-go.

    Note

    You can change the billing method in the console after purchasing the instance.

    • Subscription: You pay for a subscription when you create the instance. This billing method is suitable for long-term use and is more cost-effective than pay-as-you-go; longer subscription terms receive larger discounts.

    • Pay-as-you-go: The system generates one billing order per hour based on the instance configuration and deducts the amount from your account balance. This billing method is suitable for short-term use. Release the instance when you no longer need it to save costs.

  5. Configure the instance parameters.

    Lindorm V1

    Parameter

    Description

    Basic instance fee

    Fixed to Lindorm Multi-modal Service.

    Deployment Method

    • Single-zone Deployment: Primary and secondary nodes in the same zone. Supports single-zone disaster recovery.

    • Multi-zone Deployment (HA): Primary and secondary nodes in different zones. Cross-zone disaster recovery. Supports LindormTable only.

    • Multi-zone Deployment (Basic): Primary and secondary nodes in different zones. Cross-zone disaster recovery. Supports all engines.

    Region

    Select the deployment region.

    Note

    • The region cannot be changed after the instance is created, so choose it carefully.

    • If your application runs on an ECS instance, choose the same region for the Lindorm instance. Otherwise, the instances cannot communicate over the internal network.

    Availability Zone

    Select an availability zone.

    Note

    If your application runs on an ECS instance, we recommend placing the Lindorm and ECS instances in the same availability zone to reduce network latency.

    Multi-zone

    This parameter is displayed only when Deployment Method is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic). You cannot choose an availability zone manually. Lindorm automatically selects an availability-zone combination in regions that support multiple availability zones.

    Network Type

    Fixed to VPC.

    VPC

    Select a VPC. If needed,Create and manage a VPC.

    vSwitch

    Select a vSwitch. If needed,Create a vSwitch.

    Note

    This parameter is not available if Deployment Method is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

    Primary Zone

    Select availability zones. Primary, secondary, and coordinator nodes must be in different zones.

    Note

    This parameter is displayed only when Deployment Method is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

    Secondary Zone

    Client Node Zone

    vSwitch for Primary Zone

    Select a vSwitch.

    Note

    This parameter is displayed only when Deployment Method is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

    vSwitch for Secondary Zone

    vSwitch for Client Node Zone

    Cluster Name

    Enter an instance name that helps you identify it later.

    Storage Type

    Available storage types are Standard Cloud Storage, Performance Cloud Storage, Capacity Cloud Storage, local SSD, and Big Data (local HDD). Storage types.

    • Standard: Suitable for scenarios that require real-time data access, such as feed data, chats, real-time reports, and online computing.

    • Performance: Suitable for scenarios that require low-latency data access, including ad auctions, user profiles, audience segmentation, real-time search, and risk control.

    • Capacity: Suitable for infrequently accessed data, such as monitoring logs, historical orders, audio and video archives, data lake storage, and offline computing.

    • Local SSD: This type uses local disks on a single physical server. It offers low latency, high random IOPS, and high throughput at a competitive cost. It is suitable for I/O-intensive online services such as online games, e-commerce, live streaming, and media, and meets the low-latency and high I/O performance requirements of I/O-intensive applications that use block storage.

    • Big Data: This type uses local disks on a single physical server. It offers low latency, high random IOPS, and high throughput at a competitive cost. It is suitable for internet and financial industries that need to store and analyze large volumes of data and perform offline computing.

    Select Engine Type

    Available engines include LindormTable, LindormTSDB, Lindorm Search, and Lindorm Stream. Choose the node specifications and number of nodes for each engine. For more information, see Select engine types. For node-sizing details, see Select node specifications and number of nodes.

    • LindormTable: Select the Node Spec of Wide Table Engine (HBase/Cassandra APIs) and Wide Table Nodes as needed. Specify the engine size in cores.

    • LindormTSDB: Select the Node Spec of Time Series Engine (TSDB API) and Time Series Engine Nodes as needed. Specify the engine size in cores.

    • Lindorm Search: Select the Node Spec of Search Engine (Solr API) and Search Engine Nodes as needed. Specify the engine size in cores.

    • Lindorm Stream: Select the Node Specifications of Streaming Engine Nodes and Number of Streaming Engine Nodes as needed. Specify the engine size in cores.

    Note

    • If you set Storage Type to Local SSD or Big Data, you cannot select node specifications for the data engines. You can only select the Node Spec of Local Disk and the number of nodes for the engines.

    • If Storage Type is set to Big Data, you cannot select Lindorm Stream.

    Storage Space

    Select the storage capacity for the instance.

    Purchase Capacity Storage

    Choose whether to enable capacity-oriented cloud storage for the instance. For more information, see Introduction to Capacity-Oriented Cloud Storage.

    Note

    Cloud storage instances provide usable capacity equal to the purchased capacity. Local-disk clusters use a three-replica architecture, so usable capacity is one-third of the total capacity.

    Capacity Storage

    Select the capacity of capacity-oriented cloud storage for the instance.

    Note

    This parameter is required only if you select Purchase Capacity Storage for the Yes parameter.

    Whether to activate the computing engine

    Choose whether to enable the compute engine.

    Subscription Length

    For subscription instances, select a monthly term of 1–9 months or an annual term of 1–3 years.

    Note

    To renew the instance automatically when it expires, select Auto-renewal Recommended and make sure your account has sufficient balance before the instance expires.

    Resource Group

    Select an existing resource group to manage the instance, or create a new one. For instructions, see Create a resource group.

    Lindorm

    Parameter

    Description

    Deployment Scenario

    • Single Zone: Primary and secondary nodes in the same zone. Supports single-zone disaster recovery.

    • Multi-zone Deployment (HA): Primary and secondary nodes in different zones. Cross-zone disaster recovery. Supports LindormTable only.

    • Multi-zone Deployment (Basic): Primary and secondary nodes in different zones. Cross-zone disaster recovery. Supports all engines.

    Instance name

    Enter an instance name that helps you identify it later.

    Region Type

    Select the deployment region.

    Note

    • The region cannot be changed after the instance is created, so choose it carefully.

    • If your application runs on an ECS instance, choose the same region for the Lindorm instance. Otherwise, the instances cannot communicate over the internal network.

    Availability Zone

    Select an availability zone.

    Note

    If your application runs on an ECS instance, we recommend placing the Lindorm and ECS instances in the same availability zone to reduce network latency.

    VPC

    Select a VPC. If needed,Create and manage a VPC.

    Create a VPC.

    Select a vSwitch. If needed,Create a vSwitch.

    Note

    This parameter is not available if Deployment Scenario is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

    Primary Zone

    Select availability zones. Primary, secondary, and coordinator nodes must be in different zones.

    Note

    This parameter is displayed only when Deployment Scenario is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

    Secondary Zone

    Coordinator Node Zone

    Primary AZ Switch

    Select a vSwitch.

    Note

    This parameter is displayed only when Deployment Scenario is set to Multi-zone Deployment (HA) or Multi-zone Deployment (Basic).

    Standby zone switch

    Coordination Node Availability Zone Switch

    Storage Type

    Available storage types are Standard Cloud Storage, Performance Cloud Storage, Capacity Cloud Storage, local SSD, and Big Data (local HDD). Storage types.

    • Performance: Suitable for scenarios that require low-latency data access, including ad auctions, user profiles, audience segmentation, real-time search, and risk control.

    • Standard: Suitable for scenarios that require real-time data access, such as feed data, chats, real-time reports, and online computing.

    • Big Data: This type uses local disks on a single physical server. It offers low latency, high random IOPS, and high throughput at a competitive cost. It is suitable for internet and financial industries that need to store and analyze large volumes of data and perform offline computing.

    • Local SSD: This type uses local disks on a single physical server. It offers low latency, high random IOPS, and high throughput at a competitive cost. It is suitable for I/O-intensive online services such as online games, e-commerce, live streaming, and media, and meets the low-latency and high I/O performance requirements of I/O-intensive applications that use block storage.

    Note

    This parameter is displayed only when Deployment Scenario is set to Single Zone.

    Instance Configuration

    Select the data engines you need. Click the image.png icon in the upper-right corner of a card to change the node type, specifications, and number of nodes, and to configure whether to attach cloud disks and, if so, their type and capacity.

    Choose the node specifications and number of nodes for each engine. For more information, see Select engine types. For node-sizing details, see Select node specifications and number of nodes.

    Whether to select capacity cloud storage

    Suitable for scenarios that require infrequent access to data, such as monitoring logs, historical orders, audio and video archiving, data lake storage, and offline computing.

    Choose whether to enable capacity-oriented cloud storage for the instance. For more information, see Introduction to Capacity-Oriented Cloud Storage.

    Note

    Cloud storage instances provide usable capacity equal to the purchased capacity. Local-disk clusters use a three-replica architecture, so usable capacity is one-third of the total capacity.

    Capacity-based cloud storage capacity

    Select the capacity of capacity-oriented cloud storage for the instance.

    Note

    This parameter is required only if you select Whether to select capacity cloud storage for the Yes parameter.

    Whether to activate the computing engine

    Choose whether to enable the compute engine.

    Duration

    For subscription instances, select a monthly term of 1–9 months or an annual term of 1–3 years.

    Note

    To renew the instance automatically when it expires, select Auto-renewal Recommended and make sure your account has sufficient balance before the instance expires.

    Resource Group

    Select an existing resource group to manage the instance, or create a new one. For instructions, see Create a resource group.

    LindormTunnel channel service

    Parameter

    Description

    Region and Zone

    Select the deployment region.

    Note

    • The region cannot be changed after the instance is created, so choose it carefully.

    • If your application runs on an ECS instance, choose the same region for the Lindorm instance. Otherwise, the instances cannot communicate over the internal network.

    Zone

    Select an availability zone.

    Note

    If your application runs on an ECS instance, we recommend placing the Lindorm and ECS instances in the same availability zone to reduce network latency.

    Network Type

    Fixed to VPC.

    Virtual Private Cloud (VPC)

    Select a VPC. If needed,Create and manage a VPC.

    vSwitch

    Select a vSwitch. If needed,Create a vSwitch.

    Cluster Name

    Enter an instance name that helps you identify it later.

    Node Specifications

    Select the required node specifications.

    Nodes

    Enter the required number of nodes.

    Duration

    For subscription instances, select a monthly term of 1–9 months or an annual term of 1–3 years.

    Note

    To renew the instance automatically when it expires, select Auto-renewal Recommended and make sure your account has sufficient balance before the instance expires.

    Resource Group

    Select an existing resource group to manage the instance, or create a new one. For instructions, see Create a resource group.

  6. After you configure the parameters, click Buy Now.

  7. On the Confirm Order page, review and accept the terms of service, then click Pay.

  8. After the payment is complete, click Go to Console to open the Lindorm console.

Previous：Getting started overviewNext：Configure a whitelist