Help Center> Distributed Message Service for Kafka> User Guide (Kuala Lumpur Region)> Buying an Instance
Updated on 2022-08-12 GMT+08:00
View PDF

Buying an Instance

Scenario

DMS for Kafka provides Kafka instances, which are physically isolated and exclusively occupied by each tenant. You can customize the computing capabilities and storage space of an instance based on service requirements.

Before You Start

  • Before buying a Kafka instance, ensure that a VPC configured with security groups and subnets is available.
  • The broker quantity varies according to the underlying resources, and the underlying resources vary from region to region. Therefore, different instances have different broker quantities.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner to select a region.

    Select the same region as your application service.

  3. Click and choose Application > Distributed Message Service for Kafka to open the console of DMS for Kafka.
  4. Click Buy Instance in the upper right corner of the page.

    By default, you can create a maximum of 100 Kafka instances for each project. To create more instances, contact customer service to increase your quota.

  5. Specify Billing Mode, Region, Project, and AZ.
  6. Enter an instance name and select an enterprise project.
  7. Configure the following instance parameters:

    1. Version: Currently, Kafka v1.1.0, v2.3.0, and v2.7 are supported. v2.7 is recommended.
    2. CPU Architecture: Currently, only x86 architecture is supported.
    3. Specifications:

      You can view the ECS quantity and flavor, the maximum number of partitions allowed, and number of consumer groups recommended for each bandwidth option.

      The Maximum Partitions parameter indicates the maximum number of partitions that can be created for a Kafka instance. If the total number of partitions of all topics exceeds this threshold, topic creation will fail.

    4. Storage Space: Total disk space for storing the instance data.

      The storage space is the total space to be consumed by all replicas. Specify the storage space based on the expected service message size and the number of replicas. For example, if the required disk size to store the data for the retention period is 100 GB, the disk capacity must be at least: 100 GB x Number of replicas + 100 GB (reserved).

      Disks are formatted when an instance is created. As a result, the actual available disk space is 93% to 95% of the total disk space.

      • 100 MB/s bandwidth: The value range of Storage Space is 600–90,000 GB.
      • 300 MB/s bandwidth: The value range of Storage Space is 1200–90,000 GB.
      • 600 MB/s bandwidth: The value range of Storage Space is 2400–90,000 GB.
      • 1200 MB/s bandwidth: The value range of Storage Space is 4800–90,000 GB.
      • High I/O + 100 MB/s bandwidth: If the average message size is 1 KB, the transactions per second (TPS) can reach 100,000 in high throughput scenarios and 60,000 in synchronous replication scenarios.
      • High I/O + 300 MB/s bandwidth: If the average message size is 1 KB, the TPS can reach 300,000 in high throughput scenarios and 150,000 in synchronous replication scenarios.
      • Ultra-high I/O + 100 MB/s bandwidth: If the average message size is 1 KB, the TPS can reach 100,000 in high throughput scenarios and 80,000 in synchronous replication scenarios.
      • Ultra-high I/O + 300 MB/s bandwidth: If the average message size is 1 KB, the TPS can reach 300,000 in high throughput scenarios and 200,000 in synchronous replication scenarios.
      • Ultra-high I/O + 600 MB/s bandwidth: If the average message size is 1 KB, the TPS can reach 600,000 in high throughput scenarios and 300,000 in synchronous replication scenarios.
      • Ultra-high I/O + 1200 MB/s bandwidth: If the average message size is 1 KB, the TPS can reach 1,200,000 in high throughput scenarios and 400,000 in synchronous replication scenarios.
    5. Capacity Threshold Policy: policy used when the disk usage reaches the threshold. The default capacity threshold is 95%.
      • Automatically delete: Messages can be created and retrieved, but 10% of the earliest messages will be deleted to ensure sufficient disk space. This policy is suitable for scenarios where no service interruption can be tolerated. Data may be lost.
      • Stop production: New messages cannot be created, but existing messages can still be retrieved. This policy is suitable for scenarios where no data loss can be tolerated.
    6. Select a VPC and a subnet.

      A VPC provides an isolated virtual network for your Kafka instances. You can configure and manage the network as required.

      After the Kafka instance is created, its VPC and subnet cannot be changed.

    7. Select a security group.

      A security group is a set of rules that control access to Elastic Cloud Servers (ECSs). It provides access policies for mutually trusted ECSs with the same security protection requirements in the same VPC.

      You can click Manage Security Group to view or create security groups on the network console.

  8. Configure the username and password for logging in to Kafka Manager.

    Kafka Manager is an open-source tool for managing Kafka clusters. After a Kafka instance is created, you can go to the instance details page to obtain the address for logging in to Kafka Manager. In Kafka Manager, you can view the monitoring statistics and broker information of your Kafka clusters.

  9. Click Advanced Settings to configure more parameters.

    1. Configure Kafka SASL_SSL.

      This parameter indicates whether to enable SSL authentication when a client connects to the instance. If you enable Kafka SASL_SSL, data will be encrypted before transmission to enhance security.

      This setting cannot be changed after the instance is created. If you want to use a different SASL_SSL setting after the instance is created, you must create a new instance.

      If you enable Kafka SASL_SSL, you must also set the username and password for accessing the instance.

    2. Configure Automatic Topic Creation.

      If it is enabled, a topic will be automatically created with 3 partitions and 3 replicas when a message is created in or retrieved from a topic that does not exist.

    3. Specify Tags.

      Tags are used to identify cloud resources. When you have many cloud resources of the same type, you can use tags to classify them by dimension (for example, use, owner, or environment).

      • If you have predefined tags, select a predefined pair of tag key and value. Click View predefined tags on the right. On the Tag Management Service (TMS) console, view predefined tags or create tags.
      • You can also create new tags by specifying Tag key and Tag value.

      Up to 20 tags can be added to each Kafka instance. For details about the requirements on tags, see Managing Instance Tags.

    4. Enter a description of the instance.

  10. Click Buy.
  11. Confirm the instance information and click Submit.
  12. Return to the instance list and check whether the Kafka instance has been created.

    It takes 3 to 15 minutes to create an instance. During this period, the instance status is Creating.

    • If the instance is created successfully, its status changes to Running.
    • If the instance fails to be created, view Instance Creation Failures. Delete the instance by referring to Deleting an Instance and create another instance. If the instance creation fails again, contact customer service.

      Instances that fail to be created do not occupy other resources.