Updated on 2024-11-20 GMT+08:00

Creating a Logstash Cluster

Prerequisites

You have planned the Logstash clusters that need to be created by following the instructions in Logstash Cluster Planning Suggestions.

Creating a Cluster

  1. Log in to the CSS management console.
  2. On the Dashboard page, click Create Cluster in the upper right corner. The Create Cluster page is displayed.

    Alternatively, choose Clusters > Logstash in the navigation tree on the left. Click Create Cluster in the upper right corner.

  3. On the Basic Configuration page, configure basic information and resources for the Logstash cluster.
    Table 1 Basic configuration of the Logstash cluster

    Parameter

    Description

    Billing Mode

    Select Yearly/Monthly or Pay-per-use.

    • Yearly/monthly: You pay for the cluster by year or month, in advance. The service duration range is one month to three years. If you plan to use a cluster for more than nine months, you are advised to purchase a yearly package for a better price.
    • Pay-per-use: You are billed by actual duration of use, with a billing cycle of one hour. For example, 58 minutes of usage will be rounded up to an hour and billed.

    Required Duration

    The duration for which the purchased EIP will be used. The duration must be specified if the Billing Mode is set to Yearly/Monthly.

    Configure automatic renewal if necessary.

    Region

    Select the region where the cluster is located.

    ECSs in different regions cannot communicate with each other over an intranet. For lower network latency and quicker resource access, select the nearest region.

    AZ

    Select AZs associated with the cluster region.

    A maximum of two AZs can be configured. For details about the use of multiple AZs, see Planning Cluster AZs.

    Type

    Select Logstash.

    Version

    Select a cluster version from the drop-down list box.

    Name

    Cluster name, which contains 4 to 32 characters. Only letters, numbers, hyphens (-), and underscores (_) are allowed and the value must start with a letter.

    Nodes

    Number of nodes in a cluster. in the range 1 to 100.

    CPU Architecture

    Only x86 is supported.

    Node Specifications

    Specifications of nodes in a cluster. You can select node specifications based on your needs. Each cluster supports only one specification. For details, see ECS Types.

    Node Storage Type

    If you select EVS for node storage, you need to further select the EVS disk type. Options include Common I/O, High I/O, Ultra-high I/O, and Extreme SSD.

    NOTE:

    If the type of storage in use is not supported, the storage type is not displayed.

    Node Storage Capacity

    Node storage capacity. Its value range varies with node specifications.

    It can only be set to 40 GB for a Logstash cluster.

    Enterprise Project

    When creating a CSS cluster, you can bind an enterprise project to the cluster if you have enabled the enterprise project function.

    Select an enterprise project from the Enterprise Project drop-down list, or click View Enterprise Project to go to the Enterprise Project Management Service page and check existing enterprise projects.

  4. Click Next: Network.
  5. On the Network page, configure the network and security group settings for the Logstash cluster.
    Table 2 Parameter description

    Parameter

    Description

    VPC

    Specify a VPC to isolate the cluster's network.

    Click View VPC to go to the VPC management console and check the created VPCs or VPCs shared with the current account.

    If no VPC is available, contact the CSS administrator to create a new VPC. For details, see Creating a VPC and Subnet.

    NOTE:

    The VPC must contain CIDRs. Otherwise, cluster creation will fail. By default, a created VPC contains CIDRs.

    Subnet

    A subnet provides dedicated network resources that are isolated from other networks, improving network security.

    Select a subnet needed by the cluster in the current VPC. You may select a subnet in a shared VPC.

    Security Group

    A security group serves as a virtual firewall that provides access control policies for clusters.

    Select a security group for the cluster. Click View Security Group to go to the security group list, where you can view details about security groups.

    NOTE:

    Ensure that Port Range/ICMP Type is Any or a port range includes port 9200 for the selected security group.

    Figure 1 Configuring network specifications
  6. Click Next: Advanced Settings.
  7. On the Advanced Settings page, configure advanced settings for the Logstash cluster.

    If you select Custom, you can set tags.

    • Default: Tags are disabled by default.
    • Custom: Configure Tags for the cluster if necessary.

    Tags

    Adding tags to clusters can help you identify and manage your cluster resources. You can customize tags or use tags preset by Tag Management Service (TMS).

    If your organization has configured tag policies for CSS, add cluster tags based on these policies. If a tag does not comply with the tag policies, cluster creation may fail. Contact the administrator to learn more about tag policies.

    Table 3 Tag rules

    Parameter

    Description

    Tag Key

    • Must be unique in a cluster.
    • Enter up to 64 characters.
    • It can contain only numbers, letters, Chinese characters, and the following special characters: _.:=+-@ The value cannot start or end with a space.
    • Cannot be blank.

    Tag Value

    • Enter up to 64 characters.
    • It can contain only numbers, letters, Chinese characters, and the following special characters: _.:=+-@ The value cannot start or end with a space.
    • Cannot be blank.
  8. Click Next: Confirm Configuration. Confirm the settings, and click Create Now to create the cluster.
  9. Click Back to Cluster List to switch to the Clusters page. The cluster you created is listed on the displayed page and its status is Creating. If the cluster is successfully created, its status will change to Available.

    If cluster creation fails, try creating the cluster again by rectifying the errors returned.