From 1588318a68d9ff552af004aec874bdbea71d069a Mon Sep 17 00:00:00 2001 From: "Chen, Junjie" Date: Wed, 14 Aug 2024 12:31:58 +0000 Subject: [PATCH] DMS UMN 20240723 version Reviewed-by: Antonova, Ekaterina Co-authored-by: Chen, Junjie Co-committed-by: Chen, Junjie --- docs/dms/umn/ALL_META.TXT.json | 365 ++++++++----- docs/dms/umn/CLASS.TXT.json | 480 ++++++++++-------- docs/dms/umn/CreateUserAndGrantPolicy.html | 2 +- docs/dms/umn/Kafka-client-best-practice.html | 2 +- .../umn/ProductDescPrivilegeManagement.html | 170 +++++-- docs/dms/umn/TagManagement.html | 6 +- docs/dms/umn/en-us_image_0000001314995070.png | Bin 0 -> 348 bytes docs/dms/umn/en-us_image_0000001382159745.png | Bin 17406 -> 0 bytes docs/dms/umn/en-us_image_0000001926137265.png | Bin 15329 -> 0 bytes docs/dms/umn/en-us_image_0000001987139953.png | Bin 0 -> 15196 bytes ...9.png => en-us_image_0000001992720829.png} | Bin docs/dms/umn/en-us_image_0000001998520149.png | Bin 0 -> 42475 bytes docs/dms/umn/kafka-bp-migration.html | 46 +- docs/dms/umn/kafka-dnat.html | 7 +- docs/dms/umn/kafka-faq-200426013.html | 2 +- docs/dms/umn/kafka-qs-0409001.html | 79 ++- docs/dms/umn/kafka-ug-00001.html | 10 +- docs/dms/umn/kafka-ug-0001.html | 27 +- docs/dms/umn/kafka-ug-0002.html | 17 +- docs/dms/umn/kafka-ug-0003.html | 33 +- docs/dms/umn/kafka-ug-0004.html | 8 +- docs/dms/umn/kafka-ug-0006.html | 52 +- docs/dms/umn/kafka-ug-0007.html | 259 +++++----- docs/dms/umn/kafka-ug-0011.html | 2 +- docs/dms/umn/kafka-ug-0012.html | 60 ++- docs/dms/umn/kafka-ug-0014.html | 75 ++- docs/dms/umn/kafka-ug-0015.html | 57 ++- docs/dms/umn/kafka-ug-0034.html | 164 ++++++ docs/dms/umn/kafka-ug-0035.html | 103 ++++ docs/dms/umn/kafka-ug-0038.html | 34 +- docs/dms/umn/kafka-ug-0041.html | 22 +- docs/dms/umn/kafka-ug-0053.html | 5 +- docs/dms/umn/kafka-ug-0056.html | 5 +- docs/dms/umn/kafka-ug-0061.html | 2 +- docs/dms/umn/kafka-ug-0065.html | 27 + docs/dms/umn/kafka-ug-0069.html | 3 +- docs/dms/umn/kafka-ug-0319001.html | 4 +- docs/dms/umn/kafka-ug-180413001.html | 2 +- docs/dms/umn/kafka-ug-180413002.html | 432 +++++++++------- docs/dms/umn/kafka-ug-180418002.html | 31 +- docs/dms/umn/kafka-ug-180524001.html | 11 +- docs/dms/umn/kafka-ug-180604013.html | 166 +++--- docs/dms/umn/kafka-ug-180604014.html | 174 ++++--- docs/dms/umn/kafka-ug-180604015.html | 5 +- docs/dms/umn/kafka-ug-180604016.html | 5 +- docs/dms/umn/kafka-ug-180604018.html | 102 ++-- docs/dms/umn/kafka-ug-180604019.html | 44 +- docs/dms/umn/kafka-ug-180604020.html | 19 +- docs/dms/umn/kafka-ug-180801001.html | 27 +- docs/dms/umn/kafka-ug-181221001.html | 85 ++-- docs/dms/umn/kafka-ug-190605001.html | 9 +- docs/dms/umn/kafka-ug-190904001.html | 5 +- docs/dms/umn/kafka-ug-200119002.html | 2 +- docs/dms/umn/kafka-ug-200506001.html | 4 +- docs/dms/umn/kafka_ug_0016.html | 2 + docs/dms/umn/kafka_ug_0017.html | 30 ++ docs/dms/umn/kafka_ug_0018.html | 37 ++ docs/dms/umn/kafka_ug_0021.html | 47 +- docs/dms/umn/kafka_ug_0023.html | 229 +++++---- docs/dms/umn/kafka_ug_0024.html | 4 +- docs/dms/umn/kafka_ug_0027.html | 2 +- docs/dms/umn/kafka_ug_0041.html | 23 + docs/dms/umn/kafka_ug_0043.html | 6 +- docs/dms/umn/kafka_ug_0044.html | 10 +- docs/dms/umn/kafka_ug_0045.html | 8 +- docs/dms/umn/kafka_ug_0046.html | 17 +- 66 files changed, 2368 insertions(+), 1298 deletions(-) create mode 100644 docs/dms/umn/en-us_image_0000001314995070.png delete mode 100644 docs/dms/umn/en-us_image_0000001382159745.png delete mode 100644 docs/dms/umn/en-us_image_0000001926137265.png create mode 100644 docs/dms/umn/en-us_image_0000001987139953.png rename docs/dms/umn/{en-us_image_0000001803876329.png => en-us_image_0000001992720829.png} (100%) create mode 100644 docs/dms/umn/en-us_image_0000001998520149.png create mode 100644 docs/dms/umn/kafka-ug-0034.html create mode 100644 docs/dms/umn/kafka-ug-0035.html create mode 100644 docs/dms/umn/kafka-ug-0065.html create mode 100644 docs/dms/umn/kafka_ug_0017.html create mode 100644 docs/dms/umn/kafka_ug_0018.html create mode 100644 docs/dms/umn/kafka_ug_0041.html diff --git a/docs/dms/umn/ALL_META.TXT.json b/docs/dms/umn/ALL_META.TXT.json index 116796d6..e435e627 100644 --- a/docs/dms/umn/ALL_META.TXT.json +++ b/docs/dms/umn/ALL_META.TXT.json @@ -206,7 +206,7 @@ "node_id":"productdescprivilegemanagement.xml", "product_code":"kafka", "code":"12", - "des":"You can use Identity and Access Management (IAM) to manage DMS for Kafka permissions and control access to your resources. IAM provides identity authentication, permissio", + "des":"If you need to grant your enterprise personnel permission to access your DMS resources, use Identity and Access Management (IAM). IAM provides identity authentication, fi", "doc_type":"usermanual", "kw":"Permission,Service Overview,User Guide", "search_title":"", @@ -242,7 +242,7 @@ "node_id":"kafka-qs-0409001.xml", "product_code":"kafka", "code":"14", - "des":"This section takes the example of creating a Kafka 2.7 instance (ciphertext access and SASL_SSL) and accessing it on the client (private network, within a virtual private", + "des":"This section takes the example of creating a Kafka instance (ciphertext access and SASL_SSL) and accessing it on the client (private network, within a virtual private clo", "doc_type":"usermanual", "kw":"Getting Started with Kafka for Message Production and Consumption,Getting Started,User Guide", "search_title":"", @@ -260,7 +260,7 @@ "node_id":"kafka-ug-0069.xml", "product_code":"kafka", "code":"15", - "des":"The following figure shows the process of using a Kafka instance to produce and consume messages.Creating a User and Granting DMS for Kafka PermissionsCreate IAM users an", + "des":"Distributed Message Service is a message queuing service that is based on the open-source Apache Kafka. It provides Kafka instances with isolated computing, storage, and ", "doc_type":"usermanual", "kw":"Process of Using Kafka,User Guide", "search_title":"", @@ -354,7 +354,7 @@ "node_id":"kafka-ug-180604018.xml", "product_code":"kafka", "code":"20", - "des":"Topics store messages created by producers and subscribed by consumers. If automatic topic creation is not enabled during Kafka instance creation, you need to manually cr", + "des":"Topics store messages created by producers and subscribed by consumers. If Automatic Topic Creation is not enabled during Kafka instance creation, you need to manually cr", "doc_type":"usermanual", "kw":"Creating a Kafka Topic,Configuring Topics,User Guide", "search_title":"", @@ -373,7 +373,7 @@ "node_id":"kafka-ug-0002.xml", "product_code":"kafka", "code":"21", - "des":"DMS supports access control list (ACL) for topics. You can differentiate user permissions by granting users different permissions in a topic.This section describes how to", + "des":"Kafka instances with ciphertext access enabled support access control list (ACL) for topics. You can differentiate user permissions by granting users different permission", "doc_type":"usermanual", "kw":"Configuring Kafka Topic Permissions,Configuring Topics,User Guide", "search_title":"", @@ -411,7 +411,7 @@ "node_id":"kafka_ug_0045.xml", "product_code":"kafka", "code":"23", - "des":"On the console, you can view the details of a Kafka instance including subscriptions to a topic, offsets and number of messages in each partition, and producer addresses.", + "des":"On the Kafka console, you can view basic information, partition and producer information, and subscriptions of a topic.Select the region where your Kafka instance is loca", "doc_type":"usermanual", "kw":"Viewing Kafka Topic Details,Managing Topics,User Guide", "search_title":"", @@ -506,7 +506,7 @@ "node_id":"kafka_ug_0043.xml", "product_code":"kafka", "code":"28", - "des":"Automatic topic creation: A topic will be automatically created when a message is produced in or consumed from a topic that does not exist. By default, the topic has para", + "des":"Automatic Topic Creation indicates that a topic will be automatically created when a message is produced in or consumed from a topic that does not exist. By default, the ", "doc_type":"usermanual", "kw":"Configuring Automatic Topic Creation,Managing Topics,User Guide", "search_title":"", @@ -639,7 +639,7 @@ "node_id":"kafka-dnat.xml", "product_code":"kafka", "code":"35", - "des":"You can use destination NAT (DNAT) to access a Kafka instance so that the instance can provide services on the public network through port mapping.You have created EIPs. ", + "des":"Enable public access in either of the following ways:On the Kafka console, access Kafka instances using EIPs. For details, see Configuring Kafka Public Access.Configure p", "doc_type":"usermanual", "kw":"Accessing Kafka in a Public Network Using DNAT,Configuring Kafka Network Connections,User Guide", "search_title":"", @@ -696,9 +696,9 @@ "node_id":"kafka-ug-0003.xml", "product_code":"kafka", "code":"38", - "des":"DMS supports access control list (ACL) for topics. You can differentiate user permissions by granting users different permissions in a topic.This section describes how to", + "des":"Kafka instances with ciphertext access enabled support access control list (ACL) for topics. You can isolate users by granting them different permissions in a topic.This ", "doc_type":"usermanual", - "kw":"Configuring Kafka Users,Configuring Kafka Access Control,User Guide", + "kw":"Configuring Kafka ACL Users,Configuring Kafka Access Control,User Guide", "search_title":"", "metedata":[ { @@ -707,7 +707,7 @@ "documenttype":"usermanual" } ], - "title":"Configuring Kafka Users", + "title":"Configuring Kafka ACL Users", "githuburl":"" }, { @@ -769,7 +769,7 @@ "node_id":"kafka-ug-180604020.xml", "product_code":"kafka", "code":"42", - "des":"This section describes how to use an open-source Kafka client to access a Kafka instance in plaintext. Two scenarios: private network within a VPC and public network. To ", + "des":"This section describes how to access a Kafka instance in plaintext on an open-source Kafka client. With plaintext access enabled, there is no authentication required in s", "doc_type":"usermanual", "kw":"Connecting to Kafka Using the Client (Plaintext Access),Connecting to an Instance,User Guide", "search_title":"", @@ -788,7 +788,7 @@ "node_id":"kafka-ug-180801001.xml", "product_code":"kafka", "code":"43", - "des":"If you enable ciphertext access when creating an instance, SASL authentication will be required when your client connects to a Kafka instance.For security purposes, TLS_E", + "des":"This section describes how to access a Kafka instance in ciphertext on an open-source Kafka client. Accessing in ciphertext requires SASL authentication. The protocol SAS", "doc_type":"usermanual", "kw":"Connecting to Kafka Using the Client (Ciphertext Access),Connecting to an Instance,User Guide", "search_title":"", @@ -864,7 +864,7 @@ "node_id":"kafka_ug_0046.xml", "product_code":"kafka", "code":"47", - "des":"This section describes how to delete messages on the console.Deleted messages cannot be recovered.Before deleting a message, set the auto.offset.reset parameter in the co", + "des":"This section describes how to delete messages stored in a topic on the console.Deleted messages cannot be recovered.Before deleting a message, set the auto.offset.reset p", "doc_type":"usermanual", "kw":"Deleting Kafka Messages,Managing Messages,User Guide", "search_title":"", @@ -902,7 +902,7 @@ "node_id":"kafka-ug-0041.xml", "product_code":"kafka", "code":"49", - "des":"Create a consumer group on the console.auto.create.groups.enable: a consumer group is automatically created when a consumer attempts to enter a group that does not exist.", + "des":"A consumer subscribes to a topic. A consumer group consists of one or more consumers. Within a consumer group, each consumer can consume multiple partitions at the same t", "doc_type":"usermanual", "kw":"Creating a Kafka Consumer Group,Managing Consumer Groups,User Guide", "search_title":"", @@ -921,7 +921,7 @@ "node_id":"kafka_ug_0021.xml", "product_code":"kafka", "code":"50", - "des":"This section describes how to query the consumer group list.Select the region where your Kafka instance is located.The consumer group name, status, and Coordinator (ID) a", + "des":"After a consumer group is created, you can view its configuration and status.Select the region where your Kafka instance is located.The consumer group name, status, and C", "doc_type":"usermanual", "kw":"Querying the Kafka Consumer Group List,Managing Consumer Groups,User Guide", "search_title":"", @@ -940,9 +940,9 @@ "node_id":"kafka-ug-0015.xml", "product_code":"kafka", "code":"51", - "des":"This section describes how to view the consumer list and consumer connection addresses.The consumer list and connection address can be viewed only when consumers in a con", + "des":"If a consumer group has consumers who are accessing a Kafka instance, you can view their connection information.The consumer list and connection address can be viewed onl", "doc_type":"usermanual", - "kw":"Viewing Kafka Consumer Details,Managing Consumer Groups,User Guide", + "kw":"Viewing Kafka Consumer Information,Managing Consumer Groups,User Guide", "search_title":"", "metedata":[ { @@ -951,7 +951,7 @@ "documenttype":"usermanual" } ], - "title":"Viewing Kafka Consumer Details", + "title":"Viewing Kafka Consumer Information", "githuburl":"" }, { @@ -959,7 +959,7 @@ "node_id":"kafka-ug-0014.xml", "product_code":"kafka", "code":"52", - "des":"This section describes how to view and reset consumption offsets. Resetting consumption offsets is to change the consumption position for consumers.Messages may be retrie", + "des":"A consumption offset indicates the consumption progress of a consumer. This section describes how to view and reset consumption offsets.Messages may be retrieved more tha", "doc_type":"usermanual", "kw":"Viewing and Resetting Kafka Consumption Offsets,Managing Consumer Groups,User Guide", "search_title":"", @@ -978,7 +978,7 @@ "node_id":"kafka-ug-0056.xml", "product_code":"kafka", "code":"53", - "des":"Export the consumer group list from the console.Select the region where your Kafka instance is located.Select the desired consumer groups and choose Export > Export selec", + "des":"You can export a list of consumer groups in a Kafka instance.Select the region where your Kafka instance is located.Select the desired consumer groups and choose Export >", "doc_type":"usermanual", "kw":"Exporting Kafka Consumer Groups,Managing Consumer Groups,User Guide", "search_title":"", @@ -1035,7 +1035,7 @@ "node_id":"kafka-ug-180604014.xml", "product_code":"kafka", "code":"56", - "des":"This section describes how to view the details, and modify the basic information of a Kafka instance on the console.After creating a Kafka instance, you can modify some p", + "des":"After creating a Kafka instance, you can view the details or modify some parameters of it on the console as required. These parameters include the instance name, descript", "doc_type":"usermanual", "kw":"Viewing and Modifying Basic Information of a Kafka Instance,Managing Instances,User Guide", "search_title":"", @@ -1054,7 +1054,7 @@ "node_id":"kafka-ug-0004.xml", "product_code":"kafka", "code":"57", - "des":"This section describes how to view the disk usage of each broker on the Kafka console.This function is unavailable for single-node instances.Select the region where your ", + "des":"This section describes how to view the disk usage of each broker of a Kafka instance on the console.This function is unavailable for single-node instances.Select the regi", "doc_type":"usermanual", "kw":"Viewing Kafka Disk Usage,Managing Instances,User Guide", "search_title":"", @@ -1092,7 +1092,7 @@ "node_id":"kafka_ug_0024.xml", "product_code":"kafka", "code":"59", - "des":"On the console, view sample code for creating and retrieving messages in Java, Go, and Python.Select the region where your Kafka instance is located.View sample code for ", + "des":"Distributed Message Service allows you to view sample Java, Go, and Python code of producing and consuming messages on the console. You can quickly complete Kafka client ", "doc_type":"usermanual", "kw":"Viewing Sample Code of Kafka Production and Consumption,Managing Instances,User Guide", "search_title":"", @@ -1149,7 +1149,7 @@ "node_id":"kafka-ug-0053.xml", "product_code":"kafka", "code":"62", - "des":"This section describes how to export the Kafka instance list from the console.Select the region where your Kafka instance is located.Select the desired instances and choo", + "des":"You can export a list of instances on the DMS console.Select the region where your Kafka instance is located.Select the desired instances and choose Export > Export selec", "doc_type":"usermanual", "kw":"Exporting the Kafka Instance List,Managing Instances,User Guide", "search_title":"", @@ -1168,7 +1168,7 @@ "node_id":"kafka-ug-180604015.xml", "product_code":"kafka", "code":"63", - "des":"Restart one or more Kafka instances at a time on the DMS console.When a Kafka instance is being restarted, message retrieval and creation requests of clients will be reje", + "des":"You can restart one or more Kafka instances in batches on the DMS console.When a Kafka instance is being restarted, message retrieval and creation requests of clients wil", "doc_type":"usermanual", "kw":"Restarting a Kafka Instance,Managing Instances,User Guide", "search_title":"", @@ -1257,11 +1257,124 @@ "title":"Kafka Data Migration Overview", "githuburl":"" }, + { + "uri":"kafka-ug-0065.html", + "node_id":"kafka-ug-0065.xml", + "product_code":"kafka", + "code":"68", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Migrating Data Using Smart Connect", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Migrating Data Using Smart Connect", + "githuburl":"" + }, + { + "uri":"kafka_ug_0017.html", + "node_id":"kafka_ug_0017.xml", + "product_code":"kafka", + "code":"69", + "des":"Smart Connect synchronizes data between Kafka and other cloud services (such as OBS) or between two Kafka instances for backup or migration.Procedure for using Smart Conn", + "doc_type":"usermanual", + "kw":"Enabling Smart Connect,Migrating Data Using Smart Connect,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "opensource":"true", + "documenttype":"usermanual" + } + ], + "title":"Enabling Smart Connect", + "githuburl":"" + }, + { + "uri":"kafka-ug-0034.html", + "node_id":"kafka-ug-0034.xml", + "product_code":"kafka", + "code":"70", + "des":"Create a Smart Connect task to copy data unidirectionally or bidirectionally between two Kafka instances.Data in the source Kafka instance is synchronized to the target K", + "doc_type":"usermanual", + "kw":"Replicating Kafka Instance Data,Migrating Data Using Smart Connect,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "opensource":"true", + "documenttype":"usermanual" + } + ], + "title":"Replicating Kafka Instance Data", + "githuburl":"" + }, + { + "uri":"kafka-ug-0035.html", + "node_id":"kafka-ug-0035.xml", + "product_code":"kafka", + "code":"71", + "des":"Create a Smart Connect task to dump Kafka instance data to OBS for message data backup.Data in the source Kafka instance is synchronized to the dumping file in real time.", + "doc_type":"usermanual", + "kw":"Dumping Kafka Data to Object Storage Service (OBS),Migrating Data Using Smart Connect,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "opensource":"true", + "documenttype":"usermanual" + } + ], + "title":"Dumping Kafka Data to Object Storage Service (OBS)", + "githuburl":"" + }, + { + "uri":"kafka_ug_0018.html", + "node_id":"kafka_ug_0018.xml", + "product_code":"kafka", + "code":"72", + "des":"View, delete, start, pause, or restart a Smart Connect task.This function is unavailable for single-node instances. Kafka 3.x instances do not support this function.A Sma", + "doc_type":"usermanual", + "kw":"Managing Smart Connect Tasks,Migrating Data Using Smart Connect,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "opensource":"true", + "documenttype":"usermanual" + } + ], + "title":"Managing Smart Connect Tasks", + "githuburl":"" + }, + { + "uri":"kafka_ug_0041.html", + "node_id":"kafka_ug_0041.xml", + "product_code":"kafka", + "code":"73", + "des":"Disable Smart Connect and resources can be freed.Disabling Smart Connect does not affect services.This function is unavailable for single-node instances. Kafka 3.x instan", + "doc_type":"usermanual", + "kw":"Disabling Smart Connect,Migrating Data Using Smart Connect,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "opensource":"true", + "documenttype":"usermanual" + } + ], + "title":"Disabling Smart Connect", + "githuburl":"" + }, { "uri":"kafka-ug-180413001.html", "node_id":"kafka-ug-180413001.xml", "product_code":"kafka", - "code":"68", + "code":"74", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Monitoring and Alarms", @@ -1280,10 +1393,10 @@ "uri":"kafka-ug-190605001.html", "node_id":"kafka-ug-190605001.xml", "product_code":"kafka", - "code":"69", + "code":"75", "des":"Cloud Eye monitors Kafka instance metrics in real time. You can view these metrics on the Cloud Eye console.At least one Kafka instance has been created. The instance has", "doc_type":"usermanual", - "kw":"Viewing Kafka Monitoring Metrics,Monitoring and Alarms,User Guide", + "kw":"Viewing Kafka Metrics,Monitoring and Alarms,User Guide", "search_title":"", "metedata":[ { @@ -1292,14 +1405,14 @@ "documenttype":"usermanual" } ], - "title":"Viewing Kafka Monitoring Metrics", + "title":"Viewing Kafka Metrics", "githuburl":"" }, { "uri":"kafka-ug-180413002.html", "node_id":"kafka-ug-180413002.xml", "product_code":"kafka", - "code":"70", + "code":"76", "des":"This section describes metrics reported by DMS to Cloud Eye as well as their namespaces and dimensions. You can use the Cloud Eye console or APIs to query the Kafka metri", "doc_type":"usermanual", "kw":"Kafka Metrics,Monitoring and Alarms,User Guide", @@ -1318,7 +1431,7 @@ "uri":"kafka-ug-180524001.html", "node_id":"kafka-ug-180524001.xml", "product_code":"kafka", - "code":"71", + "code":"77", "des":"This section describes the alarm rules of some metrics and how to configure them. In actual services, you are advised to configure alarm rules for metrics based on the fo", "doc_type":"usermanual", "kw":"Configuring a Kafka Alarm Rule,Monitoring and Alarms,User Guide", @@ -1337,7 +1450,7 @@ "uri":"kafka-ug-180418002.html", "node_id":"kafka-ug-180418002.xml", "product_code":"kafka", - "code":"72", + "code":"78", "des":"With Cloud Trace Service (CTS), you can record operations associated with DMS for later query, audit, and backtrack operations.CTS has been enabled.See Querying Real-Time", "doc_type":"usermanual", "kw":"Viewing Kafka Audit Logs,User Guide", @@ -1356,7 +1469,7 @@ "uri":"kafka-ug-0723004.html", "node_id":"kafka-ug-0723004.xml", "product_code":"kafka", - "code":"73", + "code":"79", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQs", @@ -1374,7 +1487,7 @@ "uri":"kafka-faq-191030002.html", "node_id":"kafka-faq-191030002.xml", "product_code":"kafka", - "code":"74", + "code":"80", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Instances", @@ -1392,7 +1505,7 @@ "uri":"kafka-faq-200426002.html", "node_id":"kafka-faq-200426002.xml", "product_code":"kafka", - "code":"75", + "code":"81", "des":"To improve the reliability of a Kafka instance, you are advised to select three AZs or more when creating the instance. You cannot select two AZs.Each Kafka instance cont", "doc_type":"usermanual", "kw":"Why Can't I Select Two AZs?,Instances,User Guide", @@ -1410,7 +1523,7 @@ "uri":"kafka-faq-200426003.html", "node_id":"kafka-faq-200426003.xml", "product_code":"kafka", - "code":"76", + "code":"82", "des":"This may be because you do not have the Server Administrator and VPC Administrator permissions. For details about how to add permissions to a user group, see Viewing and ", "doc_type":"usermanual", "kw":"Why Can't I View the Subnet and Security Group Information When Creating a DMS Instance?,Instances,U", @@ -1428,7 +1541,7 @@ "uri":"kafka-faq-200426005.html", "node_id":"kafka-faq-200426005.xml", "product_code":"kafka", - "code":"77", + "code":"83", "des":"The storage space is the space for storing messages (including messages in replicas), logs and metadata. To select a storage space, specify the disk type and disk size. F", "doc_type":"usermanual", "kw":"How Do I Select Storage Space for a Kafka Instance?,Instances,User Guide", @@ -1446,7 +1559,7 @@ "uri":"kafka-faq-200426006.html", "node_id":"kafka-faq-200426006.xml", "product_code":"kafka", - "code":"78", + "code":"84", "des":"High I/O: The average latency is 6 to 10 ms, and the maximum bandwidth is 150 MB/s (read + write).Ultra-high I/O: The average latency is 1 to 3 ms, and the maximum bandwi", "doc_type":"usermanual", "kw":"How Do I Choose Between High I/O and Ultra-high I/O?,Instances,User Guide", @@ -1464,7 +1577,7 @@ "uri":"kafka-faq-200426007.html", "node_id":"kafka-faq-200426007.xml", "product_code":"kafka", - "code":"79", + "code":"85", "des":"The following policies are supported:Stop productionWhen the memory usage reaches the disk capacity threshold (95%), new messages will no longer be created, but existing ", "doc_type":"usermanual", "kw":"Which Capacity Threshold Policy Should I Use?,Instances,User Guide", @@ -1482,7 +1595,7 @@ "uri":"kafka-faq-200426008.html", "node_id":"kafka-faq-200426008.xml", "product_code":"kafka", - "code":"80", + "code":"86", "des":"Kafka v2.3.0, v2.7, and v3.x.For details about how to create a Kafka instance, see Creating a Kafka Instance.", "doc_type":"usermanual", "kw":"Which Kafka Versions Are Supported?,Instances,User Guide", @@ -1500,7 +1613,7 @@ "uri":"kafka-faq-200426009.html", "node_id":"kafka-faq-200426009.xml", "product_code":"kafka", - "code":"81", + "code":"87", "des":"Kafka instances are managed using ZooKeeper. Opening ZooKeeper may cause misoperations and service losses. ZooKeeper is used only within Kafka clusters and does not provi", "doc_type":"usermanual", "kw":"What Is the ZooKeeper Address of a Kafka Instance?,Instances,User Guide", @@ -1518,7 +1631,7 @@ "uri":"kafka-faq-200426010.html", "node_id":"kafka-faq-200426010.xml", "product_code":"kafka", - "code":"82", + "code":"88", "des":"Kafka instances are classified into single-node and cluster types. A single-node instance has only one broker in single-node mode. A cluster instance consists of three or", "doc_type":"usermanual", "kw":"Are Kafka Instances in Cluster Mode?,Instances,User Guide", @@ -1536,7 +1649,7 @@ "uri":"kafka-faq-200426011.html", "node_id":"kafka-faq-200426011.xml", "product_code":"kafka", - "code":"83", + "code":"89", "des":"No. You must access a Kafka instance through one of the following ports:Accessing a Kafka instance without SASL:The port varies with the access mode:Intra-VPC access: por", "doc_type":"usermanual", "kw":"Can I Modify the Port for Accessing a Kafka Instance?,Instances,User Guide", @@ -1554,7 +1667,7 @@ "uri":"kafka-faq-200426012.html", "node_id":"kafka-faq-200426012.xml", "product_code":"kafka", - "code":"84", + "code":"90", "des":"The certificates are valid for more than 15 years. You do not need to worry about certificate expiration. The certificates are used for one-way authentication when enabli", "doc_type":"usermanual", "kw":"How Long Are Kafka SSL Certificates Valid for?,Instances,User Guide", @@ -1572,8 +1685,8 @@ "uri":"kafka-faq-200426013.html", "node_id":"kafka-faq-200426013.xml", "product_code":"kafka", - "code":"85", - "des":"Unfortunately, you cannot synchronize two Kafka instances in real time. To migrate services from one instance to another, create messages to both instances. After all mes", + "code":"91", + "des":"On the Kafka console, you can create a Smart Connect task for instance data replication. For details, see Replicating Kafka Instance Data.", "doc_type":"usermanual", "kw":"How Do I Synchronize Data from One Kafka Instance to Another?,Instances,User Guide", "search_title":"", @@ -1590,7 +1703,7 @@ "uri":"kafka-faq-200426014.html", "node_id":"kafka-faq-200426014.xml", "product_code":"kafka", - "code":"86", + "code":"92", "des":"The SASL_SSL setting can be changed for cluster instances (see Configuring Plaintext or Ciphertext Access to Kafka Instances), but cannot be changed for single-node insta", "doc_type":"usermanual", "kw":"How Do I Change the SASL_SSL Setting of a Kafka Instance?,Instances,User Guide", @@ -1608,7 +1721,7 @@ "uri":"kafka_faq_0052.html", "node_id":"kafka_faq_0052.xml", "product_code":"kafka", - "code":"87", + "code":"93", "des":"After an instance is created, its SASL mechanism cannot be modified. If you want to change it, create an instance again.", "doc_type":"usermanual", "kw":"How Do I Modify the SASL Mechanism?,Instances,User Guide", @@ -1626,7 +1739,7 @@ "uri":"kafka_faq_0062.html", "node_id":"kafka_faq_0062.xml", "product_code":"kafka", - "code":"88", + "code":"94", "des":"The security protocol can be changed on the console. In the Connection area on the Kafka instance details page, disable Ciphertext Access and then configure security prot", "doc_type":"usermanual", "kw":"How Do I Change the Security Protocol?,Instances,User Guide", @@ -1644,7 +1757,7 @@ "uri":"kafka-faq-0008.html", "node_id":"kafka-faq-0008.xml", "product_code":"kafka", - "code":"89", + "code":"95", "des":"No. A Kafka instance will not be restarted if you modify its enterprise project.", "doc_type":"usermanual", "kw":"Will a Kafka Instance Be Restarted After Its Enterprise Project Is Modified?,Instances,User Guide", @@ -1662,7 +1775,7 @@ "uri":"kafka-faq-0015.html", "node_id":"kafka-faq-0015.xml", "product_code":"kafka", - "code":"90", + "code":"96", "des":"Kafka brokers and ZooKeeper are deployed on the same VM.", "doc_type":"usermanual", "kw":"Are Kafka Brokers and ZooKeeper Deployed on the Same VM or on Different VMs?,Instances,User Guide", @@ -1680,7 +1793,7 @@ "uri":"kafka-faq-0020.html", "node_id":"kafka-faq-0020.xml", "product_code":"kafka", - "code":"91", + "code":"97", "des":"For security purposes, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is supported.", "doc_type":"usermanual", "kw":"Which Cipher Suites Are Supported by Kafka?,Instances,User Guide", @@ -1698,7 +1811,7 @@ "uri":"kafka-faq-0023.html", "node_id":"kafka-faq-0023.xml", "product_code":"kafka", - "code":"92", + "code":"98", "des":"No. The AZ cannot be changed once the instance is created. To use multiple AZs, create another instance.", "doc_type":"usermanual", "kw":"Can I Change Single-AZ Deployment to Multi-AZ Deployment for an Instance?,Instances,User Guide", @@ -1716,7 +1829,7 @@ "uri":"kafka-faq-0025.html", "node_id":"kafka-faq-0025.xml", "product_code":"kafka", - "code":"93", + "code":"99", "des":"DMS for Kafka supports cross-AZ disaster recovery. If you select multiple AZs when creating an instance, cross-AZ disaster recovery will be available.You can view the AZs", "doc_type":"usermanual", "kw":"Does DMS for Kafka Support Cross-AZ Disaster Recovery? Where Can I Check Whether an Existing Instanc", @@ -1734,7 +1847,7 @@ "uri":"kafka-faq-0030.html", "node_id":"kafka-faq-0030.xml", "product_code":"kafka", - "code":"94", + "code":"100", "des":"Yes.", "doc_type":"usermanual", "kw":"Do Kafka Instances Support Disk Encryption?,Instances,User Guide", @@ -1752,7 +1865,7 @@ "uri":"kafka-faq-0036.html", "node_id":"kafka-faq-0036.xml", "product_code":"kafka", - "code":"95", + "code":"101", "des":"No. Once an instance is created, its VPC and subnet cannot be changed.", "doc_type":"usermanual", "kw":"Can I Change the VPC and Subnet After a Kafka Instance Is Created?,Instances,User Guide", @@ -1770,7 +1883,7 @@ "uri":"kafka-faq-0037.html", "node_id":"kafka-faq-0037.xml", "product_code":"kafka", - "code":"96", + "code":"102", "des":"You can find Kafka Streams use cases on the official Kafka website.", "doc_type":"usermanual", "kw":"Where Can I Find Kafka Streams Use Cases?,Instances,User Guide", @@ -1788,7 +1901,7 @@ "uri":"kafka-faq-0040.html", "node_id":"kafka-faq-0040.xml", "product_code":"kafka", - "code":"97", + "code":"103", "des":"No. Kafka instances cannot be upgraded once they are created. To use a higher Kafka version, create another Kafka instance.", "doc_type":"usermanual", "kw":"Can I Upgrade Kafka Instances?,Instances,User Guide", @@ -1806,7 +1919,7 @@ "uri":"kafka_faq_0046.html", "node_id":"kafka_faq_0046.xml", "product_code":"kafka", - "code":"98", + "code":"104", "des":"On the DMS console, click the name of the target Kafka instance. Disable Public Access in the Connection section on the Basic Information tab page, and then enable it aga", "doc_type":"usermanual", "kw":"How Do I Bind an EIP Again?,Instances,User Guide", @@ -1824,7 +1937,7 @@ "uri":"kafka_faq_0053.html", "node_id":"kafka_faq_0053.xml", "product_code":"kafka", - "code":"99", + "code":"105", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Specification Modification", @@ -1842,7 +1955,7 @@ "uri":"kafka-faq-0035.html", "node_id":"kafka-faq-0035.xml", "product_code":"kafka", - "code":"100", + "code":"106", "des":"Table 1 describes the impact of increasing specifications. It takes 5 to 10 minutes to modify specifications on one broker. The more brokers, the longer time the modifica", "doc_type":"usermanual", "kw":"Does Specification Modification Affect Services?,Specification Modification,User Guide", @@ -1860,7 +1973,7 @@ "uri":"kafka_faq_0054.html", "node_id":"kafka_faq_0054.xml", "product_code":"kafka", - "code":"101", + "code":"107", "des":"No. Data will not be migrated when you increase specifications.", "doc_type":"usermanual", "kw":"Will Data Migration Be Involved When I Increase Specifications?,Specification Modification,User Guid", @@ -1878,7 +1991,7 @@ "uri":"kafka_faq_0056.html", "node_id":"kafka_faq_0056.xml", "product_code":"kafka", - "code":"102", + "code":"108", "des":"Possible cause: When you increase the broker flavor, a rolling restart is performed on brokers. During the restart, partition leaders are changed. The producer has cached", "doc_type":"usermanual", "kw":"Why Does Message Production Fail During Scaling?,Specification Modification,User Guide", @@ -1896,7 +2009,7 @@ "uri":"kafka_faq_0057.html", "node_id":"kafka_faq_0057.xml", "product_code":"kafka", - "code":"103", + "code":"109", "des":"Symptom: Specifications fail to be increased, and a message is displayed indicating that the underlying ECS/EVS resources are insufficient. However, the required ECSs can", "doc_type":"usermanual", "kw":"What Can I Do When I Fail to Increase Specifications Due to Insufficient Resources?,Specification Mo", @@ -1914,7 +2027,7 @@ "uri":"kafka-faq-191030001.html", "node_id":"kafka-faq-191030001.xml", "product_code":"kafka", - "code":"104", + "code":"110", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Connections", @@ -1932,7 +2045,7 @@ "uri":"kafka-faq-180604024.html", "node_id":"kafka-faq-180604024.xml", "product_code":"kafka", - "code":"105", + "code":"111", "des":"Kafka instances can be accessed within a VPC, across VPCs, through DNAT, or over public networks. Before accessing a Kafka instance, configure a security group.If they us", "doc_type":"usermanual", "kw":"How Do I Select and Configure a Security Group?,Connections,User Guide", @@ -1950,7 +2063,7 @@ "uri":"kafka-faq-200426015.html", "node_id":"kafka-faq-200426015.xml", "product_code":"kafka", - "code":"106", + "code":"112", "des":"Yes. For details, see the instance access instructions.", "doc_type":"usermanual", "kw":"Can I Access a Kafka Instance Over a Public Network?,Connections,User Guide", @@ -1968,7 +2081,7 @@ "uri":"kafka-faq-200426016.html", "node_id":"kafka-faq-200426016.xml", "product_code":"kafka", - "code":"107", + "code":"113", "des":"The number of connection addresses of a Kafka instance is the same as the number of brokers of the instance. The following table lists the number of brokers corresponding", "doc_type":"usermanual", "kw":"How Many Connection Addresses Does a Kafka Instance Have by Default?,Connections,User Guide", @@ -1986,7 +2099,7 @@ "uri":"kafka-faq-200426017.html", "node_id":"kafka-faq-200426017.xml", "product_code":"kafka", - "code":"108", + "code":"114", "des":"Yes. You can access a Kafka instance across regions over a public network or by using direct connections.", "doc_type":"usermanual", "kw":"Do Kafka Instances Support Cross-Region Access?,Connections,User Guide", @@ -2004,7 +2117,7 @@ "uri":"kafka-faq-200426019.html", "node_id":"kafka-faq-200426019.xml", "product_code":"kafka", - "code":"109", + "code":"115", "des":"Yes. You can use one of the following methods to access a Kafka instance across VPCs:Establish a VPC peering connection to allow two VPCs to communicate with each other. ", "doc_type":"usermanual", "kw":"Do Kafka Instances Support Cross-VPC Access?,Connections,User Guide", @@ -2022,7 +2135,7 @@ "uri":"kafka-faq-200426020.html", "node_id":"kafka-faq-200426020.xml", "product_code":"kafka", - "code":"110", + "code":"116", "des":"Yes.If the client and the instance are in the same VPC, cross-subnet access is supported. By default, subnets in the same VPC can communicate with each other.", "doc_type":"usermanual", "kw":"Do Kafka Instances Support Cross-Subnet Access?,Connections,User Guide", @@ -2040,7 +2153,7 @@ "uri":"kafka-faq-200426023.html", "node_id":"kafka-faq-200426023.xml", "product_code":"kafka", - "code":"111", + "code":"117", "des":"No, Kerberos authentication is not supported. Kafka supports client authentication with SASL and API calling authentication using tokens and AK/SK.To access an instance i", "doc_type":"usermanual", "kw":"Does DMS for Kafka Support Authentication with Kerberos?,Connections,User Guide", @@ -2058,7 +2171,7 @@ "uri":"kafka-faq-200708002.html", "node_id":"kafka-faq-200708002.xml", "product_code":"kafka", - "code":"112", + "code":"118", "des":"Yes. No password is required when accessing a Kafka instance in plaintext. For details, see Connecting to Kafka Using the Client (Plaintext Access).", "doc_type":"usermanual", "kw":"Does DMS for Kafka Support Password-Free Access?,Connections,User Guide", @@ -2076,7 +2189,7 @@ "uri":"kafka-faq-0001.html", "node_id":"kafka-faq-0001.xml", "product_code":"kafka", - "code":"113", + "code":"119", "des":"Click the name of your Kafka instance. In the Connection section on the Basic Information tab page, view Instance Address (Public Network).For details about how to connec", "doc_type":"usermanual", "kw":"How Do I Obtain the Public Access Address After Public Access Is Enabled?,Connections,User Guide", @@ -2094,7 +2207,7 @@ "uri":"kafka-faq-0026.html", "node_id":"kafka-faq-0026.xml", "product_code":"kafka", - "code":"114", + "code":"120", "des":"No.", "doc_type":"usermanual", "kw":"Does DMS for Kafka Support Authentication on Clients by the Server?,Connections,User Guide", @@ -2112,7 +2225,7 @@ "uri":"kafka-faq-0027.html", "node_id":"kafka-faq-0027.xml", "product_code":"kafka", - "code":"115", + "code":"121", "des":"No. You can only use JKS certificates for connecting to instances in Java.", "doc_type":"usermanual", "kw":"Can I Use PEM SSL Truststore When Connecting to a Kafka Instance with SASL_SSL Enabled?,Connections,", @@ -2130,7 +2243,7 @@ "uri":"kafka-faq-0028.html", "node_id":"kafka-faq-0028.xml", "product_code":"kafka", - "code":"116", + "code":"122", "des":"JKS certificates are used for connecting to instances in Java and CRT certificates are used for connecting to instances in Python.", "doc_type":"usermanual", "kw":"What Are the Differences Between JKS and CRT Certificates?,Connections,User Guide", @@ -2148,7 +2261,7 @@ "uri":"kafka-faq-0029.html", "node_id":"kafka-faq-0029.xml", "product_code":"kafka", - "code":"117", + "code":"123", "des":"TLS 1.2.", "doc_type":"usermanual", "kw":"Which TLS Version Does DMS for Kafka Support?,Connections,User Guide", @@ -2166,7 +2279,7 @@ "uri":"kafka-faq-0033.html", "node_id":"kafka-faq-0033.xml", "product_code":"kafka", - "code":"118", + "code":"124", "des":"Yes. The maximum allowed number of client connections varies by instance specifications.", "doc_type":"usermanual", "kw":"Is There a Limit on the Number of Client Connections to a Kafka Instance?,Connections,User Guide", @@ -2184,7 +2297,7 @@ "uri":"kafka-faq-0034.html", "node_id":"kafka-faq-0034.xml", "product_code":"kafka", - "code":"119", + "code":"125", "des":"Each Kafka broker allows a maximum of 1000 connections from each IP address by default. Excess connections will be rejected. You can change the limit by referring to Modi", "doc_type":"usermanual", "kw":"How Many Connections Are Allowed from Each IP Address?,Connections,User Guide", @@ -2202,7 +2315,7 @@ "uri":"kafka_faq_0048.html", "node_id":"kafka_faq_0048.xml", "product_code":"kafka", - "code":"120", + "code":"126", "des":"No, and you cannot specify the IP addresses.", "doc_type":"usermanual", "kw":"Can I Change the Private Network Addresses of a Kafka Instance?,Connections,User Guide", @@ -2220,7 +2333,7 @@ "uri":"kafka_faq_0051.html", "node_id":"kafka_faq_0051.xml", "product_code":"kafka", - "code":"121", + "code":"127", "des":"Yes. All Kafka instances and users use the same SSL certificate.To obtain the SSL certificate, perform the following steps:", "doc_type":"usermanual", "kw":"Is the Same SSL Certificate Used for Different Instances?,Connections,User Guide", @@ -2238,7 +2351,7 @@ "uri":"kafka_faq_0061.html", "node_id":"kafka_faq_0061.xml", "product_code":"kafka", - "code":"122", + "code":"128", "des":"If a Sarama client is used to send and receive messages, the following issues may occur:Sarama cannot detect partition changes. Adding topic partitions requires client re", "doc_type":"usermanual", "kw":"Why Is It Not Recommended to Use a Sarama Client for Messaging?,Connections,User Guide", @@ -2256,7 +2369,7 @@ "uri":"kafka-faq-191030003.html", "node_id":"kafka-faq-191030003.xml", "product_code":"kafka", - "code":"123", + "code":"129", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Topics and Partitions", @@ -2274,7 +2387,7 @@ "uri":"kafka-faq-200426024.html", "node_id":"kafka-faq-200426024.xml", "product_code":"kafka", - "code":"124", + "code":"130", "des":"The number of topics is related to the total number of topic partitions and the number of partitions in each topic. There is an upper limit on the aggregate number of par", "doc_type":"usermanual", "kw":"Is There a Limit on the Number of Topics in a Kafka Instance?,Topics and Partitions,User Guide", @@ -2292,7 +2405,7 @@ "uri":"kafka-faq-200426025.html", "node_id":"kafka-faq-200426025.xml", "product_code":"kafka", - "code":"125", + "code":"131", "des":"Kafka manages messages by partition. If there are too many partitions, message creation, storage, and retrieval will be fragmented, affecting the performance and stabilit", "doc_type":"usermanual", "kw":"Why Is Partition Quantity Limited?,Topics and Partitions,User Guide", @@ -2310,7 +2423,7 @@ "uri":"kafka-faq-200426101.html", "node_id":"kafka-faq-200426101.xml", "product_code":"kafka", - "code":"126", + "code":"132", "des":"No. If you want to use fewer partitions, delete the corresponding topic, create another one, and specify the desired number of partitions.", "doc_type":"usermanual", "kw":"Can I Reduce the Partition Quantity?,Topics and Partitions,User Guide", @@ -2328,7 +2441,7 @@ "uri":"kafka-faq-200426026.html", "node_id":"kafka-faq-200426026.xml", "product_code":"kafka", - "code":"127", + "code":"133", "des":"Possible cause: The aggregate number of partitions of created topics has reached the upper limit. The upper limit on partitions varies by instance specifications. For det", "doc_type":"usermanual", "kw":"Why Do I Fail to Create Topics?,Topics and Partitions,User Guide", @@ -2346,7 +2459,7 @@ "uri":"kafka-faq-200426027.html", "node_id":"kafka-faq-200426027.xml", "product_code":"kafka", - "code":"128", + "code":"134", "des":"Automatic topic creation is supported, but batch topic import is not supported. You can only export topics in batches.Enable automatic topic creation using one of the fol", "doc_type":"usermanual", "kw":"Do Kafka Instances Support Batch Importing Topics or Automatic Topic Creation?,Topics and Partitions", @@ -2364,7 +2477,7 @@ "uri":"kafka-faq-200426028.html", "node_id":"kafka-faq-200426028.xml", "product_code":"kafka", - "code":"129", + "code":"135", "des":"Possible cause: Automatic topic creation has been enabled and a consumer is connecting to the topic. If no existing topics are available for message creation, new topics ", "doc_type":"usermanual", "kw":"Why Do Deleted Topics Still Exist?,Topics and Partitions,User Guide", @@ -2382,7 +2495,7 @@ "uri":"kafka-faq-200426030.html", "node_id":"kafka-faq-200426030.xml", "product_code":"kafka", - "code":"130", + "code":"136", "des":"Yes. Use either of the following methods to check the disk space used by a topic:In the row containing the desired Kafka instance, click View Metric to go to the Cloud Ey", "doc_type":"usermanual", "kw":"Can I View the Disk Space Used by a Topic?,Topics and Partitions,User Guide", @@ -2400,7 +2513,7 @@ "uri":"kafka-faq-200426032.html", "node_id":"kafka-faq-200426032.xml", "product_code":"kafka", - "code":"131", + "code":"137", "des":"If you have enabled SASL_SSL for your Kafka instance, you can configure ACL permissions for your topics. On the Topics tab page of the Kafka console, click Grant User Per", "doc_type":"usermanual", "kw":"Can I Add ACL Permissions for Topics?,Topics and Partitions,User Guide", @@ -2418,7 +2531,7 @@ "uri":"kafka-faq-0003.html", "node_id":"kafka-faq-0003.xml", "product_code":"kafka", - "code":"132", + "code":"138", "des":"Messages are not deleted immediately after being retrieved. They are deleted only when the aging time expires.You can shorten the aging time or expand the storage space.", "doc_type":"usermanual", "kw":"What Should I Do If Kafka Storage Space Is Used Up Because Retrieved Messages Are Not Deleted?,Topic", @@ -2436,7 +2549,7 @@ "uri":"kafka-faq-0005.html", "node_id":"kafka-faq-0005.xml", "product_code":"kafka", - "code":"133", + "code":"139", "des":"You can increase the partition quantity by adding brokers.To do so, go to the Kafka console, locate the row that contains the desired instance, and choose More > Modify S", "doc_type":"usermanual", "kw":"How Do I Increase the Partition Quantity?,Topics and Partitions,User Guide", @@ -2454,7 +2567,7 @@ "uri":"kafka-faq-0010.html", "node_id":"kafka-faq-0010.xml", "product_code":"kafka", - "code":"134", + "code":"140", "des":"Enabling or disabling automatic topic creation may cause instance restarts. For details, see the information displayed on the Kafka console.", "doc_type":"usermanual", "kw":"Will a Kafka Instance Be Restarted After Its Automatic Topic Creation Setting Is Modified?,Topics an", @@ -2472,7 +2585,7 @@ "uri":"kafka-faq-0031.html", "node_id":"kafka-faq-0031.xml", "product_code":"kafka", - "code":"135", + "code":"141", "des":"Just simply unsubscribe from them on the Kafka client.", "doc_type":"usermanual", "kw":"Can I Delete Unnecessary Topics in a Consumer Group?,Topics and Partitions,User Guide", @@ -2490,7 +2603,7 @@ "uri":"kafka-faq-0038.html", "node_id":"kafka-faq-0038.xml", "product_code":"kafka", - "code":"136", + "code":"142", "des":"Symptom: Different consumers in a consumer group have different topic permissions. When a consumer attempts to retrieve messages from a topic, the error message \"Not auth", "doc_type":"usermanual", "kw":"What Can I Do If a Consumer Fails to Retrieve Messages from a Topic Due to Insufficient Permissions?", @@ -2508,7 +2621,7 @@ "uri":"kafka-faq-200423001.html", "node_id":"kafka-faq-200423001.xml", "product_code":"kafka", - "code":"137", + "code":"143", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Consumer Groups", @@ -2526,7 +2639,7 @@ "uri":"kafka-faq-200426033.html", "node_id":"kafka-faq-200426033.xml", "product_code":"kafka", - "code":"138", + "code":"144", "des":"When parameter auto.create.groups.enable is set to true, you do not need to create a consumer group, producer, or consumer because they are generated automatically when y", "doc_type":"usermanual", "kw":"Do I Need to Create Consumer Groups, Producers, and Consumers for Kafka Instances?,Consumer Groups,U", @@ -2544,7 +2657,7 @@ "uri":"kafka-faq-0043.html", "node_id":"kafka-faq-0043.xml", "product_code":"kafka", - "code":"139", + "code":"145", "des":"This depends on the offsets.retention.minutes and auto.create.groups.enable parameters.For instances created much earlier, auto.create.groups.enable is set to true by def", "doc_type":"usermanual", "kw":"Will a Consumer Group Without Active Consumers Be Automatically Deleted in 14 Days?,Consumer Groups,", @@ -2562,7 +2675,7 @@ "uri":"kafka_faq_0059.html", "node_id":"kafka_faq_0059.xml", "product_code":"kafka", - "code":"140", + "code":"146", "des":"Possible cause: Automatic consumer group creation has been enabled and your service is connected to the consumer group and consuming messages. Therefore, the consumer gro", "doc_type":"usermanual", "kw":"Why Does a Deleted Consumer Group Still Exist?,Consumer Groups,User Guide", @@ -2580,7 +2693,7 @@ "uri":"kafka_faq_0060.html", "node_id":"kafka_faq_0060.xml", "product_code":"kafka", - "code":"141", + "code":"147", "des":"Check whether Flink is used for consumption. Flink uses the assign mode and the client assigns specific partitions to be consumed, so you cannot see any consumer on the K", "doc_type":"usermanual", "kw":"Why Can't I View Consumers When Instance Consumption Is Normal?,Consumer Groups,User Guide", @@ -2598,7 +2711,7 @@ "uri":"kafka-faq-190416001.html", "node_id":"kafka-faq-190416001.xml", "product_code":"kafka", - "code":"142", + "code":"148", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Messages", @@ -2616,7 +2729,7 @@ "uri":"kafka-faq-200426035.html", "node_id":"kafka-faq-200426035.xml", "product_code":"kafka", - "code":"143", + "code":"149", "des":"10 MB.", "doc_type":"usermanual", "kw":"What Is the Maximum Size of a Message that Can be Created?,Messages,User Guide", @@ -2634,7 +2747,7 @@ "uri":"kafka-faq-200426036.html", "node_id":"kafka-faq-200426036.xml", "product_code":"kafka", - "code":"144", + "code":"150", "des":"Rebalancing is a process where partitions of topics are re-allocated for a consumer group.In normal cases, rebalancing occurs inevitably when a consumer is added to or re", "doc_type":"usermanual", "kw":"Why Does Message Poll Often Fail During Rebalancing?,Messages,User Guide", @@ -2652,7 +2765,7 @@ "uri":"kafka-faq-200426037.html", "node_id":"kafka-faq-200426037.xml", "product_code":"kafka", - "code":"145", + "code":"151", "des":"Possible cause 1: The message has been aged.Solution: Change the aging time.Solution: Change the aging time.Possible cause 2: The createTime timestamp of the message is i", "doc_type":"usermanual", "kw":"Why Can't I Query Messages on the Console?,Messages,User Guide", @@ -2670,7 +2783,7 @@ "uri":"kafka-faq-200426100.html", "node_id":"kafka-faq-200426100.xml", "product_code":"kafka", - "code":"146", + "code":"152", "des":"Symptom: An alarm is generated for the Accumulated Messages metric.Solution:Log in to the Kafka console and click the instance for which the alarm is generated. The insta", "doc_type":"usermanual", "kw":"What Can I Do If Kafka Messages Are Accumulated?,Messages,User Guide", @@ -2688,7 +2801,7 @@ "uri":"kafka-faq-200708001.html", "node_id":"kafka-faq-200708001.xml", "product_code":"kafka", - "code":"147", + "code":"153", "des":"If the aging time has been set for a topic, the value of the log.retention.hours parameter does not take effect for the topic. The value of the log.retention.hours parame", "doc_type":"usermanual", "kw":"Why Do Messages Still Exist After the Retention Period Elapses?,Messages,User Guide", @@ -2706,7 +2819,7 @@ "uri":"kafka-faq-0018.html", "node_id":"kafka-faq-0018.xml", "product_code":"kafka", - "code":"148", + "code":"154", "des":"No.", "doc_type":"usermanual", "kw":"Do Kafka Instances Support Delayed Message Delivery?,Messages,User Guide", @@ -2724,7 +2837,7 @@ "uri":"kafka-faq-0041.html", "node_id":"kafka-faq-0041.xml", "product_code":"kafka", - "code":"149", + "code":"155", "des":"View the number of accumulated messages using any of the following methods:On the Consumer Groups page of an instance, click the name of the consumer group whose accumula", "doc_type":"usermanual", "kw":"How Do I View the Number of Accumulated Messages?,Messages,User Guide", @@ -2742,7 +2855,7 @@ "uri":"kafka-faq-0045.html", "node_id":"kafka-faq-0045.xml", "product_code":"kafka", - "code":"150", + "code":"156", "des":"The message creation time is specified by CreateTime when a producer creates messages. If this parameter is not set during message creation, the message creation time is ", "doc_type":"usermanual", "kw":"Why Is the Message Creation Time Displayed as Year 1970?,Messages,User Guide", @@ -2760,7 +2873,7 @@ "uri":"kafka_faq_0058.html", "node_id":"kafka_faq_0058.xml", "product_code":"kafka", - "code":"151", + "code":"157", "des":"message.max.bytes can be modified on the Parameters page on the console. For details, see Modifying Kafka Instance Configuration Parameters.The maximum value of message.m", "doc_type":"usermanual", "kw":"How Do I Modify message.max.bytes?,Messages,User Guide", @@ -2778,7 +2891,7 @@ "uri":"kafka-faq-191030004.html", "node_id":"kafka-faq-191030004.xml", "product_code":"kafka", - "code":"152", + "code":"158", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Monitoring & Alarm", @@ -2796,7 +2909,7 @@ "uri":"kafka-faq-200426041.html", "node_id":"kafka-faq-200426041.xml", "product_code":"kafka", - "code":"153", + "code":"159", "des":"If topic monitoring data is not displayed, the possible causes are as follows:The topic name starts with a special character, such as an underscore (_) or a number sign (", "doc_type":"usermanual", "kw":"Why Can't I View the Monitoring Data?,Monitoring & Alarm,User Guide", @@ -2814,7 +2927,7 @@ "uri":"kafka-faq-0007.html", "node_id":"kafka-faq-0007.xml", "product_code":"kafka", - "code":"154", + "code":"160", "des":"Symptom: The monitoring data shows that there are 810 million accumulated messages. However, the Kafka console shows that there are 100 million messages in all six topics", "doc_type":"usermanual", "kw":"Why Is the Monitored Number of Accumulated Messages Inconsistent with the Message Quantity Displayed", @@ -2832,7 +2945,7 @@ "uri":"kafka-faq-0022.html", "node_id":"kafka-faq-0022.xml", "product_code":"kafka", - "code":"155", + "code":"161", "des":"The monitoring data is reported every minute. The reported data will be displayed on the monitoring page after being sorted. This process takes less than 20 minutes. Afte", "doc_type":"usermanual", "kw":"Why Is a Consumer Group Still on the Monitoring Page After Being Deleted?,Monitoring & Alarm,User Gu", @@ -2850,7 +2963,7 @@ "uri":"kafka-ug-0723006.html", "node_id":"kafka-ug-0723006.xml", "product_code":"kafka", - "code":"156", + "code":"162", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Troubleshooting", @@ -2868,7 +2981,7 @@ "uri":"kafka-faq-0604001.html", "node_id":"kafka-faq-0604001.xml", "product_code":"kafka", - "code":"157", + "code":"163", "des":"This section describes how to troubleshoot Kafka connection problems.If the connection to a Kafka instance is abnormal, perform the following operations to troubleshoot t", "doc_type":"usermanual", "kw":"Troubleshooting Kafka Connection Exceptions,Troubleshooting,User Guide", @@ -2886,7 +2999,7 @@ "uri":"kafka-trouble-0709001.html", "node_id":"kafka-trouble-0709001.xml", "product_code":"kafka", - "code":"158", + "code":"164", "des":"The duration from message creation to retrieval occasionally reaches 6 minutes, which is not tolerable to services.Service requests are stacked and cannot be processed in", "doc_type":"usermanual", "kw":"Troubleshooting 6-Min Latency Between Message Creation and Retrieval,Troubleshooting,User Guide", @@ -2904,7 +3017,7 @@ "uri":"kafka-trouble-0001.html", "node_id":"kafka-trouble-0001.xml", "product_code":"kafka", - "code":"159", + "code":"165", "des":"The system displays the error message \"Disk error when trying to access log file on the disk\".The disk usage of the broker is too high.Expand the disk space by referring ", "doc_type":"usermanual", "kw":"Troubleshooting Message Creation Failures,Troubleshooting,User Guide", @@ -2922,7 +3035,7 @@ "uri":"kafka-trouble-0002.html", "node_id":"kafka-trouble-0002.xml", "product_code":"kafka", - "code":"160", + "code":"166", "des":"A deleted topic still exists.Automatic topic creation has been enabled for the instance, and a consumer is connecting to the topic. If services are not stopped, message c", "doc_type":"usermanual", "kw":"Troubleshooting Topic Deletion Failures,Troubleshooting,User Guide", @@ -2940,7 +3053,7 @@ "uri":"kafka-trouble-0004.html", "node_id":"kafka-trouble-0004.xml", "product_code":"kafka", - "code":"161", + "code":"167", "des":"For a Kafka instance deployed in multiple AZs, if one of the AZs is faulty, error message \"Topic {{topic_name}} not present in metadata after 60000 ms\" may be reported on", "doc_type":"usermanual", "kw":"Troubleshooting Error \"Topic {{topic_name}} not present in metadata after 60000 ms\" During Message P", @@ -2958,7 +3071,7 @@ "uri":"kafka-ug-00001.html", "node_id":"kafka-ug-00001.xml", "product_code":"kafka", - "code":"162", + "code":"168", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", @@ -2976,7 +3089,7 @@ "uri":"kafka-ug-00002.html", "node_id":"kafka-ug-00002.xml", "product_code":"dms", - "code":"163", + "code":"169", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Acronyms and Abbreviations,User Guide", @@ -2994,7 +3107,7 @@ "uri":"dms-ug-0312114.html", "node_id":"dms-ug-0312114.xml", "product_code":"dms", - "code":"164", + "code":"170", "des":"See Glossary.", "doc_type":"usermanual", "kw":"Glossary,User Guide", diff --git a/docs/dms/umn/CLASS.TXT.json b/docs/dms/umn/CLASS.TXT.json index 9b4143ba..d333a24d 100644 --- a/docs/dms/umn/CLASS.TXT.json +++ b/docs/dms/umn/CLASS.TXT.json @@ -99,7 +99,7 @@ "code":"11" }, { - "desc":"You can use Identity and Access Management (IAM) to manage DMS for Kafka permissions and control access to your resources. IAM provides identity authentication, permissio", + "desc":"If you need to grant your enterprise personnel permission to access your DMS resources, use Identity and Access Management (IAM). IAM provides identity authentication, fi", "product_code":"dms", "title":"Permission", "uri":"ProductDescPrivilegeManagement.html", @@ -117,7 +117,7 @@ "code":"13" }, { - "desc":"This section takes the example of creating a Kafka 2.7 instance (ciphertext access and SASL_SSL) and accessing it on the client (private network, within a virtual private", + "desc":"This section takes the example of creating a Kafka instance (ciphertext access and SASL_SSL) and accessing it on the client (private network, within a virtual private clo", "product_code":"dms", "title":"Getting Started with Kafka for Message Production and Consumption", "uri":"kafka-qs-0409001.html", @@ -126,7 +126,7 @@ "code":"14" }, { - "desc":"The following figure shows the process of using a Kafka instance to produce and consume messages.Creating a User and Granting DMS for Kafka PermissionsCreate IAM users an", + "desc":"Distributed Message Service is a message queuing service that is based on the open-source Apache Kafka. It provides Kafka instances with isolated computing, storage, and ", "product_code":"dms", "title":"Process of Using Kafka", "uri":"kafka-ug-0069.html", @@ -171,7 +171,7 @@ "code":"19" }, { - "desc":"Topics store messages created by producers and subscribed by consumers. If automatic topic creation is not enabled during Kafka instance creation, you need to manually cr", + "desc":"Topics store messages created by producers and subscribed by consumers. If Automatic Topic Creation is not enabled during Kafka instance creation, you need to manually cr", "product_code":"dms", "title":"Creating a Kafka Topic", "uri":"kafka-ug-180604018.html", @@ -180,7 +180,7 @@ "code":"20" }, { - "desc":"DMS supports access control list (ACL) for topics. You can differentiate user permissions by granting users different permissions in a topic.This section describes how to", + "desc":"Kafka instances with ciphertext access enabled support access control list (ACL) for topics. You can differentiate user permissions by granting users different permission", "product_code":"dms", "title":"Configuring Kafka Topic Permissions", "uri":"kafka-ug-0002.html", @@ -198,7 +198,7 @@ "code":"22" }, { - "desc":"On the console, you can view the details of a Kafka instance including subscriptions to a topic, offsets and number of messages in each partition, and producer addresses.", + "desc":"On the Kafka console, you can view basic information, partition and producer information, and subscriptions of a topic.Select the region where your Kafka instance is loca", "product_code":"dms", "title":"Viewing Kafka Topic Details", "uri":"kafka_ug_0045.html", @@ -243,7 +243,7 @@ "code":"27" }, { - "desc":"Automatic topic creation: A topic will be automatically created when a message is produced in or consumed from a topic that does not exist. By default, the topic has para", + "desc":"Automatic Topic Creation indicates that a topic will be automatically created when a message is produced in or consumed from a topic that does not exist. By default, the ", "product_code":"dms", "title":"Configuring Automatic Topic Creation", "uri":"kafka_ug_0043.html", @@ -306,7 +306,7 @@ "code":"34" }, { - "desc":"You can use destination NAT (DNAT) to access a Kafka instance so that the instance can provide services on the public network through port mapping.You have created EIPs. ", + "desc":"Enable public access in either of the following ways:On the Kafka console, access Kafka instances using EIPs. For details, see Configuring Kafka Public Access.Configure p", "product_code":"dms", "title":"Accessing Kafka in a Public Network Using DNAT", "uri":"kafka-dnat.html", @@ -333,9 +333,9 @@ "code":"37" }, { - "desc":"DMS supports access control list (ACL) for topics. You can differentiate user permissions by granting users different permissions in a topic.This section describes how to", + "desc":"Kafka instances with ciphertext access enabled support access control list (ACL) for topics. You can isolate users by granting them different permissions in a topic.This ", "product_code":"dms", - "title":"Configuring Kafka Users", + "title":"Configuring Kafka ACL Users", "uri":"kafka-ug-0003.html", "doc_type":"usermanual", "p_code":"36", @@ -369,7 +369,7 @@ "code":"41" }, { - "desc":"This section describes how to use an open-source Kafka client to access a Kafka instance in plaintext. Two scenarios: private network within a VPC and public network. To ", + "desc":"This section describes how to access a Kafka instance in plaintext on an open-source Kafka client. With plaintext access enabled, there is no authentication required in s", "product_code":"dms", "title":"Connecting to Kafka Using the Client (Plaintext Access)", "uri":"kafka-ug-180604020.html", @@ -378,7 +378,7 @@ "code":"42" }, { - "desc":"If you enable ciphertext access when creating an instance, SASL authentication will be required when your client connects to a Kafka instance.For security purposes, TLS_E", + "desc":"This section describes how to access a Kafka instance in ciphertext on an open-source Kafka client. Accessing in ciphertext requires SASL authentication. The protocol SAS", "product_code":"dms", "title":"Connecting to Kafka Using the Client (Ciphertext Access)", "uri":"kafka-ug-180801001.html", @@ -414,7 +414,7 @@ "code":"46" }, { - "desc":"This section describes how to delete messages on the console.Deleted messages cannot be recovered.Before deleting a message, set the auto.offset.reset parameter in the co", + "desc":"This section describes how to delete messages stored in a topic on the console.Deleted messages cannot be recovered.Before deleting a message, set the auto.offset.reset p", "product_code":"dms", "title":"Deleting Kafka Messages", "uri":"kafka_ug_0046.html", @@ -432,7 +432,7 @@ "code":"48" }, { - "desc":"Create a consumer group on the console.auto.create.groups.enable: a consumer group is automatically created when a consumer attempts to enter a group that does not exist.", + "desc":"A consumer subscribes to a topic. A consumer group consists of one or more consumers. Within a consumer group, each consumer can consume multiple partitions at the same t", "product_code":"dms", "title":"Creating a Kafka Consumer Group", "uri":"kafka-ug-0041.html", @@ -441,7 +441,7 @@ "code":"49" }, { - "desc":"This section describes how to query the consumer group list.Select the region where your Kafka instance is located.The consumer group name, status, and Coordinator (ID) a", + "desc":"After a consumer group is created, you can view its configuration and status.Select the region where your Kafka instance is located.The consumer group name, status, and C", "product_code":"dms", "title":"Querying the Kafka Consumer Group List", "uri":"kafka_ug_0021.html", @@ -450,16 +450,16 @@ "code":"50" }, { - "desc":"This section describes how to view the consumer list and consumer connection addresses.The consumer list and connection address can be viewed only when consumers in a con", + "desc":"If a consumer group has consumers who are accessing a Kafka instance, you can view their connection information.The consumer list and connection address can be viewed onl", "product_code":"dms", - "title":"Viewing Kafka Consumer Details", + "title":"Viewing Kafka Consumer Information", "uri":"kafka-ug-0015.html", "doc_type":"usermanual", "p_code":"48", "code":"51" }, { - "desc":"This section describes how to view and reset consumption offsets. Resetting consumption offsets is to change the consumption position for consumers.Messages may be retrie", + "desc":"A consumption offset indicates the consumption progress of a consumer. This section describes how to view and reset consumption offsets.Messages may be retrieved more tha", "product_code":"dms", "title":"Viewing and Resetting Kafka Consumption Offsets", "uri":"kafka-ug-0014.html", @@ -468,7 +468,7 @@ "code":"52" }, { - "desc":"Export the consumer group list from the console.Select the region where your Kafka instance is located.Select the desired consumer groups and choose Export > Export selec", + "desc":"You can export a list of consumer groups in a Kafka instance.Select the region where your Kafka instance is located.Select the desired consumer groups and choose Export >", "product_code":"dms", "title":"Exporting Kafka Consumer Groups", "uri":"kafka-ug-0056.html", @@ -495,7 +495,7 @@ "code":"55" }, { - "desc":"This section describes how to view the details, and modify the basic information of a Kafka instance on the console.After creating a Kafka instance, you can modify some p", + "desc":"After creating a Kafka instance, you can view the details or modify some parameters of it on the console as required. These parameters include the instance name, descript", "product_code":"dms", "title":"Viewing and Modifying Basic Information of a Kafka Instance", "uri":"kafka-ug-180604014.html", @@ -504,7 +504,7 @@ "code":"56" }, { - "desc":"This section describes how to view the disk usage of each broker on the Kafka console.This function is unavailable for single-node instances.Select the region where your ", + "desc":"This section describes how to view the disk usage of each broker of a Kafka instance on the console.This function is unavailable for single-node instances.Select the regi", "product_code":"dms", "title":"Viewing Kafka Disk Usage", "uri":"kafka-ug-0004.html", @@ -522,7 +522,7 @@ "code":"58" }, { - "desc":"On the console, view sample code for creating and retrieving messages in Java, Go, and Python.Select the region where your Kafka instance is located.View sample code for ", + "desc":"Distributed Message Service allows you to view sample Java, Go, and Python code of producing and consuming messages on the console. You can quickly complete Kafka client ", "product_code":"dms", "title":"Viewing Sample Code of Kafka Production and Consumption", "uri":"kafka_ug_0024.html", @@ -549,7 +549,7 @@ "code":"61" }, { - "desc":"This section describes how to export the Kafka instance list from the console.Select the region where your Kafka instance is located.Select the desired instances and choo", + "desc":"You can export a list of instances on the DMS console.Select the region where your Kafka instance is located.Select the desired instances and choose Export > Export selec", "product_code":"dms", "title":"Exporting the Kafka Instance List", "uri":"kafka-ug-0053.html", @@ -558,7 +558,7 @@ "code":"62" }, { - "desc":"Restart one or more Kafka instances at a time on the DMS console.When a Kafka instance is being restarted, message retrieval and creation requests of clients will be reje", + "desc":"You can restart one or more Kafka instances in batches on the DMS console.When a Kafka instance is being restarted, message retrieval and creation requests of clients wil", "product_code":"dms", "title":"Restarting a Kafka Instance", "uri":"kafka-ug-180604015.html", @@ -602,6 +602,60 @@ "p_code":"66", "code":"67" }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dms", + "title":"Migrating Data Using Smart Connect", + "uri":"kafka-ug-0065.html", + "doc_type":"usermanual", + "p_code":"66", + "code":"68" + }, + { + "desc":"Smart Connect synchronizes data between Kafka and other cloud services (such as OBS) or between two Kafka instances for backup or migration.Procedure for using Smart Conn", + "product_code":"dms", + "title":"Enabling Smart Connect", + "uri":"kafka_ug_0017.html", + "doc_type":"usermanual", + "p_code":"68", + "code":"69" + }, + { + "desc":"Create a Smart Connect task to copy data unidirectionally or bidirectionally between two Kafka instances.Data in the source Kafka instance is synchronized to the target K", + "product_code":"dms", + "title":"Replicating Kafka Instance Data", + "uri":"kafka-ug-0034.html", + "doc_type":"usermanual", + "p_code":"68", + "code":"70" + }, + { + "desc":"Create a Smart Connect task to dump Kafka instance data to OBS for message data backup.Data in the source Kafka instance is synchronized to the dumping file in real time.", + "product_code":"dms", + "title":"Dumping Kafka Data to Object Storage Service (OBS)", + "uri":"kafka-ug-0035.html", + "doc_type":"usermanual", + "p_code":"68", + "code":"71" + }, + { + "desc":"View, delete, start, pause, or restart a Smart Connect task.This function is unavailable for single-node instances. Kafka 3.x instances do not support this function.A Sma", + "product_code":"dms", + "title":"Managing Smart Connect Tasks", + "uri":"kafka_ug_0018.html", + "doc_type":"usermanual", + "p_code":"68", + "code":"72" + }, + { + "desc":"Disable Smart Connect and resources can be freed.Disabling Smart Connect does not affect services.This function is unavailable for single-node instances. Kafka 3.x instan", + "product_code":"dms", + "title":"Disabling Smart Connect", + "uri":"kafka_ug_0041.html", + "doc_type":"usermanual", + "p_code":"68", + "code":"73" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dms", @@ -609,16 +663,16 @@ "uri":"kafka-ug-180413001.html", "doc_type":"usermanual", "p_code":"", - "code":"68" + "code":"74" }, { "desc":"Cloud Eye monitors Kafka instance metrics in real time. You can view these metrics on the Cloud Eye console.At least one Kafka instance has been created. The instance has", "product_code":"dms", - "title":"Viewing Kafka Monitoring Metrics", + "title":"Viewing Kafka Metrics", "uri":"kafka-ug-190605001.html", "doc_type":"usermanual", - "p_code":"68", - "code":"69" + "p_code":"74", + "code":"75" }, { "desc":"This section describes metrics reported by DMS to Cloud Eye as well as their namespaces and dimensions. You can use the Cloud Eye console or APIs to query the Kafka metri", @@ -626,8 +680,8 @@ "title":"Kafka Metrics", "uri":"kafka-ug-180413002.html", "doc_type":"usermanual", - "p_code":"68", - "code":"70" + "p_code":"74", + "code":"76" }, { "desc":"This section describes the alarm rules of some metrics and how to configure them. In actual services, you are advised to configure alarm rules for metrics based on the fo", @@ -635,8 +689,8 @@ "title":"Configuring a Kafka Alarm Rule", "uri":"kafka-ug-180524001.html", "doc_type":"usermanual", - "p_code":"68", - "code":"71" + "p_code":"74", + "code":"77" }, { "desc":"With Cloud Trace Service (CTS), you can record operations associated with DMS for later query, audit, and backtrack operations.CTS has been enabled.See Querying Real-Time", @@ -645,7 +699,7 @@ "uri":"kafka-ug-180418002.html", "doc_type":"usermanual", "p_code":"", - "code":"72" + "code":"78" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -654,7 +708,7 @@ "uri":"kafka-ug-0723004.html", "doc_type":"usermanual", "p_code":"", - "code":"73" + "code":"79" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -662,8 +716,8 @@ "title":"Instances", "uri":"kafka-faq-191030002.html", "doc_type":"usermanual", - "p_code":"73", - "code":"74" + "p_code":"79", + "code":"80" }, { "desc":"To improve the reliability of a Kafka instance, you are advised to select three AZs or more when creating the instance. You cannot select two AZs.Each Kafka instance cont", @@ -671,8 +725,8 @@ "title":"Why Can't I Select Two AZs?", "uri":"kafka-faq-200426002.html", "doc_type":"usermanual", - "p_code":"74", - "code":"75" + "p_code":"80", + "code":"81" }, { "desc":"This may be because you do not have the Server Administrator and VPC Administrator permissions. For details about how to add permissions to a user group, see Viewing and ", @@ -680,8 +734,8 @@ "title":"Why Can't I View the Subnet and Security Group Information When Creating a DMS Instance?", "uri":"kafka-faq-200426003.html", "doc_type":"usermanual", - "p_code":"74", - "code":"76" + "p_code":"80", + "code":"82" }, { "desc":"The storage space is the space for storing messages (including messages in replicas), logs and metadata. To select a storage space, specify the disk type and disk size. F", @@ -689,8 +743,8 @@ "title":"How Do I Select Storage Space for a Kafka Instance?", "uri":"kafka-faq-200426005.html", "doc_type":"usermanual", - "p_code":"74", - "code":"77" + "p_code":"80", + "code":"83" }, { "desc":"High I/O: The average latency is 6 to 10 ms, and the maximum bandwidth is 150 MB/s (read + write).Ultra-high I/O: The average latency is 1 to 3 ms, and the maximum bandwi", @@ -698,8 +752,8 @@ "title":"How Do I Choose Between High I/O and Ultra-high I/O?", "uri":"kafka-faq-200426006.html", "doc_type":"usermanual", - "p_code":"74", - "code":"78" + "p_code":"80", + "code":"84" }, { "desc":"The following policies are supported:Stop productionWhen the memory usage reaches the disk capacity threshold (95%), new messages will no longer be created, but existing ", @@ -707,8 +761,8 @@ "title":"Which Capacity Threshold Policy Should I Use?", "uri":"kafka-faq-200426007.html", "doc_type":"usermanual", - "p_code":"74", - "code":"79" + "p_code":"80", + "code":"85" }, { "desc":"Kafka v2.3.0, v2.7, and v3.x.For details about how to create a Kafka instance, see Creating a Kafka Instance.", @@ -716,8 +770,8 @@ "title":"Which Kafka Versions Are Supported?", "uri":"kafka-faq-200426008.html", "doc_type":"usermanual", - "p_code":"74", - "code":"80" + "p_code":"80", + "code":"86" }, { "desc":"Kafka instances are managed using ZooKeeper. Opening ZooKeeper may cause misoperations and service losses. ZooKeeper is used only within Kafka clusters and does not provi", @@ -725,8 +779,8 @@ "title":"What Is the ZooKeeper Address of a Kafka Instance?", "uri":"kafka-faq-200426009.html", "doc_type":"usermanual", - "p_code":"74", - "code":"81" + "p_code":"80", + "code":"87" }, { "desc":"Kafka instances are classified into single-node and cluster types. A single-node instance has only one broker in single-node mode. A cluster instance consists of three or", @@ -734,8 +788,8 @@ "title":"Are Kafka Instances in Cluster Mode?", "uri":"kafka-faq-200426010.html", "doc_type":"usermanual", - "p_code":"74", - "code":"82" + "p_code":"80", + "code":"88" }, { "desc":"No. You must access a Kafka instance through one of the following ports:Accessing a Kafka instance without SASL:The port varies with the access mode:Intra-VPC access: por", @@ -743,8 +797,8 @@ "title":"Can I Modify the Port for Accessing a Kafka Instance?", "uri":"kafka-faq-200426011.html", "doc_type":"usermanual", - "p_code":"74", - "code":"83" + "p_code":"80", + "code":"89" }, { "desc":"The certificates are valid for more than 15 years. You do not need to worry about certificate expiration. The certificates are used for one-way authentication when enabli", @@ -752,17 +806,17 @@ "title":"How Long Are Kafka SSL Certificates Valid for?", "uri":"kafka-faq-200426012.html", "doc_type":"usermanual", - "p_code":"74", - "code":"84" + "p_code":"80", + "code":"90" }, { - "desc":"Unfortunately, you cannot synchronize two Kafka instances in real time. To migrate services from one instance to another, create messages to both instances. After all mes", + "desc":"On the Kafka console, you can create a Smart Connect task for instance data replication. For details, see Replicating Kafka Instance Data.", "product_code":"dms", "title":"How Do I Synchronize Data from One Kafka Instance to Another?", "uri":"kafka-faq-200426013.html", "doc_type":"usermanual", - "p_code":"74", - "code":"85" + "p_code":"80", + "code":"91" }, { "desc":"The SASL_SSL setting can be changed for cluster instances (see Configuring Plaintext or Ciphertext Access to Kafka Instances), but cannot be changed for single-node insta", @@ -770,8 +824,8 @@ "title":"How Do I Change the SASL_SSL Setting of a Kafka Instance?", "uri":"kafka-faq-200426014.html", "doc_type":"usermanual", - "p_code":"74", - "code":"86" + "p_code":"80", + "code":"92" }, { "desc":"After an instance is created, its SASL mechanism cannot be modified. If you want to change it, create an instance again.", @@ -779,8 +833,8 @@ "title":"How Do I Modify the SASL Mechanism?", "uri":"kafka_faq_0052.html", "doc_type":"usermanual", - "p_code":"74", - "code":"87" + "p_code":"80", + "code":"93" }, { "desc":"The security protocol can be changed on the console. In the Connection area on the Kafka instance details page, disable Ciphertext Access and then configure security prot", @@ -788,8 +842,8 @@ "title":"How Do I Change the Security Protocol?", "uri":"kafka_faq_0062.html", "doc_type":"usermanual", - "p_code":"74", - "code":"88" + "p_code":"80", + "code":"94" }, { "desc":"No. A Kafka instance will not be restarted if you modify its enterprise project.", @@ -797,8 +851,8 @@ "title":"Will a Kafka Instance Be Restarted After Its Enterprise Project Is Modified?", "uri":"kafka-faq-0008.html", "doc_type":"usermanual", - "p_code":"74", - "code":"89" + "p_code":"80", + "code":"95" }, { "desc":"Kafka brokers and ZooKeeper are deployed on the same VM.", @@ -806,8 +860,8 @@ "title":"Are Kafka Brokers and ZooKeeper Deployed on the Same VM or on Different VMs?", "uri":"kafka-faq-0015.html", "doc_type":"usermanual", - "p_code":"74", - "code":"90" + "p_code":"80", + "code":"96" }, { "desc":"For security purposes, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is supported.", @@ -815,8 +869,8 @@ "title":"Which Cipher Suites Are Supported by Kafka?", "uri":"kafka-faq-0020.html", "doc_type":"usermanual", - "p_code":"74", - "code":"91" + "p_code":"80", + "code":"97" }, { "desc":"No. The AZ cannot be changed once the instance is created. To use multiple AZs, create another instance.", @@ -824,8 +878,8 @@ "title":"Can I Change Single-AZ Deployment to Multi-AZ Deployment for an Instance?", "uri":"kafka-faq-0023.html", "doc_type":"usermanual", - "p_code":"74", - "code":"92" + "p_code":"80", + "code":"98" }, { "desc":"DMS for Kafka supports cross-AZ disaster recovery. If you select multiple AZs when creating an instance, cross-AZ disaster recovery will be available.You can view the AZs", @@ -833,8 +887,8 @@ "title":"Does DMS for Kafka Support Cross-AZ Disaster Recovery? Where Can I Check Whether an Existing Instance is Across-AZs?", "uri":"kafka-faq-0025.html", "doc_type":"usermanual", - "p_code":"74", - "code":"93" + "p_code":"80", + "code":"99" }, { "desc":"Yes.", @@ -842,8 +896,8 @@ "title":"Do Kafka Instances Support Disk Encryption?", "uri":"kafka-faq-0030.html", "doc_type":"usermanual", - "p_code":"74", - "code":"94" + "p_code":"80", + "code":"100" }, { "desc":"No. Once an instance is created, its VPC and subnet cannot be changed.", @@ -851,8 +905,8 @@ "title":"Can I Change the VPC and Subnet After a Kafka Instance Is Created?", "uri":"kafka-faq-0036.html", "doc_type":"usermanual", - "p_code":"74", - "code":"95" + "p_code":"80", + "code":"101" }, { "desc":"You can find Kafka Streams use cases on the official Kafka website.", @@ -860,8 +914,8 @@ "title":"Where Can I Find Kafka Streams Use Cases?", "uri":"kafka-faq-0037.html", "doc_type":"usermanual", - "p_code":"74", - "code":"96" + "p_code":"80", + "code":"102" }, { "desc":"No. Kafka instances cannot be upgraded once they are created. To use a higher Kafka version, create another Kafka instance.", @@ -869,8 +923,8 @@ "title":"Can I Upgrade Kafka Instances?", "uri":"kafka-faq-0040.html", "doc_type":"usermanual", - "p_code":"74", - "code":"97" + "p_code":"80", + "code":"103" }, { "desc":"On the DMS console, click the name of the target Kafka instance. Disable Public Access in the Connection section on the Basic Information tab page, and then enable it aga", @@ -878,8 +932,8 @@ "title":"How Do I Bind an EIP Again?", "uri":"kafka_faq_0046.html", "doc_type":"usermanual", - "p_code":"74", - "code":"98" + "p_code":"80", + "code":"104" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -887,8 +941,8 @@ "title":"Specification Modification", "uri":"kafka_faq_0053.html", "doc_type":"usermanual", - "p_code":"73", - "code":"99" + "p_code":"79", + "code":"105" }, { "desc":"Table 1 describes the impact of increasing specifications. It takes 5 to 10 minutes to modify specifications on one broker. The more brokers, the longer time the modifica", @@ -896,8 +950,8 @@ "title":"Does Specification Modification Affect Services?", "uri":"kafka-faq-0035.html", "doc_type":"usermanual", - "p_code":"99", - "code":"100" + "p_code":"105", + "code":"106" }, { "desc":"No. Data will not be migrated when you increase specifications.", @@ -905,8 +959,8 @@ "title":"Will Data Migration Be Involved When I Increase Specifications?", "uri":"kafka_faq_0054.html", "doc_type":"usermanual", - "p_code":"99", - "code":"101" + "p_code":"105", + "code":"107" }, { "desc":"Possible cause: When you increase the broker flavor, a rolling restart is performed on brokers. During the restart, partition leaders are changed. The producer has cached", @@ -914,8 +968,8 @@ "title":"Why Does Message Production Fail During Scaling?", "uri":"kafka_faq_0056.html", "doc_type":"usermanual", - "p_code":"99", - "code":"102" + "p_code":"105", + "code":"108" }, { "desc":"Symptom: Specifications fail to be increased, and a message is displayed indicating that the underlying ECS/EVS resources are insufficient. However, the required ECSs can", @@ -923,8 +977,8 @@ "title":"What Can I Do When I Fail to Increase Specifications Due to Insufficient Resources?", "uri":"kafka_faq_0057.html", "doc_type":"usermanual", - "p_code":"99", - "code":"103" + "p_code":"105", + "code":"109" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -932,8 +986,8 @@ "title":"Connections", "uri":"kafka-faq-191030001.html", "doc_type":"usermanual", - "p_code":"73", - "code":"104" + "p_code":"79", + "code":"110" }, { "desc":"Kafka instances can be accessed within a VPC, across VPCs, through DNAT, or over public networks. Before accessing a Kafka instance, configure a security group.If they us", @@ -941,8 +995,8 @@ "title":"How Do I Select and Configure a Security Group?", "uri":"kafka-faq-180604024.html", "doc_type":"usermanual", - "p_code":"104", - "code":"105" + "p_code":"110", + "code":"111" }, { "desc":"Yes. For details, see the instance access instructions.", @@ -950,8 +1004,8 @@ "title":"Can I Access a Kafka Instance Over a Public Network?", "uri":"kafka-faq-200426015.html", "doc_type":"usermanual", - "p_code":"104", - "code":"106" + "p_code":"110", + "code":"112" }, { "desc":"The number of connection addresses of a Kafka instance is the same as the number of brokers of the instance. The following table lists the number of brokers corresponding", @@ -959,8 +1013,8 @@ "title":"How Many Connection Addresses Does a Kafka Instance Have by Default?", "uri":"kafka-faq-200426016.html", "doc_type":"usermanual", - "p_code":"104", - "code":"107" + "p_code":"110", + "code":"113" }, { "desc":"Yes. You can access a Kafka instance across regions over a public network or by using direct connections.", @@ -968,8 +1022,8 @@ "title":"Do Kafka Instances Support Cross-Region Access?", "uri":"kafka-faq-200426017.html", "doc_type":"usermanual", - "p_code":"104", - "code":"108" + "p_code":"110", + "code":"114" }, { "desc":"Yes. You can use one of the following methods to access a Kafka instance across VPCs:Establish a VPC peering connection to allow two VPCs to communicate with each other. ", @@ -977,8 +1031,8 @@ "title":"Do Kafka Instances Support Cross-VPC Access?", "uri":"kafka-faq-200426019.html", "doc_type":"usermanual", - "p_code":"104", - "code":"109" + "p_code":"110", + "code":"115" }, { "desc":"Yes.If the client and the instance are in the same VPC, cross-subnet access is supported. By default, subnets in the same VPC can communicate with each other.", @@ -986,8 +1040,8 @@ "title":"Do Kafka Instances Support Cross-Subnet Access?", "uri":"kafka-faq-200426020.html", "doc_type":"usermanual", - "p_code":"104", - "code":"110" + "p_code":"110", + "code":"116" }, { "desc":"No, Kerberos authentication is not supported. Kafka supports client authentication with SASL and API calling authentication using tokens and AK/SK.To access an instance i", @@ -995,8 +1049,8 @@ "title":"Does DMS for Kafka Support Authentication with Kerberos?", "uri":"kafka-faq-200426023.html", "doc_type":"usermanual", - "p_code":"104", - "code":"111" + "p_code":"110", + "code":"117" }, { "desc":"Yes. No password is required when accessing a Kafka instance in plaintext. For details, see Connecting to Kafka Using the Client (Plaintext Access).", @@ -1004,8 +1058,8 @@ "title":"Does DMS for Kafka Support Password-Free Access?", "uri":"kafka-faq-200708002.html", "doc_type":"usermanual", - "p_code":"104", - "code":"112" + "p_code":"110", + "code":"118" }, { "desc":"Click the name of your Kafka instance. In the Connection section on the Basic Information tab page, view Instance Address (Public Network).For details about how to connec", @@ -1013,8 +1067,8 @@ "title":"How Do I Obtain the Public Access Address After Public Access Is Enabled?", "uri":"kafka-faq-0001.html", "doc_type":"usermanual", - "p_code":"104", - "code":"113" + "p_code":"110", + "code":"119" }, { "desc":"No.", @@ -1022,8 +1076,8 @@ "title":"Does DMS for Kafka Support Authentication on Clients by the Server?", "uri":"kafka-faq-0026.html", "doc_type":"usermanual", - "p_code":"104", - "code":"114" + "p_code":"110", + "code":"120" }, { "desc":"No. You can only use JKS certificates for connecting to instances in Java.", @@ -1031,8 +1085,8 @@ "title":"Can I Use PEM SSL Truststore When Connecting to a Kafka Instance with SASL_SSL Enabled?", "uri":"kafka-faq-0027.html", "doc_type":"usermanual", - "p_code":"104", - "code":"115" + "p_code":"110", + "code":"121" }, { "desc":"JKS certificates are used for connecting to instances in Java and CRT certificates are used for connecting to instances in Python.", @@ -1040,8 +1094,8 @@ "title":"What Are the Differences Between JKS and CRT Certificates?", "uri":"kafka-faq-0028.html", "doc_type":"usermanual", - "p_code":"104", - "code":"116" + "p_code":"110", + "code":"122" }, { "desc":"TLS 1.2.", @@ -1049,8 +1103,8 @@ "title":"Which TLS Version Does DMS for Kafka Support?", "uri":"kafka-faq-0029.html", "doc_type":"usermanual", - "p_code":"104", - "code":"117" + "p_code":"110", + "code":"123" }, { "desc":"Yes. The maximum allowed number of client connections varies by instance specifications.", @@ -1058,8 +1112,8 @@ "title":"Is There a Limit on the Number of Client Connections to a Kafka Instance?", "uri":"kafka-faq-0033.html", "doc_type":"usermanual", - "p_code":"104", - "code":"118" + "p_code":"110", + "code":"124" }, { "desc":"Each Kafka broker allows a maximum of 1000 connections from each IP address by default. Excess connections will be rejected. You can change the limit by referring to Modi", @@ -1067,8 +1121,8 @@ "title":"How Many Connections Are Allowed from Each IP Address?", "uri":"kafka-faq-0034.html", "doc_type":"usermanual", - "p_code":"104", - "code":"119" + "p_code":"110", + "code":"125" }, { "desc":"No, and you cannot specify the IP addresses.", @@ -1076,8 +1130,8 @@ "title":"Can I Change the Private Network Addresses of a Kafka Instance?", "uri":"kafka_faq_0048.html", "doc_type":"usermanual", - "p_code":"104", - "code":"120" + "p_code":"110", + "code":"126" }, { "desc":"Yes. All Kafka instances and users use the same SSL certificate.To obtain the SSL certificate, perform the following steps:", @@ -1085,8 +1139,8 @@ "title":"Is the Same SSL Certificate Used for Different Instances?", "uri":"kafka_faq_0051.html", "doc_type":"usermanual", - "p_code":"104", - "code":"121" + "p_code":"110", + "code":"127" }, { "desc":"If a Sarama client is used to send and receive messages, the following issues may occur:Sarama cannot detect partition changes. Adding topic partitions requires client re", @@ -1094,8 +1148,8 @@ "title":"Why Is It Not Recommended to Use a Sarama Client for Messaging?", "uri":"kafka_faq_0061.html", "doc_type":"usermanual", - "p_code":"104", - "code":"122" + "p_code":"110", + "code":"128" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1103,8 +1157,8 @@ "title":"Topics and Partitions", "uri":"kafka-faq-191030003.html", "doc_type":"usermanual", - "p_code":"73", - "code":"123" + "p_code":"79", + "code":"129" }, { "desc":"The number of topics is related to the total number of topic partitions and the number of partitions in each topic. There is an upper limit on the aggregate number of par", @@ -1112,8 +1166,8 @@ "title":"Is There a Limit on the Number of Topics in a Kafka Instance?", "uri":"kafka-faq-200426024.html", "doc_type":"usermanual", - "p_code":"123", - "code":"124" + "p_code":"129", + "code":"130" }, { "desc":"Kafka manages messages by partition. If there are too many partitions, message creation, storage, and retrieval will be fragmented, affecting the performance and stabilit", @@ -1121,8 +1175,8 @@ "title":"Why Is Partition Quantity Limited?", "uri":"kafka-faq-200426025.html", "doc_type":"usermanual", - "p_code":"123", - "code":"125" + "p_code":"129", + "code":"131" }, { "desc":"No. If you want to use fewer partitions, delete the corresponding topic, create another one, and specify the desired number of partitions.", @@ -1130,8 +1184,8 @@ "title":"Can I Reduce the Partition Quantity?", "uri":"kafka-faq-200426101.html", "doc_type":"usermanual", - "p_code":"123", - "code":"126" + "p_code":"129", + "code":"132" }, { "desc":"Possible cause: The aggregate number of partitions of created topics has reached the upper limit. The upper limit on partitions varies by instance specifications. For det", @@ -1139,8 +1193,8 @@ "title":"Why Do I Fail to Create Topics?", "uri":"kafka-faq-200426026.html", "doc_type":"usermanual", - "p_code":"123", - "code":"127" + "p_code":"129", + "code":"133" }, { "desc":"Automatic topic creation is supported, but batch topic import is not supported. You can only export topics in batches.Enable automatic topic creation using one of the fol", @@ -1148,8 +1202,8 @@ "title":"Do Kafka Instances Support Batch Importing Topics or Automatic Topic Creation?", "uri":"kafka-faq-200426027.html", "doc_type":"usermanual", - "p_code":"123", - "code":"128" + "p_code":"129", + "code":"134" }, { "desc":"Possible cause: Automatic topic creation has been enabled and a consumer is connecting to the topic. If no existing topics are available for message creation, new topics ", @@ -1157,8 +1211,8 @@ "title":"Why Do Deleted Topics Still Exist?", "uri":"kafka-faq-200426028.html", "doc_type":"usermanual", - "p_code":"123", - "code":"129" + "p_code":"129", + "code":"135" }, { "desc":"Yes. Use either of the following methods to check the disk space used by a topic:In the row containing the desired Kafka instance, click View Metric to go to the Cloud Ey", @@ -1166,8 +1220,8 @@ "title":"Can I View the Disk Space Used by a Topic?", "uri":"kafka-faq-200426030.html", "doc_type":"usermanual", - "p_code":"123", - "code":"130" + "p_code":"129", + "code":"136" }, { "desc":"If you have enabled SASL_SSL for your Kafka instance, you can configure ACL permissions for your topics. On the Topics tab page of the Kafka console, click Grant User Per", @@ -1175,8 +1229,8 @@ "title":"Can I Add ACL Permissions for Topics?", "uri":"kafka-faq-200426032.html", "doc_type":"usermanual", - "p_code":"123", - "code":"131" + "p_code":"129", + "code":"137" }, { "desc":"Messages are not deleted immediately after being retrieved. They are deleted only when the aging time expires.You can shorten the aging time or expand the storage space.", @@ -1184,8 +1238,8 @@ "title":"What Should I Do If Kafka Storage Space Is Used Up Because Retrieved Messages Are Not Deleted?", "uri":"kafka-faq-0003.html", "doc_type":"usermanual", - "p_code":"123", - "code":"132" + "p_code":"129", + "code":"138" }, { "desc":"You can increase the partition quantity by adding brokers.To do so, go to the Kafka console, locate the row that contains the desired instance, and choose More > Modify S", @@ -1193,8 +1247,8 @@ "title":"How Do I Increase the Partition Quantity?", "uri":"kafka-faq-0005.html", "doc_type":"usermanual", - "p_code":"123", - "code":"133" + "p_code":"129", + "code":"139" }, { "desc":"Enabling or disabling automatic topic creation may cause instance restarts. For details, see the information displayed on the Kafka console.", @@ -1202,8 +1256,8 @@ "title":"Will a Kafka Instance Be Restarted After Its Automatic Topic Creation Setting Is Modified?", "uri":"kafka-faq-0010.html", "doc_type":"usermanual", - "p_code":"123", - "code":"134" + "p_code":"129", + "code":"140" }, { "desc":"Just simply unsubscribe from them on the Kafka client.", @@ -1211,8 +1265,8 @@ "title":"Can I Delete Unnecessary Topics in a Consumer Group?", "uri":"kafka-faq-0031.html", "doc_type":"usermanual", - "p_code":"123", - "code":"135" + "p_code":"129", + "code":"141" }, { "desc":"Symptom: Different consumers in a consumer group have different topic permissions. When a consumer attempts to retrieve messages from a topic, the error message \"Not auth", @@ -1220,8 +1274,8 @@ "title":"What Can I Do If a Consumer Fails to Retrieve Messages from a Topic Due to Insufficient Permissions?", "uri":"kafka-faq-0038.html", "doc_type":"usermanual", - "p_code":"123", - "code":"136" + "p_code":"129", + "code":"142" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1229,8 +1283,8 @@ "title":"Consumer Groups", "uri":"kafka-faq-200423001.html", "doc_type":"usermanual", - "p_code":"73", - "code":"137" + "p_code":"79", + "code":"143" }, { "desc":"When parameter auto.create.groups.enable is set to true, you do not need to create a consumer group, producer, or consumer because they are generated automatically when y", @@ -1238,8 +1292,8 @@ "title":"Do I Need to Create Consumer Groups, Producers, and Consumers for Kafka Instances?", "uri":"kafka-faq-200426033.html", "doc_type":"usermanual", - "p_code":"137", - "code":"138" + "p_code":"143", + "code":"144" }, { "desc":"This depends on the offsets.retention.minutes and auto.create.groups.enable parameters.For instances created much earlier, auto.create.groups.enable is set to true by def", @@ -1247,8 +1301,8 @@ "title":"Will a Consumer Group Without Active Consumers Be Automatically Deleted in 14 Days?", "uri":"kafka-faq-0043.html", "doc_type":"usermanual", - "p_code":"137", - "code":"139" + "p_code":"143", + "code":"145" }, { "desc":"Possible cause: Automatic consumer group creation has been enabled and your service is connected to the consumer group and consuming messages. Therefore, the consumer gro", @@ -1256,8 +1310,8 @@ "title":"Why Does a Deleted Consumer Group Still Exist?", "uri":"kafka_faq_0059.html", "doc_type":"usermanual", - "p_code":"137", - "code":"140" + "p_code":"143", + "code":"146" }, { "desc":"Check whether Flink is used for consumption. Flink uses the assign mode and the client assigns specific partitions to be consumed, so you cannot see any consumer on the K", @@ -1265,8 +1319,8 @@ "title":"Why Can't I View Consumers When Instance Consumption Is Normal?", "uri":"kafka_faq_0060.html", "doc_type":"usermanual", - "p_code":"137", - "code":"141" + "p_code":"143", + "code":"147" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1274,8 +1328,8 @@ "title":"Messages", "uri":"kafka-faq-190416001.html", "doc_type":"usermanual", - "p_code":"73", - "code":"142" + "p_code":"79", + "code":"148" }, { "desc":"10 MB.", @@ -1283,8 +1337,8 @@ "title":"What Is the Maximum Size of a Message that Can be Created?", "uri":"kafka-faq-200426035.html", "doc_type":"usermanual", - "p_code":"142", - "code":"143" + "p_code":"148", + "code":"149" }, { "desc":"Rebalancing is a process where partitions of topics are re-allocated for a consumer group.In normal cases, rebalancing occurs inevitably when a consumer is added to or re", @@ -1292,8 +1346,8 @@ "title":"Why Does Message Poll Often Fail During Rebalancing?", "uri":"kafka-faq-200426036.html", "doc_type":"usermanual", - "p_code":"142", - "code":"144" + "p_code":"148", + "code":"150" }, { "desc":"Possible cause 1: The message has been aged.Solution: Change the aging time.Solution: Change the aging time.Possible cause 2: The createTime timestamp of the message is i", @@ -1301,8 +1355,8 @@ "title":"Why Can't I Query Messages on the Console?", "uri":"kafka-faq-200426037.html", "doc_type":"usermanual", - "p_code":"142", - "code":"145" + "p_code":"148", + "code":"151" }, { "desc":"Symptom: An alarm is generated for the Accumulated Messages metric.Solution:Log in to the Kafka console and click the instance for which the alarm is generated. The insta", @@ -1310,8 +1364,8 @@ "title":"What Can I Do If Kafka Messages Are Accumulated?", "uri":"kafka-faq-200426100.html", "doc_type":"usermanual", - "p_code":"142", - "code":"146" + "p_code":"148", + "code":"152" }, { "desc":"If the aging time has been set for a topic, the value of the log.retention.hours parameter does not take effect for the topic. The value of the log.retention.hours parame", @@ -1319,8 +1373,8 @@ "title":"Why Do Messages Still Exist After the Retention Period Elapses?", "uri":"kafka-faq-200708001.html", "doc_type":"usermanual", - "p_code":"142", - "code":"147" + "p_code":"148", + "code":"153" }, { "desc":"No.", @@ -1328,8 +1382,8 @@ "title":"Do Kafka Instances Support Delayed Message Delivery?", "uri":"kafka-faq-0018.html", "doc_type":"usermanual", - "p_code":"142", - "code":"148" + "p_code":"148", + "code":"154" }, { "desc":"View the number of accumulated messages using any of the following methods:On the Consumer Groups page of an instance, click the name of the consumer group whose accumula", @@ -1337,8 +1391,8 @@ "title":"How Do I View the Number of Accumulated Messages?", "uri":"kafka-faq-0041.html", "doc_type":"usermanual", - "p_code":"142", - "code":"149" + "p_code":"148", + "code":"155" }, { "desc":"The message creation time is specified by CreateTime when a producer creates messages. If this parameter is not set during message creation, the message creation time is ", @@ -1346,8 +1400,8 @@ "title":"Why Is the Message Creation Time Displayed as Year 1970?", "uri":"kafka-faq-0045.html", "doc_type":"usermanual", - "p_code":"142", - "code":"150" + "p_code":"148", + "code":"156" }, { "desc":"message.max.bytes can be modified on the Parameters page on the console. For details, see Modifying Kafka Instance Configuration Parameters.The maximum value of message.m", @@ -1355,8 +1409,8 @@ "title":"How Do I Modify message.max.bytes?", "uri":"kafka_faq_0058.html", "doc_type":"usermanual", - "p_code":"142", - "code":"151" + "p_code":"148", + "code":"157" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1364,8 +1418,8 @@ "title":"Monitoring & Alarm", "uri":"kafka-faq-191030004.html", "doc_type":"usermanual", - "p_code":"73", - "code":"152" + "p_code":"79", + "code":"158" }, { "desc":"If topic monitoring data is not displayed, the possible causes are as follows:The topic name starts with a special character, such as an underscore (_) or a number sign (", @@ -1373,8 +1427,8 @@ "title":"Why Can't I View the Monitoring Data?", "uri":"kafka-faq-200426041.html", "doc_type":"usermanual", - "p_code":"152", - "code":"153" + "p_code":"158", + "code":"159" }, { "desc":"Symptom: The monitoring data shows that there are 810 million accumulated messages. However, the Kafka console shows that there are 100 million messages in all six topics", @@ -1382,8 +1436,8 @@ "title":"Why Is the Monitored Number of Accumulated Messages Inconsistent with the Message Quantity Displayed on the Kafka Console?", "uri":"kafka-faq-0007.html", "doc_type":"usermanual", - "p_code":"152", - "code":"154" + "p_code":"158", + "code":"160" }, { "desc":"The monitoring data is reported every minute. The reported data will be displayed on the monitoring page after being sorted. This process takes less than 20 minutes. Afte", @@ -1391,8 +1445,8 @@ "title":"Why Is a Consumer Group Still on the Monitoring Page After Being Deleted?", "uri":"kafka-faq-0022.html", "doc_type":"usermanual", - "p_code":"152", - "code":"155" + "p_code":"158", + "code":"161" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1401,7 +1455,7 @@ "uri":"kafka-ug-0723006.html", "doc_type":"usermanual", "p_code":"", - "code":"156" + "code":"162" }, { "desc":"This section describes how to troubleshoot Kafka connection problems.If the connection to a Kafka instance is abnormal, perform the following operations to troubleshoot t", @@ -1409,8 +1463,8 @@ "title":"Troubleshooting Kafka Connection Exceptions", "uri":"kafka-faq-0604001.html", "doc_type":"usermanual", - "p_code":"156", - "code":"157" + "p_code":"162", + "code":"163" }, { "desc":"The duration from message creation to retrieval occasionally reaches 6 minutes, which is not tolerable to services.Service requests are stacked and cannot be processed in", @@ -1418,8 +1472,8 @@ "title":"Troubleshooting 6-Min Latency Between Message Creation and Retrieval", "uri":"kafka-trouble-0709001.html", "doc_type":"usermanual", - "p_code":"156", - "code":"158" + "p_code":"162", + "code":"164" }, { "desc":"The system displays the error message \"Disk error when trying to access log file on the disk\".The disk usage of the broker is too high.Expand the disk space by referring ", @@ -1427,8 +1481,8 @@ "title":"Troubleshooting Message Creation Failures", "uri":"kafka-trouble-0001.html", "doc_type":"usermanual", - "p_code":"156", - "code":"159" + "p_code":"162", + "code":"165" }, { "desc":"A deleted topic still exists.Automatic topic creation has been enabled for the instance, and a consumer is connecting to the topic. If services are not stopped, message c", @@ -1436,8 +1490,8 @@ "title":"Troubleshooting Topic Deletion Failures", "uri":"kafka-trouble-0002.html", "doc_type":"usermanual", - "p_code":"156", - "code":"160" + "p_code":"162", + "code":"166" }, { "desc":"For a Kafka instance deployed in multiple AZs, if one of the AZs is faulty, error message \"Topic {{topic_name}} not present in metadata after 60000 ms\" may be reported on", @@ -1445,8 +1499,8 @@ "title":"Troubleshooting Error \"Topic {{topic_name}} not present in metadata after 60000 ms\" During Message Production or Consumption", "uri":"kafka-trouble-0004.html", "doc_type":"usermanual", - "p_code":"156", - "code":"161" + "p_code":"162", + "code":"167" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1455,7 +1509,7 @@ "uri":"kafka-ug-00001.html", "doc_type":"usermanual", "p_code":"", - "code":"162" + "code":"168" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1464,7 +1518,7 @@ "uri":"kafka-ug-00002.html", "doc_type":"usermanual", "p_code":"", - "code":"163" + "code":"169" }, { "desc":"See Glossary.", @@ -1473,6 +1527,6 @@ "uri":"dms-ug-0312114.html", "doc_type":"usermanual", "p_code":"", - "code":"164" + "code":"170" } ] \ No newline at end of file diff --git a/docs/dms/umn/CreateUserAndGrantPolicy.html b/docs/dms/umn/CreateUserAndGrantPolicy.html index 245c3ca1..4c8c09ab 100644 --- a/docs/dms/umn/CreateUserAndGrantPolicy.html +++ b/docs/dms/umn/CreateUserAndGrantPolicy.html @@ -15,7 +15,7 @@
  • Choose Service List > Distributed Message Service. Then click Create Instance on the console of DMS for Kafka. If a message appears indicating that you cannot perform the operation, the DMS ReadOnlyAccess policy is in effect.
  • Choose Service List > Elastic Volume Service. If a message appears indicating that you have insufficient permissions, the DMS ReadOnlyAccess policy is in effect.
  • Choose Service List > Distributed Message Service. If the Kafka instance list can be displayed, the DMS ReadOnlyAccess policy is in effect.
-

Example Custom Policies

You can create custom policies to supplement the system-defined policies of DMS for Kafka. For details about actions supported in custom policies, see "Permissions Policies and Supported Actions" in Distributed Message Service API Reference

+

Example Custom Policies

You can create custom policies to supplement the system-defined policies of DMS for Kafka. For details about actions supported in custom policies, see Permissions Policies and Supported Actions"Permissions Policies and Supported Actions" in Distributed Message Service API Reference

To create a custom policy, choose either visual editor or JSON.

  • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
  • JSON: Create a JSON policy or edit an existing one.

For details, see Creating a Custom Policy. The following lists examples of common DMS for Kafka custom policies.

diff --git a/docs/dms/umn/Kafka-client-best-practice.html b/docs/dms/umn/Kafka-client-best-practice.html index 9abf69c4..8b886d9f 100644 --- a/docs/dms/umn/Kafka-client-best-practice.html +++ b/docs/dms/umn/Kafka-client-best-practice.html @@ -6,7 +6,7 @@

Producers

  1. Synchronous replication: Set acks to all.
  2. Retry message sending: Set retries to 3.
  3. Optimize message sending: For latency-sensitive messages, set linger.ms to 0. For latency-insensitive messages, set linger.ms to a value ranging from 100 to 1000.
  4. Ensure that the producer has sufficient JVM memory to avoid blockages.
  5. Set the timestamp to the local time. Messages will fail to age if the timestamp is a future time.

Topics

Recommended topic configurations: Use 3 replicas, enable synchronous replication, and set the minimum number of in-sync replicas to 2. The number of in-sync replicas cannot be the same as the number of replicas of the topic. Otherwise, if one replica is unavailable, messages cannot be produced.

-

You can enable or disable automatic topic creation. If automatic topic creation is enabled, the system automatically creates a topic when a message is created in or retrieved from a topic that does not exist. This topic has the following default settings: 3 partitions, 3 replicas, aging time 72 hours, synchronous replication and flushing disabled, CreateTime message timestamp, and maximum 10,485,760 bytes message size.

+

You can enable or disable automatic topic creation. If automatic topic creation is enabled, the system automatically creates a topic when a message is produced in or consumed from a topic that does not exist. This topic has the following default settings: 3 partitions, 3 replicas, aging time 72 hours, synchronous replication and flushing disabled, CreateTime message timestamp, and maximum 10,485,760 bytes message size.

Others

Maximum number of connections: 3000

Maximum size of a message: 10 MB

diff --git a/docs/dms/umn/ProductDescPrivilegeManagement.html b/docs/dms/umn/ProductDescPrivilegeManagement.html index 51728a61..da4a6ec6 100644 --- a/docs/dms/umn/ProductDescPrivilegeManagement.html +++ b/docs/dms/umn/ProductDescPrivilegeManagement.html @@ -1,14 +1,14 @@

Permission

-

You can use Identity and Access Management (IAM) to manage DMS for Kafka permissions and control access to your resources. IAM provides identity authentication, permissions management, and access control.

+

If you need to grant your enterprise personnel permission to access your DMS resources, use Identity and Access Management (IAM). IAM provides identity authentication, fine-grained permissions management, and access control. IAM helps you secure access to your cloud resources.

You can create IAM users for your employees, and assign permissions to these users on a principle of least privilege (PoLP) basis to control their access to specific resource types. For example, you can create IAM users for software developers and assign specific permissions to allow them to use Kafka instance resources but prevent them from being able to delete resources or perform any high-risk operations.

If your account does not require individual IAM users for permissions management, skip this section.

IAM is a free service. You only pay for the resources in your account.

For more information, see IAM Service Overview.

DMS Permissions

By default, new IAM users do not have any permissions assigned. To assign permissions to these new users, add them to one or more groups, and attach permissions policies or roles to these groups.

DMS is a project-level service deployed and accessed in specific physical regions. When assigning DMS for Kafka permissions to a user group, specify region-specific projects where the permissions will take effect. If you select All projects, the permissions will be granted for all region-specific projects. When accessing DMS, the users need to switch to a region where they have been authorized to use this service.

-
You can grant permissions by using roles and policies.
  • Roles: A type of coarse-grained authorization mechanism that provides only a limited number of service-level roles. When using roles to grant permissions, you also need to assign dependency roles. However, roles are not an ideal choice for fine-grained authorization and secure access control.
  • Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization for more secure access control. For example, you can grant DMS for Kafka users only the permissions for managing instances. Most policies define permissions based on APIs. For the API actions supported by DMS for Kafka, see "Permissions Policies and Supported Actions" in the Distributed Message Service API Reference.
+
You can grant permissions by using roles and policies.
  • Roles: A type of coarse-grained authorization mechanism that provides only a limited number of service-level roles. When using roles to grant permissions, you also need to assign dependency roles. However, roles are not an ideal choice for fine-grained authorization and secure access control.
  • Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization for more secure access control. For example, you can grant DMS for Kafka users only the permissions for managing instances. Most policies define permissions based on APIs. For the API actions supported by DMS for Kafka, see Permissions Policies and Supported Actions.

Table 1 lists all the system-defined policies supported by DMS for Kafka.

@@ -67,103 +67,183 @@

None

+

DMS ELBAccess

+ +

ELB operation permissions to assign to DMS agencies.

+ +

System-defined policy

+ +

None

+ + +

DMSAgencyCheckAccessPolicy

+ +

IAM operation permissions to assign to DMS agencies.

+ +

System-defined policy

+ +

None

+ +

System-defined policies contain OBS actions. Due to data caching, the policies take effect five minutes after they are attached to a user, user group, or enterprise project.

-

Table 2 lists the common operations supported by each DMS for Kafka system policy. Select the policies as required.

+

Table 2 lists the common operations supported by each DMS for Kafka system policy. Select the policies as required.

-
Table 2 Common operations supported by each system-defined policy of DMS for Kafka

Operation

+
- - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + + + + + + + + + + + + + + + + + + + diff --git a/docs/dms/umn/TagManagement.html b/docs/dms/umn/TagManagement.html index d3721fa6..314c5b50 100644 --- a/docs/dms/umn/TagManagement.html +++ b/docs/dms/umn/TagManagement.html @@ -13,18 +13,18 @@ - -
Table 2 Common operations supported by system-defined policies

Operation

DMS FullAccess

+

DMS FullAccess

DMS UserAccess

+

DMS UserAccess

DMS ReadOnlyAccess

+

DMS ReadOnlyAccess

DMS VPCAccess

+

DMS VPCAccess

DMS KMSAccess

+

DMS KMSAccess

+

DMS ELBAccess

+

DMSAgencyCheckAccessPolicy

Creating instances

+

Creating an instance

√

+

√

×

+

×

×

+

×

×

+

×

×

+

×

+

×

+

×

Modifying instances

+

Modifying instances

√

+

√

×

+

×

×

+

×

×

+

×

×

+

×

+

×

+

×

Deleting instances

+

Deleting instances

√

+

√

×

+

×

×

+

×

×

+

×

×

+

×

+

×

+

×

Modifying instance specifications

+

Modifying instance specifications

√

+

√

×

+

×

×

+

×

×

+

×

×

+

×

+

×

+

×

Restarting instances

+

Enabling Smart Connect

√

+

√

√

+

×

×

+

×

×

+

×

×

+

×

+

×

+

×

Querying instance information

+

Creating a Smart Connect task

√

+

√

√

+

√

√

+

×

×

+

×

×

+

×

+

×

+

×

+

Restarting instances

+

√

+

√

+

×

+

×

+

×

+

×

+

×

+

Querying instance information

+

√

+

√

+

√

+

×

+

×

+

×

+

×

Tag key

  • Cannot be left blank.
  • Must be unique for the same instance.
  • Can contain 1 to 128 characters.
  • Can contain letters, digits, spaces, and special characters _.:=+-@ : = + - @
  • Cannot start or end with a space.
+
  • Cannot be left blank.
  • Must be unique for the same instance.
  • Can contain 1 to 128 characters.
  • Can contain letters, digits, spaces, and special characters _.:=+-@ : = + - @
  • Cannot start or end with a space.
  • Cannot start with _sys_.

Tag value

  • Can contain 0 to 255 characters.
  • Can contain letters, digits, spaces, and special characters _.:=+-@ : = + - @
  • Cannot start or end with a space.
+
  • Can contain 0 to 255 characters.
  • Can contain letters, digits, spaces, and special characters _.:=+-@ : = + - @
  • Cannot start or end with a space in instance creation.
-

Configuring Kafka Instance Tags

  1. Log in to the console.
  2. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
  3. Click the name of an instance.
  4. In the navigation pane on the left, choose Tags.

    View the tags of the instance.

    +

    Procedure

    1. Log in to the console.
    2. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
    3. Click the name of an instance.
    4. In the navigation pane on the left, choose Tags.

      View the tags of the instance.

    5. Perform the following operations as required:

      • Add a tag
        1. Click Create/Delete Tag.
        2. Enter a tag key and a tag value, and click Add.

          If you have predefined tags, select a predefined pair of tag key and value, and click Add.

        3. Click OK.
      • Delete a tag

        Delete a tag using either of the following methods:

        diff --git a/docs/dms/umn/en-us_image_0000001314995070.png b/docs/dms/umn/en-us_image_0000001314995070.png new file mode 100644 index 0000000000000000000000000000000000000000..9f3f6ab1dc27a06b3f710d83c419590cb710c59f GIT binary patch literal 348 zcmeAS@N?(olHy`uVBq!ia0vp^{6H+s!3HG#4~4G+QjEnx?oJHr&dIz4a#+$GeH|GX zHuiJ>Nn{1`ISV`@iy0XB4ude`@%$AjK*5imE{-7<{#!5Z=WcS4IR5aress=?g<|63 zicJ}wic(QhP6egBi&QTx6@y)dEkc5}$n^ly5q>v19mo(TcSbi@NZ{N=GmX=m! z8q*I77cNV4Ze;YF=_)KN%f@8lUc+SU3oI|Bip)J9CAOuiHy8wMvJAA%lQ0#Xe=9P01ye!^QBv_(djy8{)PweblwinFE4 z??X_C`i^D_MuvyC1JMMH`+^(}1n;6ry6ZjfZ3iO>^epb^gOw@Npe`?ov^qd^s>NWT z{DJ~*j~m*uvNDKF?zquk6B%RP)+Wf$cc<^!*lO#>zwqaZmO`tjsDwpE7K(-5L5NFA zVv&%@t1nvUgLWil=jPJ*A4MqNXIwq(eSCO4bn$w9#4|NDg|I(J(y+f>FoAgZT`ob) z4~qRdkzQ*&(5&lyi!b;Fc5-xd{QFHM~;4k+?Z4a~p=8sGg%dF+16aB+QBugp(lKQKz?v>Dy(^mGSb(j0HJ<5g-m<|}0J z{v5K~e>$l)x%=~Gtc6>mnDc>$Ck>9wtH&Tkb8lwSk$Sqt!Q|_BYBXDjB-sm+)30#> zoi$HNdiwBU`3$J(Dm^}+PgdI9wpMPAj=p`4YC{~GO}ktOZh}t|FZdkQ^7i`Na=WMl z+KXxi{Vp?qSnAHcX*tan@O=DTUd`?D8ygbRpP0`z^3R_?^~b%vA`50s@iD-cW|W2oUkxT2)kKeRTQ`bwqUFE^C_`QOBO-2NOfK!;5vxQ&iwMzF8`;10 znO4Tdgi-aIb6*qrfWaVbcy~<=Qj#apTJ-flvmjC)m=XlQw3QBR%Cl=%wM1Lfk!<|4 z^O_D?t78Oa8RGWs#$~ulAS*CKabMH}P^O!{lv58H6Vk&LeKm<3_@uZc#m(on%1Lio z%r?o^b7#pRulytQbdYlY+MlgQ-4)_)&d4aMN_S z;Q@#u$`Jp3p8mb+Tu~)#;ow|azyGHlwkbsA%d~;k(GlffSqJ%z*X}4x#yykG%qBCq z?5c7m${S13f23XR4Q-jP-MtZ*KrxLWvJT?+AnX&GFna(q&F8u~su2SxfDB*A$1B`S zOMYWXE4k5ev%|gr#Z1*k@)`csh|vDdDlplsh=&+8O7HIdfDW`tMJmrvLkz1GaY7nM zpPKT)Iq*fiq;+NqzUm1zk=PYBY?Z61nqoZM;UxTdiMzl!zluHbF;BPu8nkvvEe! zt+FrUn;f)@(L)t+8uBoGHI~b}vK<O*Julc|>SfAnw53_Y>O{A^x=<)e~Rf>P=<9&D5Ug`w1_ z-}!y-$)!E-)Zy9TC$ZJO>y-Ya^S;Z9J_~tKqvI^rGgN2-~$V^(0$?cqe26ZzxXn_>A|Cj8Lo0AId$CI1+cjFgz7LHg1$&6 zAyL$kb~um_^T514L8`Fl*@)rKkUC~2`F7<(JX~?McvEC@>pc#!jK;u`GiX#D7Ep3| zfjnC`Cqj!1->tvF5RU|%$?wcSqT?dJJrY9--Sas;I;^`8$(NTs;>#a`dEf7Xdk zl<#5Dg_L#c4Hx)gp1}2kKjN)fs4&Z4I->9c^s)P6cbOWj8!Y3oD zA;|K(J}ER&;DnM-nZXmA3FhQHVm>Hh+x|Y3L00Xe=fCW)hi0|?_U9DgejM`t2q@7= zv3XwHLEok^@01Bf$As@+?TtLwrKBBo(cAe&%6ek{aALR|iyY%i!?9E7Gu=UIEeNIP z!@`WyQz@_$VvD{2F}dH{XTxeP01ekyVq%tY;5M?whuarzGF`;R&x_v1=^sdN(HB#5 zmTR6tdGeh}k5CK*|A!w{(F+ctEW6nt8KS-l6Owcy(IrZ($Z!fgTNPKuGp8bhw!S0%hr4E?(NOhQUurWfF;+7tsT<)MD?&HW6>*&xS0bdTK%hT z(!y}gNZJYqH76#xyE@3zLss8TF2uLOv9W=vpGwh0d-yfy+|S*?k=QTBF3$6MMt$pU zoDk;p{dU>T)$_gL#o4dfLkWp8l^2(9R9vm(P67@e6xk251urhx>9{*H`h`NIqS&uU zq~rqAG+OR>QehQeAT+w+eDxsR^x*^7gcV5T^r_Z#uOX2=NPL7~jYL>Ikt^1b-fxC9 z`vl`v$3mTduh6xqJ$u8fdJ#tagVo<*(9a?rn~c)G*1Cvd2M0I157xh?5e-V%^Rtx~ zzcAa`6jYf32G06JE%CYUv#fUXyHyFPP2ea?GnHl7QhsgztZvA}WAP0@zuy&9nV28m zZ@@PDBN+64IhT>Rju|uc4qJP5W5)K^UBV%4TduF{`jghA3(e`BwBC&Nqt!sUNc0;% zrSDvQr=3ac>YsB4iXCXvUs4mbrX}F4 zU#SWCp0{VIJ;IKNn4H7iT9$4&$2vh2hnUuw9;x{zHu~oE6UMww#`cfs_~gT&xmH%Q zH0&Czk|LNtvzoJ^&7mG57xR{M<8*0Pe4g@;jZX}hyOTxc{Z^N(xsCh%VRuT+(Q4}7 zEgb*6RV6HLsOAi&2*BJkEz#W%E5p1D#h0oqmF6O#B00XCe;?OvC4h0ZMxHUUmyld) zBZm8gf>WzIjXXFc?A&5%Kc}Rbb@cK;LL@!+`qEkD;?Mc1>cssy7otT77Pc`YmbdB_ zMU?#g(6!*0Yk$;|aJ`4)$LCKez5e+fZdmy5mw>^Ak;dk@*NHHJg(6n?@uj)1_R$E!7ZfHxb z4E?Ssyc=ZXbe?6RxZJbO4f0gIYzRY76+rx29SUPGcKPO$Hs7EhV=jGqJv}>{owAo3ATff*wWl+?$iJlr0DLUSlgp+L%!D2j5yIx)IqOV{Vvy=Wp&3A(>!Pio5>Pz8aK~za!S##1 zbMN=1FDCb9DZCCt;x|~(@u+#kcmqNelbCWGiLaoax&-arSm>5Z91Wk@2+%Kn{xR4; zpO?)OscA4YIAz>;bj|Uj=?WcrDP-5Gh1=Ys#7W}wJ!0~XRpn6;nTSZZJzm*OmM4PG z*`yyc0H4XQpgHXsKABy-Mj4M~-W~|4YtzKYSM@cAz!RgkCMzLeZ$_RxEL%`y&6_0{`jj2%4A`<|-vEsYCked#Hb*0B&=T zDFi>??3VhxenX6XbPY|T2h?}$DF8cthiKm?NJ47O zyvQ-$40CuLFnhEI0JsutDNli}jr2hq^nuzsO}Om}@UFWyo%DHzZ?VafLy{KI18q(N zqkMi*b$>0A!d`@mzXt#HA}y1Pp?TksxCmT|?q!G^v=}$?ZK$3~lgtb5nL7#_Ow*mh zBV6KSCOB1dS7m}`!%(jfF9+5^ znFW2H!|LFk{p8lP;>elCW1BEHkG}^VJFdH81TXz-Z^T|WfpnP)u@~|dZbC;AOktHp z!yKq&n&Al8r=~;%cOl2VzUwSJbt|0aAS=R~ya76xAz zIzNmdE)i$eK|f>Ha7gr##C&ZN6^YpWbkQwaM0PRCLD|(JcHwP2(#t*ZyI(?iwsq-M zbY;4SxX3l%pC?>}7=Y#f1BDwBMO=gTW;5kFJ%ztnve(W>yAssgHrC3Wqo?x zED(-27(@29_VYW|);&N+1hv%v-$};*xPJYwIrLwKf)KFMA*v5qP-__(Ht@0Rv=+FsSvY{k--HZ z8c|?Vl}bq+=(h{r-~x!K{+-lq787h63~-2Nd2Xfu+YD~6FLndsDj{uS2Eb(aXcRJ! zcG}ZrTvXRN*aySY#E@}oljRE?@^gyIDFcWJj1(AHS*EHySGStx#Tki09pVEhn0?qU zHItW`>#;FK|LA@kMPPx@D_@t9DARXcW~H``Z~UpcyCNw1mv&&`=20qHe$dORDLvQy zxS*O3W3Ce*aYP&c|04?t?^@R`(WC`dsQ)d@kn=-7Nj|S3zNr)$^p~0R>vbB+nSaB8 zm8>U!MeiU)gPXeMNdf4?qu#|*(uKU}<&C1Pe^L8RBS_P^UAKF#Cr-778R6?26wP|^ zs@^8#Squ8AWY4kgvIFwwCbUE7k5}y{$^L?OhRZqt|B!?gPEZ2fWQ_9YyC|87)-ZvN z>Ax+Z>+7R+lckKecDxHxo6$NygNeH}{1x-X$;(Y4+utDG(DZp%^k^D>RidYEqsj$% z5X|bKZ$OZ?;p=xmojr^GWMhUsi}8OX+CE+YAQSfFuiNrhfD#Cl1xuVo{O+*ZEM=$A zUBmI<3e6A-5hJLxU2=Fh_QMmi9(GdylgZRC?zb?o)V@ND3JsA!iY(}y5;gcReA#IP=S(azS|R+WFH)lzA_rg86mEuMs6BxkPKF-IMc zFV5x1VjHM~*JA)HZRKzZ_dnRfAFMS@(iSO1r7Q@|1o$^FB!Dlyy|)L?;`6v%L&-3A zcB+9#7O}6P)$k~e+g|6y=IQIRnPc{_hsw9N_9}Zw7xM){fXv{pH`$*GKkfW=B+wd8iVeXYZSib$o?9fJsUY9n&{)C z?-=g;!kTv~4F-b4DrnY<&H4d?I|lX8U$UzhbIxFKZktT>@`#Fm(>5mL{k3rX1My3? z=|u}Z{_14A9#MkPDErFm-q!Yr5jw`M``S41!=+yX1dMZ-A18`YYp9PH z6JdybKmhvuzOth}mx#v-L)6%9?dZRlkomswDV~?h(qU zx7HX*mh>k&?cQ!}@uvwzPlm6;P$`QG(t?|jMtyy@cy+Z)4dM$SxR5c{M*Elq3`Z0+ zbEu3nUyz(_8NIR4@va*|$L-uv&Z|Tr!u3zH7G#U4f2n6`Hp=rHBH5P3_S|WF_DN9d zNs(D6t;}6_M_|KGzUbb`Jyvg=o3J23(yOwbjjS%2r|+!_WmEuoyv;t#5Guu7qUBR$ zW@H?`Z+cc}dp%!<2QcXUecK|;>g;&HJb%Ko$i0-Z{Wo-KAHq)6_tLL7>Px(90b4Qd zTjtK@7WqUW!}7=|@jDWB6$*)`u+13Ck>AkBtm(Qo5@iRnY8WkE-yS|S_PVo4O1<5ixnvnCV5^CVK&V~9i5WMHVw zq?oo^5v(s}o9SxudYU}UI)42qmI*S9h1x7{o$o0cXet!Cm{yrOo{GkPyULy_yu)8W zcm>to?`b8QKAG7io`F*u;#Z$~C79g~BGzP3=eZMTU_4FX%1CrV`WqR)ygc!0#L@I5?&Rw5D*dxm$gJ;cE3;as`RcTA9_16a8K{p{iukkVHB}kN;WFm zqPZ-57#ATehJ=OdgPGW_KdlPD*8J&F;t$d6@~kK`RO7Tao7HU~OK|FNzY>w%j|Gsj zqRQPG5wor z7^-m1&8!^Aaf=>@4(CI(-}CP$$kbMjw^pcNE*Go-)ngZHupu_DkHSXayq+I2;9cRz zMT#x?wz>jS$0{-KihpI%HE+H^wKulP)Jbivr_s(%H`vxKH|&_ zC-mXgS91F*?xqI(dX;K47RuJ-Y(?>GM?}O zf%#h6J~DRT=#w%*(N6@9>e9&RePFr`R%beF+L^U;FayTbo${Kr_U7(-@uiSBiPI3f+d?MseLxC)A< zbu)@;r#IWs9@qTSWJ!#_rb!s%Q?yjk)ipEjvI zgYjK?#Sd`+%9={!cG#uzUCTStegAKa0tWQqD5f!bGx9Q(q;HbTG597P_$F6gc4cZD z0HgX(H1m&W|384^f54spxx?00oGN|VNCJ(U12^#-RA#bS6zgCi(!J<- zLTL~2`j47m>YfXzr%LFeU$y-qbesB6UW**R`Ih8d`Y6?)WhM&Cv2bs*tcpEk8n&%v zYv8@Ba_7AwQB1;{kpIK|yFx)%E$vuia|#pLpeW)rI$CrS^j_Ck(fs)|Mk;ZM7t(jI z*weo63QQkx;qrpLaUx0eoV)=fj@>w z-3XymtaT*H@SvOTf~I-DxJAz@QBVMyCD*+@lTJ_6#!eQI;jMSgZ__XLfk%_0ko_-3>&_oo$aZLM z-iUk~`L@l)J;(eH*TS0hWb95}WZe#W8Ys#=#qY1K@$BpZj>We7D=EX{;cJRuJncTN zJLJtDb=m%TlvyPJnYLQ}uLI4n%Z(bDDKk^tSRu%t^j<+PwVky0aUldtDD~)chX=ql zhE%)t3x$67b0lWXf0sED-0E=gi0V*~O$;jnxvOpZt7n_bP}~z_jgIUo8%;nA@B14K z0FJzz6`N>Nl}VA%4^Il9WAm~+=5q-1D=O~=ed!n*1T63ss^tD46_`>}VONroB;lkFi4ST=O4a7KTu(VW`gwfI!>|aYP26m%{ zFh>=2*Isk;Uy@K2;%;#^M7LA`aH~bE?yUIiqD0nkIm1yALcdK#`+DLrNik*c;(jdG z1{&;${@R3D=Qz-1_Xg3-=oiwPeNHkgkUEc+zLa1h_}F=P;wYrwhtN{Ru)aZ*z7Y5` z;o^@r-Fq%qJc{*Y5+A9c&~9d)7%ye!rBYvpWv}HV3vxj{kwIK)0V32wu@W!~qB-Ao zUDJhkzUixz)xqZ^&NRP&X8~O85W7kJwNA*{P+&VzQ@ZyaQ$L0b-~EFUWj;@|jee2c z=iZ+2H=es_Hte;#XzoQ%^&PNSx$x*PeIOGIzQbVcs=l}4?0KSUX~8BLQqI~QdZ(hK zeu~94n?(~M()@w-3<>{Qka6=1x3{$-pw4DL=vVpvilNS7VbGw@d+rXh67mBi3sk$c zR}W3EHz?R9T#>>3`vWNJqcs(6d%tONj8P<^-oS`l4JQmm<&KT^&50c{F@PGeUXe)W zxJ!&IL9=rM;_bt|q6(y7Cv5cBzV?hF(PyvF%)=QwFS0Sb15D9S_+{_DMq*-k3V)TB z4hMQ2OX=8jmkklkELx`i(av2_y&2_MM-sod4A;RxqFG8g%T(W22)<}(6mIXNuv$f@ zl@C*NRcl-bj?qQ!MNM=^_Gi4zTux@~yaq_M^lK%d z*97~_o@-n${t)umc{I&;oUQv%bi6Qty_B?R?>p{(mJw?{sp zxFPV;3TscW_~MB`=*Dg-Z=^E%I+3XC*~;PGJGz|@?R#mp1~cqmsQ}}mbSfhYu2q3;nFu9-q7hn%hmJ%$ z(NV2X2dni#&(>B`1(tX$Xj0x#>=nfsZ{}F{QAfxia^iRIzR$FPie=z5dEqJxuqKe_ z+m5UuThVa*{taGrHmPe7Ea2<+UHTreV=ptbg=Hjyj`N|>)dB%A7S~kC3f_Sz#2Oun zfK<1$@p&gNqG<4xfbOxy5e@7f+aUN-P?SIFGJ4k<-RJI352qcRve^|KMZsHf;U^s} z_Bj$Y1wA)Ci6K8tQ2gg7yTE0AoJ3jpmFV66)b7Vf`M}D(E~z~v3NNr^BDzYFCsKN&Q>yFnNWjxelnIG z+V34qGudL3< zTdP8=Q2*LUr>1AmJsbbd@g{Y#ba#FSRq=Ns@CYZtC&)6X(JS2{yaV3(;(nFq_IksN zPxsf=$=N<7gR?sxmMst0z6NwYo{(|36yqO$$;CA?<#%fb_WHl|#?pu<-gExHtR_4Aaz!!sJ*%nPB21IV?F&Yjbf z9fSVDi>*hCOLGWil^cDXWUVd!@3IyxEmCr4^vZ=gHVF&h+NJI(G0=`ZL{IvnyF_8Nf%7ELwEZb!8OSK z)rgEwE@_d0zMzkhF&NEx(K-~MuN=hV-A(3_z}h8F?$WVd39QMC_+4!z#kzST{#H;@EHy zE+v7ryx_dNK2qhxQ&_}?bA5!{>{bq$VF<_hI5gg4?4jl6GkW~&z&Xnp zYdT-ih2bQ@>Zim|k#4fitEz&)`pPn28n5@)<15#=APn3k(3ZBR)|?Ux$Vz{e-HUKK|@jqg+0xAi|2 ztfi8-vbR=@YM9bdJ4s=QL z;2LvoNcvaiml;XpPs4RkBm;rc#y2~fW3b1cyJPL=4<-BF?m`cjWQ=k?euhdNWRB$# zfWbQbiX3Mm(4tu^Dn~>vB607-JhtM_e!7=J_19N;dp%@z2l1RCrRg|ZDSkIprH8X| zmi;bb`O;mTh~76&oc8|BvSZwxHyy#wCZPQ4a6RT53md+o7Yl|7ph>tr%iyW)e~R_c z*3NuiVyX~Z4VXZ-C6|o2mM=fms zfc}K|OPM|zF)tHa?tAtP4%oE;hS1?M4HlJ4b~VHz=k>aX+g#4B5L3ss$BoHdl>VF{CEtjFy`XWAG3XiS#*AA2BB;Nw{$FvECu!Bb9i)r|QGeR}EIgM1fM;rDMKS znqnB|t4nqG0lov&aplD8^if1$lO6;FaFi$>lBVb25GLscp3M{KC4;vm(*bep;${nM z6Y@`l=W()*Ot3SL_H{rLJ3PHP3M;EOf1a1I9H4bWa`3i zeJeY2C9`0an0eIzJxp1Ck}eVH}7))YO*p?MDx~{fqL|+O+ds^mYI${?l6aYUE#I z;NPji|47UH-=~piEvn+!)c=DtRj<(>h|+9)LHj=h38a{C&W}jpT19XWgy&cF#nz0e zz*Yf~DM9d^_3vzjJ`8kG1tpVAS9G|1J4%+^>~8sr<3BYrJNfsL3C>)MCqyh!-ch&tBeRO>WR8i2!0@vm%A0R30r`3Y{Q-`RSc>g2$Q z+!aVPVvbp`VVN-6V~GM6sN`0vEroV2ZAIJDo$pD0`~tWegt`s+e^7<2fHAO zs0{=BH9}` zlIj0S-~JMB{o@(z{HeX(ObDVUNx%*B)p7JuvIoGa5wK*vS#Z zhHbbj|Bge+2>&%EH=&B&ujrB`*CO|PtmNPEb|mB+&i_a}tlF+Sm8_w@Jw4gQ=_O+c zA!-*>XYROo@0DS&x4DXCdjtzSeB?+O*I}I&WwlT2AFLVIUlI7{$(XHS|1C~iV`;;Y zlE9}l!h~Y^NC!~Z?8IwOcZ#rr&Cr2p!J&^QR!8$neOCQvk!N^-N`hZsuozeAEKmZC zejV6LGXM#hZXYC1)iIywbcM2}v(IHv_Wa;SeD&*sasxZj_K*Fn4F5#l<|D z{jKN45{~_0Fl$Rxq1j<54nGg^*B9je%^;Jsi|K(XlQ$=PK)Uu63I$w(OU7XrBuUWM zLb-ROFQoinj>riAyi@))9vhxaZj?EV-rS{~z{;uyA+!L1>d!rRjoNd><#3=gM3} z;Sqwig{8*sI!`5ab|wrcE~z@|wJfJ`jpCdBTf&8kX^PIbq&ogpvI;AiMtJE%U6)yE z1N2ly-0GtyF4$xFwl$v`+<+fnlJ=_;d8ho9bgaSznHGCZn;2hkI?ZuxL~efT`z zhVdU2%zy(h%U86m{z1_L;m(2(aSpbn*gNtMgu$lz)6Vj>f3i`H5oLpoCdj>C93fI0 zR4(UOu~&lW4m3cIfaq6!9`w0NBhHZ?uBo_ZM1^0q6j4Q?H#xDdURmH@qRQ>E+LyoS zv5Popsi;#xiP$IOvsB7bb%nA{6JKh`9`B?hKSk!RTlaOf;iVKZXh3G*=P2N%xCy<(qHRwkN<&uF955w0q)WMWN%gOm*SCl*jhzjW--&b-DwqfGbvUjGdqJGqS zr!XCkQRA_hj|Em6dtzpkYXw`0#MW2)tUQagj4jPvV7DyjNeISn+1Jflbkv-Hf9VlH zSoV4vE$v*N%4t;Va`ccgP@hq)38rPT7n>|-uOkRUlbL-#H-rws_SQ55qS51XQ>-7w zT70(KI+bp!z9 zs>*(LjZFvd(oVUnlA;zz;0HkMAN#uO;!za-_1D<9ibT-)1)v7+lZNU2XhKHBiX9Aw zJF;~=`)mZLZQKK}ckz4@=@1~B)&cTPemoT!bn_9@8goM!Y8lO}=SL?yjHkHgci48D zym|0iOs^+b9|xK6Z;Lcuk~7YUT%TC%QMxg+?#U?Xu)(F)wom@P1_*DjTKPMazxy)T z%%&LZ4t?F~u@@tWM6#bE4md_GA=eCwKAXhf)3*Lk{5yai{|PTU^y=vBf2`eE4ko3+l+XLjQ|AklXt zOhnj@LPeF$m}9dEI{$#787&5V_cT~{YM}KX0Y4R;2<1Ly9-mgg`<(@)D^Oi{y}z zOz@<1LB9#!TEt=0+O4pOX^od;wC7W{)7xCO55beV?g8?X zu!|4)-qLajKEpI?g*iJXx^!u~Kd|$m-t$XL85p)dGw9M2S|@-o+c;c0b8{)1l9KsL zetvyWh2Dmv*ysJ}OR}sjN-Eh9>fo(+tP?FoK@YFpT8P6BQoh`oaFJ%8Z*r_IFJn=x z8JUrD7+^l9trmCi&4y5!hHZ?SiTrgt;3CU^{H)7x*Mmb+*geOqTUGMqT?%eUbEx#= z7A<`#x(5e~K73~undvZFaj>&rJ7*cFX5tF^as@E4Q6Ft*lSl@VZpEdWvh38_(K7)} zjiRhPO7OP7d@~Jnd9(s5xD#1wI4G0WH={L1sJk`NwWKJe5?>(Cs zzH$uYeBi2L;AHH2C)lM$*{dIQ?_CwVRv41WCJyDR!fy0JvE<@xNfnGwWwT;Sz;v?E zadT);gTn4agU`%iq@ zoqCxpgKL`-gAu?GcGNXR9R`mGhw&&A+SkjxjabzR&f4weD8GaH z+{Z>T$kEHxpl}I6P-OkD15g?q!?a8--{9zee8vNvIkq$;waAgZsq;XxHBT|-6;z)E) z7%<6I*OVy|g(U*RWUx%tunl@S@FXMJ7s)keu@sYu$v@Jm2lyq%|9clAQ?&^SaYIJBr+rabo)#Xv4le&P&D!1X-khhd~#HdL0bv!LQL)OJ1z=* z8o}ZaI+=<7y2AB#-S=XdTNTRKLPit^n;a(t_zYi3*Zitp*=3Y};6$8WVjcOL5okn^ zBdOB9&frUweaBy8#TjE)GM%UWn;Z(TD8)}qkE%7)1}r)0Uc?xz026?BDEv1sZbO2+ zywfOh0kCqAe-ernnte*Ith4w}FU~)l{^x&qaZqkjJd!|J1~~IO7LCHye~W7QA$nh^ z(V-=LkSE-B=6yrrW*oEp8aV>1pq=cpT36A2IGNQxHT7Xp#+j-#ePm(+rN*Yc-c0K@ z(g8&uFzq7Qc(=wBORdxUxE;Og}?~3SGa1$kNxNp z0QdC=XyJ>g*5dhNL~D=NUvh)k>)X=&Pb@11Fbt~+fHP$T3`5%Rd|DYu>Pf+<|DDX* z-CJl3ceFKL;f_qeMs~PN_3hDhMpsagj0@=Fh#X3s>AM=aT5*n#4nhO@${=TPr=JRocPc)YaS@LIq!3wPj6>u)Jf{{ z+nHWjW6AGh6DbR$yp%hy$Ckr?jiQ4l0d8|IL>wD_0sp0u{yn*rqBMu{DuC1Su(|j??yx0f`r{ zP~wvrJF2(UATjf1PtFPwM#Wf9S7xV4M59B8<&58!IHFKR~j>Wb2PeC z;Ew%8k386O|GZsLY0p^xK;u_;-D9+$lElDeIY0_u`L349G-Ek=_NIE}d}XlRqc?-d z$c2*1d>BP2nVREt^~LcFh`u_vhaI2k*BR*hE(bs381gL6MD0QXD`!Gw0t*w()!Re4e7rn9XG-Iw^KuU}P z{LH_X*M8yZr;5p2!Nx61}w`JI!E;3XSgD6v%>eK+2v+qX3SQarV`8-*zG z<($pmGR;g6FPbB+Ng)RatoN3sWY8|wM+?MXy)>R)QvP5z|2ep2Z9yqC?OVLwmPkHq zLU-*i)VxfRbdB{1{Mc>T%%tgtPO7cldZ^ohRgC6uz7!U5k%E&Agtn$y$Jci)n!a>2 zO;rAzYSl@G->c&aFX2GFwbig#cGg@k>9sKp^BAg~jiSY=;TQQF&&!p(_~`WwWt-SF z3gWJ0Bnl`|(On%q016Q9Hqw*N-9@DVGvjr0MOHWQ!E|b^C>u8=w@1&xT#^2Ukv#?I z`98529HTdB0uiVC0a+8gFyVJH_{VHL;m~E!Aq`BKhY}9yyII=}A9r!1|B&BXTOd5= z$Y#!oLbPH4RV>=Sxtf3ZxI;n1^+Zx!bx{0()Lp?yUnpOGyvm%tT3?c!JiWPUWGe9o zB5R@s1hY2kim#mTApn`BXe;CUR7u0U*r*3kYn=K@zpa?Dn)82{G6BX38A@kHiZ!0_ z6}^EvBZpZ~OnI#bH=CyL=dQWU9%L(oCwXye@Z1N- zLb#k@SEogr^#;o3y5n~^bs~S!pMwz%d(^h(&WxLc@rdj@oD7JeRV-00wE6VoFH z6L$VKQE2dijSBqhW1zD>LqurG$aW79`nmW+#^Q?N=~0hlXiKb%j&QyOU%=}rc(;f> zJRFDnXPEAslX3aO%a41zAfa2g$~Ow-C#$nZJOBf59@3i=jimB?g~gqFu^4adYr!XY z#DD(Y&BP;gyrG*tqI+A_uz&dJU%tTP@uZ`Ru@3v{EHCld@jFGYL%WDcq5MA6hGVFIyDPc7 zTVMEHsiy!5IA0C!%&xZdr=(!GqmLouRqllj<76P*PPj^|W^$ruvxXq%As65+DQW@_ zCIM@%{~q`;)EYcZib<|DLL4w>WRQ{nxg1gkLxw{4$rAgo96W+Y`UP1=9?*j)UQ8%9 zyHicru*8~w*8_E`kP)X%MwT-yzY-r%8viW=BW+@osgX{oBnxfB!wWc8T=oRNHWhs^ zVZ36Dz((5T1mx!uyHYwIQ}DxOw|pk|rT5>^PlDOMLqGqjzy1Fd<;g9ySe8j*HR=lr z^)HFrF5!Ljy}t5Y8qX2(O(FwIQNKlsaF|5$m}#k_2Q%ae`_0eK-@ew$C@+6jt6mKs1jM`4 zzwZU83}}M&`5e4Wv#tZEu8G#-PndvMv6trO%wyd>5Bo zOaJ)3DqKYXe~g<^s<&xRyZIZ2ox6L9G8@GoK6}GNvlW(HmUrrwq5y9`W8L`|_hzrI(u& zP|ga=I96v)Xfm1XMr7#g=!pCqm98>lF zp732VUNgzfL;gUL8ipy^CfFpoj!0F2@10 z*wy-Bzoh}0!QMVWowEUsI-3{E2$d67PV=!&n8z(KDc%MY@6!Sm&*e?tA7(KD=hR_V zrdosehuGm>S8B?Zw7^HT`^3f@g cw!^LM0?y%eRn_gcwUD)K>`E##VL)6Jm@pCaGknlAY}9P#BDDvc%X4 zGg-#iw=wpaVKC0<`#k5I>zwO4&+j_tI_ErperEZ+_xpamUibYDeX6I;dFtXR78VxH z$B!NwvalS5valRUK5>-!i6ZyeDHaw${^N)DpZSfD39ta;p`e9z)=-td&p|^bKGdDl zNnA>8WN&1z9DIbj`{oy4VWsj_)PQ6UQa_LiE8>%9-+X)ueP5dnDy^rDh>3-iD-DZbRzXm-=#gjc|gZKLq;kWE(9NCnXvCe;R;Rcqf>m*S&spp)RBhuZ(voi zw@WfOU=y&tO3E8Ld(lUL@{YVD;EA4An{(H39DV*z0p5xUoKF8yvt2D4vzsMaP55Lp1EBxq9E^pP7 zk^#GYL=j!AibeU~Y-P1W$U(i4tffZi*Ex3py|&&_1S&O|sy zh1OvMZ$NlNA6wXSmfHB@hBWi+R55VBV|t+}aScAeX{$JmW#WO8Lsh&UC9s)e)xm_0OL1L}J&Uti~Sy{ts!jx|EMWn;r zX4n41Ro0y@=P4fExetTVj)a@#(LD>#s+$c-v4u;>&8}Ei2ULB{zCGwX!0x?S8LC6L zCcTKvollNc0I9ZBy^;70ENvSf`1w^XmA47DE+gRKM&3Vgh{VLHbJ=5N zJ671bKaE&zkyMe?(7W^U&e(wO-cm@`Uwz+kH~Qsq1w}9U+|>!i>2Z^`(=NxxM8_03 zilXLBEV|O)286Apx#tWnm85!;w4s-h>Th9tz`8wV6`qY!7MPXOk5l(*xCNSr+Bb1# z1WImrclsPBBwm0tJPnk=do;_J^#Nt9tc8)#xph751L8}N!*qZ0&-ql3lc15|o0dgN zayLgr@f|i*9eJ=?uGJi+>KU-24eF7Khv;Y~cU$`IPOUnT2*WA?i>89RBa_+Dql+c- z$yWB)$CPC}m5{6>@t&Z#kQ5JPy8#!uHn)v01%bDg<%t4(x?<@@iK$ z?t^@@)3A5LIoNmDqRJ~W z7bE6kN%|sjOK$nwYT`$C-(08Ji0{o$P)cQPtNzGUmb%})Rpr8C;f|rP?f9Pk)@xu@ z3?-~LToWM_h+n{aAZX`c{^l##)B-+hBNRfT5BODh1jiOq+DKLI9FuihWAf5s4Q|C) zAukGKRP`mfyyoJjT5i}9Ql4t1d#dWYLr1kql;^Y%-gSI=I$gtL4mc}rgzy5SO6Fd< zGxcP3Ts#D*)-3|@$2(}~Fq~$MYqb#+BqW6BkiE5obUNSdhp3Q?Lki+u+sZ2V9(`i$ zqc(mO?&yE?dN(NA@`D20xrxFQSdcJDf&?JJIzgicydvDZ^wZqw45`){WECTv|3oYq zq7~{_g0CC}?o)uEN#Mb2WAAzsYn*V30SGCWG`E{xV)=%1#njBy_1#^vC&@9t$l6sH z@l)RGiBN+zN#2-?h_>d)mf9%4Ip|{T(2BEImO3pB0$T!}>Z$NYCi>B-#<=MM3&HPB zGZMt*Z^{uUu(-*5Oh~U;SxcRgIkc@9hS`X4b$T|IfmA);U`#PGW01cyk-wT{Q^u5Xx9YAp041#=hYAV>ll(X#?qzIcQZ`PM81%t z<9bh$S1vd%SN*0nwZD4e*P~WGJS|mWGc$->?BwD5>B2NJaU*omgYq`2D?k?5nlfSC zcmMERK3`Eyogntw!hsB2_pW)e|2a({wuc)UBmCK8Es z;K`#{fvHtqRUcm@O64WwX3A1Gi*3S}Co_Z;_}{$`H^GH>UKAt{Bqg>gU31JBz&o~Y z{Z_xi&ve9sqH>=MJBLF>T8~8RIwzJN1J&CeoEU$C%r87A&rnyG5x}aSdZ5z;GtTAs zeC*`Sph(=&McRFf%`9!9@T?oJCiuaoWlsG~T()1z8me|ytfuUA$@i-i%`^X zd?kbR%PlY8!zqrNqyU}v799*vMqSSn@sR?@EP80jA&PLFKzH!ni6o?dqRr(SEp$Sh zBLL}t(t%O?czEFk@dxzDdM-IB)c#tKwOg~?(&V*dd2PuDV#$#bYXO>|BY&B`_r^x$ z-m6+pPqjU5ot3yOAE$e|5(j&7TufiXP7Ct3)-)age(s$2Ez@ItrQ?P{x#QZCX{d=H zJTEh%&S9n)BiYd!;W8|8(Tpt`^@Qu$zD!i$(AI*k?hB=_C&Irb2Kn*}*wH`hbY&T@T=CA$jniqd zEahazYab=kaBNuxW1j#9#UFzkb&-v`G0hO-(i{Bk>v!d?W-O+3`;z zWwsKIyYk<@4p*u4oNlF6dF)RFlSKp8?(692uvv&pNbCp>EH?MtwOjuE9j$ix_@5J| zX+1JJxD{@rQtm^--SqI@UYo>Q!w9c~>Ri6@WE{2@zE|!`9+~Zo7gl@a-16Zpzvauu zn9CX+9UT#~kza<2Ofj@^SfV>xyEknhR~K-ww~kiRy!)qvS9_{h6Ar2i?zQRQ^p=C&GB1o#p>4E3pk`jo?fal zbYsRBZ-e%l-I(o^8^y1kz3PE>@b&A9_!RL^3#~Zhswy3O^{RGM-DVGP$l}}c`;N7{wV2&n5{41^ zUt4fTCR}P>^sTUA|0Lm1gyJmS%e?=2<=j=dyKH}TaL?~QCpN&NRW=^2j@L7L%Glps zt)7nR^2L|hU{*~JF5$%pL(DCp;fCbpl-I`?ZR8a2`rHoc2HE(b8LuhN(>Ekb)G(OR zHqD$`U-RiHL+`6zpDlqdD)?n*!jYXK@IAL;bjD0rISrFtTq^X%^MZwzm3mpDa>Dw4 zYK~Vh{DyS8qZFr%>=k$L?Yb!My_##-)K&OuEmBH~TXpN{Fd-rcOC{?%Y@k};ntcV`RoqvUpS(`J1e)c#y zFo@pTo{n~BblN!frlm4MBs|8dJtv#qC6ZUV^bz#AWK10C)5;Qa3tw&^q2R^7t~}0M zFKOvyFj81S5-6xgL79YBfI)LfNO+42PyKzTe3bRkNPC90Xax|oX)oRKK1jU7^%C-sb0wg9qpYL(@nZP+wt$Kx!!#lPgsIf^m32n0n1LkfEDY_5{>H=hyCt(v_9$dl8DeS3ibNaUwg41Djf)Ovt$Ff+Xi{Jy9&t9Ul2{ zYjAjtqo~D2lOh^@nj2bgRom>~^X^U?YVNF7*U7x^tSJFn08#i1QBY7Y(i16L;||%M zPlJ_IRw|UkIR$Rd90bf)im3X}{M*a1njqx&=k#fyLnrQKdA?yi!CCYWA?B!?ozgCn${T5ICq! z3kx}IyrRn2fi#|kMHtCFubX$Nx~@inX$181~xHdY6D;Y$saAEnlvoE zeLlP=n7IkJ$HZsSnb3AX$79McM&PEmCmr}+!1Km?QUSz(&F%<{QK@OE^*~7jeaySJ zlOoY{|4-NgEkHw8r+$VDj>8qhM}_45w|wwch^2zOIr_}RKWM5_=|o$3FJ&=~EG3rZ zykMSD0k;erOdu16Zr=d74q_XFb-dvZPW&rK{~r*+e}=EGMDq%{kpkDuXjj{6L_J8j zFYSC$5Po;nnktI8Gs*mAu_?_m{mh$x_(H}9FoLsNoqW?Qz^c&nU4+2Rz2I3FGv#~b z9|T66;uZop5Hmay8R4+y&mJK#2*Bjh$f;TZjIX+X-9*B|di(mDt8LK`9&I}1?nvG( zeBKFmq~`5D;7nrEF>Tl#(Vn$-LQA6>ft#|J3;#ABG+htu4%(Px%v6?t{X=&FzsSxO zrK#+4g8h}LzsUC<(<(o6k^^V_(!Wd-qD0j1X7hh)Pd)O_OQWaTU@K~$*X2ioHDj*= z<5X)@aap?=jjEbeRJ?ZaKcfP_QV%G`muMua(tb-2fV+7BJt+?lIkswc9atqr{J&?I zQx;KM+Y65zd-t=mcPGaexeQ?eUUf7^Wiwn~2^jEqiGEE{7V6Ran^l#QaW=){4hO&U z_H>NeXb?V+yOa$Vs!U)vC?2!5ZjQH7DAWKHK^?@(Me47909!b|OTM`e(CW#f_ZQERl_ z@Q0xG`Cr8I%H`t#wME~X%?L+zkwL3h`c){x$iwzDyEcv*`0WbFzjt*RrEuPK*ucrs z!T__ZxEo?pfx`>OWLbk!GiH$#3huU2%jfB7HD287-y_uv-V;B97&-7Hi0~ONjv)Cs z*;kt*{MO?L>g+W^>k?BOEeb;3z_+yMwA?@}N8T#^UTLa4N!QVKiBDj+b2luH`o1ty z*gtaZ!)R!Q@4?qM(=J4lCm;Yf6Ed(sP`7K~-Dd#NqKZn!J(rxb3h1(1f%!Zptlf7} z!1^r(2V*4G*%(1%7qjcRYg|6(eD!?v&5x?z|UG z-mgr*dhMOI9y#{k_-yj8Xb_E^?o^4Bsu%&n!f-E6zw32BrH=P-f2m8%O*y&v64afA z1e^)T95F}^Y?pS3rw&%AoKrFqwtiF1yGJqWtruvR&qLm;I4yo=agbUqJ`OA1mGyMK z*K3!~EO#ntF>z4Vx>UY=@YXLxJ5?s zJU_PVruy&0g!a$dYz&zH6Vh7W#z;2oyll)U4m1tWC)G}IBq*;uJOq_q4J{G5_t^w) zl#jaK;0F&!QE$(>ugS5$E3MzTw;o8%=;iB${E2h_wVdH!qKf;KRHO8zRFd71m?{Px zuRrzs<{uPf5o4lZJfE}slY@gJ_u_d;7^y#SeWWD}ca)ibGYi%CKt~QM*Z+4OVne76 z0i%NuZ~&ZYwu;{&b*1MXbeUJL_lJY6UDf@&r@_^dY*k*n#uUZ9NfTOQB!>)rZgY-% zzISKnjSSbB1~OJE#Ld!gGP55OxV>>?{7rb;&3KExW$~dGe)E|tgO>9Qbzry%hr6~n z9cKUsxwN2D6d^lD=U)y4Qz)QXcz6Zu z#3nvVKU?yFkk=+QG``Fw9(kT1Gk0^X>e*riUMzaJa>r?JS$17FFG{aB@VbX@8){NG z^mE7y_i{#SU%#^ERy`M050!@*;HZSrA3z;mO}kl54=|H^V7N*)+w}{{Kg4l@$*z@C z*V>lNcT#Ap>0rIV4ugW_S2NWn_E0YK9y<;tE4P%109lvcd%NkTe6BX9Xj`R(Io46t z4Y|Ncu=|Ak3rmia3(UNd=TwAhsB7;+q5R)N*ykXywSQzv9!l&v5;?kFd%Z?u*bQlT zA9frp^#0a-*E`6Yph?u+7Un7G-2j}m$3|>EhIT{nyqBIe`opL}1>aW`RwJnM%LZFI zC|4iBfGdS8cdcs?2F|;=`~9wxqX?D7zdh+mv!zvT#`sc{p_z^aEexu5fFPamV3ijeR8lo~cXzI5R_j{iEJsmE>ezJ`Bux z)A0!C@l??epVIK5ntOOW9Fa|Gh>&1gAu}rmNKKKjBn{tj*mS+%&V1gz>k5nS;k5k9!?d@)ZvP`5Z?9eN7Q13j9JN!wxWlU& zn=Y6WFi<7veGCUG^7Cc;!k^y4^f#t2#6>^-l74F$-fT6)eseV4Ge6*Nrm)hrPmRJpd$;x^ zM~UI{2Ng3v^6qi0+I<@8)o8HklC9!{N;mQ=xc^ymNh*Xz<#6{K5P3!S*pffU)W~k^ zZD)@p$E{L54bPiN{e&zj5s$AWZ0E|A_yD)%Jj($koU4ys?cJ)d*}lququG`w$=>6K z6EuSn3%+&&yOcYiHPU=vfTLCb)8$W9!@2_faEf(RG-`y2XK?hG%zl zH^w1rx|mk8)z-E1H4M&cS6c0KUU$oEu$*Z%14|@iw$q20$y@Bj3S~B^3+@E%47;-XE@bs7FG>S~f|;`xtv z`!icqqnXdY7hbe;>SyEC)Fi88zd>x^j+ByLC-EkcR6XB=;SKzn4o$B;J~s_389Nu0 zSTrR3ly6I-iVE6eA9-2Gz-V?z<*AiEBMHLXF2pf-JiXj4tDknQOo%H);EoP^AQP*i z4};`urs<*#_TB7C9Cm*7ozDeFhGtEp4(-kW749e_wbM?>v2s)O-6M=ws2RYWuZrDXDwxs9FZ%#P{EJvPgZgwbt(WG?WJFDS(dpA`!@5tNr7@sD1N3V1t zqN?Ro#zx2oA!vxTfMg04`pnvM3E%-T(!F)ug5+U|#rea&bC+U@t9Ox^bPW!CUqj{W*^})G#L8W2f*(7@^fqOPNLq70ARU71fzmAXJ1NoQPruoxy ztGAYAi&Ct(8%%I}<%$DQlv9lFts8Y+AGjhwaX9~+ z(cqjSmp4C# z6k@DFoQq*MP~O;$>-KhCV&D^AATgP(6(i{~ps6eO`C$!m5^>d8RadWvRDyrcNP4_a z``P}vbT;}&GQjHh}MNrQ5AKWJ|PJUVC2)4V4wMr z0rO0er(1Ar)9AZg)B|)u8{{u|hgeFb9V-5}6;mWQ#)G|b=N=6_oQ#mBNF#8fYvW5x z4Du90CWfju!_>C#vX^jcR}qwE*j912b{|%g3vei$Qv44l?m~CoGnQDFt-gWtByN; zqai{6Akk=;3BD?fF>x)O6^`%JIC@y8GMN<9ebRoG$>#j47fvS1%mGp1dl&3$i*FZo zupjN*hT2GoQsUI~iatMORUq+6Z`GG?hzCSp)P`XaK#XPK=)+b52j?#XY+hyuZbolP zZ7sshUTOCMFGX8O`c3EV-zY9BkStv)mU-Z-u6ScR&byI&3lA@B*zER?4h7d7dn)6# zBsXhHbXHFyGOoXFyFL`yDS&^kKzh68H08*&lk97gf^A~N_;YviA#^7d(m~0#{{dvl zftu0AM376R7U3ni^`#KqRSU<+po!IvdADRR;_PyY4SQ>ggu=&JC3~Op4DfV+%Jaea zWi||k%7J3w=-S^SKtUInF+R7$xuK+fUhkt4VcTKmXWht(=~a1e;HuswyJ`IU$STZo2fBFu{PT z^X|z!0_b}njpl|;d`_AMl`7I)ZGxV=2!CUchdB&X#lDbt>vC=Eis#cc^!BwMv;BEV z-cg%CHH6ucpSZy@nHS2))T=8rdSP;E^O;>xDo4%(D5)^OLT|xjKB}@Z^&D)ql)|O4DgFBgR(?-pcx@NtvpPme z>!biLk(m0G*fBlfDqvZdMGGWlY(PXVzf65#Fa_3JvY4vzOP<^L; zmFg<8y%k@Cp)XpBS~dKMoZ~YE@Cxl$c>uJMSckjUcZ@dHbGDHO*#x0pDm`%ez zgZ{$SVrPuiMkvOA|CI$Pyz2XY(Tb>}s^pLtFxi+n12HI^>qaH;$t|tSC2=Ex<&JlU znwLTYqFEC2`(@!yFkx}u$;M)cc%gIU44g~o?o;JSooj*-p2!^p2|52c-S`=Cq8RM4 zBrofkWQd(;tZue_v79qBmN{0S%2gG}J4a-v;*eu>QB;+Ei(e$Fcu-9q)Jb9ge62zu zq^od9j~*wJb30M%@A+`FcgwyJv3}hLV$ecodL~xE;N6gs$9jeD6y1c+eGj;a>^@X} zu;bOZf+)eu?cpT?g(kHYMcvjMB}%@KVSY*_>wRQ=X}JO4qNL2#|ZeULXcg1DznpYw_fS>d1ifLmBty{;5Y z$fpblp;Io%Wg}S!X{^h z^Ku4&DEmfORz%*Nh#G22?!@u36TO$Umo-I#Z|k8fieRq>`IIDAp3b$;qO5_VP;sM{ zo_j_~B^+s0fgwPWs`@P-A!|KQ`JrZ6h6C0H%mtL{)<0YlZ8~+3aJ!-<#g&g|1dL3q zdH-<(CmeLrKGp;zfS|}24z(|x$sn5ZQ z3sP0;Ywjg@-y00Aq)*MGbH8=#&Ba#_VvlvF(kTNXc>3rfVJKzX%l=TkXrVHgHRbUk zBZn6Y(l#_c;;)Sj9387Ot~Rncx4o*$C1uK=lsiD+Idt)aGRE?6)(P|7`*=7ITMH1U zxaK>@ryTaFUZrIr1}L1c?_D48l`o9C4BcoKt8yFu_|rW~ zNNJ;05G-`Z`Duwh*S&Zqt{2p=w+i;E(#Dt)uvWwc&qh}M(*n1%i;KI=#+}XU{ZX>N zyWKjO!th>)X@jks98)2?bkGlcWnE-~1lIX^zIZXobZS5sbK-qh$5p>Qu&}Vu)$IP&?TjQaxv7Cu zC*86pu(!YIKJRpEs%n`{#@!ll=X(l?)TKF{OT4?k9EetH32-=VChEVCA!SkdBvsjG zW2T*4g7KQ|U>a4NDoYKrv>vX+=;MOD%WeTphR*7fzn|s=u$Wt#BUSe znWPWhr{L3>R{btt+N=x$`YZb}TFr$8Dp_{uXEQ2v%yo9(jf^AV1D@Rk(oKB6{9Z9z zpJ-BK*DY=Ev;<#P8?JjbnMv7w_#)%3|FiR{J_L8UHmU-iZomI&^UDhQIn~PO{T%)E zW)IW$Fu*COF!slG67gtL!pFylgYPER4KknN-NRhA?3>#IZ@fLsGWXQ%`bVqaIQUFx zSe$y=N8Ev7vdP$Ow8xj-XW-FAw?>uY-^JG~S=vAAfe2|)!!z>FuH)!0nAS1fxqH7w z4whO`b7i{7R&LFV$)ZG{f$=rhy`V3_AfNARR^V@*wR7NIKf)}X)Sv$Y!u^XoL-Q+6b_^)3Z*sIZ7D+EAy-ZBw$5CvFa z_I!VrmadLyDElF*ESI?X-l-{J`l(q7PuewPU$1u zcKnwVa|wSuna>%noElGOK*t~}^ed+B<((d64Q|zEhK3*KjP$ZmKY#w@R^R(pcIkq$ zT#~%8<0S`)`ixScts7Y{V2MK`ht};m#BWh^1krunGEiG=n?QNd&&tuYR!8Tkg~=0#G2t`%bq; za_~!cxk1u*x|}@fDJBm0ou5i*=j%y?sOKE_PRnO}UsqRCY_m>$$EzoqJqc9ofG5C4 zfn>I^U6=OLK#rM^in$nJ17w_RxHEF+z(d_iR0VwTx5;((LdLN^nUe?i&!iRU$-;#1 zkB+!^BGv|cGHvNd#VDik1r3m0ncHv~6Mn9BEAIW)W4id`t$c?oTn0X~3OggCl8tgO z<4sy?}z6>a;jR$$m7J zq8|t@NC@nWoDNVFmJ1R3R5k8Tnr9B1X)h}(D&pYa7_~a+%g~@P-5gBM%1= zD)TIMym<#Eepub{(_OkY7le*gH`3FUtn$ub>Y@nn=V`2%6uV~W)Of?7 z7xB_%=V6{r;F6J$PQ4QK<_7W1?N=}(mz)<4YTHsM78o@5bHMDl< z)tBr>TAJv*Sv;}!RWE;oDyU8|xC<6&OPLH29fuI%?(XhdCqg&{zu0z@N2>%uj?{vi zOzRDCe+3f4#knUI(ZD_20pyTWaR4bb5Qj1Hd&v)WUBn8tpg%clgTlkC5#FS3oD4KYfD9?4NNy3lLoro z_|GzBQN}LlU0ulUR1K5sas0+ZW0y)XHMGmUCr~kX|3iNx=eJja^fC$x77Oyy3X6(5rxYY_++eJW9()HA8_;S>ELKO6?(D<@{Nv>j zR8d32xOmArA~`u(?)L*GS$A3$V6wSc%Ko!n&MD3RH_DoyFAFWtO%d=bcIc`|I{QkrUy1?aHTS@sjO^%hO_rbynMcN zqtT8-G7HA^HBq;`W(3SMOImW2c7p_o=%V0ir) zlMq6z=VWcTim!7*j-K()&h4OU?ihI7-_DdR^{D<0G$5C}P`&>w?1oQ!-No-(&se7~ z_}n2^DAe`#J@&uPx$F_TC)c!%%=rRtK^gfF@)je~h$$WB0q0&EjQ<;qPC>0)Cs*e6*9u0Z^Ba(+tpl9Nk_2~!E+kZQknVS!X)}Zo@3{4T;C7df&K)Jo|s$M&PsNgFB-0?frSXFZC2i#Ir z2Yy7X<@9&^BJUbziIa_7jk}ms={jwjhx-th*m~+(WesK2o!l}|Rq8e3>JDaJH}Peu z50GrOmx=DtkE@Mrdpo43RKaJxJ*!1cl8^JLteW$9lF&9;;*pw!W_2iv)C}sL%6^$^ z8f=uC@l{KG1{5QFVOrK9#@VSQJgL5?xTbv)t0|2p%z`@U)Upap)@R_<$GqPlXA>i~rP20ghjw;kJa#`=Y%4p2A?Qpbjq5DAeQPPAxExt{u~x3h z+G*Q}4z(g15A>l7XJyH1!R*U#1csDc{GaOr6AC(w=6R5FPg8eO9GPE*4vVC4uAogQc z=`_CUq_$Q3kTf21E(!NuyPD;89?1P=%Z+dz=e*l)PeA(=W8{_F@ik!?n0F%s`uGcqAXrCS6ejI|Y&bT~~;G3i*nP)gHNEf2`Y6#LRsCt=F*_fO;|=em5v9)D?NcM-RZd+`aIA{1-`BYeBgJ zAc(Bf5i3OL1n7qcT$_<61vL&tr=Z#T&N6Sm#5~fKfT4D vGX6*SW;v`tvK)%vEQeLdfAzzCgxy4366G)71?JUVmdBcU4@(|AfAe1e`?+Kd diff --git a/docs/dms/umn/en-us_image_0000001987139953.png b/docs/dms/umn/en-us_image_0000001987139953.png new file mode 100644 index 0000000000000000000000000000000000000000..474fb8f6eaa84610b5a3a687b35d34184745cbf1 GIT binary patch literal 15196 zcmdVBc|2R~`!4FOw))o82~|^PMN!l|wNK-|ugqy+7yo+k2nA_u1#1|E#rQJVEqF)mV!68m@d?Py6MT@ z!cliCsbU=4&fLOWJ@y1q8#2OKR9#<;ke#lvw3&LbcFH2RYy=Kar9Bxx8>rr*g}9ss zH(h#>hHbadddhPB&fJBNkI(BOprwOKQagR!-E%C0UfcVJXPrP0eNgJ zpWh6gV7!vF?`mx*5yN0qZB_@vrq!vPCwf)JxuU{zio2QEc$8Ng&KF!x>^R=+e_ zry|V2@bz&O>I`Pl7j%MI@!{C|!kW??6T=q^3`!xF^l_QRLyh^F*6-;H1AHprnF~1E zfitg()1o`;VIo-LdSY}z1-rj1PJm&#s4Z(Z4usI;2z<`Kkbb5fwRSpAqob%eJ&$@j zSyY#JKgY&FWG?^LUZIQd?nzs!NzFHB*D-x{flCYwf+3{{W5jj;#j0LD9n8B*G&v?R z5HEkt5LS-5fYNGmP3aXu7wkV5>)ktIIivhVQTV*?pHbrBF>CscLsN@OBS)XNA6O?? z_VKhWSa`vU*52ND>+EW_tDmUOe>}n?rsWR;Wt(}S3oh`jA2E;wMHEI)Q-A}0ieb?> zk{I(M;)Brg2gMOUwqDi|!>9hJXDc6^L>aD{T%Xy=sY`x(@=>1ew*@%g3PV9RM>!S0amQ?{$)YkirmPuG!xV8xthpS-4!`)B&Goc{XGRZtRp z>H!ugb|oF3!}#HD73a`!3<#ezQ~6pPerm`DgK`6G{T7zk>JZ9TY?h_jY*ny#`ZhBP zJ|Q%-(uDOJll#rcP}4-|dzaal72Frif1c ziNk;EcMW>I5}ME{((8TD>18ioBg`C?G#xaa>@|I`Y=u3VFB@n&2p=R55UFR8Ew<#bF3AMYw&81kv z5n1Bl?92&@kWS46YhX%9F1WLK)*vLmzaCepF4XwUMtieeZ8?H+IB*3f0^{up>P^J5 zrV1j8f1w+Igo_>nprH@cmz@9r^S5kUxY1WoiGj)7U5s~;nW{)zd&lVMTGd)tPGi1) zc=c!1zp0nzl&7=`$1N0BP;uK2?)%$(z;gI37)lklI+sul;AW$)+YfKFLErAjWL4ZN zRc=E0t!}S5_DjV<74~p#@WdER@P#Z${jCxwhe~(&a^H7Hn7IfHdp(OtP-skEp8eR2 zecgV2>vNz>w8~`|*-i7bhPS#8}WPA zufEsG@8_)?2Ii>{mDYI@dhB~tkfdoE>(F|5wyVk2snuK*|3=dhfq>(j`@Z}Q(S%13 z&!J?S*Vw#~%XMS&4m(0XG5Y$4j@DV?c}Rfid=a=2`9irJx@Z5V!wk;I%302c4vQB9I{*uXR|6xG^is_m&xX@-{UkPZX2^JjlcUQ8NNR7x5%mS z8kt(I)72KiWeAEe`^mgStl2_(EC?%k>Qw|ES=peXe_*#HUBdfwp^Rn{!J>@B_l9eq z>Rlb`KYUk0l8TwMYWM|TsWvB@mH&!s+qg`_z&Fh8^u&Al>ZHb7K}BTn831#Y+7xDX zQ+mSEAw@BQbw(yv#R82{?pYr5a9u-rdKsI1tCmrJjEyJO`T&c4E8}2nW+|Y=oM*IB zZ#k1^>W)8CW{~=9h=5dO;$~@YMAE@VkBE27;WluCrMd0NsuxgKBz0@X(Lop}TRI+V z?ElFu4SW1X8i zka?4BCUSk?vZknf>HY@_S$NIpa=_vP5U9C(waT~-@}!R4tZ5b1urBNXO`Lp10hB41 zr*Es+J)MzKA|FW4vo^e)Lp~;;S6^G-gd^F_xSQ)&r0u$M;msAjtXFTT$ewj4SnU7S zgVl)4x3pyKqhc2Jm-f#6b@Kw9H?CS%aWcH|IVRkBbWom6+&MaQu(?ww<} zs+RQ&EAl-I^;L>aC?BIy*SQ@<-zSJ0(`p>vP$>GF;&i(Z;Cg-YYyjVYFdxdBz;iwEpxC@; zlaA58{2hP2-*-=`WCS5!9-Wza1}`YOFn*{iv&h}0diIfatG`hm^C!l??*_-9PCO~? z1KiHb3g5=5S;u^mknHX*ymykv4fdO@l8$@}RE7>9XNx zg8Z(lfC>)2q zZAX<0Gwa>ZPQY!ZqC+mt=9>qdQL=c#Kt^Qp4-L>?H%)lq2xghBF;|3l$ybeLOOU~| zL#~PopSqcut@gdRHII5`S-5Fq@%)%8B-G&wV^@2_9w+$V`=g98)>zOu3bh73m-!Sb zSTf3u&bwTmCnZT-JC2d4T*Sbg0lrirIHL2tJ{kns$lKD?#D0f9n}Jv!#TblFg~^RK z)z;Tm=lV=P^L0DB#I0xXG1IyeLB9`}(jSC8Xr-pTb| zYL9Z=#dcx&%hMBA8rkIoC~z?!QQHuMQT3)<$r_{WbQn;gfgaWu>2 zuC&vN=l_h>r3ylqS~LYrW`{CqzQ61-n@sZGU6*&o zRCx{ZW#J9NLjUaI?Y=Z{)7JDzZg_ZjvQ-eZoy%$(=}-A_*45Q@e0*HI>G%9_j;7R9 zyU}QV7IcPMr=tJ)&!b$=x-TuQya}eT^DF(1;BmVbQ7ME9IHFOwL;-dOI2Q6qj%M7H zTeI!egzgN6e;$O@_QzgAI6HWe4eYABLtXJVz|AzW8@3+N(6j~K#zJu!lS3%?o#uny&AA(%fg=`t|BMi0 zRBY*QL)|V5SQ6o~^s!0R^QDo{S-#6DecsUavBHajmY?tm$Kmwxnm;^nWjx-Y|FXcrwU~02R zoagbXu7qT$?Sroejx+2OB6fdBjh#fqD)#5EPt|NxPr3EFKxuoV{g!Eg<-KnW3iJhj z3rBp--YcxpZn}r~s(bspFJVU}wtZ!qa(aGlC%T39jNQrHdY_>ZEAWa!lCaI?8N<+8rdhNNRCAo9AG`qE^h1!#r7}m{8 zaFB`_5IDJz7OLH+dS2!7+TlZMore_432VhtmQ$V1`7*)F3{YIkAqrzt`4w?!X9Y@pvS0nG zbP}VPE;-EeIs$;dHS}b8qh0;bqM(?X{8_V>b_x6jqyo?vXsl1)_LI`BJdKsmNWjUYx zy=PKKO|c4k#qJ6BQv zD0Km_bLPf!*yzLwU8S51`bL5A@bJWVz$NNkp)`lA!0Nob+w^_KExC9UKuO|P_FMc{ zKy|5u;N{kP3jq6GlzU~t3*@1&!#g!NYmD)@c9(8whDfJ_G@|ln;}fOtC}bX9S0~ye zRJ+zP&338=e6$t9G=;$|_oYa=Onkota+|6qWcm}k*Rz&FLPCIU$o@kW#zjv0c1-^v zZ)aZ*2{FyF{A;`#Wv1#bP@x>Wj-9?4<_Ak?XhPWDSe%L!rtmW_p^7$@JA{(DT=ObV z*1dv#RkyL3`y^ygR8&-jQ{G%FE~CRxv}P=Cw+mN5l={j;P&^AAZ?^~6#*1MzJlFch zSlT_CM=9#2xWXFS&RAJofYidq7=FAMT_sYcw7>4<85re01h~lvSGRO_o2m5Knva0a z(7{wQhCi@h8l4%i-Cd_5@AD6`#Svx@#Wp+3&^5d)*lnT#3O)_|g)YN&#pk^5iM=B2 zxj8#xo^>wdzku}rt1SBe%jGWHQ%sn80XYn9bC?*3sYlpXgxg}(fpJ7v<+B(+PF}*e zGFmX~>OWMYjg74$O?VZ|KGz72aj(*(s4@ESihQfhIP(tzXSLEa^)UY5fq6&s{K|z> z*)!N!&bQUAZXIRVI9?GsVZVTYlG)92TkOxdAm!Lyp+1sO>+ynCar)-DAI0kSVJXq^P}GgMbPu zf627wMkgD~YP+4M!-GFJr7ldAXEw0C3Wy;;&|iFOY#-+qNB$M$?yffsr;*N!{PR>i zSav=FV#oT`pt9eK8r0!xtU+|z)ce1P!6TXUxA1Sfl1|1ktx0XlDoW{-UaDfNK?TtI z&@p}i0X(vd@En&AdnxNb(MvDf)n_TW7>ZFP3mvtNZP7Bq@p?_KQ)$swJD4T$z}Fqp z$?w;Obc?e58h&DbZWk?l8R1fmN-kZ7^afQ1I{K^k*@I$k9MGDs4+FMSc4fl{N+{&G2EP8y ztjW035H9Sft80yne#QQ;@(?!xc0$Jg$%L%!M&4uGXyY;Q{r;wG4mb(2zf^z*I5_%( z0+EPkY!XYqYxTmVuU5;5?XBaQn_*5_%NhIO(~qom>{+mlWNI=c!`G>MFBzXmLM~V| z97s!ST`%tu@W0UqDj_85){^J-F}IdmOw-0nZ12|7+1C5-d2b~+R<>Z)6jQ@7iWxZ8 zBNZq>WvT$n_&}#H9FDUBIECqy-hD5y7H0HNN*8V{j?^(T5|IRq<7h42pQUuiOXM+6 z)`e|YjMA(uQ1=I-O1;hTrLTz4ojZal-kJT#TG*XkX3_H<9%u1S7UhDiR)(AN~QkVwpIO54nSq0u>c~%t$lex;$qH&K03?q}T zx}Ab4W4!btHmFV_=R_ILK2|^|-;Sd25`qkQd53m>3Hl7`#U4}mdo-y3uJrp|t1^g* zyGg7wT-goU&)#BHo=dNpmxeSF=re2?hq0W35IX~rh~yxKYrs2vwu8hyjY#sY%chDQs6S}!i3zg#Y3YWGxnWUq64n_I&NgkE?)&rN%>5@D#xP+CUVU?+Yr6-UrKbunL8QecB!&Z?%_O57kQ{08xSH+UHumniKpN= zZ~+Cg*2c{uP5C5?ty9nVpx5c4^JC@OjW}+#5hBwR9a~>MmaUAdlQSObf8qixYn53z z;`9_W%vbvZQ4c)nvu8X`BIy73fSy2c{ee=3ZuS4$m#+f%-|6iRkjfdlfOKZ;^l(Y~ zCt1Jv2K7~&xk@JQ=!oG`c2Jjh+xkW=Y2&j$mN;30!3+b9VHI+Ra0$hIK2sCh%>$7 zA-2+I*7QT(94hTG;6l2jKzEm`IH?^^qs5DX@UQDsg6NT{RJUVCY&h3}+ehrp9sTpf z1fY0|7Yi!G$STSUrl-*^U`}BDIcd>M2$$}wF(sR ztn#`__k3VkDAItiy0IBT$ZUFU$&Hl*qJO_02E0LCXD*Ysg|@e@kp18M^Mh{*%g_inUzoBnB-PvT5*kEi+9{XmDL`Q z$4BQf`b1|W>iSXG30u9d7^!;am>1HL6PUCl%Udf>guhKec<+PKDB^P&V6ov4e+y6K zwLW>TxeRM-AGkbiaNK9^wN$>DmnZ30CKOd8I^K-W{EOSO;T?0}&=);W>-E^7Od0 z+aYsXsxo7)nl(%=7D`~!6^=+Hp%lvUj@ss+&Yb#fePQ5 z8fCF;6L;DBXDP-2VNJ3#s!>Kwfy#{>IIi`vPlG`lGt_0n65hl-Qu{-*!%TsGn=V$( zfNr-<9*T;|0vLYOWst$_)%75P9+G+mWn|t8<(%RHRNjFn^1-4Tz|Uxwd9?&S#iepX zeD4(!vDfwiq~O(s3Ml*R3QK4-?{^}M1DAL!NSChV*Jku0N2h3~r`c#LbPR>7^GEIJ zB8&6%U_@p4$ddhPlOy9QD_%U0WL~Nor{{)801WQ^SZo8V;IQ|)-0*QwLL-GQV6;pU z)u5sjUU~%Z0WjOWrSHARw;r0g#cI|J=u(wSoEJk>)8cu^??=$TRO~Ae^=(72rPz(r zr9ViRA4|?hE#Iak;in`YgW_S=iIH0P?V@^)TfsBRkI5E~mQOQMG?20m)D!)jm3x^2 zSQ|%_q26i0j{diBl;67vjAtM8_^U%59kjxl#HP& zA`dY?;ak?qpJ-AezwEc0<2};x+V8C>8a34! z1bYksUm_c)wO_`2^BnwC#WY|6H)J#~b+LUT@Mya}r(k4cBtsF4O2tZ_P7Bo1ZXYnt zL2!`hBHdzlvKaGj179Mf20)h}>madV7MC?eVC(_aQ(5X4_P*aa>vRN4Y2 zp4E~NU|TjmP&=V;x#3GIw}8Lx&rSD9m(T9HL(>IiPdzIG`#YNnj{FdbjRqQCSsvW;) zn@ICu!5)*tzBo%`G&EnJLbW`2fbL~Zy25$2uEaQ9UJdKKYfvn$?vy)>H;8vBD)`=O zVs-zTspgIV5#@>d(2LdfdAD7LPyn2*LeUUM3gEcCiO<@5zGmA!E2K6hMH^{7w2Xh_ zZ|<#BsfPpvs@S4ZiABCNkqP&lb}&URr#`EM+BJQ9L{x8*eAM)Lrq=iy|8*vS2n<5c z?Pf%lGp$u~5zCFW`?vvx?Xi`mL#%D%ESUBF;H`UXsDl+Xm2AWVV_-4M^Tx5lwkx=a zu8d+s%@j3)lFwhGMnj47^Iwm$HX?qI0RD~ku9H~Xf|5tF+#-~M%(v+r=sujVS0&1s zHr?_2)c{Xp>tyh2gE5!|1pDJ7y9|5%h*F@S$##8({{cM#kb~P^2Fw7m{4``=BT?Mf zL6$E_iGOE$R{ALnuh<`L%n?v3FMm0Nc%5#gvj4pA$xjbA8Q|3VK!`#kce{1Wp3|Ya z3=nVpSa(EWT@jj!G&8nOMK}Lk($K9o4!fNaNKvD{a*Pq^AdoGd@4n#6e9p?dYQOfo zPm#sHPuKw+T9zn%w9cwQXalDm*?Y8 znS7;nbTgtl$T~yU>u0UZ@3R!`z{(ejaHEyWuNN?5@bPu@-k?NPK~R?0sSK32P!(sF zB`B0~xtAMoE#Dc5M_7IiM1$JlVd_&F zMQab9XyPymf|DD=Af4%ceDu12#aa5kMPb|r8_Bg7KL(D~=|IVds>ZL7hR?si@aM!( z$V%j>*;oGOyMbM;Q{j1tM|Fjr(3^ohg6S23h~$Zkmi-Tm7rU%e+?opZDKw-|&x%r~ zKNG3vYt@&3)K}>81@V9%=5{IP7A4$tUn{WvRt6c;wS2N-JJ)kN8u~u0kISnBqaMUk zVPTwNw8R)}f6!R=DQ-_oAm2!<;6xgPnQL#x%=c20W=sy!q)!4yj@3LKMRjfGLx#BA zi)Lykm2+=bL#Nz=!QIsXl2KPP3Tf(%|K1_8Ep*XAkx+^dcEyuJ2@qmTS=#i4|ocn)8O$J|54`?qrQ%%MXP8zf{Wy+%i2j3l{ zrY-~U=B9|IcLm6cW6FL53ig+XjVDaNiFAfH2vfST;<>R~U?L>-M<YP z2o_h(QoRdN`gEr#`CbNUfRo}EINq;2^%4Ykvowiuj2cComyul6D?5K(>|^<(n%<&0 zZt1SZjEvp!>;9BuGuJFD{B_#Q6~0~hK5Hn$dTlhWmVNTj_L2WBx%MB*|C;Qa?7JRl zk3xxTCh^Sed)qX`K=_O7Mu<_9sNm~jFHPW-?mHv}?H8Ht%jNQ)c)T7;^c!6A6a7Fh zT0AH@R#kr;Hxkhg=uJfbwS(bYUil%v*|)EJZOXn{hS#ao1{`OQ(WT#3W3mo+q5k*T z1Gb~Rnh(0o1uTy1k8t(muiR)E1U~HF;4kEU z0$Nb}lR7z6lWC)ZR@*h|!Avv2eRJ3I@EE>7?{#7!ae>5V+(UtCc&=aH$#3)AK+~ntf4u&zjIe#WlIb#KUJ|_4ZTtRK& zWYQePO#Jf$YZ~v{Fit435R^mn;T(ue;9*^W-)s5sNLgMh^CO9W4^?BA34RTr++Y`TrPjzF=v7N=D$ zBLCSuON4sl>3?$<_GS5<&rryQiEbS}wmU%6Vr0U4)BVSo<3D`;fKl zz?0U!%v94ftdqedMx` zGK72AGzRBMed66ssz#91FP4^Gfv2gFtF23#wE{Y1FSAw|AJ(J096)u*>8QYXU+aEP zO}coZ6!=@`*gp?f$~g_~4M8n`;BKbEcKerv*|8#h=i$S{I33T^4f^EB@!M zwMtIXD5m7tQND}gxz!osneHHVe!$&0mikG*gz}hB>s>%kkm@W!uRV6|G=w*EaZy(y z)zBbmrX2pz2JE7=3e19lJa7CR)h1sTaFmR!bLxPL{p; zIHKRb$5(5KZDdQO)i zBr~0szwORvs>M!3E1kAacdjv}{3_`8G@j1xOXvk5tEzXN=e^Ac&bx2Hr39w2AyEE7 z)@yQ&>8Mx7rC~cb!kgMhwM_GSH>MiKaVTN$_)dQO?(HfZKnlWoYY9Ge%;s>EWNE)z z#~H-3msWRQ*SM8H)1mXh-s8IAF+QhKfjU)t1&m*l{_CBW-`|=JkTC1VFKnIO9mKl7 zNa{VD@!VLp%MI5x)08g2Z`{?%N02kL0(;tY=zsAwTjCGT-vhY8X0vK7rwV`bIO(#1 zGhAg!x3e3MG}-P$f1&mK&GF!TsELMXt)+!ZB4B8h7k5-rV!bso3;3Wq7JVcN*Wh!ll1l;z)f+CxRYi55Gq4 zpSu0cY6Jt_@;FDQga36t<$nN4|3fC|Ukq}?|67_}qwRe52{pJt3KpIexKFnK9-g45 z;``bD_vV~Kx`#%o-kAqnk3hqdgc;=iJHgC}Mqe+^8hOvfE__*Y(9oBM^a>+`#R<52 zKDmPjOs`5-GO_dXO1%8(yOJSm*Y%;ILekbZ$DXt{-eE0UDN0$N+|jn$`&iy@o^}1r zfhK6!7Y;x;Z_T&=w^}vmrCCAU^w0Qg48bl~jUEs#ywLwk+| zvAqLd+x?7Bc(q=y2I$7&a9q%RpUqhwx7wD=19_%9Gz!kD$}xTmCN-fQ$FCf;87gou zh2^Sol}tDipR7_|z(C(gM8f#C11}5e3^NjCv|%%g#a2W(65>C1NjWGFibuI<*fS=<^;-I)}bBmd1Aip zb$*YGIiuRNNI=>rH2d$Uhk6Bm@$D{Hr_V~2{z9j~%}8L48=(|@F!-C;urc7`2&!F( zReT?~wD;|=MNwCfEZir+D5w65%Y2N1E*kv9w5EEaDus(>ms9$mZegsP{hOU54JE1X zZAlV`@Wrt?o#+j-U2oONkv37FEO3k907nlu7A1$jIZJot-lS$&>$H zdkLjoJji3@+tWG~Ck9`U3Pfu!$e`#|o}=r2Od{R{W_lN}XADW2aI^9_YL#Wu$?~Vw z&O8cebXsjyNBFDTWXpLzzLeq7FDlhZmO<~;lHd7iL$hS@u|jHIfj@j#;x+lrnuBP6 zx=wz+y`S~M#H7Z$C4}DAf--Z!y0@|RgdCZ!j5N+-+jY??E4f6@hEGh-)zNgLiq?b$rr>WEo>Fu{McMrXf@7y`n zPr?IdgPF9nv_=AYwyLUYYk#*e2^eyoRCCa%tnXp@b~jgcH!;-G{=SQNB>*T5?QQf0 zg%zZOm{1`2_@;D|PM5vZt3K0;Fw_a(>u@|`z_d!J2=R#9;fjbM@$90$)ZksAzjt5q zWQMbe53f)3fvq(Qz4`3h44^7l&-UgZP(V3&YX*}aRKGjOq+#jN8M7UqgiuAUgwKPB z4c;!LM{3I{kpe-#2VsXhC1#Z!u{xAo?01{C)^KKe(@4GwsgT~jWoCBniebee zJ>iyg!R5oBzXh_=Y|Hvu&*pQCxWjptRQiyvDfrXV`%c{~0OrNWs^t%S`tU@FXh%5p z$W75mKnZ+h!uYtKk8w!+@1uw3GK+O3{P`YEVc@;6-(3p&60~J}rx18I8zEsjtboJ=NH4MeE29el&BZb1n|Z_SUi;8CbY9Q&4-E(74gGUk%2&y$8h%yEfoe>7z?a zOQ#TuOG;b@(&d%?cAqEZdLWJOu&3x;>M?k|0H}M{@hjfr;sW5RD&!ktCctI*vqU>j zO*m1F%^b}-t!+Q}yGW{Tj&{VRr+AXXE}UYmVk4dT_{|+kyaCT*Sy`q z>}Sv6qAbdks$F3T16t!z81>HyMCCWBI^M)K?w2LNuL|!~<8g6B85bRMZ)$aj3i>Q1;hn zb#!#}RH$|q78aZ}X8QVDdPlo@bS~~Eb^rD20-fxB>mqeut_)<5NF)u9n4_ub>GT%P zJ<5g^QHypfkl};H|9kz^|MhNeb%gh5RHuowf@<=gChFi$z@INeet4r~xuSj~(DXK4 z0hMRmM4`F^--K*l1v#dv@{ypWrcKK}_L z64oaeiFwk?9SHTp6{mVKALXPQYv zwGp31ZYby(vSyj^ty?V)e{+MsqR*K{dHz#Ce64P>jn0G6=;=|n_l|I4K>$3^yziWL zwOqb7DA;8v76i|BDwYxRc8)PkaVmNKvKZKmMd>O*riAn1C~_VNj$r(?1mwQ$@B2Ea zXxd)sc8PaSHe$0?T(+XKq_CtCDGjx4Rbqoe@MC?VcYv;U&$@65hDjl>q)W1%lHR*! z6}tZ8a-2};W5pYmW9tyNk~H2}^Pj`t_|a=*p^!n8-bYPVUr4@yTtrthW1~)3Tn`Qt zm1y~n{>cUFFhwI=Bl30%KrlAD7~VvhawXiCSE;Uf)iHVic>}1{(PdS4>@ekf4*uBB zLTqz`d+}DF=TOeoMbBQ~tK(|J%M9{<=c~R(8rQ80Gv*9*DNGd=RV&_DheW6rW}(L| zrCBXRjQB^1Qa(R)<=T=V5cv2}_IY~pwq`a8py{6i;$xzE=>T!cX*!bEF;2d6ZA7=& z4_|}Bq}a*;w)h)6Xgbx#*f_+E^O#gWBnp)6mzJb#+t`V>D?sG?3v#4dJ9Q#jP{OvR z5VI)M=^B|gDDM+3@z%RWW_3kJ=ON!NXWB!UDz?SGu0_=Wm+P9tPJfEmyoklT4b-4* zXhIn)x5Er;q@dpr`kJ{QIQD2x>gNUeS6~a5d<81dPke=5>s`%g!e^(F=pFA0=*Jln zxn*Gkrhppx6&n&8+#Qs*2ti+hLmc3GT=cJvs$^CUjLsw(K=s@s-K-@|O3ZV1ftE4j z#`G<99msS`d*nQ=FM=58u{;vZQN zs0sceKfov=!f)cn;JM;p(9ACAeqSHXkv-s){|3p89Rm6x+s;@-dOPGKLRTLnyx(m& z#g~OOzEZyDvllOgW>5$jj5%?k(5XE{IeHge^yhG$3iDVhl7K|Qg|n;0SAYm0|y8H2NfCkOZP5P z3-E&G{7&Bu4i3Bb`5S(~srVxt+-o=m**99=nFotr{#x2ku+y35Zz|I75YY0xzH%Vs zzpIJ1m#eO1mEKZ8tu-B6JSOs*IVinfT&sL?M@tvYZSs_>u_$69l1;+@p{Qy@jkf!H zNW4?hY6qSm?IZq~j|8RIub~CMBWp#+CAZP$?N7MUsMKNq!w>b*mt8({zIhQf)Rl5k zR;u0kP7_l<^D1Td*lTf!^Ig=cQG==H3?d;fsbBm$&KD9tYsSlWAxW%gz}utwN24P| z_~rlj<&*5EHcAN!(oauRH;F7fp;g{%2-f^Muk-cS-5#wi}z9i%1I<4M!NV2+-i`5JtAadCGBw zaG@_R%5ZBzqHmbBNtc@i1gtYQg&*Scfl{UvfhzBH;!Qi)~} z!;OE3Eu6tV?0Hn=zHF?lWiQeKcCPw96Ht8q{JC@7Kowa8zBPoHhL#qFf1~l)7VOyd z!pg29m8swf?gGv=NyDpo@u&e#rO1uzBu!(_KUc#(%Yvl87w9LTXyP_PW6!tZa#@^m z)CqokeEcm*#3{X0tLI@4Fw1t1)WLBB(S~VNyNYEl%=H{8Q?rKN)h2?j?ej;JCfwP) zB=DAJtEBLS|N99sD(@F0*jjK-Z{NOM3My{w<{NhCLK1`b$9~YXZ-*Cp2!FImPfs`Z z@$u=LGEhaBM|>50*(F;rnFWkQxM;$sOk+>ZjPS&5rDS1YArN@9Mp#&QugGM1zC$2# z38f$jMX#u#1IGr*U(MJ!>*-=b^|)+!`+H4d9l|T%{d1#SF`U8nr&I{bI7W8RE9ulh zezLArXDxDrC9aroDVl1$oyvy5>0S3YVf}ksTU$gB)TA`2g^Z~mMopF9aHJKls)R}% zm$Bmss|b$Z<;7V8Mr_ zt}PktZ!;=`Um|@?N%5qtCTV(kgFTD#Lt96u!*i114wHI4GBXIRi+JK+Ch%geJ4s=zEP5W!d(^R&wQAT&-~y}hQi@qSV3OrpKgGiY*mPt>(-)LEzF)3j z=(4N@66{P&JC6F(;pXP%pmvkv%sW58$*8kNcC3K1M7 z32Ahyz`0;D?}#^N+PBG4Ul(Bl@!CUMQQ4(+@jF&832752Jr7T#dWSzMvf*W()4z6GleXzCzxth%$>BPeCTZE(OZ3dlB@`#hW{XPk&_3x#=%bU$DcP-mhYTW27w`k~F$!f- zQBgPHmim?!$~DXE;~R?Uf$HmmFZM4WIG5~c)VE|*jT3& zsjm{-4XkBIv8;fw*?*nBV=0(yylLHhLNg{$R=qO2E!VF@w=)o= zrTzY0V-M0b>}7Ajz-48wy|N`fp+d%^688?wC*r{xr9p4rbo-@Pwgac*Ro8Y1N0W%U;^vFM zw$~>uE3VCz2nN%xj|S}>)@So15iU0VdT-3lS5q7Gi)s>giO7U2E{~Hna+nG#Ro}h4 z8RHvv%@thX$6TM`XM+_EZq6TE`l77EJZnvulRW?@lAi=77GiZSvjrQ5xc&L_ClEvL z@*K!u@;!TcdXBDq+jCYVWez$sEH0aVue3go4Bgyj3K{;@rgQ zus>a4-bFfm|D)mQo5mh{#pN&>8d@s2@Rs%~oV%)$(klVKs{^O~aT80+O?x~%JQzy- z>8-#0`-!0m1Fs(`*5|-^iMKz$%kH;#E3gHd!q-T3cDcc{tGCzeY+Uvp6||!BuoxWQU^BKh1LxT2Cvl={#>s_yGtU)MBhQcblN7L{W1ETr zcqIhrF-~q0_|REs&wnbW*=?I>9wN?Bog)|wSUc8D(Fx!cHLFxBOqM6SL0>{DrLMdD z{OShQeM&1wt7_EYWNI5s5=zPo z;*@%&FU7~l5B%P+bnGl75ZOWr&xOfL=-0&TE)Br|$Hga3Sq`TzRr`gU9tL;p)eDR>g zz?KJ_PY@*v#+ibm%4XvJQLYE{>ItQR!TKk$|LNGP3sQfH@0DQO`41WJXgXLM3pJ@+ z-WPgs5`nuuYxwv=us>z+T;y>Rj*Z5RN3#8WleSs4i654Nwru-ja-^<9LT|4o;`O<_ zu)Q9(;4yp69vhddAHK!gEVrZhH9CnN&I8`Aq%J^W>EW0_OIMqFuQcPG<1%T^%;3|a z=;tq=D_kf*P^RzZB4K|NzxW(m;#gEQCsPKX)IHSU_#D$m=fKY1VD_#|G@9f#?Z7b~ zw(`9bm;R(3%8iML&}pN{oW$cCM&Wbo<)Am3dfcu&_VoDl*JEmQXTC}jZm#p5P=>QT z^KgGgQ$tHiabU#Abr2LLFI&4mpzL7MkeD6%DBp%n`OEs$zN*%1+p~v;M#yW39<$Bn zg1f=NnhM^X|bqQorE}|Enjl5#eiuk@gjQ3D}B#b^=- z2bSfe_mc?rph0R($cG~e*Stdvs933oBzQ>Mq67A`Ua+-+v)b0lt74=1g z;R20X)~&&Ek;NB>#FtKMs%sUssJuRHSkiwKq)BBqyHlq3aKxHKM0^?z`@K==2b0!U z;Ld5&Z*^Wr#aQp^STy1e#P?b_mlyHe?;SXY8LrpfUmxTv+YMMugOZcpuLi=N#25rB zu}5`YguW3%Sm5hw2VJt^NU$8Be_6=%Q0*wZ`R@e$<%335d5o8$9{8V}G2 z+Tp>S3xOp{G>PY2GE?ts9ue@(k7-6WU2S~@S*=O#YdP7st7VngPu~cnqZrETo1&U@ zK1VtQ-A$iAFrHIBee=N?g>6&AB_Y&X9gI5Ci_v`AD^;AXdWyhHHByrO_!3Wj%*cDr z$ zSSc5C_?ij>3O7^#eF5^J(JGhQsA8s478VtU?Jjr&hK8r#9goFnB&B7gam`hwZJ9el zw^p=axbo34j&FQyf3HGQjl58vza=XTf2LA(`h0v-fQo^Gl3RcC8Zs*H;NPUjFpuo%F*Q@P=rM!Wv}#)#Zg%)o20q$nDa)IHZ3l}Ok)1S%{wt(Tb5?>A!{q8~r!}!eRVpyTGl-MKu1JFVnEO6&loJtWZfPxolLw(G zr+=j5HYN>AA<`)th>4vezo{6m-s-ZJo}5k0c_?-5&lesTY}3;Jau<5B6GXX+hsWqp zHWQq8FbwUE-`80^*Qs+DYo&uI2wN>A+vtrG&Z5>kE@uxqwtgF30;?*R!@Hn;HuBsb zwO#CZT(#`*-c}|W_9K%iW1cRcFfsuosGB4cBmQjXhqiNdDow`J|L4c(4B9!@7|52~z#x z-^(-?^$gbzi*>NmsZaa!5~;7-We2e^K4qMc-visu&5IyE>b`P-jFp z1F|31@nm#4_+`Q*E0&+3d9$9H-1n-T77NCjHp}7{1Y`Wf2It#u1O^`kE<9y!TbaO> zYJrYAN2NnrioYeqqLu=F=PN_8F{%7Kij{0@>!*V#Cnb35@)||y4DEN(U;YyV+(mal z5V_t}dT%tSmI~}{K0IBKCmpvi|Dg zP7waLa6;D#DJew1KNz#dCQ|8*2(j263d3@Da|QM%3K>Gk0(r^u zrL1e3Ws;s>G-8}iP6j3*a60TyymSyc75~$RZOBj|(9)$?2`^aV%Xy+NPYX!0N2?Cz zjZPidQ!4(2*o}N6`CXbFW|FJ3oM1-A-A$BpSPS^C&2&(6%HeX?T3fQKe<|LWL7hJg zS%6|_vv7ns;UyvQULue>PJU8Gt}6HVCDDdAMkX=qQ2n9tL%%cC;Tm|kb;4ml?@=$4 zF%P(Omb0wJ9x9d8w&!ukp^l+e%zvlT;{R~3NT?dPo|{j4)RSRZJ>DgarX6b%Xvs}= zbSE%riAqgIiq)1zn^#&h$f_<@S9*JiA~0yyP}C;Xuf>li`O>kdxRmc7&n1Au6`%iR zddN3xI^DKZW<^@=nMxei@Iqto;=m0iApZ0M$Z06l!dLb*n+2%rwL z!KCSZZ9!tRM6pI|E{`YHioUdnyZ7f4s{}e_3(1H*il5@jXtep}k(#cD=T}-CtghRs z=%x#9Lqpr+ayBoeWA?plY6-;z>{Dto0za9X!1PBF2;%^x-=BFFSl;CrT=e znDVxK7pFtOj%3XphNPwkpDKX}Ge!&Q#O$$5rF;oo{X%Z)hiC2^d71}M6Tg4>%-54P z8StWlCjZnngBZfL9UWi@=k0yM&oR!tq!n ziQZ4p1r!PIZky2ObY~o)3w=1t@WHg1ifcM~r$fB;f$1lERwS250ZN1h+d_MSE~KJs z8Z6p^-CG1Qh>#y+lnB>wqL1J5R~&P(UJYjsU9D(6xj$Yi{Bu=nGy2wXk1x%H{hPia zovBM0?xh8^zu{mI`WxjuJ74<)&$^?+cWn*Vc94@S%1#36Oy{pv(q7$T;WO`LfsB}Ik&;PJ&{q)_eY5~(C z`>JuD%PgIsUjj=43xlyc=DJ%9XTI^pwJTG}ryQKHY3`H8QS&h!SW6?$35*xhd&|$; zCl>a!-QRm&wi*XtO-=Pwd-LlYRdA)&(HUz0w0+wz!WG$*3#k@sTryd*lKG^Kh$=`< zqUhqH$k_(zRI0Z0eyLh+_};_^FBE_N9N5}hh9J=?NW2|%fS=;-w5kDP&QxEzEXszG z%9o(B%0wjZa0U`IiUex;+HTIA@kKTBcz5sWaffmy;=VIWHI3)S7&gdU&a(cvKy_kA zWuf7FVl%?1_bSy@^?1w(JRd#NSS3~%yHPBJS?~+Pogd+Vg_DlIr2x1#%C_%L)^SGk zhK%mh2RU&(XG-&)I}z*orc;AgZ{34O8#UK0^*;2h!eT?^Q@RpC&c;sO4=hbj^u<@V zy<_g;QW(7k^>6r7M{_Q#Nm3u$4d>wwUC zd!MV6cR{p=syw1GvK6`auqtFUB9*b{+NWBAs?_1;=j*0p#9yM05(ii8k8d0dR}=0b zFQvA1@XJ5F0oL(m`|GPH*RZ-~Z>pfd+bBDzeBfrnT%Rt{K~Gr#o&3+5vLTp4kl!}h zm2OJrDMX&pYdf5MS!3%`_2KNOlDyJkCiU7a2rx&^YtZIEqCcDf;c=0@!x|b$R=B75 zM4QUZw7C(?_1&C9yZUz1OTXE|Gt^<92?u~*%w(LB2st9ag+nMbdkkSY8Rk< zgKv!%y!~a@Jzb2SmI6QU9SHvpr{p+5^`V!Kd)Z!t&43kQez-E2^>qJq&hHHhGAn`P zDFbl@K}KU0AnZH_OQ}nL{-Ufn>Kk3DLwBOAVx9l{ZaR5MwXIK zVZ~r7`&StEaTvzU^iL;R1UZK|ET#v+1D&7zID;?DosSV<77dpB1Wu7i2x|Kzu!M?p z(Hp0MuwImmI5xjpjMr4<7gXY+1`a=hhLVNc@XMw9rrhXEkDxt~KKpPtLA{P5yR~7Z136huJ?+MXG$d_Hrh<209Nq+4GNbR{PJCIE_rRKN91~Po z>B?SY^9i72Ut1>)SbstD-5xtiI;y|yq)P((;CW6)XV+Um>MVGBe-@=`qpYDQnwSV3 zs~9zlh^3VO;L0)=KLjU5id;g`!V`Fgxl|mfhEz?1bJY4b$jWTfC2vDY_(wmbpXt8M ztZBchuM@3*H7O;@=5cmiM}?1+k1?Tk7puM5(Y1%6lPM|FCQfv#k`%l+zL{U|;rOT> zFi|=Nwog5KuH=d?CK`+e5jkRXNxrOTyqFr_4K?(%Rc>7tU4h`?ZkNz?HICqaH%n{$ zyev&u0k?TJf{M)j4f})Eeu6V4(=5<|FAo$(Gv;ukpxcNVW^tx-ZHgml2d2-=pl0(u zafgRMq|wJiYUKEiv~!O3wm0^;(vu_IpZu{825A9@fpWD)fvxUxibls!l$f><=NN#T z$hC)_IR7I*hTuL=F*-WxOI)5&Di4s6Hm!{B?=@_N8$K@j!CDZqZ{{U`i3t<6Kt2_S zuFTMyI}it@LM<0xbKs{Oig;vv9(y|KM6Z$z`$^&PvDp4oCzLB-XLqXAhIPRU-oNE1 z)fa;SspQch**z_m_G)j|g#eC+eT=4#co@$c`_0<&H`LuMvL?_caW4AX#N2L=i6V`7Y~m<5dD|=0{*T>$V&~2b z7X7NZO3P2wW%5y54#$*-CI3JgUr-vj9;C-Go*#2QShI3;yn+z*97~owdj2e7Mg_qhypRgg6~}Tz z!%~li&3CgKu$mQIklz+wSblWvB%@*#*XvuG*#_=Oym$R*eT)s*e*`RJl5G^p*4(}U z)XviO`K2J{_nhe#s=qip#CR0zN{4^>CAfu?e*mihSWQyq7h1N5B5*k&2+Bx4>}$~; zDmXp(ZohCXVo5;o0(+!sb$;9c=A(B1YY2If>1kO`_yaw-o``+D*?0V*Vinu`%Q8T`M-k#eqlFn;A5`vpz$m-J2$&zOC0v|kwwgB|d5UYafftH{0 z@^6V;hDZeg5#MeT9wIi0#zp zn<&lqn*Qh@5%-Th7o_Ee9Wir3zQK6wl~#X?Yr5IhqL5P(67USQwWpR>oyoD)w9A4J ztB1GGD*)~WPFS&|ksMoIMMq~^-)pgCq=K)c2Hb{EIz2WUyJI#X^7hk|zA8L%5%yX` zMNW>Zt1_Me(7n;vQyZ^i(dggR3sRBH0;kU3=RrYXfXmLcs9JhctQK|0YtbLGlbD!D zfSlmhz9bvjThk9Y%#@1q4KmJIHa?xY2-BhFXzpfOfdooW-iy4yT8-7SE8nUN!SWL@ zv-ryvN+{LXq}Bfe`-97p;_Xj|FnpR1&3O~=Xku0ZWaUl##2-1u>>j3W(CTeSsp_x7 zg(wIZRbt+~dnY7@yr&k$!p;uzn|ysnzB1AE`s{F^k(&;>coH5t+x2pII3S>{cAEPB zdOD6m5L8jO4=0)cTP0CP?{79-Pm+!+1e9ifY7Pc|j9|Z+j zZWpi5x;i@mUL0FZv1A*o_g6Z+fKzu(O0!R^0xY&bd}Ra_e# zwtBa-^8gq;ro~*kco07}YGU``r%UKBMA$SHf7F9^fmR{(FlFBoZ7fEi8lUDl+gb31 zIq98mYFIs5^@joyl&XRC-{>C3`KxJ#bB{M~Hf|6nQ@$f7be1ID*#r6mR~}wo%Y|Uv zH4*?<7E*y>yd8Jy`z2`&yXpumw5?QEv}{^DqR*>TdZFs;>q`uU;NZ|mvdA8a*x}wH ztc-P~drwhw=%bFw0!%xV7Jy!d9XrzEyDb<7VcSnoo1u^6 z_c`0}TwPrqh!5J^zVwY2;)#0T?d7UfQc`lu4!D{d|4PIbCS(sRLOu~Nh{3MGLR$$3 z@D@O>tz_g?mNhE?Pr~0#IWw5ts)zpS)KL^C#KTKC2NX$^n6};0QC9MRzRSZ*f0~Lx zH9K?DS*R9ZCE<7gT@?9V%ZR|UmI9#8L{?onf{*{cb}g9n>T<)5q_v(d*GI~$&_ktu z0MuXV@~YyOS{%-ywqRX2Dxs_qK|tj52z1X3=Cjp!mH|AG3r4lIw1^xu4K}yolgM^R zPV!?=_mw=a9-n^7CG}r`d0w;zTlwVro$RX3Opz#OiwSdxiM16DHuu5VpWx7p0+gu} zoN%4>=n}#Br*PagK48{sm;iMeqzdL^W~HH_8RQ$rtni2c=xK&YkMK{nVD1R>Nq6B? zodM&K&Gx;$z09sLNq`u%2fC#}MJU=;^=vkh31LeeOeP>8_;xyL5uY5{0=eS?q+`F% z&d#3rF=|+^1iMo}4HVqFEyf1qB7Sg|<&) zwdFzKEtM0=>FJ~p`r|IhGcsdJ_+sBCzIHj1A2m_)mLm9&wTo zf;p5js_1jQw8q4TKWl2KG;jqkx9KlGx?`aO zd{kV@=Td;_6!3z)fM_fZu>LBjYJdQWSDs^=$CUZf+0)Y#`6C)_G`R>h>+{^rvYxi&Tcs zZvFK+Qdwn~lb@G#t7sZHU;Cv=B7qENfn9OW4yG*WPTtPWPQ}Wqu(2a28aJ=jE^3$OMc(hTNUP_nWJ$WXu_P8-lG@bHrY_O>YNbekdcz^!6`?*1m)cpnl!e@*y9$r~U z&+_BP`paAY$2duXQOKbN;N^n;Y@aU%uVeFYd}Odw`pzFIab zk^VoK&~&UDd7R{mm2f@OG#2?7I6Lo;TA{LU-(J;$?$h3Em{c`_X#t-Fs6ILg2?>SW zwnx~-I%28kC=;*Po00zIYlqT#x21X|2&l;#*GkoNU+?AT+8*?T7V0CjrWcjk*3`%t z_iz`!PfsjP+SBdbG)fxX7UhfbZ_wB)0Q69qKyJ1*QxFh8@C`A>rP-)ah&(P9m?1YH zXmS=8Bcuk?J-1@(c&uB8sUtlZVGBNGB$cJ~vBC9uE!$4nlsUL$=D2+5*@@Y9;4VT1 z1OVb+)olB*W{xs|YStO>QNt!4+Vm)%$6LS+m3+26<5PR4&hm2sPaNOp2 z4;H^J#p?G0uC!jdSq!}KZx3Q^-jsujIp&KBiz3-_xZ^1v-Ok@|T$noaUs`I8X!NYa zwu54IZ&yf==bm|OyO@nSqF){4<<}?mK|l)cZIwPiA?^oL8Ru0o>25wSw<8RX;m8*~ z3(rdg1Oo&>)|oP}-Yhxkf#w4Fj2RkZ?(E|g6(2?+cXGhuea+U^G%+Q<8pQdjdAWPx zSjKpG?ipHh4!op+Ok*nV^#yDj^@uOGDW*4ie&@t0K-I*Kp!Yz2=q_C_9R6f%&s=<# z6Cg=ff>?&(hEr8n$QA$VwQ8x4aU^_Z#%u^Xy$2b`OMHM!0!UE=YL;W?G!}916X#$> zy9~w1BXNay3e+6br(pv1TV|+=Famu)_y!@ zs66Bf=3q~}QSKZBpl{Pa-gx+mc|2mu-+Mhqm<3G*=eTc+F1pmdgtrQw{eck98o0^N znBUYZ51ugH^%be@Rcwr9sxp_ZvbCvtIjtOK**jm7&Hd$ERIr6I1U>H|`EI``K-kfT zBhk?ny^z*o36M9E`k-iNz`zjRvXKiY9%0!)Y}NtP$SJm9(vZP*e}cW1Fq=OBfJph- z`7v4zugS4{Ph6hz7>XPyh~85Fi9P&ehQ8WSvM;PRUx8~K(HSdzgT&j4zO9MO;B8ND zs`RKVQ&|M;ekkbWL2`!q`xVxN-e5}=l6$@zKDNvkyh|wOVm8b83xjz-&;uoK4FmXl9bX7BvOGgtxT z#OnoTGp3(EncGk1pE$ZxR@KF79Jzfq zXaHjFskeZWn;{{Q~UL52oUDnOs)Sv1G9Nq_)a#A*H zTe9o8+W?`TUnizzDwg#L)W3h1Z&@}i<=XDxCW~_8f1jY{QJ>~~6STgPKwtgwmC?*A z%1-pkAhgneCuhDE-uHpMR1qd^XeNdjsUD%VEKPU9QP`2rD6&~=YkgA^sJvz$8Pm>) zFyF&p^KL4>|tKVouHJh9KAB|*r708Wxbl(-Uap*0_ zv#-_;s8ivdgg21$$yXgXmIjtxCGzL55=`}dZ%&huS^?1dx4O##%egA(;%bEdpo&d+ z9Tcx}G=gE+A--^V^IxG`sq3Y}wMX|@@ft(6NrBD>j*Ksg3WxJqVH+=fF(p#_lFAg` zRpw;bYp#2?rXu!cscioMWa9o4d@vjR=}u|mR9tHsHnvRmeH~4$rksjbaqUTkctmK3 zIjDC61mDe7ZHMEHXYtMyjNr=Lmp_v>*=?^%)up!;7L59VKv?v;><_AdP0u90~{S2 z7+yJ8I=R^N-+^0+D+2}4cSD|<^JY3(SxpdBmdsq1OunOEYp%N)qM`8-16zxt8UN4H z7kqr0e0!tmX#w+o<_^X1ch`o25l*`}8-UK}i8$^DaD4%CE_Faj=N8foB=C0Ntt}vd zM**%MQ4<~m^(bkVzhVfiC}Va-@=YMR8c1mB{F2iGL{}8VEv`xrt0fE)uX?aLLFOfsQdrN}t z0f;VB?;%`(GtQ@2?F*CRsx&s0fVK+nj22PT71nP?lwAKUaFWcvhsyZh|CR?fVGPV~ zKOGN53YLmXKqlNNpnMKo#OP!}2lFin*QQy$82UlV(EE>Ah#lAbL8j*j9IZb>RObPmDfnz*<+O6)&Lnib%P zxBC)or?EKpXy2kRIAB)ca0fPpSc~7Cm zcQ)FyH@cJdSjY@~BcD3^Cj?qqOG8QJNdOZ$ejCU%-y7MyzqcvOp9I|gxi&|Ge(qOn zrAPA4wRjGzR!$iCh-Ejj4er4ufeZBkU9KYrP+Bwjaab_tRC=10&G3TKw}w3f|8^1iE-doMn@fK0Tv?pB0zxjh(8C= z`*6B{e&SR1jQp>CGeEJ-_&1FMazTwq@#ykTg>MWE=r}l|8j2o$K|YyP*+G ztX|qyECnj|R3_CyIAy8q=9hv>JAxN9EmwP^*QOkFfbxi2vNfE@Nbcf1mN>1vc)(v;UYjMW~>>(~VOmt5kF;1`&eI&xJsLxtR+cV#wTIK`{! z^AQI@arI9hI zl>2kC&2}TtZymbD`igJ7f~AnNfdPZ$w2iH#%zfW`=i4^*(u zZVunm!DJwK^?Nh_V`E<*y>+88tHtimt6KL8rU(r9Kq!wtrqat7x42 zc7iQ+&Hjm`=5feO_6S#q;8D4JvHhZ&ryLpgK20LjbFqc@UKOYMtWK_*{fKSt)Z3M9 zknDRB_*pUBVpJ&^*1|A$0SL1OtdBeUhdLh;+nb@y4iB77wr7~WSCTlvgi4ZDSCWBB zksR$!bGQ2w=-O~uhPE0O88cM-g?6$i8PnXu`|Wlq-HOlfYGQ&;tdYh?a@~5#;~3~J zue(rX=Tm564^1}gp7vn2S^{+{E9)5!O0lG$gHYIlttxH7g3p7v0RhN>AncxM$(JKK zr2_x=P4Bvq{~@Se<#bfJHDJQv=^jS;BfmWC0_90Lr`uWp*BHL>^8B|%TY^&T)B=CC z`6#jjCa@r{{{wOTqd8*4Ax%q7lk!R=maYeNN!}f>@CjJY_kPpZ9I5D((>L}o2Vha2 zY`|7TUjfNIuLE=>4L}?VbBxsaUKQH*BTkfeKHha;8~gHXK&x^B^zaFF z#}>SWIl;$@KJ-hPu%2Ac6v;AvrLo2k z5ZyNR6@KJwi=sc@PB`Brj-iwc=}Us-ag?b8UZiGsqR1L39J2z}2eUxyt*0mCJ&7k# z27vSkR?UbiGxHBa4!41PAnD-X;MmSUAV`%XdMO}%Hl^a`XM4IVrPt}k-H+grQ}D>? zI5U&9>ZfFzE1K`$n*qVt@5S15oE*Q1=kv4|f%e>^?=!*?!VDDAZ8I0t0to4RT3TAn z0Ht5K*kr@!6&I1L8K#0lpzO#5NIzl#q!Fj>n&04JL}}yjCZPs!-IFSduWGfZ$+E0` zDx|1YEQeE-o;e(YeOt7=h-4B@I$8tJG#DjF8sdz5zVQ{y6~Y zRq!Thlm({)Il-f5g#~zvZ$Dk(tV@Cm85e)3bG4zBEyBT5r zEyU(TYYueXic#OblK!?Itt~fI&Jy7tgdDO>@bO~y{(7#;BHU}~`;8PQpmKie4>2d< zU39!QmTVY#E)$}_mQR@$(Pri!JM^p)4?JnX9nSh6aOScnRS&yQR>R;+TIXb-5NHH) zSfxDS50tn)yG)@E0GgIXfjz)y2G-akG%K~#AGEKl9NfGMo%VgZf_gM~X;^}*oC-8< zM|~2xVF^HS0?KZ>EAfNR@H01%(mKIAr5E1%0i`zxRa4QxABEjSveuI{CW4>3-si?b z4>`()TSDfp>l~oj>!;qI1bd5ct(k!$%L)n~8=5x`aK-HP|^V%P@n z_JK0o+MeFt_`nLC$d<~j5B)KuWAya&6G#sTQES=p>ra_dSPOncT>K zLJenKRCz@*#<~_C^{2PHqyVtl5nPCq29!Gvsm*u@04D6kQc%cT&~u`i%yr8*pGKZ0 zvF?>(d5IaAES>oX;Oj0CfHUs|3OJLV!Fx-v)myVaAx_djlN+9`bs-MG70Ci@rLxjs z0D$)3QlLs0JHq^Zo$eEkV##0#47lu@&NO5_o1VcwTgBy{U%!57svxt33GoAK@uGX7 z*^M>$H%F>H(^tT$xB|xet&VMPn|k~4;; zb6dQ1x3%46%Ng~Go1W)?E^!JqDaRd-!P`R!6UqSilg$)MtVWQZ3vhZnY{5KNd(T9P z!C-AaOTiX^r9Xp6IC+&N+!;bHA7odgXJ3WfH%z+$$tZB)TXv9NK zs3VMp`jbo?z&GFkW1JV|OAepd_5Z~;Z1iA_(}B0wLWWT^AuPnD-NPB24ji%tppZu( z>y4i-a=-d;BU{;OWfGe#FEwzgeCc=-XR-mF0N`5mrBWt#hpIuM>+ca{HLby0hc~VF zAAr4B5&L%aPn}g7+*u zTqywr3m z?mOTO?Bsrn3(^%NL$2<%?SGawbe2v9@_!r3%2jJ*$S;nHQnDl@zEbwY4X-9ZRd~nX zHhLUS`tl>j*P*Ph=Yj2ar3=m1nT#@9XG6l<65Cg2Hin9GS$_rimQfHwTouOolv!V8 z>DhuY00s>k!HbcR5eEQ)m6xKxeO zy@K6YEa14}^H19`JSuadz#7(r)<|Fh<>)Bh5zGH3-TP}-Vh}+lF z(9j@@D7qU@(#R2sJAWsX&LIdK5Y~q)7tG$Bz4KdlkhHQ}I^52;lF9Lx)C;I)bKMVk zW--p+os>nztyPXi__t(RW+c)TFO6wh!}l>a_r7dcr(|X>^mAcys^KdaumL^1eG%Ht zN8QI&pyg|1WCU=RcTZ;r77I--9^#bo#5T2Ci31VrnX^O5emA8HU8n;tZ=1#%3$x

        m|r814u17Mfdq z1!gK_N=!y_r?>f|C)tssTM^!@zl6LPf5ZrV|@a>ByTys6Z+xq5BqNLp1B%ttLt znb)8>M@U9z2DS?7<>E=wU|m~Z*X%{o7=5?g%g-*d)2BF*KXmI4Om&Yq(AQZRu#dg- zQAtxR^;2!n6iW}ZPTf|E4<9sCwGqr8Zceilm6RsJaBYKg)VN2{^@}{7r3ws0L`1-{ z8&eFBQgK8XFx*jA+K#OR|KmT zjp5%)wxpvj7?i<30FL(eXIU|gKay~&Ve%7&nfsUjsii;bbxZ~RL{01u@fQcK=!f}q z1rI1(l&GlGTe#q(dp3Jr|a!; z>)r)PC1Y9%Vg_l2KKkD7d%o0t9}BeP2V6=;VBj+Y(5S5xn5}0a zkN4;?tIPu~N7{-7^N`0txl16Hh+b&r7Rn`jxnpZl2gVTdO0cqhU|oSWNlh7x_}nP4 z<-8z?Af%{QvxGBMmmIihP;lIz#DJhdtW}ec+Jy-P zloX^(M5IgU7Nj=4X{1ZKOBy7k5jG)>uu)pNyQCYGO-Of3*IE4jPmSj}?|IJ{=fn1k zgFDte*Np4B=3HN1(d~O91pc)=|Jr+>&snGnWpG$PfUA0b6<&F@-_jx_FF#N=nhy_( z%a0kZXXp7$gN9V{*!D zkcoxjynxBiJ0_JW)=Fxpwuil`woFlyVRXmWq5WI(?ofs? z9)nKRvegPc5#ih7m-z0GLWyw|Stxq>K`>s%K_<6C;SyF2>IfI><@wF6bU<@!Q=X-- zklk$U>F1q=@*-c5ZJ_KtBm*&GvD$Wl1Y33ztiVia-UX)v`^fbEnE`Soid`&p2scS{ zgsV7wj8-EhFCEM&scW_UTp)u3bRwmcJ+i70(#5WgGj&tHbqM4_=}+E4HrudpA`1`Y}BoWiE^W4wLS0cwPr9r_0W7R_k$`2jgZ4 z*m9q}mjtY-2wV;AAl4Q^spzg>tD%nDUk=TMy)g{5MQlF7R2%1--n_rmt1{cGi$?@6 zJt86^ni9?6`WBK-{pBTeYE0Sau~Y;EuZ7P!rfO$;JBkpJ#l9Nl&yKt^T5h#oG2iTxH@my?ipB0TddS z2ZN|WY%!G1e3aXaGAsUzZw$s;_7PcFI=1Yo-d)g2oP2nolUODA^5sizVPPLX{?I~8 zou{J_)7%Pz@3pnHeaRe z#8I*dup?YBxa5km=ZiJs)c;taAo_lCfGvV*k#7hQAZFMEI~qL#t6aH}BVEL$AZQQF z;xUILR8%mGkyoo`41RGPNne^U{h$RHH7w|zvn=8JaDH`9(#g+kG4DdWLI zO2>drtYMyKIZqcPgKG7dX3R$<(>3q-8_*)4U%w(_ij!jm5ev(ef}R`9XYkFv5>2g{ z_bhxMBcjnK4!K~>ZX&~+i&przJk#<$EG1=z54ib9G|+&UN9xoD4s5oy+Mj2+2GwZZ z3S_^aI0f%W~aDqWmVc{D&&wp176D9-g%WG&K>*9$fb>01?-sce% zVrU;NC|zvjeEH_RThOqdEwL}MKDoEWPV~d^0%|9Bv&*k{cGG>r;$bfkio5eofB9u3 z$p_+-RIZ1HJ!=XqDHkGF?yGTH#R7AoSn#t0<{@U0;;|>tKCWj97-a-9XBXb?Fn9VM z%@;|~y~k)D^NCX`DPIFWR!coTeOEOtXq)?zgS1n3fum=rfvGc`zNL z*DM!60^6STx12{}7ZN#d{LwdF#(( z?NM%Ve61X=9UK6w<+_pZ+(g zbOEf!HBTh0nDs`4?MyZ0q3pUw|BnM15o!gW;KiB+*#@d6EwD;oxXoUf+^#>tqS4~C z$3ZP^2zXhHa5B_ndtLr2U%eFBwxO>1RIBhAkoaJirbCd&0uW$&Q+@aj02zuON@*o> z&nzF>RI+S;09LsYTxqF2m6-q~=*SWLz529Z8w|s!MwtdO5g#HCrg5mXRs&?X!k0Ka2b+M6TiSA``dbCbIUBZN`1G zYw3dec+tm~w|3K)iOpAeT*Xhaj{klf!R4#>& zx)YES4@a}6{%Ul3Na-0Y)rdp=Yk0P1!FU)K5f&Da159Fr)AZM)G8_G}v>9x&kuoJw zq)UBAI_5PW#l0z3F6-%x?ft8KKDQ1cR!cCn!mD|qgrG1Y7UuLK7HtB3%oY)S9^bzB zfC0fZNS_N6d{i9ld8RuP3!Q)L0lewX+10kXOqL3mFE)r|4$Age*sGWkuagjjquzi9 zyLM~#$1BqKOAOE`oc-}|@j7{uKfe$MdjK*hH z8R%tFhlEMocGE%gcDZeb)tVnyl$WpIW)F}4O^Ym6^QGI2+g{sMX`X71o8A#FFK=`_>?yHx<&QtPx2NlSxo;{mA!i=O z#@{EikkQX}^0XV`L#uFi7o;2Zg!}H$r*$2{NEPl+QBex0&;TF_?_sh^AFn&Ox`}}> zHu;0<8ANp`y;4Twru_6j88FzHSx6h(XIIX&_(lC7_>K3pXj(`79Wa#qU2jL1UVnDQ zm@n`!hCZ=9(3{7vA+4cDRNO|FBD3j=OgiH6`N{sv0H`+G@9^kd7%8X=Yy zByggrI8u3(Lr}=@!|o6is3T!Slmf^j1;=!iI}=}A<(kc9DiBB(h+=7r3CxX&8qxlB zUtg$kl}Z20$GFsA?-Hh;VSPOBe7i)T)JzJNO|?m*m>{~ViyjZ_fg&ln*i}Xo`!)Kc zu35_3!GX&H#xr3&3>Tl(1kKZWim69{_jqUrur(%{P8P;hEJU@RUx70~TNN=Jojqpu z<1s?F1c1~S*#v}Dw3@lozQ7WwIgjlOmn#T((TFlV`Nv1Nqo;8hqPG_<`z=E=@NCMI ztqJ?i592B6Zh=`KQs{Ffhbgd7v zM|M=LL|21z%NA*G5d-uj30FOH^R;%7FX6s&#b$!;dss4zen3wxXV>Fe_DQKoN~P^H z^__Ruph@l08mEnRO`K$A^VxWqI358xrr4WXqcp?VttwxLht;I*Cun%!wZu9_N7+iz z`Nn8Geqm7O)&od5cpa#&%h(5l;fvS~^fTvvVaxT|7B@Q=W5S1VRueDm_cI8h2`NNe zpyjRu**;$RD(fru6o+A9PbquR;TS%_0#!OE+tn)2?^FKCZAupr7Z$*fm@jBMNfO8is6iD`37IB{z;!e{Apz)ul1ovQfP(e^t`q zkzL@6D;G<#K8~hnckC1SkzC`)P8Abs#ch@TSEsoC#iGkNGK1~ctU?9COafaZvBT>L%s3eY#j+gVUWYxAxc;b;y#f9v&HQaP`Qf|#%kUeqgDd@HOiflx$ z-1nbp=|JAx(m2)Fi|leAJ_@VcosG9&8~U1i&HxXZw#_OL=N zK*AJua3X}WPKn{eh{G&G##C#dtM)VLF8$4woljU)gkXMY^xRb${h3#F(L326T&>g2 z=Fplqv}9bCZ#YO+mfiE99xEKv3v`@9oY_}(;pg4x>fuyn;V8fdFZVU<8{J-w^T)Zz zlDTd2ys&*GWu z%g;SbOFh$U%C&Z?WU&RX%XY`KZy-^)-FDMmeFM1&4GavVZ_i;r3y#?Y7@}hlEZ8z7 z2PL4@lX11h2I1SjTg#MFd;VZg-Z!>%ePHDy?<+_h-)PRd%xss`nqeKA zH+8iboMU3VNmZO9_1v8kvw-DK!!%4x0WTSO~O|HR;bK`z~hb(ZiF|1y* z;MKMt2{_0P+G30?R7T2+y3aMC2oo;rF^D!>tr3G|Gss?p1{ zg)m5!?bS`Wu5;1zx_?KmobJ(CHHYsBP!FzSH}Jj>%pr{LL6S7OTU!~=Z8H{FkDXde z8RC}VVyym1_oUxz7Uzv~n3;ABz(w+4R>d%gJ!tS)0vsD;F1k?YOWp@f5T3L_HI;c1 zs0u>;KI*<4BXuH_3M=MkqjvLWeF_lPzlljRuA)NwmJYnQe}g+^{-yR!N6=Uhi~WNZ z=EACA(0uVvTs@9NFD68(7r<0%;KTP3{a9&G>-7tB5o1C%1oNd%E~}S z&y>w-pphU^OH7HVHXz}5%B=x|MM3^xa9@h3yZwW`f(e80tC}XPgLIH;&~&y&xDLj` z#6pA`FniaG z0k_0*CjY)()iu|isy&#=&-uXJ@M?E|Sy7Ml^f>@r0rH(bvLRz7c?z&jl&nxQZANI{ zGmd+(H+%=&)7FcT0}w3+^e_OekVdBv-Ho)Ex{DeW9bD85Zzkphq_rRWURWuj&&V>)!`u7u^^GUNBxV54ZO?FcQiE=7nk7ra5Vz>gax8nuMo)|acU3f zH53ol{uxTp@sg5};k$*+U&x23zJsNur9ELY`%IQme$%#F%T@g99w}GiB6`d0x$_1mro6+rrRd>VaV#A+&5hZf*C3qeI@RI@x*Y4Ht|oQ2Oo z*^C<4W~c+W!d-u25DUZ;R;kYV6R~ zdH716Wwbj5z3b6RZ|W?dj4p0&zrkVp;!3!AOmHZB_4BF}4XS%CXw?vqBgO6HG~XW4 zIQbt|+p>!wT!}HqxiV4hXt+`i%MgcY5hjGa_jCaUC&*lYIDY}W09U!~6&}Y+Iy$o- z%Y3B}MqgDZH4@{M-?PDsH-MfEeR@#&*CTI=p=J(iZa8T@0VIXb;H?0&R!uw}kw*Zq* z!vG+ZFGltQM+R`KdHqI`u>XL$Ko6w=Fm(PcH~G~rAj1I2)gM*>80#b^Fa^ng;honr zyR~0G+aj6?1;bMZGP!rlc*inL&#`kXr|LfL1F2ct)boCV_^|ONf?x6z9v8+)ZIzCkY+;e`;*bzmW3Y~lLjn?J&A+M z{@+07QEJomQNQ}D?dH4NtJLn!PE!n;CG3t`Ccu40AUNwl->z_STH4MeVehbA>!lJ1Jc;hrMPxo#xWg=}TcJF5ij>o+x^kWS4}!IOEkLywIRn)uL(9 zqaqKvc;S!^D#2>QhF=b2r!@V9$$RP`S zDQr#b!uzLB57x-i)g&8cX#?{?N4!sstce=bk9RFH*PbA&dgKX_}uy2gSc@ z0qkx;9>O_^FHj`Yr6VZRle}Dr>=Q>u zV4jZMpb!+ccZ6zJSs)j-Xo>X?B{}>);T^4YO+9*49v2Vw1PmRSK0DXKt_M>Na9D7d zgg*d(b?*tyH@F4YX*~oTgf)>y_IqaoU%n^+q=D42!@_uZseiV6N+?}To#^qoTZ`d$ z#UeJlU^uY?YX{S!Ox8wY>5b92l!jlKzaFAy^k$6addrWRPK2|JBB!tsjGiYH&m|x; zl64i#hzPJnVER)5L|%sRW9tJ%_4vI<g7I@=~K-QGIpkPuloJpQBcj1x;adveJo8l|;m-pB`NwTLQ>WI@%E< z1EAULve54#K%oB<$KNfjyI*R76AH0!8K_$4y$$j{i|moLMqI@LF2c*)_m_rF-ZmGQ z8pHL{PWSuFPKYtJu1=C%8eBN0W4QC@vb?GHO9r~5$Tg>d3Mm1q0E6a$vF*!l^2CCm zPB+okAa1qRp4tQQvk9Q2xw*d`nt>~`@FlLv(148wyMF5dxs+;?xh)bXI2ngU`xq|1 zQO8*7RKA+U5gTWl$Rq6c;9aH@@mW^i;>@ zER@C~>O71QsX6HEi}~flm5I># zyHemW0hutD0Flbvn{E%u`De2<)q_*$T9-QlHmG$p_X9N6uIMQ)HuOsZMK~v)OZ5;FYAg{fO zmQM9#QV3or2JX#v6^eM6x{9U0w&0Z0j~A8HHkqD-+6gtsJ=PlQtM~>(lHB{2h)mi5 z<0AHox}rDazK9QexZcM+a4?EYRPTHGJDv)wMQ=B|Ir$p7P>waFnAlh~I(Kb;T1GQL zadJuGhacN+*;}rUhAQ-PC4&H;E32Szg7)!EDeM(@qwtVa&2qSuPpIx7oiO@g$eAnz zl@8B;c-|}BlUGyM_+;3+RfS_w;^$zfn`^d|Zm=uylMsv>`JSr|c&z(VUrxdjTim;S zNbM#z#@o|GUzK~{^+7_1=2f+$-_;u~`R|I2Pda|Nef&CG^(TW{crJD!75z)8mQMBl6`zvc-Tsv=WS))}a< zzU|M>6b>e)#X_5~AMEHiS6+g>dVeOhXYo5Cnwz}*RN1t7sp!@i8Mx4AAR)Lfce&3Z zqhwkVK3k>?BiA711J=c)W_eU`?Znd^xdyQPbR4P>{_*PFFtF2X!HV5)Xuckw0A_4h zY|9=2-Zae1?_-L@RlP%hszW80i_PR-rvCmI5*69wV(X46p>u?gRt;{PvC)uLG9T#c z9pQMCSK`mB`DW0=6z9j{80Hfu8}Ab9HdZjoI1A9TsXHTjtZo2>UHT172^dK~Fml43=RZFqtG& zSC{f-M}<7%<_LPmD>RAmBZnd8Wf(VYoR;lSM%cISu)QRl?4A)L!g&L;dqV!-($w9# zXlX$~K6p7+(=*RIIv*UF2z5DZjh7#f6Orul)6y1a3f;gyo?apRxyMr^m$D&T{swf^tNL-Fl@t<3FiQbV^_f~|p#3Om5N4j@pFS^Bx(D8?U z@H;-k;6%f+d$c?sN)^@WPHV~<>@^>dUHm8DO?Ic1*z4LF;_D+@41ri-{KWP4%NymT z)>5zb{r90#^U>2q<_u4+*!I7fyu%eQoDnEv!Uc}O|NZ4GB#=IF@WSijDn$u{@69PO z@%8y-_(wqo^*3ZMCk&;HHh6uyaSOqEuLNFEP5q#>x6wOVo>(5Bw5|m_p~%byYc!N) zrXh+|S{#?rwr@c?b<0)BinfiQW7P0ZkclK5**Nm2jo!T7Uu>>ER-@xSLYC`4dNXG` z3IGkZ7_ahrdl}=FXL(924&q87=&DU3jsTd8IiZ?T6tk2GVD$z>rmwYU1%JNgydO9C+1uxB-ctpp7j83NZ zQBOKciJ-PoVPmEp=|x)h{9##H-GIG#?^unOge+pkEZaD>@GJ7K0_b2%<`cDA>RmqH5)@r)aX*Wc~9 z$Z*TpHQ< zeOS;FI;9JkVR{X=G65{}(fMNUv<4i1zZ21$=>7KyymNVW>c*kx?u%)Kc|&6tJbj@d9z0E=RI8sX;=Zz?@id+ArySJ)<^r zvLP9o(Pa7iBJNWUp(Rj6J$?FA=!tK+yryW=CsQ*sR%A2?VuND3l?8GM(Jrg_gTukC9$ zz03N5M!a{ag!Y;LsjH#aiv1=ro$$eW-2Ep(k@N^M6uZ%wh!nozVSWhj>Lfu^z_*Uu z2ov5s0ijSwqfjF4$w%q5b4$HScjjsCZSk-4iQq3wtY?BRym&HIi|7<%;a4r|Yio01 z+(Np)a|wdm;;6sj%^7M z8+9Ocq!z{qx44D<%q2H@ovt6YUI4n9#Oknk0iOkZg;jPvE@fBVm?!4C(k%v zR_T=B3GjzGHf~NEA z4cba)aQ+0}y8mJ507r^QlOr4?L)(TS$8i_irqN$C;_tVU-zqI3Jz*Q zkB^UU3NgA@yDbiu`#A`fM5v4e98!zTAf2~ti&tfw61Ad}i^~pBn|EZQbr5K_CVtGe zY+4!{A^Sc~I>J)sBQW`hKe$Kwak2Za$4SJs;sBuk#m3g7OaHGfTk~ozNIc_hYJNW9h>eG;iPTFYcF| z9qf4uFG96vXL=W>6jv+kYKvgdm@^w9QO2+7_?IkOPndVV5|L9YB?Tmnnf-x3B_=Gh z?0QAyCy)x3`r>f2-JW0vU}hmw0kdOuBVJA(!1wAp%C^z+zPKSIY+^N9d}qBYPoxpyTZKk42Y6q~bpVv!Cd-}$&W0imMdGfg0xh0ij=sQS4X5 zTxf8HflvHJLEx)Y0!0}L$y6gFiDbPZ>0yHxOS`Y@csDB&C1_6sDXyy5?@#fRlZ&gs_EdQ_Q71 zIHVZi`bp4kB!2Nv;FKJ9Xf{`Wxt$8+Lx83YLgYh@wF2{d0KKCB{0zNShkPNQN3jG| zUP4kH_tO|`X0yJ>xCXl%e}#n}t3_Zd+^KhcE-)!@F@A{mzSBW9A^^*JB5L=c7e78j zd-m3?cx_i}mYuij%%lzeD7QLs-~O3BQpSS}c}2zM7ip$VbZ{4c3NWsP01HhH8I+ll zZH7PY`q^6=$LGFR6@bBU|5ba&#?t^ek3I=;tlYoYPV00y3wy*AEGW{On{6`37?R6d z*}+@twhEKO>KT4*Oj^aYRxUAugFLG#8fZYMw}29Z8UwU>F3uG1)i_9Wb72MG&^_`t z!vn^2HA}n0|E^JcTeHl>ei9EF5C0}7tcidY2Azk>kP~z&Kvq5vI+thU?pr<_h=Zirx&jhf|&0;>O+UUTgl--F1^(*Hegq-%^3X7-l`0s&9-k8PtNM&2*sv!$>; zBJmY)q}AMDZB+pfArebPQ*0LNHBl^ct#me8Zk$Q*{)zaLLAQ;ukx{lL1Ik8oH~r$29Ph9rlnXbl3aGhR{zStOc~9n#SzOzqMm;( zwhBv|b^f^7q-bd0Ycknlf%cu9fx+X|b?2mySrc2DH!B(y42ttW%3c4AOE^~-!?dTf zb0uiH%R(pk|45GP3du5-zWiIc-~~#;K%Oitr8e(LdR2v;hPNUNK_q%QI`sqPMNyFa z9kFMz$9>GDJFJ;MxpybP251TJlViN2fzRUW`<;9ST$+yASFnhJ(q{{PeyTA&%MbAb ztbq?+JF;2WKl4NOM!sg_=l}5Ch$P3v#00pFIw_3Lz^*EQdc`|S=xU;J8A$WLfy5K5 zg9FGPCl2!dh~5VTb+mgP!WoDT@oU+y6>git_t*h1C&EE}t^k4beLAQXP=YWf0YU)= z{SEwa!3JMt0sZyFmMhSFo04=t?=RN}FcxkDxR&HUUxgI-tR#RY3%y6Uz2-IkIWUlh zI)Dsi?Y|6$T0K3$Wn9$+TMwB1?uqBgT9Qs37)15jpA-y>cmW@v{rmS1`8~Td3b~iD zqumP?VNjrZ#fj+|XQQQE&H_3`kTneZ4GlSDtVx5H#ajYcDbirc-w6_RZ(ITe!RUYMa#`$KgY@GN$>Rt1{G;Z+ zhvkyb_7Hd}M?XKAF05W?bKR3$oeYMRP^(0|=ie;H^Z4UmDloCeoK|ftP6_KmERjh& zN~jqDPeQf1$Guzm?>WHO&1tV11ZXgIehn3;emNWBN~yLUKEFG=UT)e}i?D#I&jV9H zZ$)n{1=NltBe&K1P`WA{wh#P05T4*<@oJ6_rT+g=CF&o#Bqaw@MWO;FLTfKI&!9Cb zCKHm0c0rkj-nb-y?b(Iot3dmB11uL`Sf}*USS9@WKT{*6I}H&y<%Jv1g5lCCmvY{n zq$Crc6S)dnJr;TY%hr7?TQl?1$@WX23dA|UaY%wW<$@0jhw+P5 zLz#N^&y?Kx-xlNl-!LLDX6APVToMdhbmBE=I91QxF=HU=B4sminf>c^%)boM_T3oB zo&{yuH{oDe&nA$lIJRUUrb^8B1jjdK{g9Ta?%oBT5bT0#7SjV04-juWSj$w5X3==h z5sqmTz_~ReIIR-ou1cCL7pi#gMK(#9KFNy!{GOu|W-e+;Xn1H}av1CNmR@yK3u_ ztUn=dpZ)T?=+<0>){a7gM%W29JgsX6dhZVf!EOT_pe9vUY$<+7lzxBP; zcz5LN3MK3UgJur)PJ?I1Zy`&OM;F|BK$cNmtT*@rv6m~^qqsV@*2Qo=@n^er`=7QA zMn=+N7#THHZy$2`$*rS~_6zmWUe_Fj=7sX;GlS!?dK2CdeJ|;{$|k3p5kR;g-aYd; zB*z8elP){lj4T9!T>Az&b32!5YnOd!eVI~@tv1~?qNUq+MM*G6P+J6h zvlf`KcMH_9QDUe-WX=TlrH2dIq?jjy=9N0i9HJYY%3W}@uuo)4)pp!rCu)&i^+w=~ zYHO;s3zTrzDF!32q{#C)K%FH9>-Ya)LUz+i=Z4c-&yie7GUR&Fer=kPaFx4BT@jzG@G@Ng6M{Q(p6p9V{qa=UfUI z<+7T;Oha6-DQ$48Cv+x>lFW|&&h~{)%6=>~HLfaTU~;1y?GyVK{Xv0WI40)*Vf>q; z;TfCMtVkT%;5#*4fAt9v{L^sd(O$+-3Rb&$dtWnv4$GfqFXR{#cF(TX>nZYxf`u|j z?)55O&Mof&SZ_6L{qqyK6p)}AtnpN@ZRQq~E4S8MJ(O@Yc6DTC5#DmcnBnKcXShmq zXI>j#EQ}E`1^dmZ>w5z;2h(mc5N53)^B8^u4PuxNP;!FsV&oXvk)8Z)z#N!bayXGK zPzAO9ToEnz?V4`9-s!+1@uh4+H_*7ljx6Q%yh`Jf2dBbk4fxJz>FiFe#TT_B@%xk;MdJgIUzZ z2aPY_HcNa%3^biU-JJ-@Pjh$_3i1Ti2%L|l^$Aorp`7o{c?yZy4FP$XuV2A~q{#6T zwoYvZyB?3};bPSRalf##Ipv0CyZIvJUhllkHaCkSEr^P!b`J1EzPsrG|b`Mj1%KK6t4zPOL1);PY!E$pk>buI&9b>KXt zN{y17_cQ71h(g_bflSI5>GsjJ^FOixS&a}_Ia@4{8i0Y0Yp;?zCUhqNZ!zPtH5B)d z+T`x$O-i+mbXIQA$1C>=Ao|T(Vyf%u5wr5EEufqT58cOYD`YlW3wgXf#y#!sFNz(& z*l*b9RFhNZ0mQo~1MCZ(D&f8-I!9M>C4YDq8YPV^e`^?!iQ~}<{Vkn-j6tUX&_(lI zt^T$+aiq%$>!E_ibW!~Z0rsSGC#HfA1A~JN;|+Gs)l|O?N_I0MP#fGi_tP!a3e_VF zZuWCJ>0j0pMQDhC(XQ8&2UrIKphpgY_OVSRdRaaZszI;TPVgvJjJdiK(dJ6UW<)_X6|3^f`(MixAt2 z^2DzJPzbmO?<#xpvl{BR9YI^2vdV6r~HZRNnzaMObQz`#0Ar&ugV=W=3_KmK$@jIcr|Hl#Ni~ zk()6_+lGb@$<%k@5IpZ@Yg+yV)-IKBPTNZYH5_gef(_lmCjiV6YFKNb5a?3%xSOjA zAQdg@-s0mMv!_Hl&Qmg3PaMQ*xKT{0wp@o`>2%%WDk#^K=Rkc(2}nPz4i9w*srzjE z8Mj?ezNDgMR!~0s^+RcXdWwF7vqzt-`5vIjTb(JDx?3XQVh2xE z8Cg?Z+fo%F&}GXw-m}Q3VQYw5BtKBqY)vi9G8YoMz}!$KevEqX_j-guYlwm57V=#$ z2H7B$V~G%h>D-$|{u;y7z(Rw-J7Q7h(RBg(gi>G&yFWideEPQBYr`)DSv5)GbZg{r z+Aefjvn_e=hmq*@$@?y)ywZ<;rT#rquq%YtD(F-|F~-IX!PA}pP77DGfc!AGLAk53 zV*>!xhW0nomR+Gh`%`=RKMx-9y|J^IPgtMw9co^porsoO3HEh2^ts54pYip&a$>U` zNg2QfXIS|iX~t})y2ACM(5{VoU5ta;B<4zjSANK-W&S;+J9Ohm{V->j%Dz-b(KS1%(WueQ) zTY@9z7x;c> zn!Hckh|?~s`gO$iK4(gW&+8GVC~hx2CAz^AI33ee-U4bEJcq0|+`n8OTyh2UBZ5j; zvBcU*wL!t&JONEZl8i_Cshev5A z!URudUP$wIl8n}ss)p)kn=&aw2fEGVw68a9fVOp^a{qT|bko(y4@tQiiHYZ+OQZN9 z6)IIc)D2yV84lEpnEp2R7(fPeqSDzd_rcZ+@V4EPM*G8YCF#=Qz2o^0C_i!kiP&EZ zW?u}Dqk)SGaWMbY(Z2Dvh2@CT>fogiQOx3_@!;O@GZLBGUvAE-Mm7G^1^l1LKY7aF zx#r#Y{&~p|bolT82KrB^!LqZ_71Be~hX9BXnw&YDM=19NR4-47iN=~W?FCM^NUFgOKBuzUf!{RXb)#z8Xhh&_6`@|AW9W=jjpUsJ=w;kYp}X^|*)6;JRG)bGZ}-oGQpz8f@VQ6jBWc51%qPHD^2s(% zf`ND;6Z2PGrNCM~7+7E$G#|tKTzp9y%|C`Ux%=WJItY@WL{S^scf!^Gi0Y zEuI#kK$GKphU$HSB8^P1s4DwzwwPy6C#FH`q6?!%*U*g5jvU|*Z|7XO|60r^x_Y_A z{%z(PKiQhXt!uR4=y$j6Ch1t!LqA?hJX7km?yGE1WF>W*e~2ZxkK$&#(7n|aao%qd zv&2V(mc}1tPPaOK zc9gJIe3*3R`+-#GpuVN|x{_$50lTr0%2x=DZD*CePHzldhvy?N55)yPg7CcG?`r!7 zZ>pShM}F6SYi`PbhedF^b1S_C%}$g!;|gzT_vrl(tM~&;hj+#g9~QO>HQRA6>^k$@ z|D1W*-Y?JV8Ps8E?$-@mSdhBMob$Xp_3NXIxV;X(%A7f1gWn9B>Bc;ny&0NipFIn8 zm8)$Yw%DWQ#+g1&uK7SXY-8i;<@>H?zx8LSLEruFRDoQ(&H`CUK3zP5$CiZSYqBqG zcrQB(R=s?$KNwl@uodMGJvf;;C%$*ZHF~+xs#tHhtpYQq>Y+PNO z;^Uju7JlX%yyKj@gLqDd>8^t|96#;Sy!i#x6Ll%#i_}3q!$BN|%zgHCg%6Zew?sAz z>-)i%mE8-!h8$TI1`U=CvPoLTGR+X>MDN1}%)jC{j^*0n1-!?n5?R*di_l)v-$Og!0G{oGmP0Y_st`- z-&Y97EFPqGCvRO|UVZ^{`c-+e&~lp;E3DK6zTIhhd`tv) z(L7cpF*%5y>JdXpqV9v+7qWfZxrkck_;JpHMwBTz*z8lJ(-=FQ;TgA^%BxU5MI;a% zKN8UTJEy$-i2o0N77Kou?$(F-b07`AtC(uGiOipGaJN5+Bz@idH8|I_FE*O3J1BZ4 zTqQ*3D0*bScetN^lFIRWc>6er_VZ6(;bC$EWo3>o9l-?>RXtTz zRbih?7fLLA|EUWHZR(`Ded~A967I`CUVOl=*#FBIpV0Q$&}RL$*3G7r+f>GN8K;v~ zq{VdTIO4&$N|S_2jFL&&FLr+eEo*fCXw{_;^YNc$R#db4jvIs6eh*WPTKr{iHSkX@ zu3B)?bNANQ*Pqb2iUglAzXEeR`cx=RWEqW4yY}}F*BG|1w%^&dR-N2b+y*t?5TO@R z#COzYtaEzJ_1lz=o`!{(ziklFoi%$qVuqBNsm@E9tgE9VFh=sajijPgrvYDPVtQKB z5?Ar`QQ z%T!U8wM}1r_1|Qn>Wob}@y6!1(ftFotPdqE*GW;Y)zM8|f1vzyb~<-Es~|;KVr-w< zn7Pl1=$4<6KWD(f0j8Y=?2Qzm>ROIdmr^vKbH&=@2;s4tJtw!`WigR|P8M~`xj{zf zymWX@?JtT%2fhZ`@NxG$>%xF9z^pB}F5kA&@yK5AEAzbS<^I;dvS9bC3|Cj_wbmD+ zS5)cm&dDb$Y?UUHxT9MPNk;@q`6Z53B|wnO z4*;aVxd!(nBzFo7?UL=6;Jh6J%-XlTS*Q!R)B0Yv-}M^YmQ}MG$iANn*_#VdWfHhV zJ&zN4tnvKYPoJ~78r) zn|Mm^uN1}knLW7Z8!DUXTgAA*1Q|4;%Z;3O0qFkdAm(`q0<*2RYuAZb|Dc|&%%Gy8 zQugxCD>?}&OtGB`v5$V0jCi|+TWT7RuljB8WtF#0 zvF&dCo`=Z*B|1;@HyyqK%zDKq7ghqeVz~j|i;BE$^=h`k7N8U!zOpwNNCr=CQ!{l- zLxB^6TQAaEq{ULr4BEZHOVIV2mbWbP$@yn$Ti0k=Q%AmiZt}52ta}4RmWOAeXE?5r`2)l-2bp-{5FwQkaYg<2@)1Nwc4qxKl zfO8|}u!NL#7jLZoF70Q6B{^4!^mQ~z zWRG|ZA1_VKOi>6mILNk|g>%UQ^Hq@HBGY>~`)F1hoL-W*T~AlC-AonsRs<}J%DZ=| z$s#_NLs{Ff0ofCUEBik!#Z^85+d{)vRaMnU$(wwNRfvee*VUKV`)YW(B}#T1Tv8g0Xk>nvR_xZDdQm>i^$!{+faI>ApbAM@2vZ`23;%axkojo@M5M2LA@IRg~N* z)&+VTscNQPMsdDYC121)(_1e)@UIfYrrzW7*1#-zAIQeI&DWjdgN(JgF(x3oVHF5B zq>D3yqTh&M&ys|_EkU;98=>t7(P8L&zev9J|0?c0qng^bJr06!l%|4IAx9L%LQ$G@ zm0koq(z}8vgeJX6LKP4J0R;qU0;2RH5NZM_9YRq;50NT0w9rEGR`lL??!DuU@xHys zw+ym(R+($g|8K6n*DP?)YA7ml(zx-qp^tOxF?3ZCy=DJFs!6)T-qaQDq;ZXb;+_qZ zZFC~L4-hYTUSAYt^OS7X2TgzY+v~X2uU6Y1?yie!rr$IE+RSHKN^6;8XXJ?d{@3(l zpcxR?=Vj4b^JY*VF53doY@V)QoL;H-N0@XNhv)fC8FXmvy4S`81=@nOf{lw0^Ra9lJ zfG+Io?M>%0a0bn0E8s3G4qybq<+`7f!oF#eM8(S7i;e;L?SAF)VESPC;wpup6R|Tr zWyABFwr65z3>1j?RtUumO$z9T?@U{R=@4pv+J?bkkn%IeiM?f&qPgT(@e;11vKOj+ zZ#{f_$56S(p$3O>jfiBs6e=Q+11x>^YTm*5NrnlYC>6T;5_8~s1k3GFmO{s8&q!vmJfg2*yevv#6eKB%mMqwcQZ=`$|ty6Dri zAak4J{HDMfG3)A+jw@HLOi@iy3BLIy&2%+y-)=q{9$Sz{7Xs0SWT;c?Y!I0|?9U5; z^dX7dQYDtX1&g1Apl2?qO&pw{aq+JoepVx9 z=3W|cMSiz2LT@p}yHs^Me5i0To@_#H4k)s!j!Y)Yru9ww!}%)Qw^Dft9t!AI56gG@ zNm8l_YU<5eD!NfmBvPr)08i-@?}){VL!FO()Y|Fr7Y8wZt8SM|Wmhp2u{bVJWPT(9 zPTKzQH6N~r$v9HPCZ6r;JR)wiaq=}Sct4Nf?)Jl;S z{7zHowQ|JJ3zMcjuQBhH9y-=TKknxj9%rnPePZ58-lcO^o^BmTBwrKyZ(U9YH?7*?7H>lKVGGF+u0Ixy8b?OGzSI^A|fhJM*O8=GtSeGKvba zCZ*wYo;rt!1a^U65$kmB_-4ozK;#n^f>R% z{?6zRq}8z~pDaUh#Nl#3l6R#zlYS(7a8WkJ% z-sn^ygEyvSr!`CY{KVmz9_tzST39v-9!rC?ViZq4s8RBkBocV{^0P@g-{6XHyw^p` zz2tlrm_;LFlhVnP?l#teW5^;?ib);w=@__7HZwAkYV(>*&=>mLWp>D}UuD}K`=!XV z(lb6VX>@B;#7NXq!?_nm? z%RVdPGVK67s4Lv9mDLTVw}+E~m2q3rVtJ`q`F2|ed!P?C1Wn3$9WCL4ON3fd&v-mr zRfuo^Tfv|z=mhuc7cX9b{7^8wdf19i2fT>s++!x!&Y7sedrsKYhV%}5&%82ocvW_= zHo&!xu-NTj8Gzr+Z?sW8XorGwYH-!)@lvmdyY(!6Y`rj+Ch22pUg5?{o2~(Pua7ach?+bug0swDtq(HiGR|P6wC6B zn+c7i_ALy`PvOWWd;x94D{MghI{o+%JMYm`cPHSUbDLj$eTb$)Q(>c3_>F;sepp;A zo2x!-9a3^nH@(!_>j=m50_N}7Hg3t_yu|{yUSKcV(awg>xG2f<>JElm&|8_Z>>}xu zvBdVyStEuTz^L&q3y@jeQWb@ixdVAW5}}=oc&bO%J4v0KD)iJ93geK zgVKO|00i}@^h}^0_tU1xU(M3Q+6?lf8j)6V8i6uT|&l@^VVD@TY37Mor;T_ zd5M0qY^dr+b@)`iQS-zu4%@ezyzr2L$TW8eih+H!IyuCVIkGSwPs*r(D0ysFb=;QK zR#V}AV{*-iBSsC*8vRwIw77T`=(8Ks$fBy{;wmyLbA&nw(h|B`!>CIExa8#KAOgvL zEyI~OOe1J-e`1X)sPW==PI461LrTS*9R2ar{kkyA4B1fvLcWZDV9eAdc3_RQ5rdtp!Qrk%D~1E9GWW) z)a=Xaac0mh7E=+6v!3aLH^E{dorC+W1b1h9H6e-8kMkf8VGr`4lUdG!^s)_rN4vhqaXktQ^jVaFi`S)M*Ka!U~&0}p>l)Pg5Dce@~# z!$qw+eQzF(?H{&MS=G)>uO=?+mm2EEQVW&f8^Rx{Jutjzb6~2&0$u&nRtID^1W+Z) z{&vnM>#Fac?^sV0;BoAVxt=I4Grw~7ynShZh_>z1@3)c*=>)}PKm2F1hX1baHTD3O z6h<8o%^v6Z+X>^jGDpR=;PA&$VU$Ef z)o{}**~+q$@U$q2GqD5X-&4XWR*t%;#l(<^mhKW`kwGf16o@C&T~m2JIG-jchh{WSi{g$i8aS#pV@@?O+~q5`e^NSQzbsxtWPzv z%A@OB&C;mO+%g0`RhT|AcdB>`SD`54fyK}fp0Bk%(ADHD7d|#C3aRD>X zx2I*8!JzR@^G<^;@w^32TR~3SBy%W7Kt}S%!otE-fC{9n7!)A+Kl5=zHbt_WkhG%7kgkw{vfUIcE1|M|?F4Ff33v z`Yk!GOrKG`NJAN#!E5Z%y>#};$;onQQqHNU~;Z{<_V^Su_wOX@FEM0LSqsr~z@w&n5P#>$P66(5c4#`Lz1^ z+1b~C>OWRh3%vRx{7zH^1m>#>5UNA-FEB2hW#DloXIj_^;*E36EMjf1FD7;>nL&5` zGmPIX#aEpNz&5)_=?1M3UtB5e8tvM(t5@ZQwi-_SH*Bq=;$`cPfpkD@JZPu}4Tbst zFrg(PK7ZbR2HZnX)$o|HJX)LW>{)@X?(Stu<{%b8tx7I+0U+$tzNb?-nIlA{+g>|? z{p{2#0t?^*_#bs@r}qOW-C?o-1IX>mjTkTsD4w|~4TNP|3a$Q*J!&Va3Fp#;Iw#2l&8(XVuW|V zg`|n57S1gOsPk$10J}zBr#Jkgl&GE?U&tbPi9K534|(5i;hJs6@H+y(0fUMHEf8AE zd<`jzSvlOHXqzfjBdQTtW7&cqYeMJjZ%)tw2bvUsxGD_LdC-6|gcA1vWLZvQgW=#w zJf77$m#F2sbrt^jJfM>atK-Qj*KOM}vX+0*fM(CWEF0q{Os<+pCg#nl%(a$?~{G@y8@lW`rG3C;S+R z_BHseGk>~gsV4!oi zymQ-_l@WNy)B7R+P{+@}_36vY%V5D!s95vUckRVhRc$F>s(T?-OCxy!ZOi_LwmJIWgPbRA zQ#S1*J8hRc(G|JbwfDh%mmpfU*puGABq_$J@V8oGgdLKs@kfMwFK0=cMbmAFYyvT4 zKL42$%id2988Z@;wr_R*%w=8sXBOzKwR2YAisXl8*o}RylIAo{pVo|cB2h4-zjGVGBNXqJiRgyT!$FMqY)a$;>r7FfyAHEA1akOLG8fGjdA3kXn_6k$h)v66ZF~a@B!71$hi9TO$UWn+%*{+t)x(HMf$A9pGlC zp~k|t1BLLJ9uFi;3+k9e!>Zn#7ntoOZh~a6Z(!0ZkX znevi%ncNf*tCvT%xwf6@g|~D^-MDa^WJz8}1F&f(-%!Kk!pZCt$Xil$@ywi9(! zp!$Jw`fwHfLg0*}%fSHJ0aGq6Qwyv3G+L8fTgjIP+a11tV@+l<%UW)4LmW@KR93@0 zwa;l~x{g&sTwB^3kE0WGH<}P=0AddueE8 z-JSe-Jn?*C>Uny06(W^!3PWiG4m$bZzz~n&!KF6idtrE!rCQMyFTBSk#&8+d=}*hJ zy7Tm|@D)cy1CqRsj5|8S9Q5cb+MXV}h>MI;AOnRt&1zf}eiYQ5PpYl;h zg|(mm+448UAfDcwP{d^V9bVy0Q?|R6xwWY15zOx$T!W+Dg<2N!|vAb1kWezovCsg)GdMpohPF+hOWWPpXPxf1VnfIk{ zwXi3n{|+lRciQhBnQwf6Bqh1-D34!=CfcWI*X%Vj5d&@XN<&ryj^Y+dgSY$-noqL8 z8uvP~mzu9mueg*w=J&VUbvwimuhKx9*t8T!=`EYSX%#9{JBfd*H`SxAs^~a@uTn`9mx8RQcy~+D_;JO03-oy7^<>pJ~7v##1>pG{w>X-OshiYH1 zPYpmWGN}o5Pl;0ej)TEBfrh6)Cw?r({f_Us_qYZJ1X6e(xi_RPwBU8y2M~oPD4HT( zEze649JN$WGLbftX4X#d3A^wtmH*dGJlmMG2Fv}tS0^2uesAv)j@$hH&*mL52hRi% zVYU+P_tE~fI-Cik>

        Kafka Data Migration Overview

        -

        Scenario

        You can migrate Kafka services to connect message producers and consumers to a new Kafka instance and can even migrate persisted message data to the new Kafka instance. Kafka services can be migrated in the following two scenarios:

        +

        You can migrate Kafka services to connect message producers and consumers to a new Kafka instance and can even migrate persisted message data to the new Kafka instance. Kafka services can be migrated in the following two scenarios:

        • Migrating services to the cloud without downtime

          Services that have high requirements on continuity must be smoothly migrated to the cloud because they cannot afford a long downtime.

        • Re-deploying services on the cloud

          A Kafka instance deployed within an AZ is not capable of cross-AZ disaster recovery. For higher reliability, you can re-deploy services to an instance that is deployed across AZs.

        -

        Preparation

        1. Configure the network environment.

          A Kafka instance can be accessed within a VPC or over a public network. For public network access, the producer and consumer must have public access permissions, and the following security group rules must be configured.

          -
          Table 1 Security group rules

          Direction

          +
          - - - - - - - - - - - - - -
          Table 1 Security group rules

          Direction

          Protocol

          +

          Protocol

          Port

          +

          Port

          Source

          +

          Source

          Description

          +

          Description

          Inbound

          +

          Inbound

          TCP

          +

          TCP

          9094

          +

          9094

          0.0.0.0/0

          +

          0.0.0.0/0

          Accessing a Kafka instance in a public network (in plaintext)

          +

          Accessing a Kafka instance in a public network (in plaintext)

          Inbound

          +

          Inbound

          TCP

          +

          TCP

          9095

          +

          9095

          0.0.0.0/0

          +

          0.0.0.0/0

          Accessing a Kafka instance in a public network (in ciphertext)

          +

          Accessing a Kafka instance in a public network (in ciphertext)
          -
        2. Create a Kafka instance.

          The specifications of the new instance cannot be lower than the original specifications. For more information, see Creating a Kafka Instance.

          -
        3. Create a topic.

          Create a topic with the same configurations as the original Kafka instance, including the topic name, number of replicas, number of partitions, message aging time, and whether to enable synchronous replication and flushing. For more information, see Creating a Kafka Topic.

          +
        4. Create the target Kafka instance.

          The specifications of the target instance cannot be lower than the original specifications. For more information, see Creating a Kafka Instance.

          +
        5. Create a topic in the target Kafka instance.

          Create a topic with the same configurations as the original Kafka instance, including the topic name, number of replicas, number of partitions, message aging time, and whether to enable synchronous replication and flushing. For more information, see Creating a Kafka Topic.

          6. Migration Scheme 1: Migrating the Production First

          Migrate the message production service to the new Kafka instance. After migration, the original Kafka instance will no longer produce messages. After all messages of the original Kafka instance are consumed, migrate the message consumption service to the new Kafka instance to consume messages of this instance.

          -
          1. Change the Kafka connection address of the producer to that of the new Kafka instance.
          2. Restart the production service so that the producer can send new messages to the new Kafka instance.
          3. Check the consumption progress of each consumer group in the original Kafka instance until all data in the original Kafka instance is consumed.
          4. Change the Kafka connection addresses of the consumers to those of the new Kafka instance.
          5. Restart the consumption service so that consumers can consume messages from the new Kafka instance.
          6. Check whether consumers consume messages properly from the new Kafka instance.
          7. The migration is complete.
          +
          1. Change the Kafka connection address of the producer to that of the new Kafka instance.
          2. Restart the production service so that the producer can send new messages to the new Kafka instance.
          3. Check the consumption progress of each consumer group in the original Kafka instance until all data in the original Kafka instance is consumed.
          4. Change the Kafka connection addresses of the consumers to those of the new Kafka instance.
          5. Restart the consumption service so that consumers can consume messages from the new Kafka instance.
          6. Check whether consumers consume messages properly from the new Kafka instance.
          7. The migration is complete.

          This is a common migration scheme. It is simple and easy to control on the service side. During the migration, the message sequence is ensured, so this scheme is suitable for scenarios with strict requirements on the message sequence. However, latency may occur because there is a period when you have to wait for all data to be consumed.

          Migration Scheme 2: Migrating the Production Later

          Use multiple consumers for the consumption service. Some consume messages from the original Kafka instance, and others consume messages from the new Kafka instances. Then, migrate the production service to the new Kafka instance so that all messages can be consumed in time.

          @@ -59,7 +58,12 @@

        6. Change the Kafka connection address of the producer to that of the new Kafka instance.
        7. Restart the producer client to migrate the production service to the new Kafka instance.
        8. After the production service is migrated, check whether the consumption service connected to the new Kafka instance is normal.
        9. After all data in the original Kafka is consumed, close the original consumption clients.
        10. The migration is complete.

          11. In this scheme, the migration process is controlled by services. For a certain period of time, the consumption service consumes messages from both the original and new Kafka instances. Before the migration, message consumption from the new Kafka instance has already started, so there is no latency. However, early on in the migration, data is consumed from both the original and new Kafka instances, so the messages may not be consumed in the order that they are produced. This scheme is suitable for services that require low latency but do not require strict message sequence.

          -

          How Do I Migrate Persisted Data Along with Services?

          You can migrate consumed data from the original instance to a new instance by using the open-source tool MirrorMaker. This tool mirrors the original Kafka producer and consumer into new ones and migrates data to the new Kafka instance.

          +

          Migration Scheme 3: Migrating the Consumption First

          Use Smart Connect to synchronize the two Kafka instances, migrate the consumer first and then the producer to the new Kafka instance.

          +
          1. Create a Smart Connect task for Kafka data replication. For details, see Replicating Kafka Instance Data.
          2. On the Message Query page of the Kafka console, check whether the latest messages and the synchronization progress of both Kafka instances are consistent. For details, see Viewing Kafka Messages.

            • Yes: Go to 3.
            • No: Check whether the synchronized data per minute of both Kafka instances is normal. If yes, wait for the synchronization progress of both Kafka instances to be consistent, then go to 3.
            +

          3. Change the Kafka connection addresses of the consumers to those of the new Kafka instance.
          4. Restart the consumption service so that consumers can consume messages from the new Kafka instance.
          5. Check whether consumers consume messages properly from the new Kafka instance.
          6. Change the Kafka connection address of the producer to that of the new Kafka instance.
          7. Restart the producer client to migrate the production service to the new Kafka instance.
          8. After the production service is migrated, check whether the consumption service connected to the new Kafka instance is normal.
          9. The migration is complete.
          +

          This scheme uses Smart Connect to synchronize the source and target data in real time. However, the consumption progress is synchronized in batches. The consumption progress on the source and target partition may vary from 0 to 100. As a result, some messages are repeatedly consumed. This scheme applies to services where the message production must continue, end-to-end latency must be low, and repeated consumption can be tolerated.

          +
          +

          How Do I Migrate Persisted Data Along with Services?

          You can migrate consumed data from the original instance to a new instance by using Smart Connect. This tool mirrors the original Kafka producer and consumer into new ones and migrates data to the new Kafka instance. For details, see Replicating Kafka Instance Data.

          Note that each cloud Kafka instance stores data in three replicas. Therefore, the storage space of the new instance should be three times that of the original single-replica message storage.

          diff --git a/docs/dms/umn/kafka-dnat.html b/docs/dms/umn/kafka-dnat.html index 90b24e75..23786e86 100644 --- a/docs/dms/umn/kafka-dnat.html +++ b/docs/dms/umn/kafka-dnat.html @@ -1,8 +1,9 @@

          Accessing Kafka in a Public Network Using DNAT

          -

          Scenario

          You can use destination NAT (DNAT) to access a Kafka instance so that the instance can provide services on the public network through port mapping.

          -
          +

          Enable public access in either of the following ways:

          +
          • On the Kafka console, access Kafka instances using EIPs. For details, see Configuring Kafka Public Access.
          • Configure port mapping from EIPs to specified instance ports using destination NAT (DNAT).
          +

          This section describes how to access Kafka over a public network using DNAT.

          Prerequisites

          You have created EIPs. The number of EIPs is the same as the number of brokers in the Kafka instance. For details about how to create an EIP, see Assigning an EIP.

          Step 1: Obtain Information About the Kafka Instance

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

            Select the region where your Kafka instance is located.

            @@ -23,7 +24,7 @@

          3. Create DNAT rules for other private network addresses of the Kafka instance recorded in 5. Configure a unique EIP for each DNAT rule.

            For details about how to create a DNAT rule, see 2 to 4.

          4. After all DNAT rules are created, click the DNAT Rules tab to view the created DNAT rules and record the EIPs corresponding to the private IP addresses.
          -

          Step 4: Bind EIPs on the Kafka Console

          1. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
          2. Click the desired Kafka instance to view its details.
          3. In the Advanced Settings section on the Basic Information tab page, click Modify next to Cross-VPC Access.
          4. Change the values of advertised.listeners IP Address/Domain Name to the EIPs in the DNAT rules. Ensure that the mapping between the private network addresses and the EIPs is consistent with that recorded in 6. Then click Save.

            Figure 5 Changing the advertised.listeners IP address (for DNAT access)
            +

            Step 4: Map EIPs to the Port 9011 of Private IP Addresses

            1. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
            2. Click the desired Kafka instance to view its details.
            3. In the Advanced Settings section on the Basic Information tab page, click Modify next to Cross-VPC Access.
            4. Change the values of advertised.listeners IP Address/Domain Name to the EIPs in the DNAT rules. Ensure that the mapping between the private network addresses and the EIPs is consistent with that recorded in 6. Then click Save.

              Figure 5 Changing the advertised.listeners IP address (for DNAT access)

            Step 5: Verify Connectivity

            Check whether messages can be created and retrieved by referring to Connecting to Kafka Using the Client (Plaintext Access) or Connecting to Kafka Using the Client (Ciphertext Access).

            diff --git a/docs/dms/umn/kafka-faq-200426013.html b/docs/dms/umn/kafka-faq-200426013.html index 9fd20172..6938e300 100644 --- a/docs/dms/umn/kafka-faq-200426013.html +++ b/docs/dms/umn/kafka-faq-200426013.html @@ -1,7 +1,7 @@

            How Do I Synchronize Data from One Kafka Instance to Another?

            -

            Unfortunately, you cannot synchronize two Kafka instances in real time. To migrate services from one instance to another, create messages to both instances. After all messages in the original instance have been retrieved or aged, you can migrate services to the new instance.

            +

            On the Kafka console, you can create a Smart Connect task for instance data replication. For details, see Replicating Kafka Instance Data.

            diff --git a/docs/dms/umn/kafka-qs-0409001.html b/docs/dms/umn/kafka-qs-0409001.html index d8cf5c17..7532e854 100644 --- a/docs/dms/umn/kafka-qs-0409001.html +++ b/docs/dms/umn/kafka-qs-0409001.html @@ -1,7 +1,7 @@

            Getting Started with Kafka for Message Production and Consumption

            -

            This section takes the example of creating a Kafka 2.7 instance (ciphertext access and SASL_SSL) and accessing it on the client (private network, within a virtual private cloud (VPC)) for message production and consumption to get you quickly started with Distributed Message Service (DMS).

            +

            This section takes the example of creating a Kafka instance (ciphertext access and SASL_SSL) and accessing it on the client (private network, within a virtual private cloud (VPC)) for message production and consumption to get you quickly started with Distributed Message Service (DMS).

            Figure 1 Procedure for using DMS for Kafka
            1. Step 1: Preparations

              A Kafka instance runs in a VPC. Before creating a Kafka instance, ensure that a VPC is available.

              After a Kafka instance is created, download and install the Kafka open-source client on your ECS before producing and consuming messages.

              @@ -11,9 +11,11 @@

              This section uses the example of creating a topic on the console.

            2. Step 4: Connect to a Kafka Instance to Produce and Consume Messages

              Before connecting to a Kafka instance with SASL_SSL enabled, download the certificate and configure the connection in the client configuration file.

            -

            Step 1: Preparations

            1. Before creating a Kafka instance, ensure that your account has permissions to perform operations on Kafka instances.

              To achieve fine-grained management of your cloud resources, create IAM user groups and users and grant specified permissions to the users. For more information, see Creating a User and Granting DMS for Kafka Permissions.

              -

            2. Before creating a Kafka instance, ensure that a VPC and a subnet are available.

              Configure the VPC and subnet for Kafka instances as required. You can use the current account's existing VPC and subnet, or create new ones. For details about how to create a VPC and a subnet, see Creating a VPC. Note that the VPC must be in the same region as the Kafka instance.

              -

            3. Before creating a Kafka instance, ensure that a security group is available.

              Configure the security group for Kafka instances as required. You can use the current account's existing security groups, or create new ones. For details about how to create a security group, see Creating a Security Group.

              +

              Step 1: Preparations

              1. Grant Kafka instance permissions.

                To achieve fine-grained management of your cloud resources, create Identity and Access Management (IAM) user groups and users and grant specified permissions to the users. For more information, see Creating a User and Granting DMS for Kafka Permissions.

                +

              2. Create a VPC and subnet.

                Before creating a Kafka instance, ensure that a VPC and a subnet are available. For details about how to create a VPC and a subnet, see Creating a VPC.

                +

                The VPC must be created in the same region as the Kafka instance.

                +
                +

              3. Create a security group and add security group rules.

                Before creating a Kafka instance, ensure that a security group is available. For details about how to create a security group, see Creating a Security Group.

                To connect to Kafka instances, add the security group rules described in Table 1. Other rules can be added based on site requirements.
                @@ -44,15 +46,15 @@

                After a security group is created, it has a default inbound rule that allows communication among ECSs within the security group and a default outbound rule that allows all outbound traffic. If you access your Kafka instance using the private network within a VPC, you do not need to add the rules described in Table 1.

                -

              4. Before connecting to a Kafka instance, ensure that you have created an elastic cloud server (ECS) that has an EIP, installed the JDK, configured environment variables, and downloaded an open-source Kafka client. The following steps describe how to complete these preparations.

                A Linux ECS is taken as an example. For more information on how to install JDK and configure the environment variables for a Windows ECS, please search the Internet.
                1. Log in to the console, click in the upper left corner, click Elastic Cloud Server under Computing, and then create an ECS.

                  For details about how to create an ECS, see Creating an ECS. If you already have an available ECS, skip this step.

                  +

                2. Construct a client for message production and consumption.

                  This section uses a Linux elastic cloud server (ECS) as the client. Before creating a Kafka instance, create an ECS with an EIP, install the JDK, configure environment variables, and download an open-source Kafka client.
                  1. Log in to the console, click in the upper left corner, click Elastic Cloud Server under Computing, and then create an ECS.

                    For details about how to create an ECS, see Creating an ECS. If you already have an available ECS, skip this step.

                  2. Log in to an ECS as user root.
                  3. Install Java JDK and configure the environment variables JAVA_HOME and PATH.
                    1. Download a JDK.

                      Use Oracle JDK instead of ECS's default JDK (for example, OpenJDK), because ECS's default JDK may not be suitable. Obtain Oracle JDK 1.8.111 or later from Oracle's official website.

                    2. Decompress the JDK.
                      tar -zxvf jdk-8u321-linux-x64.tar.gz

                      Change jdk-8u321-linux-x64.tar.gz to your JDK version.

                    3. Open the .bash_profile file.
                      vim ~/.bash_profile
                      -
                    4. Add the following content:
                      export JAVA_HOME=/opt/java/jdk1.8.0_321 
+
                    5. Add the following content:
                      export JAVA_HOME=/root/jdk1.8.0_321 
 export PATH=$JAVA_HOME/bin:$PATH
                      -

                      Change /opt/java/jdk1.8.0_321 to the path where you install JDK.

                      +

                      Change /root/jdk1.8.0_321 to the path where you install JDK.

                    6. Press Esc. Enter the following line and press Enter. Save the .bash_profile file and exit.
                      :wq
                    7. Run the following command to make the change take effect:
                      source .bash_profile
                    8. Check whether the JDK is installed.
                      java -version
                      @@ -65,7 +67,7 @@ export PATH=$JAVA_HOME/bin:$PATH

                -

                Step 2: Create a Kafka Instance

                1. Log in to the DMS console, then click Create Instance in the upper right corner of the page.
                2. Specify the basic instance settings. For details, see Table 2.

                  +

                  Step 2: Create a Kafka Instance

                  1. Log in to the DMS console, then click Create Instance in the upper right corner of the page.
                  2. Set basic instance information. Table 2 lists the configuration details.

                5. Table 1 Security group rules

                Direction
                Table 2 Basic instance settings

                Parameter

                Description

                @@ -135,7 +137,7 @@ export PATH=$JAVA_HOME/bin:$PATH

                Select the disk type and specify the disk size as required.

                Total storage space = Storage space per broker × Broker quantity. After the instance is created, you cannot change the disk type.

                -

                Select Ultra-high I/O and enter 100.

                +

                Select Ultra-high I/O and enter 100.

                Disk Encryption

                @@ -191,7 +193,10 @@ export PATH=$JAVA_HOME/bin:$PATH

                Ciphertext Access

                When this parameter is enabled, SASL authentication is required when a client connects to the Kafka instance.

                -
                1. Ciphertext Access is enabled.
                2. SASL_SSL is selected. Username and Password can be set.
                3. SASL/PLAIN is enabled.
                +
                1. Ciphertext Access is enabled.
                2. SASL_SSL is selected. Username and Password can be set. Enter "test" for the username. The username cannot be changed once ciphertext access is enabled.

                  A username should contain 4 to 64 characters, start with a letter, and contain only letters, digits, hyphens (-), and underscores (_).

                  +

                  A password must meet the following requirements:

                  +
                  • Contains 8 to 32 characters.
                  • Contains at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters `~! @#$ %^&*()-_=+\|[{}];:'",<.>? and spaces, and cannot start with a hyphen (-).
                  • Cannot be the username spelled forwards or backwards.
                  +
                3. SASL/PLAIN is enabled.

                Public Network Access

                @@ -204,39 +209,15 @@ export PATH=$JAVA_HOME/bin:$PATH
                -

              5. Click Advanced Settings. For more information, see Table 5.

                -

                - - - - - - - - - - - - - -
                Table 5 Advanced settings

                Parameter

                -

                Description

                -

                Automatic Topic Creation

                -

                Skip it.

                -

                Tags

                -

                Skip it.

                -

                Description

                -

                Skip it.

                -
                -
                -

              6. Click Create.
              7. Confirm the instance settings.
              8. Return to the DMS for Kafka page and check whether the 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 is in the Creation failed state, delete it. Then create a new one. If the instance creation fails again, contact customer service.

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

                  +

                • Skip Advanced Settings.
                • Click Create.
                • Confirm the instance settings.
                • Return to the DMS for Kafka page and check whether the 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 is in the Creation failed state, delete it, and create a new one. If the instance creation fails again, contact customer service.

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

                  +

                • After the instance is created, click its name to go to the instance details page.
                • In the Connection area, view and record the connection address.

                  Figure 2 Kafka instance addresses (private network) for intra-VPC access

              -

              Step 3: Create a Topic

              1. On the DMS for Kafka page, click a Kafka instance.
              2. In the navigation pane, choose Topics.
              3. Click Create Topic.
              4. Enter the topic name, specify other parameters by referring to Table 6, and click OK.

                -

                Table 6 Topic parameters

                Parameter

                +

                Step 3: Create a Topic

                1. On the DMS for Kafka page, click a Kafka instance.
                2. In the navigation pane, choose Topics.
                3. Click Create Topic.
                4. Enter the topic name, specify other parameters by referring to Table 5, and click OK.

                  +

                  @@ -246,7 +227,7 @@ export PATH=$JAVA_HOME/bin:$PATH @@ -295,9 +276,7 @@ export PATH=$JAVA_HOME/bin:$PATH

                  -

                  Step 4: Connect to a Kafka Instance to Produce and Consume Messages

                  1. Obtain the instance connection address.

                    1. In the navigation pane, click Basic Information.
                    2. In the Connection area, view the connection address.
                      Figure 2 Kafka instance addresses (private network) for intra-VPC access
                      -
                    -

                  2. Prepare the file for production and consumption configuration.

                    1. Log in to a Linux ECS.
                    2. Download the client.jks certificate and upload it to the /root directory on the ECS.

                      To obtain the certificate: On the Kafka console, click the Kafka instance to go to the Basic Information page. Click Download next to SSL Certificate in the Connection area. Decompress the package to obtain the client certificate file client.jks.

                      +

                      Step 4: Connect to a Kafka Instance to Produce and Consume Messages

                      1. Prepare the file for production and consumption configuration.

                        1. Log in to a Linux ECS.
                        2. Download the client.jks certificate and upload it to the /root directory on the ECS.

                          To obtain the certificate: On the Kafka console, click the Kafka instance to go to the Basic Information page. Click Download next to SSL Certificate in the Connection area. Decompress the package to obtain the client certificate file client.jks.

                          /root is the path for storing the certificate. Change it to the actual path if needed.

                        3. Go to the /config directory on the Kafka client.
                          cd kafka_2.12-2.7.2/config
                          @@ -311,25 +290,25 @@ ssl.truststore.location={ssl_truststore_path} ssl.truststore.password=dms@kafka ssl.endpoint.identification.algorithm=

                          Description:

                          -
                          • username and password are specified when enabling ciphertext access during instance creation.
                          • ssl.truststore.location is the path for storing the certificate obtained in 2.b.
                          • ssl.truststore.password is certified by the server, which must be set to dms@kafka and cannot be changed.
                          • ssl.endpoint.identification.algorithm decides whether to verify the certificate domain name. In this example, leave this parameter blank, which indicates disabling domain name verification.
                          +
                          • username and password are specified when enabling ciphertext access during instance creation.
                          • ssl.truststore.location is the path for storing the certificate obtained in 1.b.
                          • ssl.truststore.password is certified by the server, which must be set to dms@kafka and cannot be changed.
                          • ssl.endpoint.identification.algorithm decides whether to verify the certificate domain name. In this example, leave this parameter blank, which indicates disabling domain name verification.

                      2. Go to the /bin directory on the Kafka client.

                        cd ../bin
                        -

                      3. Produce messages.

                        ./kafka-console-producer.sh --broker-list ${connection addr} --topic ${topic name} --producer.config ../config/producer.properties
                        +

                      4. Produce messages.

                        ./kafka-console-producer.sh --broker-list ${connection address} --topic ${topic name} --producer.config ../config/producer.properties

                        Description:

                        -
                        • {connection addr}: the address obtained in 1.
                        • {topic name}: the topic name obtained in 4.
                        +
                        • {connection address}: the connection address obtained in 10
                        • {topic name}: the topic name obtained in 4

                        For example, 192.xxx.xxx.xxx:9093, 192.xxx.xxx.xxx:9093, 192.xxx.xxx.xxx:9093 are the connection addresses of the Kafka instance.

                        After running this command, you can send messages to the Kafka instance by entering the information as prompted and pressing Enter. Each line of content will be sent as a message.

                        -
                        [root@ecs-kafka bin]#./kafka-console-producer.sh --broker-list 192.xxx.xxx.xxx:9093,192.xxx.xxx.xxx:9093,192.xxx.xxx.xxx:9093  --topic topic-demo --producer.config ../config/producer.properties
+
                        [root@ecs-kafka bin]#./kafka-console-producer.sh --broker-list 192.xxx.xxx.xxx:9093,192.xxx.xxx.xxx:9093,192.xxx.xxx.xxx:9093  --topic topic-01 --producer.config ../config/producer.properties
 >Hello
 >DMS
 >Kafka!
 >^C[root@ecs-kafka bin]# 
                        
 
                        Press Ctrl+C to cancel.
                        
-
                      5. Consume messages.

                        ./kafka-console-consumer.sh --bootstrap-server ${connection addr} --topic ${topic name} --from-beginning  --consumer.config ../config/consumer.properties
                        +

                      6. Consume messages.

                        ./kafka-console-consumer.sh --bootstrap-server ${connection address} --topic ${topic name} --from-beginning  --consumer.config ../config/consumer.properties

                        Description:

                        -
                        • {connection addr}: the address obtained in 1.
                        • {topic name}: the topic name obtained in 4.
                        +
                        • {connection address}: the connection address obtained in 10
                        • {topic name}: the topic name obtained in 4

                        Sample:

                        -
                        [root@ecs-kafka bin]#  ./kafka-console-consumer.sh --bootstrap-server 192.xxx.xxx.xxx:9093,192.xxx.xxx.xxx:9093,192.xxx.xxx.xxx:9093 --topic topic-demo --from-beginning --consumer.config ../config/consumer.properties
+
                        [root@ecs-kafka bin]#  ./kafka-console-consumer.sh --bootstrap-server 192.xxx.xxx.xxx:9093,192.xxx.xxx.xxx:9093,192.xxx.xxx.xxx:9093 --topic topic-01 --from-beginning --consumer.config ../config/consumer.properties
 Hello
 Kafka!
 DMS
diff --git a/docs/dms/umn/kafka-ug-00001.html b/docs/dms/umn/kafka-ug-00001.html
index 8b67f2fe..2fc0beab 100644
--- a/docs/dms/umn/kafka-ug-00001.html
+++ b/docs/dms/umn/kafka-ug-00001.html
@@ -8,7 +8,13 @@
                  - + + +
                  Table 5 Topic parameters

                  Parameter

                  Description

                  Customize a name that contains 3 to 200 characters, starts with a letter or underscore (_), and contains only letters, digits, periods (.), hyphens (-), and underscores (_).

                  The name must be different from preset topics:

                  -
                  • _consumer_offsets
                  • _transaction_state
                  • _trace
                  • _connect-status
                  • _connect-configs
                  • _connect-offsets
                  +
                  • __consumer_offsets
                  • __transaction_state
                  • __trace
                  • __connect-status
                  • __connect-configs
                  • __connect-offsets

                  Cannot be changed once the topic is created.

                  Enter topic-01.

                  2024-06-14

                  +

                  2024-07-19

                  +

                  Added:

                  + +

                  2024-06-14

                  Added the following content:

                  @@ -25,7 +31,7 @@

                  2022-10-30

                  This release incorporates the following changes:

                  - +

                  2020-08-11

                  diff --git a/docs/dms/umn/kafka-ug-0001.html b/docs/dms/umn/kafka-ug-0001.html index 34a928ca..f4927832 100644 --- a/docs/dms/umn/kafka-ug-0001.html +++ b/docs/dms/umn/kafka-ug-0001.html @@ -1,21 +1,17 @@

                  Accessing Kafka Using a VPC Endpoint Across VPCs

                  -

                  Context

                  VPCs are logically isolated from each other. If a Kafka instance and a Kafka client are in different VPCs within a region, they cannot communicate with each other. In this case, you can use one of the following methods to access a Kafka instance across VPCs:

                  +

                  VPCs are logically isolated from each other. If a Kafka instance and a Kafka client are in different VPCs within a region, they cannot communicate with each other. In this case, you can use one of the following methods to access a Kafka instance across VPCs:

                  • Establish a VPC peering connection to allow two VPCs to communicate with each other. For details, see VPC Peering Connection.
                  • Use VPC Endpoint (VPCEP) to establish a cross-VPC connection.
                  -
                  -

                  Scenario

                  The following describes how to use VPCEP to implement cross-VPC access.

                  +

                  The following describes how to use VPCEP to implement cross-VPC access.

                  VPCEP provides two types of resources: VPC endpoint services and VPC endpoints.

                  • A VPC endpoint service can be a Kafka instance which is accessed using VPC endpoints.
                  • A VPC endpoint is a secure and private channel for connecting a VPC to a VPC endpoint service.
                  Figure 1 Working principle of accessing a Kafka instance across VPCs
                  -
                  -

                  Procedure

                  Figure 2 Process for accessing a Kafka instance across VPCs
                  -

                  Creating a VPC Endpoint Service

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

                    Select the region where your Kafka instance is located.

                    -

                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                  4. Click the desired Kafka instance to view its details.
                  5. In the Advanced Settings section on the Basic Information tab page, obtain the listeners IP addresses and port IDs of the instance for Cross-VPC Access.

                    Figure 3 Cross-VPC access–related listeners IP addresses and corresponding port IDs of the Kafka instance
                    -

                  6. In the Network section on the Basic Information tab page, view the VPC to which the Kafka instance belongs.

                    Figure 4 Viewing the VPC to which the Kafka instance belongs
                    -

                  7. Click the VPC to obtain the VPC ID on the VPC console.

                    Figure 5 Obtaining the VPC ID
                    +

                  8. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                  9. Click the desired Kafka instance to view its details.
                  10. In the Advanced Settings section on the Basic Information tab page, obtain the listeners IP addresses and port IDs of the instance for Cross-VPC Access.

                    Figure 2 Cross-VPC access–related listeners IP addresses and corresponding port IDs of the Kafka instance
                    +

                  11. In the Network section on the Basic Information tab page, view the VPC to which the Kafka instance belongs.

                    Figure 3 Viewing the VPC to which the Kafka instance belongs
                    +

                  12. Click the VPC to obtain the VPC ID on the VPC console.

                    Figure 4 Obtaining the VPC ID

                  13. Call the VPC Endpoint API to create a VPC endpoint service. For details, see Creating a VPC Endpoint Service.

                    POST https://{endpoint}/v1/{project_id}/vpc-endpoint-services

                    Set the following request parameter to the specified values, and other parameters as required.

                    • port_id: one of the port IDs obtained in 5.
                    • vpc_id: VPC ID obtained in 7.
                    • server_type: VM
                    • client_port: 9011
                    • server_port: 9011
                    • protocol: TCP
                    • approval_enabled: false
                    • service_type: interface
                    • endpoint: VPCEP endpoint obtained from Regions and Endpoints. The region must be the same as that of the Kafka instance.
                    • project_id: project ID obtained from Obtaining a Project ID. The region must be the same as that of the Kafka instance.
                    @@ -23,23 +19,24 @@

                    Record the value of service_name in the response. This parameter indicates the name of the VPC endpoint service.

                  14. Repeat 8 to create VPC endpoint services for other port IDs obtained in 5 and record the VPC endpoint service names.
                  -

                  (Optional) Adding a Whitelist Record

                  If the Kafka client and Kafka instance belong to different accounts, add the ID of the account to which the Kafka client belongs to the whitelist of the endpoint service. For details, see Add a Whitelist Record.

                  +

                  (Optional) Adding a Whitelist

                  The VPC endpoint service can be used across accounts through a whitelist.

                  +

                  If the Kafka client and Kafka instance belong to different accounts, add the ID of the account to which the Kafka client belongs to the whitelist of the endpoint service. For details, see Add a Whitelist Record.

                  Creating a VPC Endpoint

                  1. Click Service List. Then choose Network > VPC Endpoint.
                  2. Click Create VPC Endpoint.
                  3. Set the following parameters:

                    • Region: Select the region that the Kafka instance is in.
                    • Service Category: Select Find a service by name.
                    • VPC Endpoint Service Name: Enter the VPC endpoint service name recorded in 8 and click Verify. If Service name found is displayed, proceed with subsequent operations.
                    • VPC: Select the VPC that the Kafka client is in.
                    • Subnet: Select the subnet that the Kafka client is in.
                    • Private IP Address: Select Automatic.

                    Retain the default values for other parameters. For details, see Creating a VPC Endpoint.

                    -

                  4. Click Create Now.
                  5. Confirm the configurations and submit the request.
                  6. Go back to the VPC endpoint list and check whether the status of the created VPC endpoint has changed to Accepted. The Accepted state means that the VPC endpoint has been connected to the VPC endpoint service.

                    Figure 6 Checking the VPC endpoint status
                    +

                  7. Click Create Now.
                  8. Confirm the configurations and submit the request.
                  9. Go back to the VPC endpoint list and check whether the status of the created VPC endpoint has changed to Accepted. The Accepted state means that the VPC endpoint has been connected to the VPC endpoint service.

                    Figure 5 Checking the VPC endpoint status

                  10. Click the VPC endpoint ID. On the Summary tab page, obtain the private IP address.

                    You can use the private IP address to access the VPC endpoint service.

                    -
                    Figure 7 Viewing the private IP address
                    +
                    Figure 6 Viewing the private IP address

                  11. Repeat 1 to 7 to create a VPC endpoint for each VPC endpoint service created in 9, and view and record the private IP addresses of the VPC endpoint services.
                  -

                  Changing the advertised.listeners IP Addresses

                  1. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                  2. Click the desired Kafka instance to view its details.
                  3. On the Advanced Settings section of the Basic Information tab page, click Modify for Cross-VPC Access to change the value of advertised.listeners IP address to the private IP addresses recorded in 7 and 8. Click Save.

                    Each IP address must match the corresponding port ID. Otherwise, the network will be disconnected.

                    +

                    Modifying Parameter advertised.listeners IP

                    1. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                    2. Click the desired Kafka instance to view its details.
                    3. On the Advanced Settings section of the Basic Information tab page, click Modify for Cross-VPC Access to change the value of advertised.listeners IP address to the private IP addresses recorded in 7 and 8. Click Save.

                      Each IP address must match the corresponding port ID. Otherwise, the network will be disconnected.

                      -
                      Figure 8 Changing the advertised.listeners IP addresses
                      +
                      Figure 7 Changing the advertised.listeners IP addresses

                    Verifying Connectivity

                    Check whether messages can be created and retrieved by referring to Connecting to Kafka Using the Client (Plaintext Access) or Connecting to Kafka Using the Client (Ciphertext Access).

                    Notes:

                    -
                    • The address for connecting to a Kafka instance is in the format of "advertised.listeners IP:9011". For example, the addresses for connecting to the Kafka instance shown in Figure 8 are 10.158.0.151:9011,10.158.0.162:9011,10.158.0.164:9011.
                    • Configure inbound rules for the security group of the Kafka instance to allow access from 198.19.128.0/17 over port 9011.
                    • If a network access control list (ACL) has been configured for the subnet of this instance, configure inbound rules for the network ACL to allow access from 198.19.128.0/17 and from the subnet used by the VPC endpoint.
                    +
                    • The address for connecting to a Kafka instance is in the format of "advertised.listeners IP:9011". For example, the addresses for connecting to the Kafka instance shown in Figure 7 are 10.158.0.151:9011,10.158.0.162:9011,10.158.0.164:9011.
                    • Configure inbound rules for the security group of the Kafka instance to allow access from 198.19.128.0/17 over port 9011.
                    • If a network access control list (ACL) has been configured for the subnet of this instance, configure inbound rules for the network ACL to allow access from 198.19.128.0/17 and from the subnet used by the VPC endpoint.

                    198.19.128.0/17 is the network segment allocated to the VPCEP service. To use VPCEP, allow access from this network segment.

                    diff --git a/docs/dms/umn/kafka-ug-0002.html b/docs/dms/umn/kafka-ug-0002.html index 4cde3d02..dda69fe7 100644 --- a/docs/dms/umn/kafka-ug-0002.html +++ b/docs/dms/umn/kafka-ug-0002.html @@ -1,19 +1,18 @@

                    Configuring Kafka Topic Permissions

                    -

                    DMS supports access control list (ACL) for topics. You can differentiate user permissions by granting users different permissions in a topic.

                    -

                    This section describes how to grant topic permissions to users after ciphertext access is enabled for Kafka instances. For details about how to create a user, see Configuring Kafka Users.

                    +

                    Kafka instances with ciphertext access enabled support access control list (ACL) for topics. You can differentiate user permissions by granting users different permissions in a topic.

                    +

                    This section describes how to grant topic permissions to users after ciphertext access is enabled for Kafka instances. For details about how to create a user, see Configuring Kafka ACL Users.

                    This function is unavailable for single-node instances.

                    -

                    Constraints

                    • If no user is granted any permission for a topic and allow.everyone.if.no.acl.found is set to true, all users can subscribe to or publish messages to the topic.
                    • If allow.everyone.if.no.acl.found is set to false, only the authorized users can subscribe to or publish messages to the topic. The value of allow.everyone.if.no.acl.found can be modified.
                    • If one or more users are granted permissions for a topic, only the authorized users can subscribe to or publish messages to the topic.
                    • If both the default and individual user permissions are configured for a topic, the union of the permissions is used.
                    +

                    Constraints

                    • If parameter allow.everyone.if.no.acl.found is set to true and no topic is granted for a user, all users can subscribe to or publish messages to the topic. If permissions for a topic has been granted to one or more users, only these users can subscribe to or publish messages to the topic. The value of allow.everyone.if.no.acl.found can be modified.
                    • If allow.everyone.if.no.acl.found is set to false, only the authorized users can subscribe to or publish messages to the topic. The value of allow.everyone.if.no.acl.found can be modified.
                    • If both the default and individual user permissions are configured for a topic, the union of the permissions is used.
                    -

                    Prerequisites

                    +

                    Prerequisites

                    -

                    Configuring Topic Permissions

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

                      Select the region where your Kafka instance is located.

                      +

                      Procedure

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

                        Select the region where your Kafka instance is located.

                        -

                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                      4. Click the desired Kafka instance to view the instance details.
                      5. In the navigation pane, choose Topics.
                      6. In the row containing the desired topic, click Grant User Permission.

                        In the upper part of the Grant User Permission dialog box, the topic information is displayed, including the topic name, number of partitions, aging time, number of replicas, and whether synchronous flushing and replication are enabled. You can enable Default permissions to grant the same permissions for all users. You can use the search box to search for a user if there are many users. In the Users area, the list of created users is displayed. In the Selected area, grant permissions to the users.

                        -

                      7. Grant topic permissions to users.

                        • To grant the same permissions to all users, select Default permissions and then select permissions. As shown in the following figure, all users have the permission to publish messages to this topic.
                          Figure 1 Granting the same permissions to all users
                          -
                        • To grant different permissions to different users, do not select Default permissions. In the Users area of the Grant User Permission dialog box, select target users. In the Selected area, configure permissions (Subscribe, Publish, or Publish/Subscribe) for the users. As shown in the following figure, only the test, send, and receive users can subscribe to or publish messages to this topic. The send_receive user cannot subscribe to or publish messages to this topic.
                          Figure 2 Granting permissions to individual users
                          +

                        • Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                        • Click the desired Kafka instance to view the instance details.
                        • In the navigation pane, choose Topics.
                        • In the row containing the desired topic, click Grant User Permission.
                        • Grant topic permissions to users.

                          • To grant the same permissions to all users, select Default permissions and then select permissions. As shown in the following figure, all users have the permission to publish messages to this topic.
                            Figure 1 Granting the same permissions to all users
                            +
                          • To grant different permissions to different users, do not select Default permissions. In the Users area of the Grant User Permission dialog box, select target users. If there are many users, enter the username in the search box for a quick search. In the Selected area, configure permissions (Subscribe, Publish, or Publish/Subscribe) for the users. As shown in the following figure, only the test, send, and receive users can subscribe to or publish messages to this topic. The send_receive user cannot subscribe to or publish messages to this topic.
                            Figure 2 Granting permissions to individual users

                          If both the default and individual user permissions are configured for a topic, the union of the permissions is used. As shown in the following figure, the test and receive users can subscribe to and publish messages to this topic.

                          Figure 3 Granting topic permissions to users
                          @@ -21,7 +20,7 @@
                          Figure 4 Viewing authorized users and their permissions

                      -

                      (Optional) Deleting Topic Permissions

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

                        Select the region where your Kafka instance is located.

                        +

                        Deleting Topic Permissions

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

                          Select the region where your Kafka instance is located.

                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                        4. Click the desired Kafka instance to view the instance details.
                        5. In the navigation pane, choose Topics.
                        6. In the row containing the desired topic, click Grant User Permission.
                        7. In the Selected area of the displayed Grant User Permission dialog box, locate the row that contains the user whose permissions are to be removed, click Delete, and click OK.
                        diff --git a/docs/dms/umn/kafka-ug-0003.html b/docs/dms/umn/kafka-ug-0003.html index 2485753a..5c0f319e 100644 --- a/docs/dms/umn/kafka-ug-0003.html +++ b/docs/dms/umn/kafka-ug-0003.html @@ -1,7 +1,7 @@ -

                        Configuring Kafka Users

                        -

                        DMS supports access control list (ACL) for topics. You can differentiate user permissions by granting users different permissions in a topic.

                        +

                        Configuring Kafka ACL Users

                        +

                        Kafka instances with ciphertext access enabled support access control list (ACL) for topics. You can isolate users by granting them different permissions in a topic.

                        This section describes how to create users, reset the password, and delete users with ciphertext access enabled. For details about how to grant topic permissions for users, see Configuring Kafka Topic Permissions.

                        The maximum number of users that can be created for a Kafka instance is 20 or 500. Check the console for the actual limit.

                        There are two ways to create a user on the console. Accordingly, there are two ways to reset the user's password:

                        @@ -12,7 +12,28 @@

                        Creating a User

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

                          Select the region where your Kafka instance is located.

                          -

                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                        4. Click the desired Kafka instance to view its details.
                        5. On the Users page, click Create User.
                        6. In the displayed Create User dialog box, set the username and password, and click OK.

                          After the user is created, grant permissions to the user by referring to Configuring Kafka Topic Permissions.

                          +

                        7. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                        8. Click the desired instance to go to the instance details page.
                        9. On the Users page, click Create User.
                        10. Set user information by referring to Configuring Kafka ACL Users.

                          +

                          + + + + + + + + + + +
                          Table 1 User creation parameters

                          Parameter

                          +

                          Description

                          +

                          Username

                          +

                          The username used to access a Kafka instance, you can customize a name that complies with the rules: 4–64 characters; starts with a letter; can contain only letters, digits, hyphens (-), and underscores (_).

                          +

                          Password

                          +

                          The password used to access a Kafka instance. A password must meet the following requirements:

                          +
                          • Contains 8 to 32 characters.
                          • Contains at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters `~! @#$ %^&*()-_=+\|[{}];:'",<.>? and spaces, and cannot start with a hyphen (-).
                          • Cannot be the username spelled forward or backward.
                          +
                          +
                          +

                        11. Click OK.

                          After the user is created, grant permissions to the user by referring to Configuring Kafka Topic Permissions.

                        Resetting the Password (for the Initial User)

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

                          Select the region where your Kafka instance is located.

                          @@ -23,16 +44,16 @@

                        -

                        Resetting the User Password (for Non-initial Users)

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

                          Select the region where your Kafka instance is located.

                          +

                          Resetting the User Password (for Non-initial Users)

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

                            Select the region where your Kafka instance is located.

                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                          4. Click the desired Kafka instance to view its details.
                          5. On the Users page, click Reset Password in the row containing the desired user.
                          6. Enter and confirm a new password, and click OK.

                            • If the password is successfully reset, a success message is displayed.
                            • If the password fails to be reset, a failure message is displayed. In this case, reset the password again. If you still fail to reset the password after multiple attempts, contact customer service.

                            The system will display a success message only after the password is successfully reset on all brokers.

                          -

                          Deleting a User

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

                            Select the region where your Kafka instance is located.

                            +

                            Deleting a User

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

                              Select the region where your Kafka instance is located.

                              -

                            3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                            4. Click the desired Kafka instance to view its details.
                            5. Delete a user in either of the following ways:

                              • On the Users page, click Delete in the row containing the desired user.
                              • On the Users page, select one or more users and click Delete above the list.
                              +

                            6. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                            7. Click the desired Kafka instance to view its details.
                            8. In the navigation pane, choose Users.
                            9. Delete a user in either of the following ways:

                              • In the row containing the desired user, click Delete.
                              • Select one or more users and click Delete above the list.

                              The initial user set when ciphertext access is enabled for the first time cannot be deleted.

                            10. In the displayed Delete User dialog box, click OK to delete the user.
                            diff --git a/docs/dms/umn/kafka-ug-0004.html b/docs/dms/umn/kafka-ug-0004.html index b6a6de2b..4e0e184c 100644 --- a/docs/dms/umn/kafka-ug-0004.html +++ b/docs/dms/umn/kafka-ug-0004.html @@ -1,14 +1,14 @@

                            Viewing Kafka Disk Usage

                            -

                            This section describes how to view the disk usage of each broker on the Kafka console.

                            +

                            This section describes how to view the disk usage of each broker of a Kafka instance on the console.

                            This function is unavailable for single-node instances.

                            -

                            Viewing Kafka Disk Usage

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

                              Select the region where your Kafka instance is located.

                              +

                              Procedure

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

                                Select the region where your Kafka instance is located.

                                -

                              3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                              4. Click a Kafka instance to go to the Basic Information page.
                              5. Go to the Disk Usage Statistics page.

                                Figure 1 Viewing disk usage
                                -

                                You can query topics that use the most disk space or topics that have used a specified amount or percentage of disk space.

                                +

                              6. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                              7. Click a Kafka instance to go to the Basic Information page.
                              8. Go to the Disk Usage Statistics page.

                                You can query topics that use the most disk space or topics that have used a specified amount or percentage of disk space.

                                In the upper right corner of the page, click View Metric. On the displayed Cloud Eye page, you can view metrics of Kafka instances.

                                +
                                Figure 1 Viewing disk usage

                              diff --git a/docs/dms/umn/kafka-ug-0006.html b/docs/dms/umn/kafka-ug-0006.html index 37b68942..7ac3b41e 100644 --- a/docs/dms/umn/kafka-ug-0006.html +++ b/docs/dms/umn/kafka-ug-0006.html @@ -5,20 +5,60 @@

                              Changing the number of partitions does not restart the instance or affect services.

                              Methods for changing the partition quantity:

                              - -

                              Method 1: By using Kafka console

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

                                Select the region where your Kafka instance is located.

                                + +

                                Changing the Number of Topic Partitions (Console)

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

                                  Select the region where your Kafka instance is located.

                                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                4. Click the desired Kafka instance to view the instance details.
                                5. In the navigation pane, choose Topics.
                                6. Modify the number of partitions using either of the following methods:

                                  • Select one or more topics and click Edit Topic in the upper left corner.
                                  • In the row containing the desired topic, click Edit.
                                  -

                                7. In the Edit Topic dialog box, enter the number of partitions and click OK.

                                  • The number of partitions can only be increased.
                                  • To ensure performance, the Kafka console allows a maximum of 200 partitions for each topic.
                                  • The total number of partitions of all topics cannot exceed the maximum number of partitions allowed by the instance.
                                  +

                                8. In the Edit Topic dialog box, enter the number of partitions and click OK.

                                  • The number of partitions can only be increased.
                                  • To ensure performance, the Kafka console allows a maximum of 200 partitions for each topic.
                                  • The total partitions of all topics cannot exceed the maximum partitions of an instance. The maximum partitions of an instance varies by instance specifications. For details, see Specifications.

                                -

                                Method 2: By Using Kafka CLI

                                If your Kafka client version is later than 2.2, you can use kafka-topics.sh to change the partition quantity.

                                +

                                Changing the Number of Topic Partitions (Client)

                                If your Kafka client version is later than 2.2, you can use kafka-topics.sh to change the partition quantity.

                                For an instance with ciphertext access enabled, if allow.everyone.if.no.acl.found is set to false, topic partition quantity cannot be modified through the client.

                                • For a Kafka instance with ciphertext access disabled, run the following command in the /bin directory of the Kafka client:
                                  ./kafka-topics.sh --bootstrap-server ${connection-address} --topic ${topic-name} --alter --partitions ${number-of-partitions}
                                  -
                                • For a Kafka instance with ciphertext access enabled, do as follows:
                                  1. (Optional) For the Kafka security protocol, is SASL_PLAINTEXT or SASL_SSL used?
                                    • SASL_PLAINTEXT: Skip this step if the username and password are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password by referring to 3.
                                    • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password, and the SSL certificate configuration by referring to 3.
                                    -
                                  2. Run the following command in the /bin directory of the Kafka client:
                                    ./kafka-topics.sh --bootstrap-server ${connection-address} --topic ${topic-name} --alter --partitions ${number-of-partitions} --command-config ./config/ssl-user-config.properties
                                    +
                                    Parameter description:
                                    • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                    • topic-name: topic name.
                                    • number-of-partitions: number of partitions in a topic.
                                    +
                                    +

                                    Example:

                                    +
                                    [root@ecs-kafka bin]# ./kafka-topics.sh --bootstrap-server 192.168.xx.xx:9092,192.168.xx.xx:9092,192.168.xx.xx:9092 --topic topic-01 --alter --partitions 6
+[root@ecs-kafka bin]#
                                    +
                                  3. For a Kafka instance with ciphertext access enabled, do as follows:
                                    1. (Optional) Modify the client configuration file.
                                      View Security Protocol in the Connection area on the Basic Information page on the Kafka console. The configuration settings vary depending on the protocol.
                                      • SASL_PLAINTEXT: Skip this step if the username and password are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                        security.protocol=SASL_PLAINTEXT
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                        +

                                        Parameter description: username and password are the ones you set when enabling ciphertext access for the first time or when creating a user.

                                        +
                                      • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                        security.protocol=SASL_SSL
+ssl.truststore.location={ssl_truststore_path}
+ssl.truststore.password=dms@kafka
+ssl.endpoint.identification.algorithm=
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                        +

                                        Parameter description:

                                        +
                                        • ssl.truststore.location: path for storing the client.jks certificate. Even in Windows, you need to use slashes (/) for the certificate path. Do not use backslashes (\), which are used by default for paths in Windows. Otherwise, the client will fail to obtain the certificate.
                                        • ssl.truststore.password: server certificate password, which must be set to dms@kafka and cannot be changed.
                                        • ssl.endpoint.identification.algorithm: whether to verify the certificate domain name. This parameter must be left blank, which indicates disabling domain name verification.
                                        • username and password: username and password you set when enabling ciphertext access for the first time or when creating a user.
                                        +
                                      +
                                      +
                                    2. Run the following command in the /bin directory of the Kafka client:
                                      ./kafka-topics.sh --bootstrap-server ${connection-address} --topic ${topic-name} --alter --partitions ${number-of-partitions} --command-config ../config/ssl-user-config.properties
                                      +
                                      Parameter description:
                                      • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                      • topic-name: topic name.
                                      • number-of-partitions: number of partitions in a topic.
                                      +
                                      +

                                      Example:

                                      +
                                      [root@ecs-kafka bin]# ./kafka-topics.sh --bootstrap-server 192.168.xx.xx:9093,192.168.xx.xx:9093,192.168.xx.xx:9093 --topic topic-01 --alter --partitions 6 --command-config ../config/ssl-user-config.properties
+[root@ecs-kafka bin]#
                                      +

                                diff --git a/docs/dms/umn/kafka-ug-0007.html b/docs/dms/umn/kafka-ug-0007.html index 215d0b40..74ccd404 100644 --- a/docs/dms/umn/kafka-ug-0007.html +++ b/docs/dms/umn/kafka-ug-0007.html @@ -1,312 +1,323 @@

                                Modifying Kafka Instance Configuration Parameters

                                -

                                Scenario

                                Your Kafka instances, topics, and consumers come with default configuration parameter settings. You can modify common parameters on the DMS console. For details about parameters that are not listed on the console, see the Kafka official website.

                                +

                                Your Kafka instances, topics, and consumers come with default configuration parameter settings. You can modify common parameters on the DMS console. For details about parameters that are not listed on the console, see the Kafka official website.

                                Kafka instances have dynamic and static parameters:

                                • Dynamic parameters: Modifying dynamic parameters will not restart the instance.
                                • Static parameters: After static parameters are modified, you must manually restart the instance.
                                • Configuration parameters of some old instances cannot be modified. Check whether your instance parameters can be modified on the console. If they cannot be modified, contact customer service.
                                • This function is not available for single-node instances.
                                -

                                Prerequisites

                                You can modify configuration parameters of a Kafka instance when the instance is in the Running state.

                                -

                                Modifying Kafka Instance Configuration Parameters

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

                                  Select the region where your Kafka instance is located.

                                  +

                                  Procedure

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

                                    Select the region where your Kafka instance is located.

                                    -

                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                  4. Click the desired Kafka instance to view the instance details.
                                  5. On the Parameters page, click Edit in the row containing the parameter to modify.

                                    Parameters of v1.1.0 instances are described in Table 2 and Table 1. Parameters of v2.3.0/v2.7/3.x instances are described in Table 3 and Table 4.

                                    +

                                  6. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                  7. Click the desired Kafka instance to view the instance details.
                                  8. On the Parameters page, click Edit in the row containing the parameter to modify.

                                    Parameters of v1.1.0 instances are described in Table 1 and Table 2. Parameters of v2.3.0/v2.7/3.x instances are described in Table 3 and Table 4.

                                    -
                                    Table 1 Dynamic parameters (v1.1.0 instances)

                                    Parameter

                                    +
                                    - - - - - - - - - - -
                                    Table 1 Dynamic parameters (v1.1.0 instances)

                                    Parameter

                                    Description

                                    +

                                    Description

                                    Value Range

                                    +

                                    Value Range

                                    Default Value

                                    +

                                    Default Value

                                    auto.create.groups.enable

                                    +

                                    auto.create.groups.enable

                                    Whether to automatically create consumer groups.

                                    +

                                    Whether to automatically create consumer groups.

                                    This parameter is not displayed on the console for some earlier instances. The function of automatically creating consumer groups is enabled by default and cannot be disabled on the console.

                                    true/false

                                    +

                                    true/false

                                    true

                                    +

                                    true

                                    offsets.retention.minutes

                                    +

                                    offsets.retention.minutes

                                    The longest period a consumption position can be retained starts from the time of submission. Positions retained beyond this duration will be deleted. Each time a consumption position is submitted to a topic partition, its retention period resets to 0. The unit is minute.

                                    +

                                    The longest period a consumption position can be retained starts from the time of submission. Positions retained beyond this duration will be deleted. Each time a consumption position is submitted to a topic partition, its retention period resets to 0.

                                    This parameter is displayed as a static one for certain earlier instances.

                                    1440–30240

                                    +

                                    1440–30240

                                    +

                                    Unit: minute

                                    20160

                                    +

                                    20160
                                    -
                                    Table 2 Static parameters (v1.1.0 instances)

                                    Parameter

                                    +
                                    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                    Table 2 Static parameters (v1.1.0 instances)

                                    Parameter

                                    Description

                                    +

                                    Description

                                    Value Range

                                    +

                                    Value Range

                                    Default Value

                                    +

                                    Default Value

                                    min.insync.replicas

                                    +

                                    min.insync.replicas

                                    If a producer sets the acks parameter to all (or -1), the min.insync.replicas parameter specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful.

                                    +

                                    If a producer sets the acks parameter to all (or -1), the min.insync.replicas parameter specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful.

                                    1–3

                                    +

                                    1–3

                                    1

                                    +

                                    1

                                    message.max.bytes

                                    +

                                    message.max.bytes

                                    Maximum length of a single message, in bytes.

                                    +

                                    Maximum length of a single message.

                                    0–10,485,760

                                    +

                                    0–10,485,760

                                    +

                                    Unit: byte

                                    10,485,760

                                    +

                                    10,485,760

                                    unclean.leader.election.enable

                                    +

                                    unclean.leader.election.enable

                                    Indicates whether to allow replicas not in the ISR set to be elected as the leader as a last resort, even though doing so may result in data loss.

                                    +

                                    Indicates whether to allow replicas not in the ISR set to be elected as the leader as a last resort, even though doing so may result in data loss.

                                    true or false

                                    +

                                    true or false

                                    false

                                    +

                                    false

                                    connections.max.idle.ms

                                    +

                                    connections.max.idle.ms

                                    Idle connection timeout (in ms). Connections that are idle for the duration specified by this parameter will be closed.

                                    +

                                    Idle connection timeout (in ms). Connections that are idle for the duration specified by this parameter will be closed.

                                    5000–600,000

                                    +

                                    5000–600,000

                                    +

                                    Unit: millisecond

                                    600,000

                                    +

                                    600,000

                                    log.retention.hours

                                    +

                                    log.retention.hours

                                    Duration (in hours) for retaining a log file.

                                    +

                                    Maximum duration for storing log files.

                                    This parameter takes effect only for topics that have no aging time configured. If there is aging time configured for topics, it overrides this parameter.

                                    1–168

                                    +

                                    1–168

                                    +

                                    Unit: hour

                                    72

                                    +

                                    72

                                    max.connections.per.ip

                                    +

                                    max.connections.per.ip

                                    The maximum number of connections allowed from each IP address. Request for new connections will be rejected once the limit is reached.

                                    +

                                    The maximum number of connections allowed from each IP address. Request for new connections will be rejected once the limit is reached.

                                    100–20,000

                                    +

                                    100–20,000

                                    1000

                                    +

                                    1000

                                    group.max.session.timeout.ms

                                    +

                                    group.max.session.timeout.ms

                                    The maximum session timeout (in ms) for consumers. A longer timeout gives consumers more time to process messages between heartbeats but results in a longer time to detect failures.

                                    +

                                    Maximum session timeout for consumers. A longer timeout gives consumers more time to process messages between heartbeats but results in a longer time to detect failures.

                                    6000–1,800,000

                                    +

                                    6000–1,800,000

                                    +

                                    Unit: millisecond

                                    1,800,000

                                    +

                                    1,800,000

                                    default.replication.factor

                                    +

                                    default.replication.factor

                                    The default number of replicas configured for an automatically created topic.

                                    +

                                    The default number of replicas configured for an automatically created topic.

                                    1–3

                                    +

                                    1–3

                                    3

                                    +

                                    3

                                    allow.everyone.if.no.acl.found

                                    +

                                    allow.everyone.if.no.acl.found

                                    When this parameter is set to true, all users can access resources without ACL rules.

                                    +

                                    When this parameter is set to true, all users can access resources without ACL rules.

                                    This parameter is displayed only when is enabled for the instance or ciphertext access is used.

                                    This parameter cannot be modified for certain earlier instances.

                                    true/false

                                    +

                                    true/false

                                    true

                                    +

                                    true

                                    num.partitions

                                    +

                                    num.partitions

                                    The default number of partitions configured for each automatically created topic.

                                    +

                                    The default number of partitions configured for each automatically created topic.

                                    1 ~ 200

                                    +

                                    1–200

                                    3

                                    +

                                    3

                                    group.min.session.timeout.ms

                                    +

                                    group.min.session.timeout.ms

                                    The minimum session timeout (in ms) for consumers. A shorter timeout enables quicker failure detection but results in more frequent consumer heartbeating, which can overwhelm broker resources.

                                    +

                                    Minimum session timeout for consumers. A shorter timeout enables quicker failure detection but results in more frequent consumer heartbeating, which can overwhelm broker resources.

                                    6000–300,000

                                    +

                                    6000–300,000

                                    +

                                    Unit: millisecond

                                    6000

                                    +

                                    6000
                                    -
                                    Table 3 Dynamic parameters (2.3.0/2.7/3.x instances)

                                    Parameter

                                    +
                                    - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                    Table 3 Dynamic parameters (2.3.0/2.7/3.x instances)

                                    Parameter

                                    Description

                                    +

                                    Description

                                    Value Range

                                    +

                                    Value Range

                                    Default Value

                                    +

                                    Default Value

                                    min.insync.replicas

                                    +

                                    min.insync.replicas

                                    If a producer sets the acks parameter to all (or -1), the min.insync.replicas parameter specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful.

                                    +

                                    If a producer sets the acks parameter to all (or -1), the min.insync.replicas parameter specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful.

                                    1–3

                                    +

                                    1–3

                                    1

                                    +

                                    1

                                    message.max.bytes

                                    +

                                    message.max.bytes

                                    Maximum length of a single message, in bytes.

                                    +

                                    Maximum length of a single message.

                                    0–10,485,760

                                    +

                                    0–10,485,760

                                    +

                                    Unit: byte

                                    10,485,760

                                    +

                                    10,485,760

                                    auto.create.groups.enable

                                    +

                                    auto.create.groups.enable

                                    Whether to automatically create consumer groups.

                                    +

                                    Whether to automatically create consumer groups.

                                    This parameter is not displayed on the console for some earlier instances. The function of automatically creating consumer groups is enabled by default and cannot be disabled on the console.

                                    true/false

                                    +

                                    true/false

                                    true

                                    +

                                    true

                                    max.connections.per.ip

                                    +

                                    max.connections.per.ip

                                    The maximum number of connections allowed from each IP address. Request for new connections will be rejected once the limit is reached.

                                    +

                                    The maximum number of connections allowed from each IP address. Request for new connections will be rejected once the limit is reached.

                                    100–20,000

                                    +

                                    100–20,000

                                    1000

                                    +

                                    1000

                                    unclean.leader.election.enable

                                    +

                                    unclean.leader.election.enable

                                    Indicates whether to allow replicas not in the ISR set to be elected as the leader as a last resort, even though doing so may result in data loss.

                                    +

                                    Indicates whether to allow replicas not in the ISR set to be elected as the leader as a last resort, even though doing so may result in data loss.

                                    true or false

                                    +

                                    true or false

                                    false

                                    +

                                    false

                                    offsets.retention.minutes

                                    +

                                    offsets.retention.minutes

                                    The longest period a consumption position can be retained starts from the time of submission. Positions retained beyond this duration will be deleted. Each time a consumption position is submitted to a topic partition, its retention period resets to 0. The unit is minute.

                                    +

                                    The longest period a consumption position can be retained starts from the time of submission. Positions retained beyond this duration will be deleted. Each time a consumption position is submitted to a topic partition, its retention period resets to 0.

                                    This parameter is displayed as a static one for certain earlier instances.

                                    1440–30240

                                    +

                                    1440–30240

                                    +

                                    Unit: minute

                                    20160

                                    +

                                    20160
                                    -
                                    Table 4 Static parameters (2.3.0/2.7/3.x instances)

                                    Parameter

                                    +
                                    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/dms/umn/kafka-ug-0011.html b/docs/dms/umn/kafka-ug-0011.html index f13db34a..0a993498 100644 --- a/docs/dms/umn/kafka-ug-0011.html +++ b/docs/dms/umn/kafka-ug-0011.html @@ -9,7 +9,7 @@
                                  9. Querying the Kafka Consumer Group List
                                    10. -
                                  10. Viewing Kafka Consumer Details
                                    +
                                  11. Viewing Kafka Consumer Information
                                  12. Viewing and Resetting Kafka Consumption Offsets
                                    13. diff --git a/docs/dms/umn/kafka-ug-0012.html b/docs/dms/umn/kafka-ug-0012.html index a43395e4..0ac22f8d 100644 --- a/docs/dms/umn/kafka-ug-0012.html +++ b/docs/dms/umn/kafka-ug-0012.html @@ -3,10 +3,10 @@

                                    Deleting a Kafka Consumer Group

                                    You can delete a consumer group in either of the following ways:

                                    • Method 1: Delete a consumer group on the console.
                                    • Method 2: Use Kafka CLI to delete a consumer group. (Ensure that the Kafka instance version is the same as the CLI version.)
                                    -

                                    Prerequisites

                                    The status of the consumer group to be deleted is EMPTY.

                                    -

                                    Constraints

                                    • If auto.create.groups.enable is set to true, the consumer group status is EMPTY, and no offset has been submitted, the system automatically deletes the consumer group 10 minutes later.
                                    • If auto.create.groups.enable is set to false, the system does not automatically delete consumer groups. You can manually delete them.
                                    • If a consumer group has never committed an offset, the group will be deleted after the Kafka instance restarts.
                                    +

                                    Prerequisites

                                    The status of the consumer group to be deleted is EMPTY.

                                    +

                                    Method 1: Deleting a Consumer Group on the Console

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

                                      Select the region where your Kafka instance is located.

                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                    4. Click the desired Kafka instance to view the instance details.
                                    5. In the navigation pane, choose the Consumer Groups tab.
                                    6. Delete consumer groups using either of the following methods:

                                      • Select one or more consumer groups and click Delete Consumer Group above the consumer group list.
                                      • In the row containing the consumer group you want to delete, click Delete.
                                      @@ -17,15 +17,53 @@

                                    7. In the displayed Delete Consumer Group dialog box, click OK.

                                    Method 2: Using the CLI to Delete a Consumer Group

                                    The following uses Linux as an example.

                                    -
                                    1. Download Kafka CLI v1.1.0, v2.3.0, or v2.7.2, or v3.4.0. Ensure that the Kafka instance and the CLI are of the same version.
                                    2. Use the CLI to connect to the Kafka instance. For details, see Connecting to Kafka Using the Client (Plaintext Access) or Connecting to Kafka Using the Client (Ciphertext Access).
                                    3. In the /bin directory of the Kafka client, run the following command:

                                      ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --delete --group ${consumer-group-name}
                                      -

                                      Example:

                                      -
                                      [root@zk-server-1 bin]# ./kafka-consumer-groups.sh --bootstrap-server 192.168.1.245:9091,192.168.1.86:9091,192.168.1.128:9091 --delete --group bbbb
-Note: This will not show information about old Zookeeper-based consumers.
-Deletion of requested consumer groups ('bbbb') was successful.
                                      -

                                      If ciphertext access is enabled for the Kafka instance, the --command-config {consumer.properties file with SASL authentication} parameter must be added to the preceding commands. For details about the consumer.properties file, see Connecting to Kafka Using the Client (Ciphertext Access).

                                      -
                                      -

                                    -

                                    +
                                    • For a Kafka instance with ciphertext access disabled, run the following command in the /bin directory of the Kafka client:
                                      ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --delete --group ${consumer-group-name}
                                      +

                                      Parameter description:

                                      +
                                      • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                      • consumer-group-name: consumer group name.
                                      +

                                      Example:

                                      +
                                      [root@ecs-kafka bin]# ./kafka-consumer-groups.sh --bootstrap-server 192.168.xx.xx:9092,192.168.xx.xx:9092,192.168.xx.xx:9092 --delete --group group-01
+Deletion of requested consumer groups ('group-01') was successful.
+[root@ecs-kafka bin]#
                                      +
                                    • For a Kafka instance with ciphertext access enabled, do as follows:
                                      1. (Optional) Modify the client configuration file.
                                        View Security Protocol in the Connection area on the Basic Information page on the Kafka console. The configuration settings vary depending on the protocol.
                                        • SASL_PLAINTEXT: Skip this step if the username and password are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                          security.protocol=SASL_PLAINTEXT
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                          +

                                          Parameter description: username and password are the ones you set when enabling ciphertext access for the first time or when creating a user.

                                          +
                                        • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                          security.protocol=SASL_SSL
+ssl.truststore.location={ssl_truststore_path}
+ssl.truststore.password=dms@kafka
+ssl.endpoint.identification.algorithm=
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                          +

                                          Parameter description:

                                          +
                                          • ssl.truststore.location: path for storing the client.jks certificate. Even in Windows, you need to use slashes (/) for the certificate path. Do not use backslashes (\), which are used by default for paths in Windows. Otherwise, the client will fail to obtain the certificate.
                                          • ssl.truststore.password: server certificate password, which must be set to dms@kafka and cannot be changed.
                                          • ssl.endpoint.identification.algorithm: whether to verify the certificate domain name. This parameter must be left blank, which indicates disabling domain name verification.
                                          • username and password: username and password you set when enabling ciphertext access for the first time or when creating a user.
                                          +
                                        +
                                        +
                                      2. In the /bin directory of the Kafka client, run the following command:
                                        ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --delete --group ${consumer-group-name} --command-config ../config/ssl-user-config.properties
                                        +

                                        Parameter description:

                                        +
                                        • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                        • consumer-group-name: consumer group name.
                                        +

                                        Example:

                                        +
                                        [root@ecs-kafka bin]# ./kafka-consumer-groups.sh --bootstrap-server 192.168.xx.xx:9093,192.168.xx.xx:9093,192.168.xx.xx:9093 --delete --group group-02 --command-config ../config/ssl-user-config.properties
+Deletion of requested consumer groups ('group-02') was successful.
+[root@ecs-kafka bin]#
                                        +

                                        +
                                      +
                                    diff --git a/docs/dms/umn/kafka-ug-0014.html b/docs/dms/umn/kafka-ug-0014.html index 659d939e..363b71e8 100644 --- a/docs/dms/umn/kafka-ug-0014.html +++ b/docs/dms/umn/kafka-ug-0014.html @@ -1,7 +1,7 @@

                                    Viewing and Resetting Kafka Consumption Offsets

                                    -

                                    This section describes how to view and reset consumption offsets. Resetting consumption offsets is to change the consumption position for consumers.

                                    +

                                    A consumption offset indicates the consumption progress of a consumer. This section describes how to view and reset consumption offsets.

                                    Messages may be retrieved more than once after the offset is reset. Exercise caution when performing this operation.

                                    Prerequisites

                                    The consumer offset cannot be reset on the fly. You must first stop retrieval of the desired consumer group.

                                    @@ -13,14 +13,79 @@

                                  13. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                  14. Click the desired Kafka instance to view the instance details.
                                  15. In the navigation pane, choose Consumer Groups.
                                  16. Click the name of the desired consumer group.
                                  17. On the Consumer Offset tab page, view the list of topics that the consumer group has subscribed to, total number of messages accumulated in the topic, message consumption progress in each partition of the topic (accumulated messages, offset, latest offset, consumer ID, consumer address, and client ID).
                                  18. (Optional) To query the consumer offsets of a specific topic, enter the topic name in the search box and press Enter.

                                    19. Viewing Consumer Offsets (Kafka CLI)

                                    • For a Kafka instance with ciphertext access disabled, run the following command in the /bin directory of the Kafka client:
                                      ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --offsets --describe --all-groups
                                      -
                                    • For a Kafka instance with ciphertext access enabled, do as follows:
                                      1. (Optional) For the Kafka security protocol, is SASL_PLAINTEXT or SASL_SSL used?
                                        • SASL_PLAINTEXT: Skip this step if the username and password are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password by referring to 3.
                                        • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password, and the SSL certificate configuration by referring to 3.
                                        -
                                      2. Run the following command in the /bin directory of the Kafka client:
                                        ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --offsets --describe --all-groups --command-config ./config/ssl-user-config.properties
                                        +

                                        Parameter description: connection-address indicates the Kafka instance address, which can be obtained in the Connection area on the Basic Information page on the Kafka console.

                                        +

                                        Example:

                                        +
                                        [root@ecs-kafka bin]# ./kafka-consumer-groups.sh --bootstrap-server 192.168.xx.xx:9092,192.168.xx.xx:9092,192.168.xx.xx:9092 --offsets --describe --all-groups
+
+Consumer group '__consumer-group-dial-test' has no active members.
+
+GROUP                      TOPIC           PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG             CONSUMER-ID     HOST            CLIENT-ID
+__consumer-group-dial-test __dms_dial_test 0          350             350             0               -               -               -
+__consumer-group-dial-test __dms_dial_test 1          350             350             0               -               -               -
+__consumer-group-dial-test __dms_dial_test 2          350             350             0               -               -               -
+
+Consumer group 'test' has no active members.
+
+GROUP           TOPIC           PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG             CONSUMER-ID     HOST            CLIENT-ID
+test            topic-01        0          5               5               0               -               -               -
+test            topic-01        1          3               3               0               -               -               -
+test            topic-01        2          10              10              0               -               -               -
+[root@ecs-kafka bin]#
                                        +
                                      3. For a Kafka instance with ciphertext access enabled, do as follows:
                                        1. (Optional) Modify the client configuration file.
                                          View Security Protocol in the Connection area on the Basic Information page on the Kafka console. The configuration settings vary depending on the protocol.
                                          • SASL_PLAINTEXT: Skip this step if the username and password are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                            security.protocol=SASL_PLAINTEXT
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                            +

                                            Parameter description: username and password are the ones you set when enabling ciphertext access for the first time or when creating a user.

                                            +
                                          • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                            security.protocol=SASL_SSL
+ssl.truststore.location={ssl_truststore_path}
+ssl.truststore.password=dms@kafka
+ssl.endpoint.identification.algorithm=
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                            +

                                            Parameter description:

                                            +
                                            • ssl.truststore.location: path for storing the client.jks certificate. Even in Windows, you need to use slashes (/) for the certificate path. Do not use backslashes (\), which are used by default for paths in Windows. Otherwise, the client will fail to obtain the certificate.
                                            • ssl.truststore.password: server certificate password, which must be set to dms@kafka and cannot be changed.
                                            • ssl.endpoint.identification.algorithm: whether to verify the certificate domain name. This parameter must be left blank, which indicates disabling domain name verification.
                                            • username and password: username and password you set when enabling ciphertext access for the first time or when creating a user.
                                            +
                                          +
                                          +
                                        2. Run the following command in the /bin directory of the Kafka client:
                                          ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --offsets --describe --all-groups --command-config ../config/ssl-user-config.properties
                                          +

                                          Parameter description: connection-address indicates the Kafka instance address, which can be obtained in the Connection area on the Basic Information page on the Kafka console.

                                          +

                                          Example:

                                          +
                                          [root@ecs-kafka bin]# ./kafka-consumer-groups.sh --bootstrap-server 192.168.xx.xx:9093,192.168.xx.xx:9093,192.168.xx.xx:9093 --offsets --describe --all-groups --command-config ../config/ssl-user-config.properties
+
+Consumer group '__consumer-group-dial-test' has no active members.
+
+GROUP                      TOPIC           PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG             CONSUMER-ID     HOST            CLIENT-ID
+__consumer-group-dial-test __dms_dial_test 0          347             347             0               -               -               -
+__consumer-group-dial-test __dms_dial_test 1          347             347             0               -               -               -
+__consumer-group-dial-test __dms_dial_test 2          347             347             0               -               -               -
+
+Consumer group 'test' has no active members.
+
+GROUP           TOPIC           PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG             CONSUMER-ID     HOST            CLIENT-ID
+test            topic-01        0          5               5               0               -               -               -
+test            topic-01        1          3               3               0               -               -               -
+test            topic-01        2          10              10              0               -               -               -
+[root@ecs-kafka bin]#
                                    -

                                    Resetting Consumer Offsets

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

                                      Select the region where your Kafka instance is located.

                                      +

                                      Resetting Consumer Offsets

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

                                        Select the region where your Kafka instance is located.

                                        -

                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                      4. Click the desired Kafka instance to view the instance details.
                                      5. In the navigation pane, choose the Consumer Groups tab.
                                      6. Click the name of the desired consumer group.
                                      7. On the Consumer Offset tab page, you can perform the following operations:

                                        • To reset the consumer offset of all partitions of a single topic, click Reset Consumer Offset in the row containing the desired topic.
                                        • To reset the consumer offset of a single partition of a single topic, click Reset Consumer Offset in the row containing the desired partition.
                                        • To reset the consumer offset of all partitions in all topics, click One-touch Reset Consumer Offset above the list.
                                        +

                                      8. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                      9. Click the desired Kafka instance to view the instance details.
                                      10. In the navigation pane, choose the Consumer Groups tab.
                                      11. Click the name of the desired consumer group.
                                      12. On the Consumer Offset tab page, you can perform the following operations:

                                        • To reset the consumer offset of all partitions of a single topic, click Reset Consumer Offset in the row containing the desired topic.
                                        • To reset the consumer offset of a single partition of a single topic, click Reset Consumer Offset in the row containing the desired partition.
                                        • To reset the consumer offset of all partitions in all topics, click One-touch Reset Consumer Offset above the list.

                                      13. In the displayed Reset Consumer Offset dialog box, set the parameters by referring to Table 1.

                                    Table 4 Static parameters (2.3.0/2.7/3.x instances)

                                    Parameter

                                    Description

                                    +

                                    Description

                                    Value Range

                                    +

                                    Value Range

                                    Default Value

                                    +

                                    Default Value

                                    connections.max.idle.ms

                                    +

                                    connections.max.idle.ms

                                    Idle connection timeout (in ms). Connections that are idle for the duration specified by this parameter will be closed.

                                    +

                                    Idle connection timeout (in ms). Connections that are idle for the duration specified by this parameter will be closed.

                                    5000–600,000

                                    +

                                    5000–600,000

                                    +

                                    Unit: millisecond

                                    600,000

                                    +

                                    600,000

                                    log.retention.hours

                                    +

                                    log.retention.hours

                                    Duration (in hours) for retaining a log file.

                                    +

                                    Maximum duration for storing log files.

                                    This parameter takes effect only for topics that have no aging time configured. If there is aging time configured for topics, it overrides this parameter.

                                    1–168

                                    +

                                    1–168

                                    +

                                    Unit: hour

                                    72

                                    +

                                    72

                                    group.max.session.timeout.ms

                                    +

                                    group.max.session.timeout.ms

                                    The maximum session timeout (in ms) for consumers. A longer timeout gives consumers more time to process messages between heartbeats but results in a longer time to detect failures.

                                    +

                                    Maximum session timeout for consumers. A longer timeout gives consumers more time to process messages between heartbeats but results in a longer time to detect failures.

                                    6000–1,800,000

                                    +

                                    6000–1,800,000

                                    +

                                    Unit: millisecond

                                    1,800,000

                                    +

                                    1,800,000

                                    default.replication.factor

                                    +

                                    default.replication.factor

                                    The default number of replicas configured for an automatically created topic.

                                    +

                                    The default number of replicas configured for an automatically created topic.

                                    1–3

                                    +

                                    1–3

                                    3

                                    +

                                    3

                                    allow.everyone.if.no.acl.found

                                    +

                                    allow.everyone.if.no.acl.found

                                    When this parameter is set to true, all users can access resources without ACL rules.

                                    +

                                    When this parameter is set to true, all users can access resources without ACL rules.

                                    This parameter is displayed only when is enabled for the instance or ciphertext access is used.

                                    This parameter of some earlier instances cannot be modified.

                                    true/false

                                    +

                                    true/false

                                    true

                                    +

                                    true

                                    num.partitions

                                    +

                                    num.partitions

                                    The default number of partitions configured for each automatically created topic.

                                    +

                                    The default number of partitions configured for each automatically created topic.

                                    1 ~ 200

                                    +

                                    1 ~ 200

                                    3

                                    +

                                    3

                                    group.min.session.timeout.ms

                                    +

                                    group.min.session.timeout.ms

                                    The minimum session timeout (in ms) for consumers. A shorter timeout enables quicker failure detection but results in more frequent consumer heartbeating, which can overwhelm broker resources.

                                    +

                                    Minimum session timeout for consumers. A shorter timeout enables quicker failure detection but results in more frequent consumer heartbeating, which can overwhelm broker resources.

                                    6000–300,000

                                    +

                                    6000–300,000

                                    +

                                    Unit: millisecond

                                    6000

                                    +

                                    6000
                                    diff --git a/docs/dms/umn/kafka-ug-0015.html b/docs/dms/umn/kafka-ug-0015.html index 9d4bcef7..2b2bc53d 100644 --- a/docs/dms/umn/kafka-ug-0015.html +++ b/docs/dms/umn/kafka-ug-0015.html @@ -1,21 +1,66 @@ -

                                    Viewing Kafka Consumer Details

                                    -

                                    This section describes how to view the consumer list and consumer connection addresses.

                                    +

                                    Viewing Kafka Consumer Information

                                    +

                                    If a consumer group has consumers who are accessing a Kafka instance, you can view their connection information.

                                    Prerequisites

                                    The consumer list and connection address can be viewed only when consumers in a consumer group are connected to the Kafka instance (that is, the consumer group is in the STABLE state).

                                    Viewing the Consumer List (Console)

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

                                      Select the region where your Kafka instance is located.

                                      -

                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                    4. Click the desired Kafka instance to view the instance details.
                                    5. In the navigation pane, choose Consumer Groups.
                                    6. Click the name of the desired consumer group.
                                    7. On the Consumers tab page, view the consumer list.

                                      In the consumer list, you can view the consumer ID, consumer address, and client ID.

                                      +

                                    8. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                    9. Click an instance to go to the instance details page.
                                    10. In the navigation pane, choose Consumer Groups.
                                    11. Click the name of the desired consumer group.
                                    12. On the Consumers tab page, view the consumer list.

                                      In the consumer list, you can view the consumer ID, consumer address, and client ID.

                                    13. (Optional) To query a specific consumer, enter the consumer ID in the search box and press Enter.

                                    Viewing the Consumer List (Kafka CLI)

                                    • For a Kafka instance with ciphertext access disabled, run the following command in the /bin directory of the Kafka client:
                                      ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --group ${group-name} --members --describe
                                      -
                                    • For a Kafka instance with ciphertext access enabled, do as follows:
                                      1. (Optional) For the Kafka security protocol, is SASL_PLAINTEXT or SASL_SSL used?
                                        • SASL_PLAINTEXT: Skip this step if the username and password are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password by referring to 3.
                                        • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password, and the SSL certificate configuration by referring to 3.
                                        -
                                      2. Run the following command in the /bin directory of the Kafka client:
                                        ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --group ${group-name} --members --describe --command-config ./config/ssl-user-config.properties
                                        +

                                        Parameter description:

                                        +
                                        • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                        • group-name: consumer group name.
                                        +

                                        Example:

                                        +
                                        [root@ecs-kafka bin]# ./kafka-consumer-groups.sh --bootstrap-server 192.168.xx.xx:9092,192.168.xx.xx:9092,192.168.xx.xx:9092 --group test --members --describe
+
+GROUP           CONSUMER-ID                                           HOST            CLIENT-ID        #PARTITIONS     
+test            console-consumer-571a64fe-b0c4-47ce-833d-9e0da5a88d14 /192.168.0.215  console-consumer 3               
+[root@ecs-kafka bin]#
                                        +
                                      3. For a Kafka instance with ciphertext access enabled, do as follows:
                                        1. (Optional) Modify the client configuration file.
                                          View Security Protocol in the Connection area on the Basic Information page on the Kafka console. The configuration settings vary depending on the protocol.
                                          • SASL_PLAINTEXT: Skip this step if the username and password are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                            security.protocol=SASL_PLAINTEXT
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                            +

                                            Parameter description: username and password are the ones you set when enabling ciphertext access for the first time or when creating a user.

                                            +
                                          • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                            security.protocol=SASL_SSL
+ssl.truststore.location={ssl_truststore_path}
+ssl.truststore.password=dms@kafka
+ssl.endpoint.identification.algorithm=
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                            +

                                            Parameter description:

                                            +
                                            • ssl.truststore.location: path for storing the client.jks certificate. Even in Windows, you need to use slashes (/) for the certificate path. Do not use backslashes (\), which are used by default for paths in Windows. Otherwise, the client will fail to obtain the certificate.
                                            • ssl.truststore.password: server certificate password, which must be set to dms@kafka and cannot be changed.
                                            • ssl.endpoint.identification.algorithm: whether to verify the certificate domain name. This parameter must be left blank, which indicates disabling domain name verification.
                                            • username and password: username and password you set when enabling ciphertext access for the first time or when creating a user.
                                            +
                                          +
                                          +
                                        2. Run the following command in the /bin directory of the Kafka client:
                                          ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --group ${group-name} --members --describe --command-config ../config/ssl-user-config.properties
                                          +

                                          Parameter description:

                                          +
                                          • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                          • group-name: consumer group name.
                                          +

                                          Example:

                                          +
                                          [root@ecs-kafka bin]# ./kafka-consumer-groups.sh --bootstrap-server 192.168.xx.xx:9093,192.168.xx.xx:9093,192.168.xx.xx:9093 --group test --members --describe --command-config ../config/ssl-user-config.properties
+
+GROUP           CONSUMER-ID                                           HOST            CLIENT-ID        #PARTITIONS     
+test            console-consumer-566d0c82-07d3-4d87-9a6e-f57a9bc9fc69 /192.168.0.215  console-consumer 3               
+[root@ecs-kafka bin]#
                                    -

                                    Viewing Consumer Connection Addresses (Console)

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

                                      Select the region where your Kafka instance is located.

                                      +

                                      Viewing Consumer Connection Addresses (Console)

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

                                        Select the region where your Kafka instance is located.

                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                      4. Click the desired Kafka instance to view the instance details.
                                      5. In the navigation pane, choose Consumer Groups.
                                      6. Click the desired consumer group.
                                      7. On the Consumers tab page, view the consumer addresses.
                                      diff --git a/docs/dms/umn/kafka-ug-0034.html b/docs/dms/umn/kafka-ug-0034.html new file mode 100644 index 00000000..288c3684 --- /dev/null +++ b/docs/dms/umn/kafka-ug-0034.html @@ -0,0 +1,164 @@ + + +

                                      Replicating Kafka Instance Data

                                      +

                                      Create a Smart Connect task to copy data unidirectionally or bidirectionally between two Kafka instances.

                                      +

                                      Data in the source Kafka instance is synchronized to the target Kafka instance in real time.

                                      +
                                      +

                                      Notes and Constraints

                                      • This function is unavailable for single-node Kafka 3.x instances.
                                      • A maximum of 18 Smart Connect tasks can be created for an instance.
                                      • When you copy Kafka data, the two Kafka instances must be connected through the intranet. If they are in different VPCs, connect the network by referring to Accessing Kafka Using a VPC Endpoint Across VPCs or VPC Peering Connection.
                                      • After a Smart Connect task is created, task parameters cannot be modified.
                                      +
                                      +

                                      Prerequisites

                                      +
                                      +

                                      Procedure

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

                                        Select the region where your Kafka instance is located.

                                        +
                                        +

                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                      4. Click the desired Kafka instance to view its details.
                                      5. In the navigation pane, choose Smart Connect.
                                      6. On the displayed page, click Create Task.
                                      7. For Task Name, enter a unique Smart Connect task name. Naming rules: 4–64 characters and only letters, digits, hyphens (-), or underscores (_).
                                      8. For Task Type, select Copy Kafka data.
                                      9. For Start Immediately, specify whether to execute the task immediately after the task is created. By default, the task is executed immediately. If you disable this option, you can enable it later in the task list.
                                      10. In the Current Kafka area, set the instance alias. Naming rules: 1–20 characters and only letters, digits, hyphens (-), or underscores (_).

                                        The instance alias is used in the following scenarios:

                                        +
                                        • If you enable Rename Topics and select Push or Both for Sync Direction, the alias of the current Kafka instance will be added to the topic names of the peer end Kafka instance. For example, if the alias of the current Kafka instance is A and the topic name of the peer end Kafka instance is test, the renamed topic will be A.test.
                                        • After a Smart Connect task of Kafka data replication is created, a topic named mm2-offset-syncs.peer end Kafka instance alias.internal is generated for the current Kafka instance. If the task has Sync Consumer Offset enabled and uses Pull or Both for Sync Direction, a topic named peer end Kafka instance alias.checkpoints.internal is also created for the current Kafka instance. The two topics are used to store internal data. If they are deleted, data replication will fail.
                                        +

                                      11. In the Peer Kafka area, configure the following parameters.

                                        +

                                    Table 1 Parameters for resetting the consumer offset

                                    Parameter

                                    + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                    Table 1 Peer Kafka parameters

                                    Parameter

                                    +

                                    Description

                                    +

                                    Instance Alias

                                    +

                                    Naming rules: 1–20 characters and only letters, digits, hyphens (-), or underscores (_).

                                    +

                                    The instance alias is used in the following scenarios:

                                    +
                                    • If you enable Rename Topics and select Pull or Both for Sync Direction, the alias of the peer end Kafka instance will be added to the topic names of the current Kafka instance. For example, if the alias of the peer end Kafka instance is B and the topic name of the current Kafka instance is test01, the renamed topic will be B.test01.
                                    • After a Smart Connect task of Kafka data replication is created, if the task has Sync Consumer Offset enabled and uses Push or Both for Sync Direction, a topic named current Kafka instance alias.checkpoints.internal is also created for the peer end Kafka instance. This topic is used to store internal data. If it is deleted, data replication will fail.
                                    +

                                    Config Type

                                    +

                                    Options:

                                    +
                                    • Kafka address: Enter Kafka instance addresses.
                                    • Instance name: Select an existing Kafka instance.
                                    +

                                    Instance Name

                                    +

                                    Set this parameter when Config Type is set to Instance name.

                                    +

                                    Select an existing Kafka instance from the drop-down list.

                                    +

                                    The peer Kafka instance and the current Kafka instance must be in the same VPC. Otherwise, they cannot be identified.

                                    +

                                    Kafka Address

                                    +

                                    Set this parameter when Config Type is set to Kafka address.

                                    +

                                    Enter the IP addresses and port numbers for connecting to the Kafka instance.

                                    +

                                    When you copy Kafka data, the two Kafka instances must be connected through the intranet. If they are in different VPCs, connect the network by referring to Accessing Kafka Using a VPC Endpoint Across VPCs or VPC Peering Connection.

                                    +

                                    Authentication

                                    +

                                    Options:

                                    +
                                    • SASL_SSL: The Kafka instance has enabled SASL_SSL, clients can connect to it with SASL and the data will be encrypted using the SSL certificate.
                                    • SASL_PLAINTEXT: The Kafka instance has enabled SASL_PLAINTEXT, clients can connect to it with SASL and the data will be transmitted in plaintext.
                                    • PLAINTEXT: The instance is not using authentication.
                                    +

                                    Authentication Mechanism

                                    +

                                    Set this parameter when Authentication is set to SASL_SSL/SASL_PLAINTEXT.

                                    +
                                    • SCRAM-SHA-512: uses the hash algorithm to generate credentials for usernames and passwords to verify identities. SCRAM-SHA-512 is more secure than PLAIN.
                                    • PLAIN: a simple username and password verification mechanism.
                                    +

                                    Username

                                    +

                                    Set this parameter when Authentication is set to SASL_SSL/SASL_PLAINTEXT.

                                    +

                                    Set in instance creation or user creation.

                                    +

                                    Password

                                    +

                                    Set this parameter when Authentication is set to SASL_SSL/SASL_PLAINTEXT.

                                    +

                                    Set in instance creation or user creation.

                                    +
                                    +
                                    +

                                    After a Smart Connect task is created, modifying the authentication method or mechanism, or password of the peer end instance causes the synchronization task to fail. In this case, delete the current task and create another one.

                                    +
                                    +

                                  19. In the Rules area, configure the following parameters.

                                    +

                                    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                    Table 2 Parameters for configuring data replication rules

                                    Parameter

                                    +

                                    Description

                                    +

                                    Sync Direction

                                    +

                                    There are three synchronization directions:

                                    +
                                    • Pull: Replicates data from the peer Kafka instance to the current Kafka instance.
                                    • Push: Replicates data from the current Kafka instance to the peer Kafka instance.
                                    • Both: Bidirectional replication of Kafka instance data on both ends.
                                    +

                                    Topics

                                    +

                                    Specify the topics whose data is to be replicated.

                                    +
                                    • Regular expression: Use a regular expression to match topics.
                                    • Enter/Select: Enter topic names. To enter multiple topic names, press Enter after entering each topic name. You can also select topics from the drop-down list. A maximum of 20 topics can be entered or selected.
                                    +
                                    NOTE:

                                    Data of topics whose names end with "internal" (for example, topic.internal) will not be synchronized.

                                    +
                                    +

                                    Tasks

                                    +

                                    Number of data replication tasks. The default value is 2. You are advised to use the default value.

                                    +

                                    If Sync Direction is set to Both, the actual number of tasks will be twice the number of tasks you configure here.

                                    +

                                    Rename Topics

                                    +

                                    Add the alias of the source Kafka instance before the target topic name to form a new name of the target topic. For example, if the alias of the source instance is A and the target topic name is test, the renamed target topic will be A.test.

                                    +

                                    If you select Both for Sync Direction, enable Rename Topics to prevent infinite replication.

                                    +

                                    Add Source Header

                                    +

                                    The target topic receives the replicated messages. The message header contains the message source.

                                    +

                                    If you select Both for Sync Direction, Add Source Header is enabled by default to prevent infinite replication.

                                    +

                                    Sync Consumer Offset

                                    +

                                    Enable this option to synchronize the consumer offset to the target Kafka instance.

                                    +
                                    NOTICE:

                                    After enabling Sync Consumer Offset, pay attention to the following:

                                    +
                                    • The source and target Kafka instances cannot consume messages at the same time. Otherwise, the synchronized consumer offset will be abnormal.
                                    • The consumer offset is synchronized every minute. As a result, the consumer offset on the target end may be slightly smaller than that on the source end, and some messages are repeatedly consumed. The service logic of the consumer client must be able to handle repeated consumption.
                                    • The offset synchronized from the source end is not the same as the offset on the target end. Instead, there is a mapping relationship. If the consumer offset is maintained by the consumer client, the consumer client does not obtain the consumer offset from the target Kafka instance after switching consumption from the source Kafka instance to the target Kafka instance. As a result, the offset may be incorrect or the consumer offset may be reset.
                                    +
                                    +

                                    Replicas

                                    +

                                    Number of topic replicas when a topic is automatically created in the peer instance. The value of this parameter cannot exceed the number of brokers in the peer instance.

                                    +

                                    This parameter takes precedence over the default.replication.factor parameter set in the peer instance.

                                    +

                                    Start Offset

                                    +

                                    Options:

                                    +
                                    • Minimum offset: dumping the earliest data
                                    • Maximum offset: dumping the latest data
                                    +

                                    Compression

                                    +

                                    Compression algorithm to use for copying messages.

                                    +

                                    Topic Mapping

                                    +

                                    Customize the target topic name.

                                    +

                                    Maximum mappings: 20. Rename Topic and Topic Mapping cannot be configured at the same time.

                                    +
                                    +
                                    +
                                    • When creating a bidirectional replication task, you must enable Rename Topics or Add Source Header to prevent infinite replication. If you specify the same topic for a pull task and a push task between two instances (forming bidirectional replication), and Rename Topics and Add Source Header are not enabled for the two tasks, data will be replicated infinitely.
                                    • If you create two or more tasks with the same configuration and enable Sync Consumer Offset for them, data will be repeatedly replicated and the consumer offset of the target topic will be abnormal.
                                    +
                                    +

                                  20. (Optional) In the lower right corner of the page, click Check to test the connectivity between the Kafka instances.

                                    If "Connectivity check passed." is displayed, the Kafka instances are connected.

                                    +

                                  21. Click Create. The Smart Connect task list page is displayed. The message "Task xxx was created successfully." is displayed in the upper right corner of the page.

                                    • After a Smart Connect task of Kafka data replication is created, a topic named mm2-offset-syncs.peer end Kafka instance alias.internal is generated for the current Kafka instance. If the task has Sync Consumer Offset enabled and uses Pull or Both for Sync Direction, a topic named peer end Kafka instance alias.checkpoints.internal is also created for the current Kafka instance. The two topics are used to store internal data. If they are deleted, data replication will fail.
                                    • After a Smart Connect task of Kafka data replication is created, if the task has Sync Consumer Offset enabled and uses Push or Both for Sync Direction, a topic named current Kafka instance alias.checkpoints.internal is also created for the peer end Kafka instance. This topic is used to store internal data. If it is deleted, data replication will fail.
                                    +
                                    +

                                    22. + + + + diff --git a/docs/dms/umn/kafka-ug-0035.html b/docs/dms/umn/kafka-ug-0035.html new file mode 100644 index 00000000..8e859491 --- /dev/null +++ b/docs/dms/umn/kafka-ug-0035.html @@ -0,0 +1,103 @@ + + +

                                    Dumping Kafka Data to Object Storage Service (OBS)

                                    +

                                    Create a Smart Connect task to dump Kafka instance data to OBS for message data backup.

                                    +

                                    Data in the source Kafka instance is synchronized to the dumping file in real time.

                                    +
                                    +

                                    Notes and Constraints

                                    • This function is unavailable for single-node Kafka 3.x instances.
                                    • A maximum of 18 Smart Connect tasks can be created for an instance.
                                    • After a Smart Connect task is created, task parameters cannot be modified.
                                    +
                                    +

                                    Prerequisites

                                    • You have enabled Smart Connect.
                                    • A Kafka instance has been created and is in the Running state.
                                    • The OBS bucket must be created in the same region as the Kafka instance.
                                    +
                                    +

                                    Procedure

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

                                      Select the region where your Kafka instance is located.

                                      +
                                      +

                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                    4. Click the desired Kafka instance to view its details.
                                    5. In the navigation pane, choose Smart Connect.
                                    6. On the displayed page, click Create Task.
                                    7. For Task Name, enter a unique Smart Connect task name. Naming rules: 4–64 characters and only letters, digits, hyphens (-), or underscores (_).
                                    8. For Task Type, select Dumping.
                                    9. For Start Immediately, specify whether to execute the task immediately after the task is created. By default, the task is executed immediately. If you disable this option, you can enable it later in the task list.
                                    10. In the Source area, retain the default setting.
                                    11. In the Topics area, set parameters based on the following table.

                                      +

                                      + + + + + + + + + + +
                                      Table 1 Topic parameters

                                      Parameter

                                      +

                                      Description

                                      +

                                      Regular expression

                                      +

                                      A regular expression is used to subscribe to topics whose messages you want to dump.

                                      +

                                      Enter/Select

                                      +

                                      Enter or select the names of the topics to be dumped. Separate them with commas (,). A maximum of 20 topics can be entered or selected.

                                      +
                                      +
                                      +

                                    12. In the Target area, set parameters based on the following table.

                                      +

                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                      Table 2 Target parameters

                                      Parameter

                                      +

                                      Description

                                      +

                                      Offset

                                      +

                                      Options:

                                      +
                                      • Minimum offset: dumping the earliest data
                                      • Maximum offset: dumping the latest data
                                      +

                                      Dumping Period (s)

                                      +

                                      Interval for periodically dumping data. The time unit is second and the default interval is 300 seconds.

                                      +

                                      No package files will be generated if there is no data within an interval.

                                      +

                                      AK

                                      +

                                      Access key ID.

                                      +

                                      For details about how to obtain the AK, see Access Keys.

                                      +

                                      SK

                                      +

                                      Secret access key used together with the access key ID.

                                      +

                                      For details about how to obtain the SK, see Access Keys.

                                      +

                                      Dumping Address

                                      +

                                      The OBS bucket used to store the topic data.

                                      +
                                      • Select: You can select an existing OBS bucket from the drop-down list or click Create Dumping Address to create an OBS bucket.
                                      • Enter: You can enter an existing OBS bucket or click Create Dumping Address to create an OBS bucket. The OBS bucket to be entered must be in the same region as the Kafka instance.
                                      +

                                      Dumping Directory

                                      +

                                      Directory for storing topic files dumped to OBS. Use slashes (/) to separate directory levels.

                                      +

                                      Time Directory Format

                                      +

                                      Data is saved to a hierarchical time directory in the dumping directory. For example, if the time directory is accurate to day, the directory will be in the format of bucket name/file directory/year/month/day.

                                      +

                                      Record Separator

                                      +

                                      Select a separator to separate OBS dumping records.

                                      +

                                      Use Storage Key

                                      +

                                      Specifies whether to dump keys.

                                      +
                                      +
                                      +

                                      Do not use the key of a message as the dumping file name.

                                      +
                                      +

                                    13. Click Create. The Smart Connect task list page is displayed. The message "Task xxx was created successfully." is displayed in the upper right corner of the page.
                                    +
                                    +
                                    + + diff --git a/docs/dms/umn/kafka-ug-0038.html b/docs/dms/umn/kafka-ug-0038.html index eecbf6cf..df595de2 100644 --- a/docs/dms/umn/kafka-ug-0038.html +++ b/docs/dms/umn/kafka-ug-0038.html @@ -2,51 +2,51 @@

                                    Modifying Kafka Topic Configurations

                                    This section describes how to modify following configurations of a Kafka topic on the console.

                                    +

                                    Modifying Synchronous Replication, Synchronous Flushing, Message Timestamp, or Max. Message Size does not require instance restart.

                                    +
                                    -
                                    Table 1 Kafka topic configuration parameters

                                    Parameter

                                    +
                                    - - - - - - - - - - - - -
                                    Table 1 Kafka topic configuration parameters

                                    Parameter

                                    Description

                                    +

                                    Description

                                    Partitions

                                    +

                                    Partitions

                                    Number of partitions in a topic. For details about how to change, see Changing Kafka Partition Quantity.

                                    +

                                    Number of partitions in a topic. For details about how to change, see Changing Kafka Partition Quantity.

                                    Aging Time (h)

                                    +

                                    Aging Time (h)

                                    Maximum message retention. For details about how to change, see Changing Kafka Message Retention Period.

                                    +

                                    Maximum message retention. For details about how to change, see Changing Kafka Message Retention Period.

                                    Synchronous Replication

                                    +

                                    Synchronous Replication

                                    A message is returned to the client only after the message creation request has been received and the message has been acknowledged by all replicas.

                                    +

                                    A message is returned to the client only after the message creation request has been received and the message has been acknowledged by all replicas.

                                    Synchronous Flushing

                                    +

                                    Synchronous Flushing

                                    • Enabled: A message is immediately flushed to disk once it is created, bringing higher reliability.
                                    • Disabled: A message is stored in the memory instead of being immediately flushed to disk once created.
                                    +
                                    • Enabled: A message is immediately flushed to disk once it is created, bringing higher reliability.
                                    • Disabled: A message is stored in the memory instead of being immediately flushed to disk once created.

                                    Message Timestamp

                                    +

                                    Message Timestamp

                                    Timestamp type of a message. Options:
                                    • CreateTime: time when the producer created the message.
                                    • LogAppendTime: time when the broker appended the message to the log.
                                    +
                                    Timestamp type of a message. Options:
                                    • CreateTime: time when the producer created the message.
                                    • LogAppendTime: time when the broker appended the message to the log.

                                    Max. Message Size

                                    +

                                    Max. Message Size

                                    Maximum size of messages to be processed in batches. If message compression is enabled, this parameter indicates the size after compression.

                                    +

                                    Maximum size of messages to be processed in batches. If message compression is enabled, this parameter indicates the size after compression.

                                    If this value is increased and the consumer version is earlier than 0.10.2, the consumers' fetch size must also be increased so that they can obtain the latest value.
                                    -

                                    Modifying Synchronous Replication, Synchronous Flushing, Message Timestamp, or Max. Message Size does not require instance restart.

                                    -
                                    -

                                    Modifying Topic Configurations

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

                                      Select the region where your Kafka instance is located.

                                      +

                                      Procedure

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

                                        Select the region where your Kafka instance is located.

                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                      4. Click the desired Kafka instance to view the instance details.
                                      5. In the navigation pane, choose Topics.
                                      6. Modify topic configurations in either of the following ways:

                                        • Select one or more topics and click Edit Topic above the topic list.
                                        • In the row containing the desired topic, click Edit.

                                      7. In the Edit Topic dialog box, change configurations and click OK.

                                        • If there is only one replica, Synchronous Replication cannot be enabled.
                                        • After enabling synchronous replication, set acks to all or –1 on the client. Otherwise, this function will not take effect.
                                        diff --git a/docs/dms/umn/kafka-ug-0041.html b/docs/dms/umn/kafka-ug-0041.html index 2b7312a6..e07af3ab 100644 --- a/docs/dms/umn/kafka-ug-0041.html +++ b/docs/dms/umn/kafka-ug-0041.html @@ -1,23 +1,27 @@

                                        Creating a Kafka Consumer Group

                                        -

                                        Create a consumer group on the console.

                                        -

                                        auto.create.groups.enable: a consumer group is automatically created when a consumer attempts to enter a group that does not exist.

                                        -
                                        • This operation is optional when auto.create.groups.enable is true in Configuring Parameters.
                                        • A consumer group is required before consuming messages when auto.create.groups.enable is false in Configuring Parameters. Otherwise, consumption will fail.
                                        -
                                        • If auto.create.groups.enable is set to true, the consumer group status is EMPTY, and no offset has been submitted, the system automatically deletes the consumer group 10 minutes later.
                                        • If auto.create.groups.enable is set to false, the system does not automatically delete consumer groups. You can manually delete them.
                                        • If a consumer group has never committed an offset, the group will be deleted after the Kafka instance restarts.
                                        • Creating a consumer group on the console does not require instance restart.
                                        +

                                        A consumer subscribes to a topic. A consumer group consists of one or more consumers. Within a consumer group, each consumer can consume multiple partitions at the same time. Each partition can be consumed by one consumer at a time.

                                        +
                                        Figure 1 Example consumption
                                        +

                                        auto.create.groups.enable: a consumer group is automatically created when a consumer attempts to enter a group that does not exist.

                                        +
                                        • A consumer group is required before consuming messages when auto.create.groups.enable is false in Configuring Parameters. Otherwise, consumption will fail.
                                        • A consumer group is created automatically before consuming messages when auto.create.groups.enable is true in Configuring Parameters.
                                        +

                                        Create a consumer group on the console.

                                        +

                                        Creating a consumer group on the console does not require an instance restart.

                                        -

                                        Creating a Kafka Consumer Group

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

                                          Select the region where your Kafka instance is located.

                                          +

                                          Notes and Constraints

                                          • If auto.create.groups.enable is set to true, the consumer group status is EMPTY, and no offset has been submitted, the system automatically deletes the consumer group 10 minutes later.
                                          • If auto.create.groups.enable is set to false, the system does not automatically delete consumer groups. You can manually delete them.
                                          • If a consumer group has never committed an offset, the group will be deleted after the Kafka instance restarts.
                                          +
                                          +

                                          Procedure

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

                                            Select the region where your Kafka instance is located.

                                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                          4. Click the desired Kafka instance to view the instance details.
                                          5. In the navigation pane, choose Consumer Groups.
                                          6. Click Create Consumer Group.
                                          7. Set consumer group parameters by referring to Table 1 and click OK.

                                            -

                                            Table 1 Consumer group parameters

                                            Parameter

                                            +
                                            - - - diff --git a/docs/dms/umn/kafka-ug-0053.html b/docs/dms/umn/kafka-ug-0053.html index 4a5b1b8f..a8018aea 100644 --- a/docs/dms/umn/kafka-ug-0053.html +++ b/docs/dms/umn/kafka-ug-0053.html @@ -1,9 +1,8 @@

                                            Exporting the Kafka Instance List

                                            -

                                            Scenario

                                            This section describes how to export the Kafka instance list from the console.

                                            -
                                            -

                                            Exporting the Kafka Instance List

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

                                              Select the region where your Kafka instance is located.

                                              +

                                              You can export a list of instances on the DMS console.

                                              +

                                              Procedure

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

                                                Select the region where your Kafka instance is located.

                                              3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                              4. Export the instance list using either of the following methods:

                                                • Select the desired instances and choose Export > Export selected data to an XLSX file to export specified instances.
                                                • Choose Export > Export all data to an XLSX file to export all instances.

                                              diff --git a/docs/dms/umn/kafka-ug-0056.html b/docs/dms/umn/kafka-ug-0056.html index f9ba335c..6772212b 100644 --- a/docs/dms/umn/kafka-ug-0056.html +++ b/docs/dms/umn/kafka-ug-0056.html @@ -1,9 +1,8 @@

                                              Exporting Kafka Consumer Groups

                                              -

                                              Scenario

                                              Export the consumer group list from the console.

                                              -
                                              -

                                              Exporting Kafka Consumer Groups

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

                                                Select the region where your Kafka instance is located.

                                                +

                                                You can export a list of consumer groups in a Kafka instance.

                                                +

                                                Procedure

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

                                                  Select the region where your Kafka instance is located.

                                                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                4. Click the desired Kafka instance to view its details.
                                                5. In the navigation pane, choose Consumer Groups.
                                                6. Export consumer groups in either of the following ways:

                                                  • Select the desired consumer groups and choose Export > Export selected data to an XLSX file to export specified consumer groups.
                                                  • Choose Export > Export all data to an XLSX file to export all consumer groups.

                                                diff --git a/docs/dms/umn/kafka-ug-0061.html b/docs/dms/umn/kafka-ug-0061.html index 2624f327..e4afd796 100644 --- a/docs/dms/umn/kafka-ug-0061.html +++ b/docs/dms/umn/kafka-ug-0061.html @@ -10,7 +10,7 @@ diff --git a/docs/dms/umn/kafka-ug-0065.html b/docs/dms/umn/kafka-ug-0065.html new file mode 100644 index 00000000..26643117 --- /dev/null +++ b/docs/dms/umn/kafka-ug-0065.html @@ -0,0 +1,27 @@ + + + +

                                                Migrating Data Using Smart Connect

                                                + +

                                                +
                                                + + + diff --git a/docs/dms/umn/kafka-ug-0069.html b/docs/dms/umn/kafka-ug-0069.html index 560f0e56..7d9444ae 100644 --- a/docs/dms/umn/kafka-ug-0069.html +++ b/docs/dms/umn/kafka-ug-0069.html @@ -1,13 +1,12 @@

                                                Process of Using Kafka

                                                -

                                                The following figure shows the process of using a Kafka instance to produce and consume messages.

                                                +

                                                Distributed Message Service is a message queuing service that is based on the open-source Apache Kafka. It provides Kafka instances with isolated computing, storage, and bandwidth resources. The following figure shows the process of message production and consumption using a Kafka instance.

                                                Figure 1 Process of using Kafka
                                                1. Creating a User and Granting DMS for Kafka Permissions

                                                  Create IAM users and grant them only the DMS for Kafka permissions required to perform a given task based on their job responsibilities.

                                                2. Creating a Kafka Instance

                                                  Kafka instances are tenant-exclusive, and physically isolated in deployment.

                                                3. Creating a Kafka Topic

                                                  Create a topic for storing messages so that producers can produce messages and consumers can subscribe to messages.

                                                4. Connecting to an Instance

                                                  The client uses commands to connect to Kafka instances in a private or public network, and produces and consumes messages.

                                                  -
                                                5. Managing Messages

                                                  View messages on the console.

                                                diff --git a/docs/dms/umn/kafka-ug-0319001.html b/docs/dms/umn/kafka-ug-0319001.html index 616f1639..37180e93 100644 --- a/docs/dms/umn/kafka-ug-0319001.html +++ b/docs/dms/umn/kafka-ug-0319001.html @@ -5,7 +5,7 @@

                                                If you no longer need public access to the instance, you can disable it as required.

                                                Prerequisites

                                                • You can change the public access setting only when the Kafka instance is in the Running state.
                                                • Kafka instances only support IPv4 EIPs. IPv6 EIPs are not supported.
                                                -

                                                Enabling Public Access

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

                                                  Select the region where your Kafka instance is located.

                                                  +

                                                  Enabling Public Access

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

                                                    Select the region where your Kafka instance is located.

                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                  4. Click a Kafka instance to go to the Basic Information page.
                                                  5. Click next to Public Access to enable public access. For Elastic IP Address, select an EIP for each broker. If the number of EIPs is insufficient, click Create Elastic IP to go to the Create EIP page and create EIPs. For details, see Assigning an EIP. After the creation is complete, return to the page for enabling the public access. Click next to Elastic IP Address, select EIPs from the drop-down list. The number of EIPs must be the same as the number of brokers. Then click and the Background Tasks page is displayed.

                                                    If the status of the task turns to Successful, public access is successfully enabled.
                                                    Figure 1 Enabling public access
                                                    @@ -50,7 +50,7 @@

                                                -

                                                Disabling Public Access

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

                                                  Select the region where your Kafka instance is located.

                                                  +

                                                  Disabling Public Access

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

                                                    Select the region where your Kafka instance is located.

                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                  4. Click a Kafka instance to go to the Basic Information page.
                                                  5. Before disabling public access, disable Plaintext Access and Ciphertext Access next to Public Network Access. Then click next to Public Access.
                                                  6. Click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, public access is successfully disabled.

                                                    After public access is disabled, configure security group rules listed in Table 2 before attempting to access Kafka in a VPC. For details about accessing Kafka, see Connecting to an Instance.
                                            Table 1 Consumer group parameters

                                            Parameter

                                            Description

                                            +

                                            Description

                                            Consumer Group Name

                                            +

                                            Consumer Group Name

                                            Enter 3 to 64 characters, starting with a letter or underscore (_). Use only letters, digits, periods (.), hyphens (-), and underscores (_).

                                            +

                                            Enter 3 to 64 characters, starting with a letter or underscore (_). Use only letters, digits, periods (.), hyphens (-), and underscores (_).

                                            If a consumer group name starts with a special character, for example, an underscore (_) or a number sign (#), monitoring data cannot be displayed.
                                            Table 2 Security group rules (private network access)

                                            Direction

                                            diff --git a/docs/dms/umn/kafka-ug-180413001.html b/docs/dms/umn/kafka-ug-180413001.html index bc4eee52..20f94343 100644 --- a/docs/dms/umn/kafka-ug-180413001.html +++ b/docs/dms/umn/kafka-ug-180413001.html @@ -4,7 +4,7 @@
                                              -
                                            • Viewing Kafka Monitoring Metrics
                                              +
                                            • Viewing Kafka Metrics
                                            • Kafka Metrics
                                              • diff --git a/docs/dms/umn/kafka-ug-180413002.html b/docs/dms/umn/kafka-ug-180413002.html index 0e2248b4..3742be9d 100644 --- a/docs/dms/umn/kafka-ug-180413002.html +++ b/docs/dms/umn/kafka-ug-180413002.html @@ -7,376 +7,378 @@

                                              Namespace

                                              SYS.DMS

                                              Instance Metrics

                                              -
                                              Table 1 Instance metrics

                                              Metric ID

                                              +
                                              - - - - - - - - - - - - - - - - - - - - - - -
                                              Table 1 Instance metrics

                                              Metric ID

                                              Metric Name

                                              +

                                              Metric Name

                                              Description

                                              +

                                              Description

                                              Value Range

                                              +

                                              Value Range

                                              Monitored Object

                                              +

                                              Monitored Object

                                              Monitoring Period (Raw Data)

                                              +

                                              Monitoring Period (Raw Data)

                                              current_partitions

                                              +

                                              current_partitions

                                              Partitions

                                              +

                                              Partitions

                                              Number of used partitions in the instance

                                              +

                                              Number of used partitions in the instance

                                              Unit: count

                                              0~100000

                                              +

                                              0–100,000

                                              Kafka instance

                                              +

                                              Kafka instance

                                              1 minute

                                              +

                                              1 minute

                                              current_topics

                                              +

                                              current_topics

                                              Topics

                                              +

                                              Topics

                                              Number of created topics in the instance

                                              +

                                              Number of created topics in the instance

                                              Unit: count

                                              0~100000

                                              +

                                              0–100,000

                                              Kafka instance

                                              +

                                              Kafka instance

                                              1 minute

                                              +

                                              1 minute

                                              group_msgs

                                              +

                                              group_msgs

                                              Accumulated Messages

                                              +

                                              Accumulated Messages

                                              Total number of accumulated messages in all consumer groups of the instance

                                              +

                                              Total number of accumulated messages in all consumer groups of the instance

                                              Unit: count

                                              0–1,000,000,000

                                              +

                                              0–1,000,000,000

                                              Kafka instance

                                              +

                                              Kafka instance

                                              1 minute

                                              +

                                              1 minute
                                              -

                                              Broker Metrics

                                              -
                                              Table 2 Broker metrics

                                              Metric ID

                                              +

                                              Broker Metrics

                                              Enabling Smart Connect for a Kafka instance creates two or more brokers. On the By Broker tab page, select "connector" for Node Type for Smart Connect broker metrics, or select "broker" for Node Type for Kafka instance broker metrics.

                                              +

                                              Metrics of Smart Connect brokers: disk capacity usage, memory usage, JVM heap memory usage, node alive status, and connections.

                                              + +
                                              - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -586,7 +588,7 @@
                                              NOTE:
                                              • On the Cloud Eye console, this metric is available only when Queue is set to a specific topic name and Scope is set to Basic monitoring on the Consumer Groups tab page.
                                              • On the Monitoring page of the DMS console, this metric is available only when Topic is set to a specific topic name and Monitoring Type is set to Basic monitoring on the By Consumer Group tab page.
                                              - @@ -602,7 +604,7 @@
                                              NOTE:
                                              • On the Cloud Eye console, this metric is available only when Queues is set to All queues on the Consumer Groups tab page.
                                              • On the Monitoring page of the DMS console, this metric is available only when Topic is set to All topics on the By Consumer Group tab page.
                                              - @@ -618,7 +620,7 @@
                                              NOTE:
                                              • On the Cloud Eye console, this metric is available only when Queues is set to All queues on the Consumer Groups tab page.
                                              • On the Monitoring page of the DMS console, this metric is available only when Topic is set to All topics on the By Consumer Group tab page.
                                              - @@ -629,46 +631,122 @@
                                              Table 2 Broker metrics

                                              Metric ID

                                              Metric Name

                                              +

                                              Metric Name

                                              Description

                                              +

                                              Description

                                              Value Range

                                              +

                                              Value Range

                                              Monitored Object

                                              +

                                              Monitored Object

                                              Monitoring Period (Raw Data)

                                              +

                                              Monitoring Period (Raw Data)

                                              broker_data_size

                                              +

                                              broker_data_size

                                              Message Size

                                              +

                                              Message Size

                                              Total size of messages in the broker

                                              +

                                              Total size of messages in the broker

                                              Unit: byte, KB, MB, GB, TB or PB

                                              0–5,000,000,000,000

                                              +

                                              0–5,000,000,000,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_messages_in_rate

                                              +

                                              broker_messages_in_rate

                                              Message Creation Rate

                                              +

                                              Message Creation Rate

                                              Number of messages created per second

                                              +

                                              Number of messages created per second

                                              Unit: count/s

                                              0–500,000

                                              +

                                              0–500,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_bytes_out_rate

                                              +

                                              broker_bytes_out_rate

                                              Message Retrieval

                                              +

                                              Message Retrieval

                                              Number of bytes retrieved per second

                                              +

                                              Number of bytes retrieved per second

                                              Unit: byte/s, KB/s, MB/s, or GB/s

                                              0–500,000,000

                                              +

                                              0–500,000,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_bytes_in_rate

                                              +

                                              broker_bytes_in_rate

                                              Message Creation

                                              +

                                              Message Creation

                                              Number of bytes created per second

                                              +

                                              Number of bytes created per second

                                              Unit: byte/s, KB/s, MB/s, or GB/s

                                              0–500,000,000

                                              +

                                              0–500,000,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_public_bytes_in_rate

                                              +

                                              broker_public_bytes_in_rate

                                              Public Inbound Traffic

                                              +

                                              Public Inbound Traffic

                                              Inbound traffic over public networks per second

                                              +

                                              Inbound traffic over public networks per second

                                              Unit: byte/s, KB/s, MB/s, or GB/s

                                              NOTE:

                                              You can view this metric on the EIP console if public access has been enabled and EIPs have been assigned to the instance.

                                              0–500,000,000

                                              +

                                              0–500,000,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_public_bytes_out_rate

                                              +

                                              broker_public_bytes_out_rate

                                              Public Outbound Traffic

                                              +

                                              Public Outbound Traffic

                                              Outbound traffic over public networks per second

                                              +

                                              Outbound traffic over public networks per second

                                              Unit: byte/s, KB/s, MB/s, or GB/s

                                              NOTE:

                                              You can view this metric on the EIP console if public access has been enabled and EIPs have been assigned to the instance.

                                              0–500,000,000

                                              +

                                              0–500,000,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_fetch_mean

                                              +

                                              broker_fetch_mean

                                              Average Message Retrieval Processing Duration

                                              +

                                              Average Message Retrieval Processing Duration

                                              Average time that the broker spends processing message retrieval requests

                                              +

                                              Average time that the broker spends processing message retrieval requests

                                              Unit: ms

                                              0–10,000

                                              +

                                              0–10,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_produce_mean

                                              +

                                              broker_produce_mean

                                              Average Message Creation Processing Duration

                                              +

                                              Average Message Creation Processing Duration

                                              Average time that the broker spends processing message creation requests

                                              +

                                              Average time that the broker spends processing message creation requests

                                              Unit: ms

                                              0–10,000

                                              +

                                              0–10,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_cpu_core_load

                                              +

                                              broker_cpu_core_load

                                              Average Load per CPU Core

                                              +

                                              Average Load per CPU Core

                                              Average load of each CPU core of the Kafka VM

                                              +

                                              Average load of each CPU core of the Kafka VM

                                              Unit: %

                                              0–20

                                              +

                                              0–20

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_disk_usage

                                              +

                                              broker_disk_usage

                                              Disk Capacity Usage

                                              +

                                              Disk Capacity Usage

                                              Disk usage of the Kafka VM

                                              +

                                              Disk usage of the Kafka VM

                                              Unit: %

                                              0–100

                                              +

                                              0–100

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_memory_usage

                                              +

                                              broker_memory_usage

                                              Memory Usage

                                              +

                                              Memory Usage

                                              Memory usage of the Kafka VM

                                              +

                                              Memory usage of the Kafka VM

                                              Unit: %

                                              0–100

                                              +

                                              0–100

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_heap_usage

                                              +

                                              broker_heap_usage

                                              JVM Heap Memory Usage of Kafka

                                              +

                                              JVM Heap Memory Usage of Kafka

                                              Heap memory usage of the Kafka JVM

                                              +

                                              Heap memory usage of the Kafka JVM

                                              Unit: %

                                              0–100

                                              +

                                              0–100

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_alive

                                              +

                                              broker_alive

                                              Broker Alive

                                              +

                                              Broker Alive

                                              Whether the Kafka broker is alive

                                              +

                                              Whether the Kafka broker is alive

                                              • 1: alive
                                              • 0: not alive
                                              +
                                              • 1: alive
                                              • 0: not alive

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_connections

                                              +

                                              broker_connections

                                              Connections

                                              +

                                              Connections

                                              Total number of TCP connections on the Kafka broker

                                              +

                                              Total number of TCP connections on the Kafka broker

                                              Unit: count

                                              0–65,535

                                              +

                                              0–65,535

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_cpu_usage

                                              +

                                              broker_cpu_usage

                                              CPU Usage

                                              +

                                              CPU Usage

                                              CPU usage of the Kafka VM

                                              +

                                              CPU usage of the Kafka VM

                                              Unit: %

                                              0–100

                                              +

                                              0–100

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_disk_read_await

                                              +

                                              broker_disk_read_await

                                              Average Disk Read Time

                                              +

                                              Average Disk Read Time

                                              Average time for each disk I/O read in the monitoring period

                                              +

                                              Average time for each disk I/O read in the monitoring period

                                              Unit: ms

                                              > 0

                                              +

                                              > 0

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_disk_write_await

                                              +

                                              broker_disk_write_await

                                              Average Disk Write Time

                                              +

                                              Average Disk Write Time

                                              Average time for each disk I/O write in the monitoring period

                                              +

                                              Average time for each disk I/O write in the monitoring period

                                              Unit: ms

                                              > 0

                                              +

                                              > 0

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_total_bytes_in_rate

                                              +

                                              broker_total_bytes_in_rate

                                              Inbound Traffic

                                              +

                                              Inbound Traffic

                                              Inbound traffic per second

                                              +

                                              Inbound traffic per second

                                              Unit: byte/s

                                              0–1,000,000,000

                                              +

                                              0–1,000,000,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_total_bytes_out_rate

                                              +

                                              broker_total_bytes_out_rate

                                              Outbound Traffic

                                              +

                                              Outbound Traffic

                                              Outbound traffic per second

                                              +

                                              Outbound traffic per second

                                              Unit: byte/s

                                              0–1,000,000,000

                                              +

                                              0–1,000,000,000

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_disk_read_rate

                                              +

                                              broker_disk_read_rate

                                              Disk Read Speed

                                              +

                                              Disk Read Speed

                                              Read traffic on the disk

                                              +

                                              Read traffic on the disk

                                              Unit: byte/s, KB/s, MB/s, or GB/s

                                              ≥ 0

                                              +

                                              ≥ 0

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              broker_disk_write_rate

                                              +

                                              broker_disk_write_rate

                                              Disk Write Speed

                                              +

                                              Disk Write Speed

                                              Write traffic on the disk

                                              +

                                              Write traffic on the disk

                                              Unit: byte/s, KB/s, MB/s, or GB/s

                                              ≥ 0

                                              +

                                              ≥ 0

                                              Kafka instance broker

                                              +

                                              Kafka instance broker

                                              1 minute

                                              +

                                              1 minute

                                              0 to 263–1

                                              +

                                              0 to 263–1

                                              Consumer group of a Kafka instance

                                              0 to 263–1

                                              +

                                              0 to 263–1

                                              Consumer group of a Kafka instance

                                              0 to 263–1

                                              +

                                              0 to 263–1

                                              Consumer group of a Kafka instance

                                              -

                                              Dimension

                                              -

                                              Key

                                              +

                                              Smart Connect Metrics

                                              +
                                              - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - +
                                              Table 5 Smart Connect metrics

                                              Metric ID

                                              Value

                                              +

                                              Metric Name

                                              +

                                              Description

                                              +

                                              Value Range

                                              +

                                              Monitored Object

                                              +

                                              Monitoring Period (Raw Data)

                                              kafka_instance_id

                                              +

                                              kafka_wait_synchronize_data

                                              Kafka instance

                                              +

                                              Kafka Data to Sync

                                              +

                                              Data to synchronize in the Kafka migration task

                                              +

                                              Unit: count

                                              +

                                              ≥ 0

                                              +

                                              Smart Connect task of a Kafka instance

                                              +

                                              1 minute

                                              kafka_broker

                                              +

                                              kafka_synchronize_rate

                                              Kafka instance broker

                                              +

                                              Kafka Data Synced per Minute

                                              +

                                              Data synchronized per minute in the Kafka migration task

                                              +

                                              Unit: count

                                              +

                                              ≥ 0

                                              +

                                              Smart Connect task of a Kafka instance

                                              +

                                              1 minute

                                              kafka_topics

                                              +

                                              task_status

                                              Kafka instance topic

                                              +

                                              Task Status

                                              +

                                              Status of the current task

                                              +
                                              • 0: abnormal
                                              • 1: normal
                                              +

                                              Smart Connect task of a Kafka instance

                                              +

                                              1 minute

                                              kafka_partitions

                                              +

                                              message_delay

                                              Partition in a Kafka instance

                                              +

                                              Message Delay

                                              +

                                              Time elapsed between when a message is sent from the source and received by the target

                                              +

                                              Unit: ms

                                              +

                                              ≥ 0

                                              +

                                              Smart Connect task of a Kafka instance

                                              +

                                              1 minute

                                              kafka_groups-partitions

                                              +
                                              +
                                              +
                                              • A Smart Connect task that bidirectionally copies Kafka data is split into two tasks for monitoring: Smart Connect task name_source_0 and Smart Connect task name_source_1.
                                              • If all messages in a topic have aged before the next synchronization, there is no Kafka data to be synchronized. However, since the Kafka data synchronization metric uses the offset value that contains aged data, Kafka Data Synced per Minute will display the number of aged messages.
                                              +
                                              +
                                              +

                                              Dimension

                                              +
                                              + + + + - - - - - + + + + + + + + + + + + diff --git a/docs/dms/umn/kafka-ug-180418002.html b/docs/dms/umn/kafka-ug-180418002.html index bd88e26b..523b978b 100644 --- a/docs/dms/umn/kafka-ug-180418002.html +++ b/docs/dms/umn/kafka-ug-180418002.html @@ -1,8 +1,7 @@

                                              Viewing Kafka Audit Logs

                                              -

                                              Scenario

                                              With Cloud Trace Service (CTS), you can record operations associated with DMS for later query, audit, and backtrack operations.

                                              -
                                              +

                                              With Cloud Trace Service (CTS), you can record operations associated with DMS for later query, audit, and backtrack operations.

                                              Prerequisite

                                              CTS has been enabled.

                                              DMS Operations Supported by CTS

                                              @@ -231,6 +230,34 @@
                                              + + + + + + + + + + + + + + + +

                                              Key

                                              +

                                              Value

                                              +

                                              kafka_instance_id

                                              Partition consumer group in a Kafka instance

                                              +

                                              Kafka instance

                                              kafka_groups_topics

                                              +

                                              kafka_broker

                                              Topic consumer group in a Kafka instance

                                              +

                                              Kafka instance broker

                                              kafka_groups

                                              +

                                              kafka_topics

                                              Consumer group of a Kafka instance

                                              +

                                              Kafka instance topic

                                              +

                                              kafka_partitions

                                              +

                                              Partition in a Kafka instance

                                              +

                                              kafka_groups-partitions

                                              +

                                              Partition consumer group in a Kafka instance

                                              +

                                              kafka_groups_topics

                                              +

                                              Topic consumer group in a Kafka instance

                                              +

                                              kafka_groups

                                              +

                                              Consumer group of a Kafka instance

                                              deleteDMSBackendJobFailure

                                              Successfully enabling Smart Connect

                                              +

                                              kafka

                                              +

                                              createConnectorTaskSuccess

                                              +

                                              Successfully creating a Smart Connect task

                                              +

                                              kafka

                                              +

                                              createConnectorSinkTaskSuccess

                                              +

                                              Failing to enable Smart Connect

                                              +

                                              kafka

                                              +

                                              createConnectorTaskFailure

                                              +

                                              Failing to create a Smart Connect task

                                              +

                                              kafka

                                              +

                                              createConnectorSinkTaskFailure

                                              +

                                              Successfully creating a topic for a Kafka instance

                                              kafka

                                              diff --git a/docs/dms/umn/kafka-ug-180524001.html b/docs/dms/umn/kafka-ug-180524001.html index 4c0edf43..48433c9e 100644 --- a/docs/dms/umn/kafka-ug-180524001.html +++ b/docs/dms/umn/kafka-ug-180524001.html @@ -125,13 +125,14 @@
                                              -

                                              Configuring a Kafka Alarm Rule

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

                                                Select the region where your Kafka instance is located.

                                                +

                                                Procedure

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

                                                  Select the region where your Kafka instance is located.

                                                  -

                                                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                4. In the row containing the desired instance, click View Metric.

                                                  You are redirected to the Cloud Eye console page displaying metrics of the selected instance.

                                                  -

                                                5. Hover the mouse pointer over a metric and click to create an alarm rule for the metric.
                                                6. Specify the alarm details.

                                                  For more information about creating alarm rules, see Creating an Alarm Rule.

                                                  -
                                                  1. Set the alarm name and description.
                                                  2. Specify the alarm policy and alarm severity.

                                                    As shown in the following figure, if the original disk capacity usage is equal to or higher than 85% for three consecutive periods, an alarm is generated. If the alarm is not handled on time, an alarm notification is sent.

                                                    +

                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                  4. Go to the monitoring page in either of the following ways:

                                                    • Click View Metric in the row containing the desired Kafka instance.
                                                    • Click the desired Kafka instance to go to the instance details page. Choose Monitoring in the navigation pane.
                                                    +

                                                  5. Hover the mouse pointer over a metric and click to create an alarm rule for the metric. The Create Alarm Rule page is displayed.
                                                  6. Specify the alarm details.

                                                    For more information about creating alarm rules, see Creating an Alarm Rule.

                                                    +
                                                    1. Set the alarm name and description.
                                                    2. Set the alarm policy.

                                                      As shown in the following figure, if the original disk capacity usage is equal to or higher than 85% for three consecutive periods, an alarm is generated. If the alarm is not handled on time, an alarm notification is sent.

                                                      Figure 1 Setting the alarm policy and alarm severity
                                                      -
                                                    3. Set the alarm notification configurations. If you enable Alarm Notification, specify Notification Window, Notification Object, and Trigger Condition.
                                                    4. Click Create.
                                                    +
                                                  7. Set the alarm notification configurations.

                                                    If you enable Alarm Notification, specify Notification Window, Notification Object, and Trigger Condition.

                                                    +
                                                  8. Click Create.

                                                diff --git a/docs/dms/umn/kafka-ug-180604013.html b/docs/dms/umn/kafka-ug-180604013.html index a6a817ed..e9750a57 100644 --- a/docs/dms/umn/kafka-ug-180604013.html +++ b/docs/dms/umn/kafka-ug-180604013.html @@ -1,9 +1,8 @@

                                                Creating a Kafka Instance

                                                -

                                                Scenario

                                                Kafka instances are tenant-exclusive, and physically isolated in deployment. You can customize the computing capabilities and storage space of a Kafka instance as required.

                                                -
                                                -

                                                Prerequisites

                                                Before creating a Kafka instance, prepare the resources listed in Table 1.

                                                +

                                                Kafka instances are tenant-exclusive, and physically isolated in deployment. You can customize the computing capabilities and storage space of a Kafka instance as required.

                                                +

                                                Preparing Instance Dependencies

                                                Before creating a Kafka instance, prepare the resources listed in Table 1.

                                                @@ -31,7 +30,7 @@ - @@ -40,7 +39,7 @@ -
                                                Table 1 Kafka resources

                                                Resource

                                                EIP

                                                To create a Kafka instance and access it over a public network, create EIPs in advance.

                                                +

                                                To access a Kafka instance on a client over a public network, create EIPs in advance.

                                                Note the following when creating EIPs:

                                                • The EIPs must be created in the same region as the Kafka instance.
                                                • The number of EIPs must be the same as the number of Kafka instance brokers.
                                                • The Kafka console cannot identify IPv6 EIPs.

                                                KMS key

                                                To encrypt the disk for a Kafka instance, prepare a KMS key.

                                                +

                                                To encrypt the disk for a Kafka instance, create a KMS key.

                                                The KMS key must be created in the same region as the Kafka instance.

                                                For details about how to create a KMS key, see Creating a Key.

                                                @@ -50,31 +49,30 @@
                                                -

                                                Creating a Kafka Instance

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

                                                  Select a region near you to ensure the lowest latency possible.

                                                  -

                                                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                4. Click Create Instance in the upper right corner of the page.
                                                5. Specify Region, Project, and AZ.

                                                  Select one AZ or at least three AZs.

                                                  +

                                                  Procedure

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

                                                    Select a region near you to ensure the lowest latency possible.

                                                    +

                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                  4. Click Create Instance in the upper right corner of the page.
                                                  5. Select a region.

                                                    DMS for Kafka instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.

                                                    +

                                                  6. Select a Project.

                                                    Projects isolate compute, storage, and network resources across geographical regions. For each region, a preset project is available.

                                                    +

                                                  7. Select an AZ.

                                                    An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

                                                    +

                                                    Select one AZ or at least three AZs.

                                                  8. Enter an Instance Name.

                                                    You can customize a name that complies with the rules: 4–64 characters; starts with a letter; can contain only letters, digits, hyphens (-), and underscores (_).

                                                  9. Select an Enterprise Project.

                                                    This parameter is for enterprise users. An enterprise project manages cloud resources. The enterprise project management service unifies cloud resources in projects, and resources and members in a project. The default project is default.

                                                    -

                                                  10. Configure the following instance parameters:

                                                    Specifications: Select Cluster or Single-node.

                                                    -
                                                    • If you select Cluster, specify the version, broker flavor and quantity, disk type, and storage space to be supported by the cluster Kafka instance as required. Cluster instances support Kafka versions 2.3.0, 2.7, and 3.x.
                                                    • Single-node: Create a Kafka 2.7 instance with one broker. For details about single-node instances, see Comparing Single-node and Cluster Kafka Instances.
                                                    -

                                                    If you select Cluster, specify the version, broker flavor and quantity, disk type, and storage space to be supported by the Kafka instance as required.

                                                    -
                                                    1. Version: Cluster instances support Kafka 2.3.0, 2.7, and 3.x. The version cannot be changed once the instance is created.
                                                    2. CPU Architecture: The x86 architecture is supported.
                                                    3. Broker Flavor: Select a broker flavor that best fit your needs.

                                                      Maximum number of partitions per broker x Number of brokers = Maximum number of partitions of an instance. If the total number of partitions of all topics exceeds the upper limit of partitions, topic creation fails.

                                                      -
                                                    4. For Brokers, specify the broker quantity. A 3.x instance can only have three brokers (not changeable).
                                                    5. Storage space per broker: Disk type and size for storing the instance data.

                                                      The disk type cannot be changed once the Kafka instance is created.

                                                      -

                                                      The storage space is consumed by message replicas, logs, and metadata. Specify the storage space based on the expected service message size, the number of replicas, and the reserved disk space. Each Kafka broker reserves 33 GB disk space for storing logs and metadata.

                                                      +

                                                    6. Configure the following instance specifications:

                                                      Specifications: Select Cluster or Single-node.

                                                      +
                                                      • If you select Cluster, specify the version, broker flavor and quantity, disk type, and storage space to be supported by the cluster Kafka instance as required.
                                                        1. Version: Cluster instances support Kafka 2.3.0, 2.7, and 3.x. The version cannot be changed once the instance is created.
                                                        2. CPU Architecture: The x86 architecture is supported.
                                                        3. Broker Flavor: Select a broker flavor that best fit your needs.

                                                          Maximum number of partitions per broker x Number of brokers = Maximum number of partitions of an instance. If the total number of partitions of all topics exceeds the upper limit of partitions, topic creation fails.

                                                          +
                                                        4. For Brokers, specify the broker quantity. A 3.x instance can only have three brokers (not changeable).
                                                        5. Storage space per broker: Disk type and size for storing the instance data. The disk type cannot be changed once the Kafka instance is created.

                                                          The storage space is consumed by message replicas, logs, and metadata. Specify the storage space based on the expected service message size, the number of replicas, and the reserved disk space. Each Kafka broker reserves 33 GB disk space for storing logs and metadata.

                                                          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.

                                                          -

                                                          The disk supports high I/O and ultra-high I/O types. For more information, see Disk Types and Performance.

                                                          +

                                                          The disk type can be high I/O or ultra-high I/O. For more information, see Disk Types and Performance.

                                                          Each broker of a 3.x instance can only have 100 GB storage space (not changeable).

                                                        6. Disk Encryption: Specify whether to enable disk encryption.

                                                          Enabling disk encryption improves data security, but slows down disk read/write. Disk encryption depends on Key Management Service (KMS). If you enable disk encryption, select a KMS key. This parameter cannot be modified once the Kafka instance is created.

                                                          -
                                                        7. Capacity Threshold Policy: Policy used when the disk usage reaches the threshold. The 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.
                                                          +
                                                        8. Capacity Threshold Policy: Policy used when the disk usage reaches the threshold. The 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.
                                                        -

                                                        If you select Single-node, a v2.7 instance with one broker will be created.

                                                        -
                                                        1. Version: Kafka version, which can only be 2.7.
                                                        2. CPU Architecture: The x86 architecture is supported.
                                                        3. Broker Flavor: Select a broker flavor that best fit your needs.
                                                        4. Brokers: The instance can have only one broker.
                                                        5. Storage space per broker: Disk type and size for storing the instance data.

                                                          The disk type cannot be changed once the Kafka instance is created.

                                                          -

                                                          The storage space is consumed by message replicas, logs, and metadata. Specify the storage space based on the expected service message size, the number of replicas, and the reserved disk space. Each Kafka broker reserves 33 GB disk space for storing logs and metadata.

                                                          +
                                                        6. Single-node: Create a Kafka 2.7 instance with one broker. For details about single-node instances, see Comparing Single-node and Cluster Kafka Instances.
                                                          1. Version: Kafka version, which can only be 2.7.
                                                          2. CPU Architecture: The x86 architecture is supported.
                                                          3. Broker Flavor: Select a broker flavor that best fit your needs.
                                                          4. Brokers: The instance can have only one broker.
                                                          5. Storage space per broker: Disk type and size for storing the instance data. The disk type cannot be changed once the Kafka instance is created.

                                                            The storage space is consumed by message replicas, logs, and metadata. Specify the storage space based on the expected service message size, the number of replicas, and the reserved disk space. Each Kafka broker reserves 33 GB disk space for storing logs and metadata.

                                                            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.

                                                            -

                                                            The disk supports high I/O and ultra-high I/O types. For more information, see Disk Types and Performance.

                                                            +

                                                            The disk type can be high I/O or ultra-high I/O. For more information, see Disk Types and Performance.

                                                          6. Disk Encryption: Specify whether to enable disk encryption.

                                                            Enabling disk encryption improves data security, but slows down disk read/write. Disk encryption depends on Key Management Service (KMS). If you enable disk encryption, select a KMS key. This parameter cannot be modified once the Kafka instance is created.

                                                            -
                                                          7. Capacity Threshold Policy: Policy used when the disk usage reaches the threshold. The 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.
                                                            +
                                                          8. Capacity Threshold Policy: Policy used when the disk usage reaches the threshold. The 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.
                                                          -
                                                          Figure 1 Single-node instances
                                                          +
                                                          Figure 1 Single-node instance specifications
                                                          +

                                                    7. Configure the instance network parameters.

                                                      • Select the created VPC and subnet from the VPC drop-down list.

                                                        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.

                                                        @@ -82,53 +80,53 @@

                                                        Before accessing a Kafka instance on the client, configure security group rules based on the access mode. For details about security group rules, see Table 2.

                                                    8. Configure the instance access mode.

                                                      -

                                                      Table 2 Instance access modes

                                                      Public or Private Network

                                                      +
                                                      - - - - - - - - - - - - - - @@ -140,112 +138,124 @@

                                                      The security protocol, SASL/PLAIN mechanism, username, and password are described as follows.

                                                      -
                                                      Table 2 Instance access modes

                                                      Public or Private Network

                                                      Plaintext or Ciphertext

                                                      +

                                                      Plaintext or Ciphertext

                                                      Description

                                                      +

                                                      Description

                                                      Private Network Access

                                                      +

                                                      Private Network Access

                                                      Plaintext Access

                                                      +

                                                      Plaintext Access

                                                      Clients connect to the Kafka instance without SASL authentication.

                                                      +

                                                      Clients connect to the Kafka instance without SASL authentication.

                                                      Once enabled, private network access cannot be disabled. Enable plaintext or ciphertext access, or both.

                                                      Ciphertext Access

                                                      +

                                                      Ciphertext Access

                                                      Clients connect to the Kafka instance with SASL authentication.

                                                      +

                                                      Clients connect to the Kafka instance with SASL authentication.

                                                      Once enabled, private network access cannot be disabled. Enable plaintext or ciphertext access, or both. To disable ciphertext access, contact customer service.

                                                      If you enable Ciphertext Access, specify a security protocol, SASL/PLAIN, username, and password.

                                                      After an instance is created, disabling and re-enabling Ciphertext Access do not affect users.

                                                      Public Network Access

                                                      +

                                                      Public Network Access

                                                      Plaintext Access

                                                      +

                                                      Plaintext Access

                                                      Clients connect to the Kafka instance without SASL authentication.

                                                      +

                                                      Clients connect to the Kafka instance without SASL authentication.

                                                      Enable or disable plaintext access, and configure addresses for public network access.

                                                      Ciphertext Access

                                                      +

                                                      Ciphertext Access

                                                      Clients connect to the Kafka instance with SASL authentication.

                                                      +

                                                      Clients connect to the Kafka instance with SASL authentication.

                                                      Enable or disable ciphertext access, and configure addresses for public network access.

                                                      If you enable Ciphertext Access, specify a security protocol, SASL/PLAIN, username, and password.

                                                      After an instance is created, disabling and re-enabling Ciphertext Access do not affect users.

                                                      Public IP Addresses

                                                      +

                                                      Public IP Addresses

                                                      Select the number of public IP addresses as required.

                                                      +

                                                      Select the number of public IP addresses as required.

                                                      If EIPs are insufficient, click Create Elastic IP to create EIPs. Then, return to the Kafka console and click next to Public IP Address to refresh the public IP address list.

                                                      Kafka instances only support IPv4 EIPs.
                                                      Table 3 Ciphertext access parameters

                                                      Parameter

                                                      +
                                                      - - - - - - - - - - + + + + - - -
                                                      Table 3 Ciphertext access parameters

                                                      Parameter

                                                      Value

                                                      +

                                                      Value

                                                      Description

                                                      +

                                                      Description

                                                      Security Protocol

                                                      +

                                                      Security Protocol

                                                      SASL_SSL

                                                      +

                                                      SASL_SSL

                                                      SASL is used for authentication. Data is encrypted with SSL certificates for high-security transmission.

                                                      +

                                                      SASL is used for authentication. Data is encrypted with SSL certificates for high-security transmission.

                                                      SCRAM-SHA-512 is enabled by default. To use PLAIN, enable SASL/PLAIN.

                                                      What are SCRAM-SHA-512 and PLAIN mechanisms?

                                                      • SCRAM-SHA-512: uses the hash algorithm to generate credentials for usernames and passwords to verify identities. SCRAM-SHA-512 is more secure than PLAIN.
                                                      • PLAIN: a simple username and password verification mechanism.

                                                      SASL_PLAINTEXT

                                                      +

                                                      SASL_PLAINTEXT

                                                      SASL is used for authentication. Data is transmitted in plaintext for high performance.

                                                      +

                                                      SASL is used for authentication. Data is transmitted in plaintext for high performance.

                                                      SCRAM-SHA-512 is enabled by default. To use PLAIN, enable SASL/PLAIN. SCRAM-SHA-512 authentication is recommended for plaintext transmission.

                                                      SASL/PLAIN

                                                      +

                                                      Cross-VPC Access Protocol

                                                      -

                                                      +

                                                      -

                                                      • If SASL/PLAIN is disabled, the SCRAM-SHA-512 mechanism is used for username and password authentication.
                                                      • If SASL/PLAIN is enabled, both the SCRAM-SHA-512 and PLAIN mechanisms are supported. You can select either of them as required.
                                                      +
                                                      • When Plaintext Access is enabled and Ciphertext Access is disabled, PLAINTEXT is used for Cross-VPC Access Protocol.
                                                      • When Ciphertext Access is enabled and Security Protocol is SASL_SSL, SASL_SSL is used for Cross-VPC Access Protocol.
                                                      • When Ciphertext Access is enabled and Security Protocol is SASL_PLAINTEXT, SASL_PLAINTEXT is used for Cross-VPC Access Protocol.
                                                      +

                                                      Fixed once the instance is created.

                                                      +

                                                      SASL/PLAIN

                                                      +

                                                      -

                                                      +
                                                      • If SASL/PLAIN is disabled, the SCRAM-SHA-512 mechanism is used for username and password authentication.
                                                      • If SASL/PLAIN is enabled, both the SCRAM-SHA-512 and PLAIN mechanisms are supported. You can select either of them as required.

                                                      The SASL/PLAIN setting cannot be changed once ciphertext access is enabled.

                                                      Username and Password

                                                      +

                                                      Username and Password

                                                      -

                                                      +

                                                      -

                                                      Username and password used by the client to connect to the Kafka instance.

                                                      +

                                                      Username and password used by the client to connect to the Kafka instance.

                                                      A username should contain 4 to 64 characters, start with a letter, and contain only letters, digits, hyphens (-), and underscores (_).

                                                      A password must meet the following requirements:

                                                      -
                                                      • Contains 8 to 32 characters.
                                                      • Contains at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters `~! @#$ %^&*()-_=+\|[{}];:'",<.>? and spaces, and cannot start with a hyphen (-).
                                                      • Cannot be the username spelled forwards or backwards.
                                                      +
                                                      • Contains 8 to 32 characters.
                                                      • Cannot start with a hyphen (-) and must contain at least three of the following character types: uppercase letters, lowercase letters, digits, spaces, and special characters `~! @#$ %^&*()-_=+\|[{}];:'",<.>?
                                                      • Cannot be the username spelled forwards or backwards.

                                                      The username cannot be changed once ciphertext access is enabled.
                                                      -

                                                    9. Click Advanced Settings to configure more parameters.

                                                      1. Configure Automatic Topic Creation.

                                                        This setting is disabled by default. You can enable or disable it as required.

                                                        -

                                                        If this option is enabled, a topic will be automatically created when a message is produced in or consumed from a topic that does not exist. By default, the topic has parameters listed in Table 4.

                                                        -

                                                        After you change the value of the log.retention.hours, default.replication.factor, or num.partitions parameter, the value will be used in later topics that are automatically created. For example, assume that num.partitions is changed to 5, an automatically created topic has parameters listed in Table 4.

                                                        +

                                                      2. Click Advanced Settings to configure more parameters.

                                                        1. Configure Smart Connect.

                                                          Smart Connect is used for data synchronization between heterogeneous systems. You can configure Smart Connect tasks to synchronize data between Kafka and another cloud service or between two Kafka instances.

                                                          +

                                                          Enabling Smart Connect creates two brokers.

                                                          +

                                                          Single-node instances do not have this parameter. Kafka 3.x instances do not support this parameter.

                                                          +
                                                          +
                                                        2. Configure Automatic Topic Creation.

                                                          This setting is disabled by default. You can enable or disable it as required.

                                                          +

                                                          If this option is enabled, a topic will be automatically created when a message is produced in or consumed from a topic that does not exist. The default topic parameters are listed in Table 4.

                                                          +

                                                          After you change the value of the log.retention.hours (retention period), default.replication.factor (replica quantity), or num.partitions (partition quantity) parameter, the value will be used in later topics that are automatically created. For example, assume that num.partitions is changed to 5, an automatically created topic has parameters listed in Table 4.

                                                          -
                                                          Table 4 Topic parameters

                                                          Parameter

                                                          +
                                                          - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/dms/umn/kafka-ug-180604014.html b/docs/dms/umn/kafka-ug-180604014.html index 6c762356..068925f3 100644 --- a/docs/dms/umn/kafka-ug-180604014.html +++ b/docs/dms/umn/kafka-ug-180604014.html @@ -1,56 +1,54 @@

                                                          Viewing and Modifying Basic Information of a Kafka Instance

                                                          -

                                                          Scenario

                                                          This section describes how to view the details, and modify the basic information of a Kafka instance on the console.

                                                          -

                                                          After creating a Kafka instance, you can modify some parameters of it as required, including the instance name, description, security group, and capacity threshold policy.

                                                          +

                                                          After creating a Kafka instance, you can view the details or modify some parameters of it on the console as required. These parameters include the instance name, description, security group, and capacity threshold policy.

                                                          Single-node instances do not support reconfiguration of private network access.

                                                          -

                                                          Prerequisite

                                                          You can modify basic information of a Kafka instance when the instance is in the Running state.

                                                          Viewing Kafka Instance Details

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

                                                            Select the region where your Kafka instance is located.

                                                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                          4. Search for a Kafka instance by specifying filters. You can filter instances by tag, status, name, version, flavor, used/available storage space, maximum partitions, billing mode, and enterprise project.Only enterprise users can filter instances by enterprise projects. For Kafka instance statuses, see Table 1.

                                                            -

                                                          Table 4 Topic parameters

                                                          Parameter

                                                          Default Value

                                                          +

                                                          Default Value

                                                          Modified Value

                                                          +

                                                          Modified Value

                                                          Partitions

                                                          +

                                                          Partitions

                                                          3

                                                          +

                                                          3

                                                          5

                                                          +

                                                          5

                                                          Replicas

                                                          +

                                                          Replicas

                                                          3

                                                          +

                                                          3

                                                          3

                                                          +

                                                          3

                                                          Aging Time (h)

                                                          +

                                                          Aging Time (h)

                                                          72

                                                          +

                                                          72

                                                          72

                                                          +

                                                          72

                                                          Synchronous Replication

                                                          +

                                                          Synchronous Replication

                                                          Disabled

                                                          +

                                                          Disabled

                                                          Disabled

                                                          +

                                                          Disabled

                                                          Synchronous Flushing

                                                          +

                                                          Synchronous Flushing

                                                          Disabled

                                                          +

                                                          Disabled

                                                          Disabled

                                                          +

                                                          Disabled

                                                          Message Timestamp

                                                          +

                                                          Message Timestamp

                                                          CreateTime

                                                          +

                                                          CreateTime

                                                          CreateTime

                                                          +

                                                          CreateTime

                                                          Max. Message Size (bytes)

                                                          +

                                                          Max. Message Size (bytes)

                                                          10,485,760

                                                          +

                                                          10,485,760

                                                          10,485,760

                                                          +

                                                          10,485,760
                                                          Table 1 Kafka instance status description

                                                          Status

                                                          +
                                                          - - - - - - - - - - - - - - - @@ -59,114 +57,114 @@

                                                        3. Click the name of the desired Kafka instance and view detailed information about the instance on the Basic Information tab page.

                                                          Table 2 describes the parameters for connecting to a Kafka instance. For details about other parameters, see the Basic Information tab page of the Kafka instance on the console.

                                                          -
                                                          4. Table 1 Kafka instance status description

                                                          Status

                                                          Description

                                                          +

                                                          Description

                                                          Creating

                                                          +

                                                          Creating

                                                          The instance is being created.

                                                          +

                                                          The instance is being created.

                                                          Creation failed

                                                          +

                                                          Creation failed

                                                          The instance failed to be created.

                                                          +

                                                          The instance failed to be created.

                                                          Running

                                                          +

                                                          Running

                                                          The instance is running properly.

                                                          +

                                                          The instance is running properly.

                                                          Only instances in the Running state can provide services.

                                                          Faulty

                                                          +

                                                          Faulty

                                                          The instance is not running properly.

                                                          +

                                                          The instance is not running properly.

                                                          Restarting

                                                          +

                                                          Restarting

                                                          The instance is being restarted.

                                                          +

                                                          The instance is being restarted.

                                                          Changing

                                                          +

                                                          Changing

                                                          The instance specifications or public access configurations are being modified.

                                                          +

                                                          The instance specifications or public access configurations are being modified.

                                                          Change failed

                                                          +

                                                          Change failed

                                                          The instance specifications or public access configurations failed to be modified.

                                                          +

                                                          The instance specifications or public access configurations failed to be modified.

                                                          You cannot restart, delete, or modify an instance in the Change failed state. Contact customer service.
                                                          Table 2 Connection parameters

                                                          Section

                                                          +
                                                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -175,84 +173,84 @@

                                                          -

                                                          Modifying Basic Information of a Kafka Instance

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

                                                            Select the region where your Kafka instance is located.

                                                            +

                                                            Modifying Basic Information of a Kafka Instance

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

                                                              Select the region where your Kafka instance is located.

                                                            3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                            4. Click the desired Kafka instance to view its details.
                                                            5. Modify the following parameters if needed:

                                                              -

                                                          Table 2 Connection parameters

                                                          Section

                                                          Parameter

                                                          +

                                                          Parameter

                                                          Sub-Parameter

                                                          +

                                                          Sub-Parameter

                                                          Description

                                                          +

                                                          Description

                                                          Connection

                                                          +

                                                          Connection

                                                          Username

                                                          +

                                                          Username

                                                          -

                                                          +

                                                          -

                                                          Username for accessing the instance with ciphertext access enabled.

                                                          +

                                                          Username for accessing the instance with ciphertext access enabled.

                                                          Private Network Access

                                                          +

                                                          Private Network Access

                                                          Plaintext Access

                                                          +

                                                          Plaintext Access

                                                          Indicates whether plaintext access is enabled.

                                                          +

                                                          Indicates whether plaintext access is enabled.

                                                          Address (Private Network, Plaintext)

                                                          +

                                                          Address (Private Network, Plaintext)

                                                          This parameter is displayed only after you enable Plaintext Access.

                                                          +

                                                          This parameter is displayed only after you enable Plaintext Access.

                                                          Ciphertext Access

                                                          +

                                                          Ciphertext Access

                                                          Indicates whether ciphertext access is enabled.

                                                          +

                                                          Indicates whether ciphertext access is enabled.

                                                          This function is unavailable for single-node instances.

                                                          Address (Private Network, Ciphertext)

                                                          +

                                                          Address (Private Network, Ciphertext)

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          +

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          Security Protocol

                                                          +

                                                          Security Protocol

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          +

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          Public Network Access

                                                          +

                                                          Public Network Access

                                                          Toggle switch

                                                          +

                                                          Toggle switch

                                                          Indicates whether public access has been enabled.

                                                          +

                                                          Indicates whether public access has been enabled.

                                                          Plaintext Access

                                                          +

                                                          Plaintext Access

                                                          This parameter is displayed only when Public Access is enabled.

                                                          +

                                                          This parameter is displayed only when Public Access is enabled.

                                                          Indicates whether plaintext access is enabled.

                                                          Address (Public Network, Plaintext)

                                                          +

                                                          Address (Public Network, Plaintext)

                                                          This parameter is displayed only after you enable Plaintext Access.

                                                          +

                                                          This parameter is displayed only after you enable Plaintext Access.

                                                          Ciphertext Access

                                                          +

                                                          Ciphertext Access

                                                          This parameter is displayed only when Public Access is enabled.

                                                          +

                                                          This parameter is displayed only when Public Access is enabled.

                                                          Indicates whether ciphertext access is enabled.

                                                          This function is unavailable for single-node instances.

                                                          Address (Public Network, Ciphertext)

                                                          +

                                                          Address (Public Network, Ciphertext)

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          +

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          Security Protocol

                                                          +

                                                          Security Protocol

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          +

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          SASL Mechanism

                                                          +

                                                          SASL Mechanism

                                                          -

                                                          +

                                                          -

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          +

                                                          This parameter is displayed only after you enable Ciphertext Access.

                                                          SSL Certificate

                                                          +

                                                          SSL Certificate

                                                          -

                                                          +

                                                          -

                                                          This parameter is displayed only when SASL_SSL is enabled.

                                                          +

                                                          This parameter is displayed only when SASL_SSL is enabled.

                                                          Click Download to download the SSL certificate for accessing the instance.
                                                          Table 3 Modifiable Kafka parameters

                                                          Parameter

                                                          +
                                                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/dms/umn/kafka-ug-180604015.html b/docs/dms/umn/kafka-ug-180604015.html index ee836265..241965e0 100644 --- a/docs/dms/umn/kafka-ug-180604015.html +++ b/docs/dms/umn/kafka-ug-180604015.html @@ -1,13 +1,12 @@

                                                          Restarting a Kafka Instance

                                                          -

                                                          Scenario

                                                          Restart one or more Kafka instances at a time on the DMS console.

                                                          +

                                                          You can restart one or more Kafka instances in batches on the DMS console.

                                                          When a Kafka instance is being restarted, message retrieval and creation requests of clients will be rejected.

                                                          -

                                                          Prerequisites

                                                          The status of the Kafka instance you want to restart is either Running or Faulty.

                                                          -

                                                          Restarting a Kafka Instance

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

                                                            Select the region where your Kafka instance is located.

                                                            +

                                                            Procedure

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

                                                              Select the region where your Kafka instance is located.

                                                            3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                            4. Restart Kafka instances using one of the following methods:

                                                              • Select one or more Kafka instances and click Restart in the upper left corner.
                                                              • In the row containing the desired instance, click Restart.
                                                              • Click the desired Kafka instance to view its details. In the upper right corner, click Restart.

                                                            5. In the Restart Instance dialog box, click Yes to restart the Kafka instance.

                                                              It takes 3 to 15 minutes to restart a Kafka instance. After the instance is successfully restarted, its status should be Running.

                                                              diff --git a/docs/dms/umn/kafka-ug-180604016.html b/docs/dms/umn/kafka-ug-180604016.html index 77f93ffe..696f750c 100644 --- a/docs/dms/umn/kafka-ug-180604016.html +++ b/docs/dms/umn/kafka-ug-180604016.html @@ -1,13 +1,12 @@

                                                              Deleting Kafka Instances

                                                              -

                                                              Scenario

                                                              Delete one or more Kafka instances at a time on the DMS console.

                                                              +

                                                              Delete one or more Kafka instances at a time on the DMS console.

                                                              Deleting a Kafka instance will delete the data in the instance without any backup. Exercise caution when performing this operation.

                                                              -

                                                              Prerequisites

                                                              The status of the Kafka instance you want to delete is Running or Faulty.

                                                              -

                                                              Deleting Kafka Instances

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

                                                                Select the region where your Kafka instance is located.

                                                                +

                                                                Procedure

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

                                                                  Select the region where your Kafka instance is located.

                                                                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                4. Delete pay-per-use Kafka instances in either of the following ways:

                                                                  • Select one or more Kafka instances and click Delete in the upper left corner.
                                                                  • In the row containing the Kafka instance to be deleted, choose More > Delete.
                                                                  • Click the desired Kafka instance to view its details. In the upper right corner, choose More > Delete.

                                                                  Kafka instances in the Creating, Changing, Change failed, or Restarting state cannot be deleted.

                                                                  diff --git a/docs/dms/umn/kafka-ug-180604018.html b/docs/dms/umn/kafka-ug-180604018.html index f2f20c35..fe0126ca 100644 --- a/docs/dms/umn/kafka-ug-180604018.html +++ b/docs/dms/umn/kafka-ug-180604018.html @@ -1,9 +1,9 @@

                                                                  Creating a Kafka Topic

                                                                  -

                                                                  Topics store messages created by producers and subscribed by consumers. If automatic topic creation is not enabled during Kafka instance creation, you need to manually create topics. If automatic topic creation has been enabled for the instance, this operation is optional.

                                                                  -

                                                                  Automatic topic creation: A topic will be automatically created when a message is produced in or consumed from a topic that does not exist. By default, the topic has parameters listed in Table 1.

                                                                  -

                                                                  After you change the value of the log.retention.hours, default.replication.factor, or num.partitions parameter, the value will be used in later topics that are automatically created. For example, assume that num.partitions is changed to 5, an automatically created topic has parameters listed in Table 1.

                                                                  +

                                                                  Topics store messages created by producers and subscribed by consumers. If Automatic Topic Creation is not enabled during Kafka instance creation, you need to manually create topics. If Automatic Topic Creation has been enabled for the instance, this operation is optional.

                                                                  +

                                                                  Automatic Topic Creation indicates that a topic will be automatically created when a message is produced in or consumed from a topic that does not exist. The default topic parameters are listed in Table 1.

                                                                  +

                                                                  After you change the value of the log.retention.hours (retention period), default.replication.factor (replica quantity), or num.partitions (partition quantity) parameter, the value will be used in later topics that are automatically created. For example, assume that num.partitions is changed to 5, an automatically created topic has parameters listed in Table 1.

                                                          Table 3 Modifiable Kafka parameters

                                                          Parameter

                                                          How to Modify

                                                          +

                                                          How to Modify

                                                          Result

                                                          +

                                                          Result

                                                          Instance Name

                                                          +

                                                          Instance Name

                                                          Click , enter a new name, and click .

                                                          +

                                                          Click , enter a new name, and click .

                                                          Naming rules: 4–64 characters; starts with a letter; can contain only letters, digits, hyphens (-), and underscores (_).

                                                          The modification result is displayed in the upper right corner of the page.

                                                          +

                                                          The modification result is displayed in the upper right corner of the page.

                                                          Enterprise Project

                                                          +

                                                          Enterprise Project

                                                          Click , select a new enterprise project from the drop-down list, and click .

                                                          +

                                                          Click , select a new enterprise project from the drop-down list, and click .

                                                          Only for enterprise users. Modifying this parameter does not restart the instance.

                                                          The modification result is displayed in the upper right corner of the page.

                                                          +

                                                          The modification result is displayed in the upper right corner of the page.

                                                          Description

                                                          +

                                                          Description

                                                          Click , enter a new description, and click .

                                                          +

                                                          Click , enter a new description, and click .

                                                          0 to 1024 characters.

                                                          The modification result is displayed in the upper right corner of the page.

                                                          +

                                                          The modification result is displayed in the upper right corner of the page.

                                                          Security Group

                                                          +

                                                          Security Group

                                                          Click , select a new security group from the drop-down list, and click .

                                                          +

                                                          Click , select a new security group from the drop-down list, and click .

                                                          Modifying this parameter does not restart the instance.

                                                          The modification result is displayed in the upper right corner of the page.

                                                          +

                                                          The modification result is displayed in the upper right corner of the page.

                                                          Private Network Access

                                                          +

                                                          Private Network Access

                                                          See Configuring Plaintext or Ciphertext Access to Kafka Instances.

                                                          +

                                                          See Configuring Plaintext or Ciphertext Access to Kafka Instances.

                                                          You will be redirected to the Background Tasks page, which displays the modification progress and result.

                                                          +

                                                          You will be redirected to the Background Tasks page, which displays the modification progress and result.

                                                          Public Access

                                                          +

                                                          Public Access

                                                          See Configuring Kafka Public Access.

                                                          +

                                                          See Configuring Kafka Public Access.

                                                          You will be redirected to the Background Tasks page, which displays the modification progress and result.

                                                          +

                                                          You will be redirected to the Background Tasks page, which displays the modification progress and result.

                                                          Capacity Threshold Policy

                                                          +

                                                          Capacity Threshold Policy

                                                          Click the desired policy. In the displayed Confirm dialog box, click OK.

                                                          +

                                                          Click the desired policy. In the displayed Confirm dialog box, click OK.

                                                          Modifying this parameter does not restart the instance.

                                                          You will be redirected to the Background Tasks page, which displays the modification progress and result.

                                                          +

                                                          You will be redirected to the Background Tasks page, which displays the modification progress and result.

                                                          Automatic Topic Creation

                                                          +

                                                          Automatic Topic Creation

                                                          Enable/Disable this Automatic Topic Creation. In the displayed Confirm dialog box, click OK.

                                                          +

                                                          Enable/Disable this Automatic Topic Creation. In the displayed Confirm dialog box, click OK.

                                                          Changing this option may restart the instance.

                                                          You will be redirected to the Background Tasks page, which displays the modification progress and result.

                                                          +

                                                          You will be redirected to the Background Tasks page, which displays the modification progress and result.

                                                          Cross-VPC Access

                                                          +

                                                          Cross-VPC Access

                                                          See Accessing Kafka Using a VPC Endpoint Across VPCs and Accessing Kafka in a Public Network Using DNAT.

                                                          +

                                                          See Accessing Kafka Using a VPC Endpoint Across VPCs and Accessing Kafka in a Public Network Using DNAT.

                                                          The modification result is displayed in the upper right corner of the page.

                                                          +

                                                          The modification result is displayed in the upper right corner of the page.
                                                          @@ -66,73 +66,73 @@
                                                          Table 1 Topic parameters

                                                          Parameter

                                                          Methods that can be used to manually create a topic:

                                                          - +

                                                          Constraints

                                                          • The total number of partitions in topics is limited. When the partition quantity limit is reached, you can no longer create topics. The total number of partitions varies by instance specifications. For details, see Specifications.
                                                          • If an instance node is faulty, an internal service error may be reported when you query messages in a topic with only one replica. Therefore, you are not advised using a topic with only one replica.
                                                          -

                                                          Method 1: Creating a Topic on the Console

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

                                                            Select the region where your Kafka instance is located.

                                                            +

                                                            Creating a Topic (Console)

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

                                                              Select the region where your Kafka instance is located.

                                                              -

                                                            3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                            4. Click the desired Kafka instance to view the instance details.
                                                            5. In the navigation pane, choose Topics. Then click Create Topic.

                                                              Figure 1 Creating a topic
                                                              -

                                                            6. Specify the topic parameters listed in the following table.

                                                              -

                                                              Table 2 Topic parameters

                                                              Parameter

                                                              +

                                                            7. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                            8. Click the desired Kafka instance to view the instance details.
                                                            9. In the navigation pane, choose Topics. Then click Create Topic.
                                                            10. Enter a topic name, specify other parameters, and click OK.

                                                              Figure 1 Creating a topic
                                                              + +
                                                              - - - - - - - - - - - - - - - - - @@ -140,14 +140,56 @@
                                                              Table 2 Topic parameters

                                                              Parameter

                                                              Description

                                                              +

                                                              Description

                                                              Topic Name

                                                              +

                                                              Topic Name

                                                              Customize a name that contains 3 to 200 characters, starts with a letter or underscore (_), and contains only letters, digits, periods (.), hyphens (-), and underscores (_).

                                                              +

                                                              Customize a name that contains 3 to 200 characters, starts with a letter or underscore (_), and contains only letters, digits, periods (.), hyphens (-), and underscores (_).

                                                              The name must be different from preset topics:

                                                              -
                                                              • _consumer_offsets
                                                              • _transaction_state
                                                              • _trace
                                                              • _connect-status
                                                              • _connect-configs
                                                              • _connect-offsets
                                                              +
                                                              • __consumer_offsets
                                                              • __transaction_state
                                                              • __trace
                                                              • __connect-status
                                                              • __connect-configs
                                                              • __connect-offsets

                                                              Once the topic is created, you cannot modify its name.

                                                              Partitions

                                                              +

                                                              Partitions

                                                              Number of partitions in the topic.

                                                              +

                                                              Number of partitions in the topic.

                                                              If the number of partitions is the same as that of consumers, the larger the partitions, the higher the consumption concurrency.

                                                              If this parameter is set to 1, messages will be retrieved in the FIFO order.

                                                              Value range: 1 to 200

                                                              Default value: 3

                                                              Replicas

                                                              +

                                                              Replicas

                                                              A higher number of replicas delivers higher reliability. Data is automatically backed up on each replica. When one Kafka broker becomes faulty, data is still available on other brokers.

                                                              +

                                                              A higher number of replicas delivers higher reliability. Data is automatically backed up on each replica. When one Kafka broker becomes faulty, data is still available on other brokers.

                                                              If this parameter is set to 1, only one set of data is available.

                                                              Value range: 1 to number of brokers

                                                              NOTE:

                                                              If an instance node is faulty, an internal service error may be reported when you query messages in a topic with only one replica. Therefore, you are not advised using a topic with only one replica.

                                                              Aging Time (h)

                                                              +

                                                              Aging Time (h)

                                                              The period that messages are retained for. Consumers must retrieve messages before this period ends. Otherwise, the messages will be deleted and can no longer be consumed.

                                                              +

                                                              The period that messages are retained for. Consumers must retrieve messages before this period ends. Otherwise, the messages will be deleted and can no longer be consumed.

                                                              Value range: 1–720

                                                              Default value: 72

                                                              Synchronous Replication

                                                              +

                                                              Synchronous Replication

                                                              A message is returned to the client only after the message creation request has been received and the message has been acknowledged by all replicas.

                                                              +

                                                              A message is returned to the client only after the message creation request has been received and the message has been acknowledged by all replicas.

                                                              After enabling this, set the parameter acks to all or -1 in the configuration file or production code on the producer client.

                                                              If there is only one replica, synchronous replication cannot be enabled.

                                                              Synchronous Flushing

                                                              +

                                                              Synchronous Flushing

                                                              • Enabled: A message is immediately flushed to disk once it is created, bringing higher reliability.
                                                              • Disabled: A message is stored in the memory instead of being immediately flushed to disk once created.
                                                              +

                                                              A message is immediately flushed to disk once it is produced, bringing higher reliability. When this option is disabled, a message is stored in the memory instead of being immediately flushed to disk once produced.

                                                              Message Timestamp

                                                              +

                                                              Message Timestamp

                                                              Timestamp type of a message. Options:

                                                              +

                                                              Timestamp type of a message. Options:

                                                              • CreateTime: time when the producer created the message.
                                                              • LogAppendTime: time when the broker appended the message to the log.

                                                              Max. Message Size

                                                              +

                                                              Max. Message Size

                                                              Maximum batch processing size allowed by Kafka. If message compression is enabled in the client configuration file or code of producers, this parameter indicates the size after compression.

                                                              +

                                                              Maximum batch processing size allowed by Kafka. If message compression is enabled in the client configuration file or code of producers, this parameter indicates the size after compression.

                                                              If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that they can fetch record batches this large.

                                                              Value range: 0 to 10,485,760
                                                              -

                                                            11. Click OK.
                                                              12. +

                                                              -

                                                              Method 2: Creating a Topic by Using Kafka CLI

                                                              If your client is v2.2 or later, you can use kafka-topics.sh to create topics and manage topic parameters.

                                                              +

                                                              Creating a Topic (Client)

                                                              If your client is v2.2 or later, you can use kafka-topics.sh to create topics and manage topic parameters.

                                                              • If a topic name starts with a special character, for example, an underscore (_) or a number sign (#), monitoring data cannot be displayed.
                                                              • For an instance with ciphertext access enabled, if allow.everyone.if.no.acl.found is set to false, topics cannot be created through the client.
                                                              • For a Kafka instance with ciphertext access disabled, run the following command in the /bin directory of the Kafka client:
                                                                ./kafka-topics.sh --create --topic ${topic-name} --bootstrap-server ${connection-address} --partitions ${number-of-partitions} --replication-factor ${number-of-replicas}
                                                                -
                                                              • For a Kafka instance with ciphertext access enabled, do as follows:
                                                                1. (Optional) For the Kafka security protocol, is SASL_PLAINTEXT or SASL_SSL used?
                                                                  • SASL_PLAINTEXT: Skip this step if the username and password are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password by referring to 3.
                                                                  • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password, and the SSL certificate configuration by referring to 3.
                                                                  -
                                                                2. Run the following command in the /bin directory of the Kafka client:
                                                                  ./kafka-topics.sh --create --topic ${topic-name} --bootstrap-server ${connection-address} --partitions ${number-of-partitions} --replication-factor ${number-of-replicas} --command-config ./config/ssl-user-config.properties
                                                                  +

                                                                  Parameter description:

                                                                  +
                                                                  • topic-name: topic name, which can be customized.
                                                                  • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                                                  • number-of-partitions: number of partitions in a topic.
                                                                  • number-of-replicas: number of replicas in a topic.
                                                                  +

                                                                  Example:

                                                                  +
                                                                  [root@ecs-kafka bin]# ./kafka-topics.sh --create --topic topic-01 --bootstrap-server 192.168.xx.xx:9092,192.168.xx.xx:9092,192.168.xx.xx:9092 --partitions 3 --replication-factor 3
+Created topic topic-01.
+[root@ecs-kafka bin]#
                                                                  +
                                                                3. For a Kafka instance with ciphertext access enabled, do as follows:
                                                                  1. (Optional) Modify the client configuration file.
                                                                    View Security Protocol in the Connection area on the Basic Information page on the Kafka console. The configuration settings vary depending on the protocol.
                                                                    • SASL_PLAINTEXT: Skip this step if the username and password are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                                                      security.protocol=SASL_PLAINTEXT
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                                                      +

                                                                      Parameter description: username and password are the ones you set when enabling ciphertext access for the first time or when creating a user.

                                                                      +
                                                                    • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                                                      security.protocol=SASL_SSL
+ssl.truststore.location={ssl_truststore_path}
+ssl.truststore.password=dms@kafka
+ssl.endpoint.identification.algorithm=
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                                                      +

                                                                      Parameter description:

                                                                      +
                                                                      • ssl.truststore.location: path for storing the client.jks certificate. Even in Windows, you need to use slashes (/) for the certificate path. Do not use backslashes (\), which are used by default for paths in Windows. Otherwise, the client will fail to obtain the certificate.
                                                                      • ssl.truststore.password: server certificate password, which must be set to dms@kafka and cannot be changed.
                                                                      • ssl.endpoint.identification.algorithm: whether to verify the certificate domain name. This parameter must be left blank, which indicates disabling domain name verification.
                                                                      • username and password: username and password you set when enabling ciphertext access for the first time or when creating a user.
                                                                      +
                                                                    +
                                                                    +
                                                                  2. Run the following command in the /bin directory of the Kafka client:
                                                                    ./kafka-topics.sh --create --topic ${topic-name} --bootstrap-server ${connection-address} --partitions ${number-of-partitions} --replication-factor ${number-of-replicas} --command-config ../config/ssl-user-config.properties
                                                                    +

                                                                    Parameter description:

                                                                    +
                                                                    • topic-name: topic name, which can be customized.
                                                                    • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                                                    • number-of-partitions: number of partitions in a topic.
                                                                    • number-of-replicas: number of replicas in a topic.
                                                                    +

                                                                    Example:

                                                                    +
                                                                    [root@ecs-kafka bin]# ./kafka-topics.sh --create --topic topic-01 --bootstrap-server 192.168.xx.xx:9093,192.168.xx.xx:9093,192.168.xx.xx:9093 --partitions 3 --replication-factor 3 --command-config ../config/ssl-user-config.properties
+Created topic topic-01.
+[root@ecs-kafka bin]#
                                                                    +

                                                              diff --git a/docs/dms/umn/kafka-ug-180604019.html b/docs/dms/umn/kafka-ug-180604019.html index dcbc91cc..2e167d6e 100644 --- a/docs/dms/umn/kafka-ug-180604019.html +++ b/docs/dms/umn/kafka-ug-180604019.html @@ -16,8 +16,48 @@

                                                              For an instance with ciphertext access enabled, if allow.everyone.if.no.acl.found is set to false, topics cannot be deleted through the client.

                                                              • For a Kafka instance with ciphertext access disabled, run the following command in the /bin directory of the Kafka client:
                                                                ./kafka-topics.sh --bootstrap-server ${connection-address} --delete --topic ${topic-name}
                                                                -
                                                              • For a Kafka instance with ciphertext access enabled, do as follows:
                                                                1. (Optional) For the Kafka security protocol, is SASL_PLAINTEXT or SASL_SSL used?
                                                                  • SASL_PLAINTEXT: Skip this step if the username and password are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password by referring to 3.
                                                                  • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password, and the SSL certificate configuration by referring to 3.
                                                                  -
                                                                2. Run the following command in the /bin directory of the Kafka client:
                                                                  ./kafka-topics.sh --bootstrap-server ${connection-address} --delete --topic ${topic-name} --command-config ./config/ssl-user-config.properties
                                                                  +

                                                                  Parameter description:

                                                                  +
                                                                  • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                                                  • topic-name: topic name.
                                                                  +

                                                                  Example:

                                                                  +
                                                                  [root@ecs-kafka bin]# ./kafka-topics.sh --bootstrap-server 192.168.xx.xx:9092,192.168.xx.xx:9092,192.168.xx.xx:9092 --delete --topic topic-01
+[root@ecs-kafka bin]#
                                                                  +
                                                                3. For a Kafka instance with ciphertext access enabled, do as follows:
                                                                  1. (Optional) Modify the client configuration file.
                                                                    View Security Protocol in the Connection area on the Basic Information page on the Kafka console. The configuration settings vary depending on the protocol.
                                                                    • SASL_PLAINTEXT: Skip this step if the username and password are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                                                      security.protocol=SASL_PLAINTEXT
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                                                      +

                                                                      Parameter description: username and password are the ones you set when enabling ciphertext access for the first time or when creating a user.

                                                                      +
                                                                    • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                                                      security.protocol=SASL_SSL
+ssl.truststore.location={ssl_truststore_path}
+ssl.truststore.password=dms@kafka
+ssl.endpoint.identification.algorithm=
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                                                      +

                                                                      Parameter description:

                                                                      +
                                                                      • ssl.truststore.location: path for storing the client.jks certificate. Even in Windows, you need to use slashes (/) for the certificate path. Do not use backslashes (\), which are used by default for paths in Windows. Otherwise, the client will fail to obtain the certificate.
                                                                      • ssl.truststore.password: server certificate password, which must be set to dms@kafka and cannot be changed.
                                                                      • ssl.endpoint.identification.algorithm: whether to verify the certificate domain name. This parameter must be left blank, which indicates disabling domain name verification.
                                                                      • username and password: username and password you set when enabling ciphertext access for the first time or when creating a user.
                                                                      +
                                                                    +
                                                                    +
                                                                  2. Run the following command in the /bin directory of the Kafka client:
                                                                    ./kafka-topics.sh --bootstrap-server ${connection-address} --delete --topic ${topic-name} --command-config ../config/ssl-user-config.properties
                                                                    +

                                                                    Parameter description:

                                                                    +
                                                                    • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                                                    • topic-name: topic name.
                                                                    +

                                                                    Example:

                                                                    +
                                                                    [root@ecs-kafka bin]# ./kafka-topics.sh --bootstrap-server 192.168.xx.xx:9093,192.168.xx.xx:9093,192.168.xx.xx:9093 --delete --topic topic-01 --command-config ../config/ssl-user-config.properties
+[root@ecs-kafka bin]#
                                                                    +

                                                              diff --git a/docs/dms/umn/kafka-ug-180604020.html b/docs/dms/umn/kafka-ug-180604020.html index f2216070..c72e5eb9 100644 --- a/docs/dms/umn/kafka-ug-180604020.html +++ b/docs/dms/umn/kafka-ug-180604020.html @@ -1,15 +1,14 @@

                                                              Connecting to Kafka Using the Client (Plaintext Access)

                                                              -

                                                              This section describes how to use an open-source Kafka client to access a Kafka instance in plaintext. Two scenarios: private network within a VPC and public network. To access a Kafka instance across VPCs, see Accessing Kafka Using a VPC Endpoint Across VPCs. To access a Kafka instance using DNAT, see Accessing Kafka in a Public Network Using DNAT. To access an instance in your service code, see the Distributed Message Service Developer Guide.

                                                              -

                                                              For details on how to use a Kafka client in different languages, visit https://cwiki.apache.org/confluence/display/KAFKA/Clients.

                                                              -

                                                              Each Kafka broker allows a maximum of 1000 connections from each IP address. Excess connections will be rejected. You can change the limit by referring to Modifying Kafka Instance Configuration Parameters, that is, to modify parameter max.connections.per.ip.

                                                              -
                                                              -

                                                              Prerequisites

                                                              • Security group rules have been properly configured.

                                                                To access a Kafka instance with ciphertext access disabled, configure proper security group rules. For details about security group configuration requirements, see Table 2.

                                                                -
                                                              • The Kafka instance address has been obtained.
                                                                • To access a Kafka instance in a private network within a VPC, use port 9092. Obtain the instance connection address in the Connection section of the Basic Information page, shown as follows.
                                                                  Figure 1 Kafka instance addresses for private access within a VPC (in plaintext)
                                                                  -
                                                                • To access a Kafka instance in a public network, use port 9094. Obtain the instance connection address in the Connection section of the Basic Information page, shown as follows.
                                                                  Figure 2 Kafka instance addresses for public access (in plaintext)
                                                                  +

                                                                  This section describes how to access a Kafka instance in plaintext on an open-source Kafka client. With plaintext access enabled, there is no authentication required in such connections, which is friendly to performance.

                                                                  +

                                                                  Each Kafka broker allows a maximum of 1000 connections from each IP address. Excess connections will be rejected. You can change the limit by referring to Modifying Kafka Instance Configuration Parameters, that is, to modify parameter max.connections.per.ip.

                                                                  +

                                                                  Prerequisites

                                                                  • The network between the client and the Kafka instance has been established. For details about the network requirements, see Kafka Network Connection Conditions.
                                                                  • Security group rules have been properly configured.

                                                                    Before accessing a Kafka instance with ciphertext access disabled on a client, configure proper security group rules for the instance. For details, see Table 2.

                                                                    +
                                                                  • The Kafka instance addresses have been obtained.
                                                                    Obtain the instance connection addresses in the Connection area on the Basic Information page on the Kafka console. The addresses are displayed in two types on the Kafka console. The one is Private Network Access or Public Network Access and the other is Address (Private Network, Plaintext) or Address (Public Network, Plaintext).
                                                                    • For private access within a VPC, the Kafka connection addresses are shown as follows.
                                                                      Figure 1 Kafka instance addresses for private access within a VPC
                                                                      +
                                                                    • For public access, the Kafka connection addresses are shown as follows.
                                                                      Figure 2 Kafka instance addresses for public access
                                                                    -
                                                                  • If automatic topic creation is not enabled for the Kafka instance, create a topic before connecting to the instance.
                                                                  • Kafka CLI v1.1.0, v2.3.0, v2.7.2, or v3.4.0 is available. Ensure that the Kafka instance and the CLI use the same version.
                                                                  • An ECS that has an EIP has been created. For intra-VPC access, ensure that its VPC, subnet, and security group configurations are the same as those of the Kafka instance. JDK v1.8.111 or later has been installed on the ECS, and the JAVA_HOME and PATH environment variables have been configured as follows:

                                                                    Add the following lines to the .bash_profile file in the home directory as an authorized user. In this command, /opt/java/jdk1.8.0_151 is the JDK installation path. Change it to the path where you install JDK.

                                                                    +
                                                                  +
                                                                • If automatic topic creation is not enabled for the Kafka instance, create a topic before connecting to the instance.
                                                                • Kafka CLI v1.1.0, v2.3.0, v2.7.2, or v3.4.0 is available. Ensure that the Kafka instance and the CLI use the same version.
                                                                • JDK v1.8.111 or later has been installed on the server, and the JAVA_HOME and PATH environment variables have been configured as follows:

                                                                  Add the following lines to the .bash_profile file in the home directory as an authorized user. In this command, /opt/java/jdk1.8.0_151 is the JDK installation path. Change it to the path where you install JDK.

                                                                  export JAVA_HOME=/opt/java/jdk1.8.0_151 
 export PATH=$JAVA_HOME/bin:$PATH

                                                                  Run the source .bash_profile command for the modification to take effect.

                                                                  @@ -24,7 +23,7 @@ export PATH=$JAVA_HOME/bin:$PATH

                                                                • Access the /bin directory of the Kafka CLI.

                                                                  In Windows, you need to access the /bin/windows directory.

                                                                • Run the following command to create messages:

                                                                  ./kafka-console-producer.sh --broker-list ${connection-address} --topic ${topic-name}

                                                                  Parameter description:

                                                                  -
                                                                  • {connection-address}: the address obtained in Prerequisites. For public access, use Address (Public Network, Plaintext). For intra-VPC access, use Address (Private Network, Plaintext).
                                                                  • {topic-name}: the name of the topic created for the Kafka instance. If automatic topic creation has enabled for the Kafka instance, set this parameter to the name of a created topic or a topic that has not been created.
                                                                  +
                                                                  • {connection-address}: the address obtained in Prerequisites.
                                                                  • {topic-name}: the name of the topic created for the Kafka instance. If automatic topic creation has enabled for the Kafka instance, set this parameter to the name of a created topic or a topic that has not been created.

                                                                  The following example uses connection addresses 10.xx.xx.45:9094,10.xx.xx.127:9094,10.xx.xx.103:9094. After running the preceding command, you can send a message to the Kafka instance by writing it and pressing Enter. Each line of content is sent as a message.

                                                                  [root@ecs-kafka bin]# ./kafka-console-producer.sh --broker-list 10.xx.xx.45:9094,10.xx.xx.127:9094,10.xx.xx.103:9094  --topic topic-demo
 >Hello
@@ -34,7 +33,7 @@ export PATH=$JAVA_HOME/bin:$PATH

                                                                  To stop creating messages, press Ctrl+C to exit.

                                                                • Run the following command to retrieve messages:

                                                                  ./kafka-console-consumer.sh --bootstrap-server ${connection-address} --topic ${topic-name} --group ${consumer-group-name} --from-beginning

                                                                  Parameter description:

                                                                  -
                                                                  • {connection-address}: the address obtained in Prerequisites. For public access, use Address (Public Network, Plaintext). For intra-VPC access, use Address (Private Network, Plaintext).
                                                                  • {topic-name}: the name of the topic created for the Kafka instance
                                                                  • {consumer-group-name}: the consumer group name set based on your service requirements. If a consumer group name has been specified in the configuration file, ensure that you use the same name in the command line. Otherwise, consumption may fail. If a consumer group name starts with a special character, such as an underscore (_) or a number sign (#), the monitoring data cannot be displayed.
                                                                  +
                                                                  • {connection-address}: the address obtained in Prerequisites.
                                                                  • {topic-name}: the name of the topic created for the Kafka instance.
                                                                  • {consumer-group-name}: the consumer group name set based on your service requirements. If a consumer group name has been specified in the configuration file, ensure that you use the same name in the command line. Otherwise, consumption may fail. If a consumer group name starts with a special character, such as an underscore (_) or a number sign (#), the monitoring data cannot be displayed.

                                                                  Example:

                                                                  [root@ecs-kafka bin]#  ./kafka-console-consumer.sh --bootstrap-server 10.xx.xx.45:9094,10.xx.xx.127:9094,10.xx.xx.103:9094 --topic topic-demo --group order-test --from-beginning
 Kafka!
diff --git a/docs/dms/umn/kafka-ug-180801001.html b/docs/dms/umn/kafka-ug-180801001.html
index 24b9080d..d6532cdb 100644
--- a/docs/dms/umn/kafka-ug-180801001.html
+++ b/docs/dms/umn/kafka-ug-180801001.html
@@ -1,23 +1,22 @@
 
 
 
                                                                  Connecting to Kafka Using the Client (Ciphertext Access)
                                                                  
-
                                                                  If you enable ciphertext access when creating an instance, SASL authentication will be required when your client connects to a Kafka instance.
                                                                  
+
                                                                  This section describes how to access a Kafka instance in ciphertext on an open-source Kafka client. Accessing in ciphertext requires SASL authentication. The protocol SASL_SSL encrypts data transmission with high security.
                                                                  
 
                                                                  For security purposes, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is supported.
                                                                  
-
                                                                  This section describes how to use an open-source Kafka client to access a Kafka instance if ciphertext access has been enabled for the instance. There are two scenarios. To access a Kafka instance across VPCs, see Accessing Kafka Using a VPC Endpoint Across VPCs. To access a Kafka instance using DNAT, see Accessing Kafka in a Public Network Using DNAT. To access an instance in your service code, see the Distributed Message Service Developer Guide.
                                                                  
-
                                                                   
                                                                  Each Kafka broker allows a maximum of 1000 connections from each IP address by default. Excess connections will be rejected. You can change the limit by referring to Modifying Kafka Instance Configuration Parameters, that is, to modify parameter max.connections.per.ip.
                                                                  
-
                                                                  
-
                                                                  Prerequisites
                                                                  • Security group rules have been properly configured.
                                                                    To access a Kafka instance with ciphertext access enabled, configure proper security group rules. For details about security group configuration requirements, see Table 2.
                                                                    
-
                                                                  • The Kafka instance address has been obtained.
                                                                    • For intra-VPC access, use port 9093. Obtain the instance connection address in the Connection section of the Basic Information tab page.
                                                                      Figure 1 Kafka instance addresses for private access within a VPC (in ciphertext)
                                                                      
-
                                                                    • For public access, use port 9095. Obtain the instance connection address in the Connection section of the Basic Information tab page.
                                                                      Figure 2 Kafka instance addresses for public access (in ciphertext)
                                                                      
+
                                                                      Each Kafka broker allows a maximum of 1000 connections from each IP address by default. Excess connections will be rejected. You can change the limit by referring to Modifying Kafka Instance Configuration Parameters, that is, to modify parameter max.connections.per.ip.
                                                                      
+
                                                                      Prerequisites
                                                                      • The network between the client and the Kafka instance has been established. For details about the network requirements, see Kafka Network Connection Conditions.
                                                                      • Security group rules have been properly configured.
                                                                        Before accessing a Kafka instance with ciphertext access enabled on a client, configure proper security group rules for the instance. For details, see Table 2.
                                                                        
+
                                                                      • The Kafka instance addresses have been obtained.
                                                                        Obtain the instance connection addresses in the Connection area on the Basic Information page on the Kafka console. The addresses are displayed in two types on the Kafka console. The one is Private Network Access or Public Network Access and the other is Address (Private Network, Ciphertext) or Address (Public Network, Ciphertext).
                                                                        • For private access within a VPC, the Kafka connection addresses are shown as follows.
                                                                          Figure 1 Kafka instance addresses for private access within a VPC
                                                                          
+
                                                                        • For public access, the Kafka connection addresses are shown as follows.
                                                                          Figure 2 Kafka instance addresses for public access
                                                                          
 
                                                                          
 
                                                                        
+
                                                                        
 
                                                                      • The SASL mechanism in use is known.
                                                                        In the Connection area on the Kafka instance details page, view SASL Mechanism. If both SCRAM-SHA-512 and PLAIN are enabled, use either of them in connection configurations. For instances that were created much earlier, if SASL Mechanism is not displayed on the instance details page, PLAIN is used by default.
                                                                        
 
                                                                        Figure 3 SASL mechanism in use
                                                                        
 
                                                                      • The security protocol in use is known.
                                                                        In the Connection area on the Kafka instance details page, view Security Protocol. For instances that were created much earlier, if Security Protocol is not displayed on the instance details page, SASL_SSL is used by default.
                                                                        
-
                                                                      • If automatic topic creation is not enabled for the Kafka instance, create a topic before connecting to the instance.
                                                                      • The client.jks certificate has been downloaded. Click the Kafka instance to go to the Basic Information tab page. Click Download next to SSL Certificate in the Connection area. Download and decompress the package to obtain the client certificate file client.jks.
                                                                         
                                                                        Later instances use the new certificate client.jks, and earlier ones use the old certificate client.truststore.jks. Later instances are incompatible with the old certificate, and earlier ones are incompatible with the new certificate.
                                                                        
-
                                                                        To determine whether a certificate is new, download it on the console and check its name.
                                                                        
+
                                                                      • If automatic topic creation is not enabled for the Kafka instance, create a topic before connecting to the instance.
                                                                      • The client.jks certificate has been downloaded. Click the Kafka instance to go to the Basic Information tab page. Click Download next to SSL Certificate in the Connection area. Download and decompress the package to obtain the client certificate file client.jks.
                                                                         
                                                                        Later instances use the new certificate, and earlier ones use the old certificate. Later instances are incompatible with the old certificate, and earlier ones are incompatible with the new certificate.
                                                                        
+
                                                                        To determine whether a certificate is new, download the Zip file of the certificate on the console and see the file name. The earlier name is kafka-certs.zip and the later one is kafka-cert-otc.zip.
                                                                        
 
                                                                        
-
                                                                      • Kafka CLI v1.1.0, v2.3.0, v2.7.2, or v3.4.0 is available. Ensure that the Kafka instance and the CLI use the same version.
                                                                      • An ECS that has an EIP has been created. For intra-VPC access, ensure that its VPC, subnet, and security group configurations are the same as those of the Kafka instance. JDK v1.8.111 or later has been installed on the ECS, and the JAVA_HOME and PATH environment variables have been configured as follows:
                                                                        Add the following lines to the .bash_profile file in the home directory as an authorized user. In this command, /opt/java/jdk1.8.0_151 is the JDK installation path. Change it to the path where you install JDK.
                                                                        
+
                                                                      • Kafka CLI v1.1.0, v2.3.0, v2.7.2, or v3.4.0 is available. Ensure that the Kafka instance and the CLI use the same version.
                                                                      • JDK v1.8.111 or later has been installed on the server, and the JAVA_HOME and PATH environment variables have been configured as follows:
                                                                        Add the following lines to the .bash_profile file in the home directory as an authorized user. In this command, /opt/java/jdk1.8.0_151 is the JDK installation path. Change it to the path where you install JDK.
                                                                        
 
                                                                        export JAVA_HOME=/opt/java/jdk1.8.0_151 
 export PATH=$JAVA_HOME/bin:$PATH
                                                                        
 
                                                                        Run the source .bash_profile command for the modification to take effect.
                                                                        
@@ -34,7 +33,7 @@ export PATH=$JAVA_HOME/bin:$PATH

                                                                  In the preceding command, [kafka_tar] indicates the name of the CLI package.

                                                                  For example:

                                                                  tar -zxf kafka_2.12-2.7.2.tgz

                                                                  -

                                                                • Modify the Kafka CLI configuration file based on the SASL mechanism.

                                                                  • If PLAIN is used, find the consumer.properties and producer.properties files in the /config directory of the Kafka CLI and add the following content to the files:
                                                                    sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+
                                                                  • Modify the Kafka CLI configuration file based on the SASL mechanism.

                                                                    • If PLAIN is used, find the consumer.properties and producer.properties files in the /config directory of the Kafka CLI and add the following content to the files:
                                                                      sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
 username="**********" \
 password="**********";        
 sasl.mechanism=PLAIN
                                                                      @@ -52,13 +51,13 @@ ssl.truststore.location={ssl_truststore_path} ssl.truststore.password=dms@kafka ssl.endpoint.identification.algorithm=

                                                                      Parameter description:

                                                                      -
                                                                      • ssl.truststore.location: path for storing the client.jks certificate. Even in Windows, you need to use slashes (/) for the certificate path. Do not use backslashes (\), which are used by default for paths in Windows. Otherwise, the client will fail to obtain the certificate.
                                                                      • ssl.truststore.password: server certificate password, which must be set to dms@kafka and cannot be changed.
                                                                      • ssl.endpoint.identification.algorithm: whether to verify the certificate domain name. This parameter must be left blank, which indicates disabling domain name verification.
                                                                      +
                                                                      • ssl.truststore.location: path for storing the client.jks certificate. Even in Windows, you need to use slashes (/) for the certificate path. Do not use backslashes (\), which are used by default for paths in Windows. Otherwise, the client will fail to obtain the certificate.
                                                                      • ssl.truststore.password: server certificate password, which must be set to dms@kafka and cannot be changed.
                                                                      • ssl.endpoint.identification.algorithm: whether to verify the certificate domain name. This parameter must be left blank, which indicates disabling domain name verification.
                                                                    • SASL_PLAINTEXT: Find the consumer.properties and producer.properties files in the /config directory of the Kafka CLI and add the following content to the files:
                                                                      security.protocol=SASL_PLAINTEXT

                                                                  • Access the /bin directory of the Kafka CLI.

                                                                    In Windows, you need to access the /bin/windows directory.

                                                                  • Run the following command to create messages:

                                                                    ./kafka-console-producer.sh --broker-list ${connection addr} --topic ${topic name} --producer.config ../config/producer.properties

                                                                    Parameter description:

                                                                    -
                                                                    • {connection-address}: the address obtained in Prerequisites. For public access, use Address (Public Network, Ciphertext). For intra-VPC access, use Address (Private Network, Ciphertext).
                                                                    • {topic-name}: the name of the topic created for the Kafka instance. If automatic topic creation has enabled for the Kafka instance, set this parameter to the name of a created topic or a topic that has not been created.
                                                                    +
                                                                    • {connection-address}: the address obtained in Prerequisites.
                                                                    • {topic-name}: the name of the topic created for the Kafka instance. If automatic topic creation has enabled for the Kafka instance, set this parameter to the name of a created topic or a topic that has not been created.

                                                                    The following example uses connection addresses 10.xx.xx.45:9095,10.xx.xx.127:9095,10.xx.xx.103:9095.

                                                                    After running the preceding command, you can send a message to the Kafka instance by writing it and pressing Enter. Each line of content is sent as a message.

                                                                    [root@ecs-kafka bin]#./kafka-console-producer.sh --broker-list 10.xx.xx.45:9095,10.xx.xx.127:9095,10.xx.xx.103:9095  --topic topic-demo --producer.config ../config/producer.properties
@@ -69,7 +68,7 @@ ssl.endpoint.identification.algorithm=

                                                                    To stop creating messages, press Ctrl+C to exit.

                                                                  • Run the following command to retrieve messages:

                                                                    ./kafka-console-consumer.sh --bootstrap-server ${connection-address} --topic ${topic-name} --group ${consumer-group-name} --from-beginning  --consumer.config ../config/consumer.properties

                                                                    Parameter description:

                                                                    -
                                                                    • {connection-address}: the address obtained in Prerequisites. For public access, use Address (Public Network, Ciphertext). For intra-VPC access, use Address (Private Network, Ciphertext).
                                                                    • {topic-name}: the name of the topic created for the Kafka instance.
                                                                    • {consumer-group-name}: the consumer group name set based on your service requirements. If a consumer group name has been specified in the configuration file, ensure that you use the same name in the command line. Otherwise, consumption may fail. If a consumer group name starts with a special character, such as an underscore (_) or a number sign (#), the monitoring data cannot be displayed.
                                                                    +
                                                                    • {connection-address}: the address obtained in Prerequisites.
                                                                    • {topic-name}: the name of the topic created for the Kafka instance.
                                                                    • {consumer-group-name}: the consumer group name set based on your service requirements. If a consumer group name has been specified in the configuration file, ensure that you use the same name in the command line. Otherwise, consumption may fail. If a consumer group name starts with a special character, such as an underscore (_) or a number sign (#), the monitoring data cannot be displayed.

                                                                    Example:

                                                                    [root@ecs-kafka bin]#  ./kafka-console-consumer.sh --bootstrap-server 10.xx.xx.45:9095,10.xx.xx.127:9095,10.xx.xx.103:9095 --topic topic-demo --group order-test --from-beginning --consumer.config ../config/consumer.properties
 Hello
diff --git a/docs/dms/umn/kafka-ug-181221001.html b/docs/dms/umn/kafka-ug-181221001.html
index 653a97f2..8008289e 100644
--- a/docs/dms/umn/kafka-ug-181221001.html
+++ b/docs/dms/umn/kafka-ug-181221001.html
@@ -1,66 +1,62 @@
 
 
 
                                                                    Modifying Kafka Instance Specifications
                                                                    
-
                                                                    Scenario
                                                                    After creating a Kafka instance, you can increase its specifications. Table 1 lists available modification options. Only one object can be modified per operation: broker quantity, bandwidth, storage space, or broker flavor.
                                                                    
+
                                                                    After creating a Kafka instance, you can increase its specifications. Table 1 lists available modification options. Only one object can be modified per operation: broker quantity, bandwidth, storage space, or broker flavor.
                                                                    
 
-
                                                                    Table 1 Specification modification options
                                                                    Old/New Flavor
                                                                    
+
                                                                    
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@@ -71,28 +67,27 @@
 
                                                                    Distinguishing between old and new specifications:
                                                                    • Old specifications: In the instance list, the instance specification is displayed as bandwidth (for example, 100 MB/s).
                                                                    • New specifications: In the instance list, the instance specification is displayed as the ECS flavor multiplied by the number of brokers (for example, kafka.2u4g.cluster*3 brokers).
                                                                    Figure 1 Instance list
                                                                    
-
                                                                    Impact of Specification Modification
                                                                    It takes 5 to 10 minutes to modify specifications on one broker. The more brokers, the longer time the modification takes.
                                                                    
 
-
                                                                    Table 1 Specification modification options
                                                                    Old/New Flavor
                                                                    
 
                                                                    Modified Object
                                                                    
+
                                                                    Modified Object
                                                                    
 
                                                                    Increase
                                                                    
+
                                                                    Increase
                                                                    
 
                                                                    Decrease
                                                                    
+
                                                                    Decrease
                                                                    
                                                                     		
 
                                                                    
 
                                                                    New flavor
                                                                    
-
                                                                    
-
                                                                    
+
                                                                    New flavor
                                                                    
 
                                                                    Broker quantity
                                                                    
+
                                                                    Broker quantity
                                                                    
 
                                                                    √
                                                                    
+
                                                                    √
                                                                    
 
                                                                    ×
                                                                    
+
                                                                    ×
                                                                    
                                                                     		
 
                                                                    Storage space
                                                                    
+
                                                                    Storage space
                                                                    
 
                                                                    √
                                                                    
+
                                                                    √
                                                                    
 
                                                                    ×
                                                                    
+
                                                                    ×
                                                                    
                                                                     		
 
                                                                    Broker flavor
                                                                    
+
                                                                    Broker flavor
                                                                    
 
                                                                    √
                                                                    
+
                                                                    √
                                                                    
 
                                                                    ×
                                                                    
+
                                                                    ×
                                                                    
                                                                     		
 
                                                                    Old flavor
                                                                    
-
                                                                    
-
                                                                    
+
                                                                    Old flavor
                                                                    
 
                                                                    Bandwidth
                                                                    
+
                                                                    Bandwidth
                                                                    
 
                                                                    √
                                                                    
+
                                                                    √
                                                                    
 
                                                                    ×
                                                                    
+
                                                                    ×
                                                                    
                                                                     		
 
                                                                    Storage space
                                                                    
+
                                                                    Storage space
                                                                    
 
                                                                    √
                                                                    
+
                                                                    √
                                                                    
 
                                                                    ×
                                                                    
+
                                                                    ×
                                                                    
                                                                     		
 
                                                                    Broker flavor
                                                                    
+
                                                                    Broker flavor
                                                                    
 
                                                                    ×
                                                                    
+
                                                                    ×
                                                                    
 
                                                                    ×
                                                                    
+
                                                                    ×
                                                                    
                                                                     		
 
                                                                    
                                                                     
 
 
 
                                                                    Table 2 Impact of specification modification
                                                                    Modified Object
                                                                    
+
                                                                    
-
-
-
-
-
-
-
                                                                    Table 2 Impact of specification modification
                                                                    Modified Object
                                                                    
 
                                                                    Impact
                                                                    
+
                                                                    Impact
                                                                    
                                                                     		
 
                                                                    
 
                                                                    Bandwidth or broker quantity
                                                                    
+
                                                                    Bandwidth or broker quantity
                                                                    
 
                                                                    • Increasing the bandwidth or adding brokers does not affect the original brokers or services.
                                                                    • When you increase the bandwidth or change the broker quantity, the storage space is proportionally expanded based on the current disk space. For example, assume that the original number of brokers of an instance is 3 and the disk size of each broker is 200 GB. If the broker quantity changes to 10 and the disk size of each broker is still 200 GB, the total disk size becomes 2000 GB.
                                                                    • New topics are created on new brokers, and the original topics are still on the original brokers, resulting in unbalanced partitions. You can reassign partitions to migrate the replicas of the original topic partitions to the new brokers.
                                                                    
+
                                                                    • Increasing the bandwidth or adding brokers does not affect the original brokers or services.
                                                                    • When you increase the bandwidth or change the broker quantity, the storage space is proportionally expanded based on the current disk space. For example, assume that the original number of brokers of an instance is 3 and the disk size of each broker is 200 GB. If the broker quantity changes to 10 and the disk size of each broker is still 200 GB, the total disk size becomes 2000 GB.
                                                                    • New topics are created on new brokers, and the original topics are still on the original brokers, resulting in unbalanced partitions. You can reassign partitions to migrate the replicas of the original topic partitions to the new brokers.
                                                                    
                                                                     		
 
                                                                    Storage space
                                                                    
+
                                                                    Storage space
                                                                    
 
                                                                    • You can expand the storage space 20 times.
                                                                    • Storage space expansion does not affect services.
                                                                    
+
                                                                    • You can expand the storage space 20 times.
                                                                    • Storage space expansion does not affect services.
                                                                    
                                                                     		
 
                                                                    Broker flavor
                                                                    
+
                                                                    Broker flavor
                                                                    
 
                                                                    • Single-replica topics do not support message production during this period. Services will be interrupted.
                                                                    • If a topic has multiple replicas, modifying the broker flavor does not interrupt services, but may cause disorder of partition messages. Evaluate this impact and avoid peak hours.
                                                                    • Broker rolling restarts will cause partition leader changes, interrupting connections for less than a minute when the network is stable. For multi-replica topics, configure the retry mechanism on the producer client. To do so:
                                                                      • If you use an open-source Kafka client, configure the retries parameter to a value in the range from 3 to 5.
                                                                      • If you use Flink, configure the retry policy by referring to the following code:
                                                                        StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment();
+
                                                                    • Single-replica topics do not support message production during this period. Services will be interrupted.
                                                                    • If a topic has multiple replicas, modifying the broker flavor does not interrupt services, but may cause disorder of partition messages. Evaluate this impact and avoid peak hours.
                                                                    • Broker rolling restarts will cause partition leader changes, interrupting connections for less than a minute when the network is stable. For multi-replica topics, configure the retry mechanism on the producer client. To do so:
                                                                      • If you use an open-source Kafka client, configure the retries parameter to a value in the range from 3 to 5.
                                                                      • If you use Flink, configure the retry policy by referring to the following code:
                                                                        StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment();
 env.setRestartStrategy(RestartStrategies.fixedDelayRestart(3, Time.seconds(20)));
                                                                        
 
                                                                      
 
                                                                    
@@ -106,28 +101,26 @@ env.setRestartStrategy(RestartStrategies.fixedDelayRestart(3, Time.seconds(20)))
 
                                                                    1. Stop the Kafka process on Broker 0.
                                                                    2. Scale up the flavor of Broker 0.
                                                                    3. Restart the Kafka process on Broker 0.
                                                                    4. Repeat 1 to 3 to scale up the flavor of Broker 1.
                                                                    5. Repeat 1 to 3 to scale up the flavor of Broker 2.
                                                                    
 
                                                                    Figure 2 Process of increasing a broker flavor
                                                                    
 
-
                                                                    Modifying Kafka Instance Specifications
                                                                    1. Log in to the console.
                                                                    2. Click  in the upper left corner to select a region.
                                                                       
                                                                      Select the region where your Kafka instance is located.
                                                                      
+
                                                                      Procedure
                                                                      1. Log in to the console.
                                                                      2. Click  in the upper left corner to select a region.
                                                                         
                                                                        Select the region where your Kafka instance is located.
                                                                        
 
                                                                        
-
                                                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                      4. In the row containing the desired instance, choose More > Modify Specifications in the Operation column.
                                                                      5. Specify the storage space, number of brokers, or broker flavor as required.
                                                                        To modify old specifications, perform the following steps:
                                                                        • Increase the bandwidth.
                                                                          1. Specify a new bandwidth and click Next.
                                                                          2. Confirm the configurations and click Submit.
                                                                          3. Return to the instance list and check whether the change succeeded.
                                                                            • If the instance status has changed from Changing to Running, the change succeeded. You can check the new bandwidth in the Flavor column.
                                                                            • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.
                                                                              Instances in the Change failed state cannot be restarted, modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations on the instance. If the status does not change to Running, contact customer service.
                                                                              
+
                                                                            • Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                            • In the row containing the desired instance, choose More > Modify Specifications in the Operation column.
                                                                            • Specify the storage space, number of brokers, or broker flavor as required.
                                                                              • Increase the bandwidth (for earlier instances).
                                                                                1. Specify a new bandwidth and click Next.
                                                                                2. Confirm the configurations and click Submit.
                                                                                3. Return to the instance list and check whether the change succeeded.
                                                                                  • If the instance status has changed from Changing to Running, the change succeeded. You can check the new bandwidth in the Flavor column.
                                                                                  • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.
                                                                                    Instances in the Change failed state cannot be restarted, modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations on the instance. If the status does not change to Running, contact customer service.
                                                                                    
 
                                                                                  
 
                                                                                
 
                                                                                 
                                                                                After increasing the bandwidth, add the IP address of the new broker to the client connection configuration to improve reliability.
                                                                                
 
                                                                                
-
                                                                              • Expand the storage space.
                                                                                1. Specify a new storage space and click Next.
                                                                                2. Confirm the configurations and click Submit.
                                                                                3. Return to the instance list and check whether the change succeeded.
                                                                                  • If the instance status has changed from Changing to Running, the change succeeded. View the new storage space (Storage space per broker x Number of brokers) in the Used/Available Storage Space (GB) column in the instance list.
                                                                                  • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.
                                                                                    Instances in the Change failed state cannot be restarted, modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations on the instance. If the status does not change to Running, contact customer service.
                                                                                    
+
                                                                                  • Expand the storage space (for earlier instances).
                                                                                    1. Specify a new storage space and click Next.
                                                                                    2. Confirm the configurations and click Submit.
                                                                                    3. Return to the instance list and check whether the change succeeded.
                                                                                      • If the instance status has changed from Changing to Running, the change succeeded. View the new storage space (Storage space per broker x Number of brokers) in the Used/Available Storage Space (GB) column in the instance list.
                                                                                      • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.
                                                                                        Instances in the Change failed state cannot be restarted, modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations on the instance. If the status does not change to Running, contact customer service.
                                                                                        
 
                                                                                      
 
                                                                                    
 
                                                                                  
-
                                                                        
-
                                                                        To modify new specifications, perform the following steps:
                                                                        
-
                                                                        • Expand the storage space.
                                                                          1. For Change By, select Storage. For Storage Space per Broker, specify a new storage space, and click Next. The storage space range varies by instance specifications. For details, see Table 1.
                                                                          2. Confirm the configurations and click Submit.
                                                                          3. Return to the instance list and check whether the change succeeded.
                                                                            • If the instance status has changed from Changing to Running, the change succeeded. View the new storage space (Storage space per broker x Number of brokers) in the Used/Available Storage Space (GB) column in the instance list.
                                                                            • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.
                                                                              Instances in the Change failed state cannot be restarted, modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations on the instance. If the status does not change to Running, contact customer service.
                                                                              
+
                                                                              • Expand the storage space (for later instances).
                                                                                1. For Change By, select Storage. For Storage Space per Broker, specify a new storage space, and click Next. The storage space range varies by instance specifications. For details, see Table 1.
                                                                                2. Confirm the configurations and click Submit.
                                                                                3. Return to the instance list and check whether the change succeeded.
                                                                                  • If the instance status has changed from Changing to Running, the change succeeded. View the new storage space (Storage space per broker x Number of brokers) in the Used/Available Storage Space (GB) column in the instance list.
                                                                                  • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.
                                                                                    Instances in the Change failed state cannot be restarted, modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations on the instance. If the status does not change to Running, contact customer service.
                                                                                    
 
                                                                                  
 
                                                                                
-
                                                                              • Add brokers.
                                                                                1. For Change By, select Brokers. Then, enter the number of brokers and click Next. The broker quantity range varies by instance specifications. For details, see Table 1. If public access has been enabled, configure EIPs for the new brokers. Then click Next.
                                                                                2. Confirm the configurations and click Submit.
                                                                                3. Return to the instance list and check whether the change succeeded.
                                                                                  • If the instance status has changed from Changing to Running, the change succeeded. You can check the new broker quantity in the Flavor column.
                                                                                  • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.
                                                                                    Instances in the Change failed state cannot be restarted, modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations on the instance. If the status does not change to Running, contact customer service.
                                                                                    
+
                                                                                  • Increase the broker quantity (for later instances).
                                                                                    1. For Change By, select Brokers. Then, enter the number of brokers and click Next. The broker quantity range varies by instance specifications. For details, see Table 1. If public access has been enabled, configure EIPs for the new brokers. Then click Next.
                                                                                    2. Confirm the configurations and click Submit.
                                                                                    3. Return to the instance list and check whether the change succeeded.
                                                                                      • If the instance status has changed from Changing to Running, the change succeeded. You can check the new broker quantity in the Flavor column.
                                                                                      • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.
                                                                                        Instances in the Change failed state cannot be restarted, modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations on the instance. If the status does not change to Running, contact customer service.
                                                                                        
 
                                                                                      
 
                                                                                    
 
                                                                                     
                                                                                    After adding brokers, add the IP addresses of the new brokers to the client connection configuration to improve reliability.
                                                                                    
 
                                                                                    
-
                                                                                  • Increase the broker flavor.
                                                                                    1. For Change By, select Broker Flavor.
                                                                                    2. Specify a new broker flavor.
                                                                                    3. In the Risk Check area, check for risks.
                                                                                      If any risk is found, handle it as prompted and click Recheck. If the risks do not need to be handled, select I understand the risks.
                                                                                      
+
                                                                                    4. Increase the broker flavor (for later instances).
                                                                                      1. For Change By, select Broker Flavor.
                                                                                      2. Specify a new broker flavor.
                                                                                      3. In the Risk Check area, check for risks.
                                                                                        If any risk is found, handle it as prompted and click Recheck. If the risks do not need to be handled, select I understand the risks.
                                                                                        
 
                                                                                      4. Click Next, confirm the information, and click Submit.
                                                                                      5. Return to the instance list and check whether the change succeeded.
                                                                                        • If the instance status has changed from Changing to Running, the change succeeded. You can check the new broker flavor in the Flavor column.
                                                                                        • If the instance status has changed from Changing to Change failed, the change failed. Move the cursor over Change failed to check the failure cause.
                                                                                          Instances in the Change failed state cannot be restarted, modified, or deleted. After the instance status automatically changes from Change failed to Running, you can continue to perform operations on the instance. If the status does not change to Running, contact customer service.
                                                                                          
 
                                                                                        
 
                                                                                      
diff --git a/docs/dms/umn/kafka-ug-190605001.html b/docs/dms/umn/kafka-ug-190605001.html
index 29b7b096..9c3abb08 100644
--- a/docs/dms/umn/kafka-ug-190605001.html
+++ b/docs/dms/umn/kafka-ug-190605001.html
@@ -1,13 +1,12 @@
 
 
-
                                                                                      Viewing Kafka Monitoring Metrics
                                                                                      
-
                                                                                      Scenario
                                                                                      Cloud Eye monitors Kafka instance metrics in real time. You can view these metrics on the Cloud Eye console.
                                                                                      
-
                                                                                      
+
                                                                                      Viewing Kafka Metrics
                                                                                      
+
                                                                                      Cloud Eye monitors Kafka instance metrics in real time. You can view these metrics on the Cloud Eye console.
                                                                                      
 
                                                                                      Prerequisites
                                                                                      At least one Kafka instance has been created. The instance has at least one available message.
                                                                                      
 
                                                                                      
-
                                                                                      Viewing Kafka Monitoring Metrics
                                                                                      1. Log in to the console.
                                                                                      2. Click  in the upper left corner to select a region.
                                                                                         
                                                                                        Select the region where your Kafka instance is located.
                                                                                        
+
                                                                                        Procedure
                                                                                        1. Log in to the console.
                                                                                        2. Click  in the upper left corner to select a region.
                                                                                           
                                                                                          Select the region where your Kafka instance is located.
                                                                                          
 
                                                                                          
-
                                                                                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                        4. View the instance metrics in either of the following ways:
                                                                                          • In the row containing the desired instance, click View Metric. On the Cloud Eye console, view the metrics of the instance, brokers, topics, and consumer groups. Metric data is reported to Cloud Eye every minute.
                                                                                          • Click the desired Kafka instance to view its details. In the navigation pane, choose Monitoring view. On the displayed page, view the metrics of the instance, brokers, topics, and consumer groups. Metric data is reported to Cloud Eye every minute.
                                                                                          
+
                                                                                        5. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                        6. View the instance metrics in either of the following ways:
                                                                                          • In the row containing the desired instance, click View Metric. The Cloud Eye console is displayed. Click By Instance, By Broker, By Topic, By Consumer Group, or By Smart Connect to view monitoring data. The data is updated every minute.
                                                                                          • Click the desired Kafka instance to view its details. Choose Monitoring. The monitoring data can be viewed on the By Instance, By Broker, By Topic, By Consumer Group, and By Smart Connect tab pages. The data is updated every minute.
                                                                                          
 
                                                                                        
 
                                                                                        
 
                                                                                        
diff --git a/docs/dms/umn/kafka-ug-190904001.html b/docs/dms/umn/kafka-ug-190904001.html
index 9f4ed472..8d87d6d0 100644
--- a/docs/dms/umn/kafka-ug-190904001.html
+++ b/docs/dms/umn/kafka-ug-190904001.html
@@ -1,9 +1,8 @@
 
 
 
                                                                                        Viewing Kafka Messages
                                                                                        
-
                                                                                        Scenario
                                                                                        You can view the offset of different partitions, the message size, creation time, and body of messages in topics.
                                                                                        
-
                                                                                        
-
                                                                                        Viewing Kafka Messages
                                                                                        1. Log in to the console.
                                                                                        2. Click  in the upper left corner to select a region.
                                                                                           
                                                                                          Select the region where your Kafka instance is located.
                                                                                          
+
                                                                                          You can view the offset of different partitions, the message size, creation time, and body of messages in topics.
                                                                                          
+
                                                                                          Procedure
                                                                                          1. Log in to the console.
                                                                                          2. Click  in the upper left corner to select a region.
                                                                                             
                                                                                            Select the region where your Kafka instance is located.
                                                                                            
 
                                                                                            
 
                                                                                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                          4. Click the desired Kafka instance to view its details.
                                                                                          5. In the left navigation pane, choose Message Query.
                                                                                          6. Set the query parameters by referring to Table 1.
                                                                                            
 
                                                                                            Table 1 Message query parameters
                                                                                            Parameter
                                                                                            
diff --git a/docs/dms/umn/kafka-ug-200119002.html b/docs/dms/umn/kafka-ug-200119002.html
index 7cee1de3..8542bae3 100644
--- a/docs/dms/umn/kafka-ug-200119002.html
+++ b/docs/dms/umn/kafka-ug-200119002.html
@@ -57,7 +57,7 @@
 
 
                                                                                            
 
                                                                                            
-
                                                                                            Viewing Kafka Background Tasks
                                                                                            1. Log in to the console.
                                                                                            2. Click  in the upper left corner to select a region.
                                                                                               
                                                                                              Select the region where your Kafka instance is located.
                                                                                              
+
                                                                                              Procedure
                                                                                              1. Log in to the console.
                                                                                              2. Click  in the upper left corner to select a region.
                                                                                                 
                                                                                                Select the region where your Kafka instance is located.
                                                                                                
 
                                                                                                
 
                                                                                              3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                              4. Click a Kafka instance to go to the Basic Information page.
                                                                                              5. In the navigation pane, choose Background Tasks.
                                                                                              6. On the Background tasks or Scheduled tasks tab page, click the time drop-down box, specify time, enter keywords in the search box, and press Enter. Tasks started in the specified time will be displayed.
                                                                                                On the Background Tasks page, you can also perform the following operations:
                                                                                                • Click  to refresh the task status.
                                                                                                • Click Delete. In the displayed Delete Task dialog box, click OK to clear the task information.
                                                                                                   
                                                                                                  You can delete a task only when it is in either of the following situations:
                                                                                                  
 
                                                                                                  • The task is complete, which can be Successful or Failed.
                                                                                                  • The task is Canceled.
                                                                                                  
diff --git a/docs/dms/umn/kafka-ug-200506001.html b/docs/dms/umn/kafka-ug-200506001.html
index 9c5f958b..5916d222 100644
--- a/docs/dms/umn/kafka-ug-200506001.html
+++ b/docs/dms/umn/kafka-ug-200506001.html
@@ -2,12 +2,12 @@
 
 
                                                                                                  Changing Kafka Message Retention Period
                                                                                                  
 
                                                                                                  Aging time is a period that messages in the topic are retained for. Consumers must retrieve messages before this period ends. Otherwise, the messages will be deleted and can no longer be retrieved.
                                                                                                  
-
                                                                                                  After creating a topic, you can change its aging time based on service requirements. Changing the aging time does not affect services. The default aging time is 72 hours.
                                                                                                  
+
                                                                                                  The topic retention period is 72 hours by default, and can be changed later as required. Changing the aging time does not affect services.
                                                                                                  
 
                                                                                                  You can change the aging time in either of the following ways:
                                                                                                  
 
 
                                                                                                   
                                                                                                  The log.retention.hours parameter takes effect only for topics that have no aging time configured. If there is aging time configured for a topic, it overrides the log.retention.hours parameter. For example, if the aging time of Topic01 is set to 60 hours and log.retention.hours is set to 72 hours, the actual aging time of Topic01 is 60 hours.
                                                                                                  
 
                                                                                                  
-
                                                                                                  Changing Kafka Message Retention Period
                                                                                                  1. Log in to the console.
                                                                                                  2. Click  in the upper left corner to select a region.
                                                                                                     
                                                                                                    Select the region where your Kafka instance is located.
                                                                                                    
+
                                                                                                    Procedure
                                                                                                    1. Log in to the console.
                                                                                                    2. Click  in the upper left corner to select a region.
                                                                                                       
                                                                                                      Select the region where your Kafka instance is located.
                                                                                                      
 
                                                                                                      
 
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Click the desired Kafka instance to view the instance details.
                                                                                                    5. In the navigation pane, choose Topics.
                                                                                                    6. Modify the topic aging time using either of the following methods:
                                                                                                      • Select one or more topics and click Edit Topic in the upper left corner.
                                                                                                      • In the row containing the desired topic, click Edit.
                                                                                                      
 
                                                                                                    7. In the Edit Topic dialog box, enter the aging time and click OK.
                                                                                                    
diff --git a/docs/dms/umn/kafka_ug_0016.html b/docs/dms/umn/kafka_ug_0016.html
index 667c4ada..5ccc22e9 100644
--- a/docs/dms/umn/kafka_ug_0016.html
+++ b/docs/dms/umn/kafka_ug_0016.html
@@ -10,6 +10,8 @@
 
 
                                                                                                    
 
diff --git a/docs/dms/umn/kafka_ug_0017.html b/docs/dms/umn/kafka_ug_0017.html
new file mode 100644
index 00000000..9db939a3
--- /dev/null
+++ b/docs/dms/umn/kafka_ug_0017.html
@@ -0,0 +1,30 @@
+
+
+
                                                                                                    Enabling Smart Connect
                                                                                                    
+
                                                                                                    Smart Connect synchronizes data between Kafka and other cloud services (such as OBS) or between two Kafka instances for backup or migration.
                                                                                                    
+
                                                                                                    Procedure for using Smart Connect:
                                                                                                    
+
                                                                                                    1. Enable Smart Connect.
                                                                                                    2. Create a Smart Connect task.
                                                                                                    
+
                                                                                                    This section describes how to enable Smart Connect.
                                                                                                    
+
                                                                                                     
                                                                                                    This function is unavailable for single-node instances. Kafka 3.x instances do not support this function.
                                                                                                    
+
                                                                                                    
+
                                                                                                    Operation Impact
                                                                                                    Enabling Smart Connect creates at least two brokers.
                                                                                                    
+
                                                                                                    For example, if you enable Smart Connect for a kafka.4u8g.cluster instance, at least two kafka.4u8g brokers will be created for Smart Connect.
                                                                                                    
+
                                                                                                    
+
                                                                                                    Prerequisites
                                                                                                    
+
                                                                                                    
+
                                                                                                    Procedure
                                                                                                    1. Log in to the console.
                                                                                                    2. Click  in the upper left corner to select a region.
                                                                                                       
                                                                                                      Select the region where your Kafka instance is located.
                                                                                                      
+
                                                                                                      
+
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Enable Smart Connect using one of the following methods:
                                                                                                      • In the row containing the desired Kafka instance, choose More > Enable Smart Connect.
                                                                                                      • Click the desired Kafka instance to view its details. In the upper right corner, choose More > Enable Smart Connect.
                                                                                                      • Click the desired Kafka instance to view its details. Click  next to Smart Connect.
                                                                                                      • Click the desired Kafka instance to view its details. In the navigation pane, choose Smart Connect. Click Enable Smart Connect.
                                                                                                      
+
                                                                                                    5. Click , enable Smart Connect, set 2–16 brokers as required, and click Next.
                                                                                                       
                                                                                                      By default, two brokers will be used. If synchronization traffic between two Kafka instances is estimated to be large, for example, greater than 50 MB/s, use more brokers.
                                                                                                      
+
                                                                                                      
+
                                                                                                    6. On the displayed Enabling Smart Connect for Kafka Instance page, ensure that Smart Connect is enabled and click Submit.
                                                                                                    
+
                                                                                                    
+
                                                                                                    Follow-up Operations
                                                                                                    Proceed to Replicating Kafka Instance Data, Dumping Kafka Data to Object Storage Service (OBS),  to synchronize data between DMS for Kafka and other cloud services.
                                                                                                    
+
                                                                                                    
+
                                                                                                    
+
+
diff --git a/docs/dms/umn/kafka_ug_0018.html b/docs/dms/umn/kafka_ug_0018.html
new file mode 100644
index 00000000..068817ec
--- /dev/null
+++ b/docs/dms/umn/kafka_ug_0018.html
@@ -0,0 +1,37 @@
+
+
+
                                                                                                    Managing Smart Connect Tasks
                                                                                                    
+
                                                                                                    View, delete, start, pause, or restart a Smart Connect task.
                                                                                                    
+
                                                                                                     
                                                                                                    This function is unavailable for single-node instances. Kafka 3.x instances do not support this function.
                                                                                                    
+
                                                                                                    
+
                                                                                                    Prerequisites
                                                                                                    A Smart Connect task has been created.
                                                                                                    
+
                                                                                                    
+
                                                                                                    Viewing Smart Connect Tasks
                                                                                                    1. Log in to the management console.
                                                                                                    2. Click  in the upper left corner to select a region.
                                                                                                       
                                                                                                      Select the region where your Kafka instance is located.
                                                                                                      
+
                                                                                                      
+
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Click the desired Kafka instance to view its details.
                                                                                                    5. In the navigation pane, choose Smart Connect.
                                                                                                    6. Click a Smart Connect task name to go to the details page.
                                                                                                    7. View the basic information, source, and target of the Smart Connect task.
                                                                                                       
                                                                                                      The source and target are displayed on the task details page only when they have been configured for the Smart Connect task.
                                                                                                      
+
                                                                                                      
+
                                                                                                    
+
                                                                                                    
+
                                                                                                    Deleting a Smart Connect Task
                                                                                                    1. Log in to the management console.
                                                                                                    2. Click  in the upper left corner to select a region.
                                                                                                       
                                                                                                      Select the region where your Kafka instance is located.
                                                                                                      
+
                                                                                                      
+
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Click the desired Kafka instance to view its details.
                                                                                                    5. In the navigation pane, choose Smart Connect.
                                                                                                    6. In the row containing the Smart Connect task to be deleted, click Delete.
                                                                                                    7. Click OK.
                                                                                                    
+
                                                                                                    
+
                                                                                                    Starting or Pausing a Smart Connect Task
                                                                                                    After a task of a Kafka instance is paused, data of the instance will not be synchronized to another Kafka instance or other cloud services.
                                                                                                    
+
                                                                                                    1. Log in to the management console.
                                                                                                    2. Click  in the upper left corner to select a region.
                                                                                                       
                                                                                                      Select the region where your Kafka instance is located.
                                                                                                      
+
                                                                                                      
+
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Click the desired Kafka instance to view its details.
                                                                                                    5. In the navigation pane, choose Smart Connect.
                                                                                                    6. Perform the required operation:
                                                                                                      • To start a Smart Connect task, click Start in the row that contains the task.
                                                                                                      • To pause a Smart Connect task, click Pause in the row containing the task, then click OK in the dialog box that is displayed.
                                                                                                      
+
                                                                                                    
+
                                                                                                    
+
                                                                                                    Restarting a Smart Connect Task
                                                                                                    1. Log in to the console.
                                                                                                    2. Click  in the upper left corner to select a region.
                                                                                                       
                                                                                                      Select the region where your Kafka instance is located.
                                                                                                      
+
                                                                                                      
+
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Click the desired Kafka instance to view its details.
                                                                                                    5. In the navigation pane, choose Smart Connect.
                                                                                                    6. In the row containing the desired Smart Connect task, click Restart.
                                                                                                       
                                                                                                      • Modifying the source or target parameters after a Smart Connect task is created may cause the restart to fail.
                                                                                                      • Restarting a Smart Connect task resets the synchronization progress and the synchronization task will be restarted.
                                                                                                      
+
                                                                                                      
+
                                                                                                    7. Click OK.
                                                                                                    
+
                                                                                                    
+
                                                                                                    
+
+
diff --git a/docs/dms/umn/kafka_ug_0021.html b/docs/dms/umn/kafka_ug_0021.html
index 103daa59..d14f7bad 100644
--- a/docs/dms/umn/kafka_ug_0021.html
+++ b/docs/dms/umn/kafka_ug_0021.html
@@ -1,7 +1,7 @@
 
 
 
                                                                                                    Querying the Kafka Consumer Group List
                                                                                                    
-
                                                                                                    This section describes how to query the consumer group list.
                                                                                                    
+
                                                                                                    After a consumer group is created, you can view its configuration and status.
                                                                                                    
 
                                                                                                    Viewing the Consumer Group List (Console)
                                                                                                    1. Log in to the console.
                                                                                                    2. Click  in the upper left corner to select a region.
                                                                                                       
                                                                                                      Select the region where your Kafka instance is located.
                                                                                                      
 
                                                                                                      
 
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Click the desired Kafka instance to view its details.
                                                                                                    5. In the navigation pane, choose the Consumer Groups tab.
                                                                                                      The consumer group name, status, and Coordinator (ID) are displayed. Coordinator (ID) indicates the broker where the coordinator component is located. The consumer group status can be:
                                                                                                      
@@ -9,8 +9,49 @@
 
                                                                                                    6. (Optional) To query a consumer group, enter a consumer group name or status, Coordinator (ID), or keyword, then press Enter.
                                                                                                    7. (Optional) To refresh the consumer group list, click  in the upper right corner.
                                                                                                    
 
                                                                                                    
 
                                                                                                    Viewing the Consumer Group List (Kafka CLI)
                                                                                                    • For a Kafka instance with ciphertext access disabled, run the following command in the /bin directory of the Kafka client:
                                                                                                      ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --list
                                                                                                      
-
                                                                                                    • For a Kafka instance with ciphertext access enabled, do as follows:
                                                                                                      1. (Optional) For the Kafka security protocol, is SASL_PLAINTEXT or SASL_SSL used?
                                                                                                        • SASL_PLAINTEXT: Skip this step if the username and password are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password by referring to 3.
                                                                                                        • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. In other cases, create the ssl-user-config.properties file in the /config directory of the Kafka client. Add the username and password, and the SSL certificate configuration by referring to 3.
                                                                                                        
-
                                                                                                      2. Run the following command in the /bin directory of the Kafka client:
                                                                                                        ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --list --command-config ./config/ssl-user-config.properties 
                                                                                                        
+
                                                                                                        Parameter description: connection-address indicates the Kafka instance address, which can be obtained in the Connection area on the Basic Information page on the Kafka console.
                                                                                                        
+
                                                                                                        Example:
                                                                                                        
+
                                                                                                        [root@ecs-kafka bin]# ./kafka-consumer-groups.sh --bootstrap-server 192.168.xx.xx:9092,192.xx.xx.212:9092,192.xx.xx.147:9092 --list
+test
+__consumer-group-dial-test
+[root@ecs-kafka bin]#
                                                                                                        
+
                                                                                                      3. For a Kafka instance with ciphertext access enabled, do as follows:
                                                                                                        1. (Optional) Modify the client configuration file.
                                                                                                          View Security Protocol in the Connection area on the Basic Information page on the Kafka console. The configuration settings vary depending on the protocol.
                                                                                                          • SASL_PLAINTEXT: Skip this step if the username and password are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                                                                                            security.protocol=SASL_PLAINTEXT
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                                                                                            
+
                                                                                                            Parameter description: username and password are the ones you set when enabling ciphertext access for the first time or when creating a user.
                                                                                                            
+
                                                                                                          • SASL_SSL: Skip this step if the username, password, and SSL certificate are already set. Otherwise, create the ssl-user-config.properties file in the /config directory on the Kafka client and add the following content to the file:
                                                                                                            security.protocol=SASL_SSL
+ssl.truststore.location={ssl_truststore_path}
+ssl.truststore.password=dms@kafka
+ssl.endpoint.identification.algorithm=
+# If the SASL mechanism is SCRAM-SHA-512, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
+# If the SASL mechanism is PLAIN, configure as follows:
+sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                                                                                            
+
                                                                                                            Parameter description:
                                                                                                            
+
                                                                                                            • ssl.truststore.location: path for storing the client.jks certificate. Even in Windows, you need to use slashes (/) for the certificate path. Do not use backslashes (\), which are used by default for paths in Windows. Otherwise, the client will fail to obtain the certificate.
                                                                                                            • ssl.truststore.password: server certificate password, which must be set to dms@kafka and cannot be changed.
                                                                                                            • ssl.endpoint.identification.algorithm: whether to verify the certificate domain name. This parameter must be left blank, which indicates disabling domain name verification.
                                                                                                            • username and password: username and password you set when enabling ciphertext access for the first time or when creating a user.
                                                                                                            
+
                                                                                                          
+
                                                                                                          
+
                                                                                                        2. Run the following command in the /bin directory of the Kafka client:
                                                                                                          ./kafka-consumer-groups.sh --bootstrap-server ${connection-address} --list --command-config ../config/ssl-user-config.properties 
                                                                                                          
+
                                                                                                          Parameter description: connection-address indicates the Kafka instance address, which can be obtained in the Connection area on the Basic Information page on the Kafka console.
                                                                                                          
+
                                                                                                          Example:
                                                                                                          
+
                                                                                                          [root@ecs-kafka bin]# ./kafka-consumer-groups.sh --bootstrap-server 192.168.xx.xx:9093,192.168.xx.xx:9093,192.168.xx.xx:9093 --list --command-config ../config/ssl-user-config.properties
+test
+__consumer-group-dial-test
+[root@ecs-kafka bin]#
                                                                                                          
 
                                                                                                        
 
                                                                                                    
 
                                                                                                    
diff --git a/docs/dms/umn/kafka_ug_0023.html b/docs/dms/umn/kafka_ug_0023.html
index 9215cbeb..bb62d397 100644
--- a/docs/dms/umn/kafka_ug_0023.html
+++ b/docs/dms/umn/kafka_ug_0023.html
@@ -1,38 +1,37 @@
 
 
 
                                                                                                    Reassigning Kafka Partitions
                                                                                                    
-
                                                                                                    Scenario
                                                                                                    Partition reassignment is to reassign replicas of a partition to different brokers to solve the problem of unbalanced broker load.
                                                                                                    
+
                                                                                                    Partition reassignment is to reassign replicas of a partition to different brokers to solve the problem of unbalanced broker load.
                                                                                                    
 
                                                                                                    Partition reassignment is required in the following scenarios:
                                                                                                    
-
                                                                                                    • After the broker quantity is increased for an instance, the replicas of the original topic partitions are migrated to the new brokers.
                                                                                                    • The leader partition is degraded to be a follower on a heavily loaded broker.
                                                                                                    • The number of replicas is increased or decreased.
                                                                                                    
+
                                                                                                    • After you add brokers to an instance, new topics are created on new brokers, and the original topics are still on the original brokers, resulting in unbalanced partitions. To migrate the replicas of the original topic partitions to the new brokers, reassign partitions.
                                                                                                    • The leader partition is degraded to be a follower on a heavily loaded broker.
                                                                                                    • The number of replicas is increased or decreased.
                                                                                                    
 
                                                                                                    The DMS for Kafka console provides automatic and manual reassignment. Automatic reassignment is recommended because it ensures that leaders are evenly distributed.
                                                                                                    
 
                                                                                                     
                                                                                                    This function is unavailable for single-node instances.
                                                                                                    
 
                                                                                                    
+
                                                                                                    Operation Impact
                                                                                                    • Partition reassignment on topics with a large amount of data consumes a large amount of network and storage bandwidth. As a result, service requests may time out or the latency may increase. Therefore, you are advised to perform reassignment during off-peak hours. Compare the current instance load based on the instance specifications to decide whether the remaining instance capacity can support partition reassignment. Do not reassign partitions when there is insufficient bandwidth or when the CPU usage is greater than 90%. To view data volume and CPU usage of a topic, see Message Size and CPU Usage on the monitoring page. For details, see Viewing Kafka Metrics.
                                                                                                    • A throttle refers to the upper limit of the bandwidth for replication of a topic, to ensure that other topics on the instance are not affected. Note that throttles apply to replication triggered by both normal message production and partition reassignment. If the throttle is too small, normal message production may be affected, and partition reassignment may never complete. If partitions are continuously reassigned, contact customer service.
                                                                                                    • You cannot delete topics whose reassignment tasks have started. Otherwise, the tasks will never complete.
                                                                                                    • You cannot modify the partition quantity of topics whose reassignment tasks have started.
                                                                                                    • Reassignment tasks cannot be manually stopped. Please wait until they complete.
                                                                                                    • If partition reassignment has been scheduled, reassignment cannot be scheduled again for any topic in this instance until this reassignment is executed.
                                                                                                    • After partition reassignment, the metadata of the topic changes. If the producer does not support the retry mechanism, a few requests will fail, causing some messages to fail to be produced.
                                                                                                    • Reassignment takes a long time if the topic has a large amount of data. You are advised to decrease the topic retention period based on the topic consumption so that historical data of the topic can be deleted in a timely manner to accelerate the migration. To view data volume of a topic, see Message Size on the monitoring page. For details, see Viewing Kafka Metrics.
                                                                                                    
 
                                                                                                    
-
                                                                                                    Operation Impact
                                                                                                    • Partition reassignment on topics with a large amount of data consumes a large amount of network and storage bandwidth. As a result, service requests may time out or the latency may increase. Therefore, you are advised to perform reassignment during off-peak hours. Compare the current instance load based on the instance specifications to decide whether the remaining instance capacity can support partition reassignment. Do not reassign partitions when there is insufficient bandwidth or when the CPU usage is greater than 90%. To view data volume and CPU usage of a topic, see Message Size and CPU Usage on the monitoring page. For details, see Viewing Kafka Monitoring Metrics.
                                                                                                    • A throttle refers to the upper limit of the bandwidth for replication of a topic, to ensure that other topics on the instance are not affected. Note that throttles apply to replication triggered by both normal message production and partition reassignment. If the throttle is too small, normal message production may be affected, and partition reassignment may never complete. If partitions are continuously reassigned, contact customer service.
                                                                                                    • You cannot delete topics whose reassignment tasks have started. Otherwise, the tasks will never complete.
                                                                                                    • You cannot modify the partition quantity of topics whose reassignment tasks have started.
                                                                                                    • Reassignment tasks cannot be manually stopped. Please wait until they complete.
                                                                                                    • If partition reassignment has been scheduled, reassignment cannot be scheduled again for any topic in this instance until this reassignment is executed.
                                                                                                    • After partition reassignment, the metadata of the topic changes. If the producer does not support the retry mechanism, a few requests will fail, causing some messages to fail to be produced.
                                                                                                    • Reassignment takes a long time if the topic has a large amount of data. You are advised to decrease the topic retention period based on the topic consumption so that historical data of the topic can be deleted in a timely manner to accelerate the migration. To view data volume of a topic, see Message Size on the monitoring page. For details, see Viewing Kafka Monitoring Metrics.
                                                                                                    
-
                                                                                                    
-
                                                                                                    Preparing for Partition Reassignment
                                                                                                    • To reduce the amount of data to be migrated, decrease the topic aging time without affecting services and wait for messages to age. After the reassignment is complete, you can restore the aging time. To view data volume of a topic, see Message Size on the monitoring page. For details, see Viewing Kafka Monitoring Metrics.
                                                                                                    • The target broker should have sufficient disk space. To check available disk space of each broker, see Viewing Kafka Disk Usage. If the remaining disk capacity of the target broker is close to the amount of data to be migrated to the broker, expand the disk capacity before the reassignment.
                                                                                                    
+
                                                                                                    Preparing for Partition Reassignment
                                                                                                    • To reduce the amount of data to be migrated, decrease the topic retention period without affecting services and wait for messages to age. After the reassignment is complete, you can restore the retention period. To change the topic retention period, see Changing Kafka Message Retention Period.
                                                                                                    • The target broker should have sufficient disk space. To check available disk space of each broker, see Viewing Kafka Disk Usage. If the remaining disk capacity of the target broker is close to the amount of data to be migrated to the broker, expand the disk capacity before the reassignment.
                                                                                                    
 
                                                                                                    
 
                                                                                                    Auto Reassignment
                                                                                                    1. Log in to the console.
                                                                                                    2. Click  in the upper left corner to select a region.
                                                                                                       
                                                                                                      Select the region where your Kafka instance is located.
                                                                                                      
 
                                                                                                      
-
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Click the desired Kafka instance to view the instance details.
                                                                                                    5. In the navigation pane, choose the Topics tab.
                                                                                                    6. Reassign partitions using either of the following methods:
                                                                                                      • Select one or more topics and choose Reassign > Auto above the topic list.
                                                                                                      • In the row that contains the desired topic, choose More > Reassign > Auto.
                                                                                                      
+
                                                                                                    7. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    8. Click the desired Kafka instance to view the instance details.
                                                                                                    9. In the navigation pane, choose Topics.
                                                                                                    10. Reassign partitions using either of the following methods:
                                                                                                      • Select one or more topics and choose Reassign > Auto above the topic list.
                                                                                                      • In the row that contains the desired topic, choose More > Reassign > Auto.
                                                                                                      
 
                                                                                                    11. Set automatic reassignment parameters.
                                                                                                      • In the Brokers area, select the brokers to assign the topic's partition replicas to.
                                                                                                      • In the Topics area, enter the number of replicas to be automatically reassigned. The number of replicas must be less than or equal to the number of brokers.
                                                                                                      • Specify throttle. The default value is -1, indicating that there is no throttle If the instance has low workload (for example, only 30/300 MB/s is used), you are not advised to limit the bandwidth. If a throttle is required, you are advised to set it to a value greater than or equal to the total production bandwidth of the to-be-reassigned topic multiplied by the maximum number of replicas of the to-be-reassigned topic. For details, see Calculating a Throttle.
                                                                                                      • For Execute, specify when to execute the reassignment. Now means to execute it immediately. As scheduled means to execute it at the scheduled time.
                                                                                                      
 
                                                                                                      Figure 1 Setting automatic reassignment parameters
                                                                                                      
 
                                                                                                    12. (Optional) Click Calculate. Time Required indicates how long automatic balancing will take.
                                                                                                    13. Click OK.
                                                                                                      The following table lists how to check whether reassignment is complete (scheduled and non-scheduled tasks):
                                                                                                      
 
-
                                                                                                      Table 1 Checking the reassignment result
                                                                                                      Task Type
                                                                                                      
+
                                                                                                      
-
-
-
-
-
@@ -46,25 +45,25 @@
 
                                                                                                      Manual Reassignment
                                                                                                      1. Log in to the console.
                                                                                                      2. Click  in the upper left corner to select a region.
                                                                                                         
                                                                                                        Select the region where your Kafka instance is located.
                                                                                                        
 
                                                                                                        
-
                                                                                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                      4. Click the desired Kafka instance to view the instance details.
                                                                                                      5. In the navigation pane, choose the Topics tab.
                                                                                                      6. Reassign partitions using either of the following methods:
                                                                                                        • Select a topic and choose Reassign > Manual above the topic list. Manual reassignment does not support batch operations.
                                                                                                        • In the row that contains the desired topic, choose More > Reassign > Manual.
                                                                                                        
+
                                                                                                      7. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                      8. Click the desired Kafka instance to view the instance details.
                                                                                                      9. In the navigation pane, choose Topics.
                                                                                                      10. Reassign partitions using either of the following methods:
                                                                                                        • Select a topic and choose Reassign > Manual above the topic list. Manual reassignment does not support batch operations.
                                                                                                        • In the row that contains the desired topic, choose More > Reassign > Manual.
                                                                                                        
 
                                                                                                      11. Set manual reassignment parameters.
                                                                                                        • In the upper right corner of the Manual dialog box, click Delete Replica or Add Replica to reduce or increase the number of replicas for each partition of the topic.
                                                                                                        • Under the name of the replica to be reassigned, click the broker name or  and select the target broker to migrate the replica to. Assign replicas of the same partition to different brokers.
                                                                                                        • Specify throttle. The default value is -1, indicating that there is no throttle If the instance has low workload (for example, only 30/300 MB/s is used), you are not advised to limit the bandwidth. If a throttle is required, you are advised to set it to a value greater than or equal to the total production bandwidth of the to-be-reassigned topic multiplied by the maximum number of replicas of the to-be-reassigned topic. For details, see Calculating a Throttle.
                                                                                                        • For Execute, specify when to execute the reassignment. Now means to execute it immediately. As scheduled means to execute it at the scheduled time.
                                                                                                        
 
                                                                                                        Figure 3 Setting manual reassignment parameters
                                                                                                        
 
                                                                                                      12. (Optional) Click Calculate. Time Required indicates how long manual balancing will take.
                                                                                                      13. Click OK.
                                                                                                        The following table lists how to check whether reassignment is complete (scheduled and non-scheduled tasks):
                                                                                                        
 
-
                                                                                                      Table 1 Checking the reassignment result
                                                                                                      Task Type
                                                                                                      
 
                                                                                                      Reassignment Result
                                                                                                      
+
                                                                                                      Reassignment Result
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Background tasks
                                                                                                      
+
                                                                                                      Background tasks
                                                                                                      
 
                                                                                                      In the upper left corner of the topic list, click View details and the Background Tasks > Background tasks page is displayed. The reassignment task is complete when it is in the Successful state.
                                                                                                      
+
                                                                                                      In the upper left corner of the topic list, click View details and the Background Tasks > Background tasks page is displayed. The reassignment task is complete when it is in the Successful state.
                                                                                                      
                                                                                                       		
 
                                                                                                      Scheduled tasks
                                                                                                      
+
                                                                                                      Scheduled tasks
                                                                                                      
 
                                                                                                      1. The Background Tasks > Scheduled tasks page is displayed. This page only shows whether scheduled tasks start to execute instead of whether they are successful.
                                                                                                        • When the task status is Pending, reassignment has not been executed.
                                                                                                        • When the task status is Successful, reassignment has started.
                                                                                                        • When the task status is Cancel, reassignment has been canceled.
                                                                                                        
+
                                                                                                      1. The Background Tasks > Scheduled tasks page is displayed. This page only shows whether scheduled tasks start to execute instead of whether they are successful.
                                                                                                        • When the task status is Pending, reassignment has not been executed.
                                                                                                        • When the task status is Successful, reassignment has started.
                                                                                                        • When the task status is Cancel, reassignment has been canceled.
                                                                                                        
 
                                                                                                      2. Click Background tasks tab page. When the task status is Successful, reassignment has completed.
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Table 2 Checking the reassignment result
                                                                                                      Task Type
                                                                                                      
+
                                                                                                      
-
-
-
-
-
@@ -86,82 +85,82 @@
 
                                                                                                      Assume that the partition reassignment task needs to be completed within 200s and each replica has 100 MB data. Calculate the throttle in the following scenarios:
                                                                                                      Scenario 1: Topic 1 has two partitions and two replicas, and Topic 2 has one partition and one replica. All leader replicas are on the same broker. One replica needs to be added for Topic 1 and Topic 2 respectively.
                                                                                                      
 
-
                                                                                                      Table 2 Checking the reassignment result
                                                                                                      Task Type
                                                                                                      
 
                                                                                                      Reassignment Result
                                                                                                      
+
                                                                                                      Reassignment Result
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Background tasks
                                                                                                      
+
                                                                                                      Background tasks
                                                                                                      
 
                                                                                                      In the upper left corner of the topic list, click View details and the Background Tasks > Background tasks page is displayed. The reassignment task is complete when it is in the Successful state.
                                                                                                      
+
                                                                                                      In the upper left corner of the topic list, click View details and the Background Tasks > Background tasks page is displayed. The reassignment task is complete when it is in the Successful state.
                                                                                                      
                                                                                                       		
 
                                                                                                      Scheduled tasks
                                                                                                      
+
                                                                                                      Scheduled tasks
                                                                                                      
 
                                                                                                      1. The Background Tasks > Scheduled tasks page is displayed. This page only shows whether scheduled tasks start to execute instead of whether they are successful.
                                                                                                        • When the task status is Pending, reassignment has not been executed.
                                                                                                        • When the task status is Successful, reassignment has started.
                                                                                                        • When the task status is Cancel, reassignment has been canceled.
                                                                                                        
+
                                                                                                      1. The Background Tasks > Scheduled tasks page is displayed. This page only shows whether scheduled tasks start to execute instead of whether they are successful.
                                                                                                        • When the task status is Pending, reassignment has not been executed.
                                                                                                        • When the task status is Successful, reassignment has started.
                                                                                                        • When the task status is Cancel, reassignment has been canceled.
                                                                                                        
 
                                                                                                      2. Click Background tasks tab page. When the task status is Successful, reassignment has completed.
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Table 3 Replica distribution before reassignment
                                                                                                      Topic Name
                                                                                                      
+
                                                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                      Table 3 Replica distribution before reassignment
                                                                                                      Topic Name
                                                                                                      
 
                                                                                                      Partition Name
                                                                                                      
+
                                                                                                      Partition Name
                                                                                                      
 
                                                                                                      Broker of Leader Replica
                                                                                                      
+
                                                                                                      Broker of Leader Replica
                                                                                                      
 
                                                                                                      Broker of Follower Replica
                                                                                                      
+
                                                                                                      Broker of Follower Replica
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 1
                                                                                                      
+
                                                                                                      0, 1
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 2
                                                                                                      
+
                                                                                                      0, 2
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 2
                                                                                                      
+
                                                                                                      Topic 2
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
                                                                                                       		
 
                                                                                                      
                                                                                                       
 
                                                                                                      
 
                                                                                                      
 
-
                                                                                                      Table 4 Replica distribution after reassignment
                                                                                                      Topic Name
                                                                                                      
+
                                                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@@ -174,100 +173,100 @@
 
                                                                                                      Scenario 2: Topic 1 has two partitions and one replica, and Topic 2 has two partitions and one replica. Leader replicas are on different brokers. One replica needs to be added for Topic 1 and Topic 2 respectively.
                                                                                                      
 
-
                                                                                                      Table 4 Replica distribution after reassignment
                                                                                                      Topic Name
                                                                                                      
 
                                                                                                      Partition Name
                                                                                                      
+
                                                                                                      Partition Name
                                                                                                      
 
                                                                                                      Broker of Leader Replica
                                                                                                      
+
                                                                                                      Broker of Leader Replica
                                                                                                      
 
                                                                                                      Broker of Follower Replica
                                                                                                      
+
                                                                                                      Broker of Follower Replica
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 1, 2
                                                                                                      
+
                                                                                                      0, 1, 2
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 1, 2
                                                                                                      
+
                                                                                                      0, 1, 2
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 2
                                                                                                      
+
                                                                                                      Topic 2
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 2
                                                                                                      
+
                                                                                                      0, 2
                                                                                                      
                                                                                                       		
 
                                                                                                      
                                                                                                       
 
                                                                                                      Table 5 Replica distribution before reassignment
                                                                                                      Topic Name
                                                                                                      
+
                                                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                      Table 5 Replica distribution before reassignment
                                                                                                      Topic Name
                                                                                                      
 
                                                                                                      Partition Name
                                                                                                      
+
                                                                                                      Partition Name
                                                                                                      
 
                                                                                                      Broker of Leader Replica
                                                                                                      
+
                                                                                                      Broker of Leader Replica
                                                                                                      
 
                                                                                                      Broker of Follower Replica
                                                                                                      
+
                                                                                                      Broker of Follower Replica
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 2
                                                                                                      
+
                                                                                                      Topic 2
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 2
                                                                                                      
+
                                                                                                      Topic 2
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      2
                                                                                                      
+
                                                                                                      2
                                                                                                      
 
                                                                                                      2
                                                                                                      
+
                                                                                                      2
                                                                                                      
                                                                                                       		
 
                                                                                                      
                                                                                                       
 
                                                                                                      
 
                                                                                                      
 
-
                                                                                                      Table 6 Replica distribution after reassignment
                                                                                                      Topic Name
                                                                                                      
+
                                                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@@ -280,64 +279,64 @@
 
                                                                                                      In conclusion, to complete the partition reassignment task within 200s, set the throttle to a value greater than or equal to 1.5 MB/s. The bandwidth should be set to be greater than or equal to 2 MB/s because the limit on it on the console must be an integer.
                                                                                                      Scenario 3: Both Topic 1 and Topic 2 have one partition and two replicas. All leader replicas are on the same broker. One replica needs to be added to Topic 1. Messages are produced on Topic 1, causing replication.
                                                                                                      
 
-
                                                                                                      Table 6 Replica distribution after reassignment
                                                                                                      Topic Name
                                                                                                      
 
                                                                                                      Partition Name
                                                                                                      
+
                                                                                                      Partition Name
                                                                                                      
 
                                                                                                      Broker of Leader Replica
                                                                                                      
+
                                                                                                      Broker of Leader Replica
                                                                                                      
 
                                                                                                      Broker of Follower Replica
                                                                                                      
+
                                                                                                      Broker of Follower Replica
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 2
                                                                                                      
+
                                                                                                      0, 2
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      1, 2
                                                                                                      
+
                                                                                                      1, 2
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 2
                                                                                                      
+
                                                                                                      Topic 2
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      1, 2
                                                                                                      
+
                                                                                                      1, 2
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 2
                                                                                                      
+
                                                                                                      Topic 2
                                                                                                      
 
                                                                                                      1
                                                                                                      
+
                                                                                                      1
                                                                                                      
 
                                                                                                      2
                                                                                                      
+
                                                                                                      2
                                                                                                      
 
                                                                                                      2, 0
                                                                                                      
+
                                                                                                      2, 0
                                                                                                      
                                                                                                       		
 
                                                                                                      
                                                                                                       
 
                                                                                                      Table 7 Replica distribution before reassignment
                                                                                                      Topic Name
                                                                                                      
+
                                                                                                      
-
-
-
-
-
-
-
-
-
-
-
                                                                                                      Table 7 Replica distribution before reassignment
                                                                                                      Topic Name
                                                                                                      
 
                                                                                                      Partition Name
                                                                                                      
+
                                                                                                      Partition Name
                                                                                                      
 
                                                                                                      Broker of Leader Replica
                                                                                                      
+
                                                                                                      Broker of Leader Replica
                                                                                                      
 
                                                                                                      Broker of Follower Replica
                                                                                                      
+
                                                                                                      Broker of Follower Replica
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 1
                                                                                                      
+
                                                                                                      0, 1
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 2
                                                                                                      
+
                                                                                                      Topic 2
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 1
                                                                                                      
+
                                                                                                      0, 1
                                                                                                      
                                                                                                       		
 
                                                                                                      
                                                                                                       
 
                                                                                                      
 
                                                                                                      
 
-
                                                                                                      
+
+
+
+
diff --git a/docs/dms/umn/kafka_ug_0045.html b/docs/dms/umn/kafka_ug_0045.html
index 65fdd95a..4841e166 100644
--- a/docs/dms/umn/kafka_ug_0045.html
+++ b/docs/dms/umn/kafka_ug_0045.html
@@ -1,17 +1,17 @@
 
                                                                                                      Viewing Kafka Topic Details
                                                                                                      
-
                                                                                                      On the console, you can view the details of a Kafka instance including subscriptions to a topic, offsets and number of messages in each partition, and producer addresses.
                                                                                                      
-
                                                                                                      Viewing Topic Details
                                                                                                      1. Log in to the console.
                                                                                                      2. Click  in the upper left corner to select a region.
                                                                                                         
                                                                                                        Select the region where your Kafka instance is located.
                                                                                                        
+
                                                                                                        On the Kafka console, you can view basic information, partition and producer information, and subscriptions of a topic.
                                                                                                        
+
                                                                                                        Procedure
                                                                                                        1. Log in to the console.
                                                                                                        2. Click  in the upper left corner to select a region.
                                                                                                           
                                                                                                          Select the region where your Kafka instance is located.
                                                                                                          
 
                                                                                                          
-
                                                                                                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                        4. Click the desired Kafka instance to view its details.
                                                                                                        5. In the navigation pane, choose the Topics tab.
                                                                                                        6. Click a topic to view its details.
                                                                                                          The general information, subscriptions, partitions, and producers are displayed.
                                                                                                          
+
                                                                                                        7. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                        8. Click the desired Kafka instance to view its details.
                                                                                                        9. In the navigation pane, choose Topics.
                                                                                                        10. Click a topic to view its details.
                                                                                                          The general information, subscriptions, partitions, and producers are displayed.
                                                                                                          
 
                                                                                                          • General information: topic name, brokers, partitions, and creation time
                                                                                                             
                                                                                                            • For topics created much earlier, creation time is not displayed on the topic details page. See the console.
                                                                                                            • For topics automatically created, and created by commands or code on the client, creation time is not displayed on the topic details page.
                                                                                                            
 
                                                                                                            
 
                                                                                                          • Subscriptions: consumer group name and status, Coordinator (ID), and accumulated messages
                                                                                                            Click Details in the Operation column or the name of a consumer group.
                                                                                                            
 
                                                                                                             
                                                                                                            If an instance contains more than 10,000 consumer groups, the subscription relationships of topics cannot be queried.
                                                                                                            
 
                                                                                                            
 
                                                                                                          • Partitions: partition No., minimum offset, maximum offset, number of messages, and message update time
                                                                                                            Figure 1 Partitions
                                                                                                            
-
                                                                                                          • Producers: broker address, producer address, and producer connected time
                                                                                                             
                                                                                                            • The producer information is displayed only when a producer is producing a message into the topic.
                                                                                                            • For topics created much earlier, Producer tab page is not displayed on the topic details page. See the console.
                                                                                                            
+
                                                                                                          • Producers: broker address, producer address, and producer connected time
                                                                                                             
                                                                                                            • The producer information is displayed only when a producer is producing messages into topics.
                                                                                                            • For topics created much earlier, Producer tab page is not displayed on the topic details page. See the console.
                                                                                                            
 
                                                                                                            
 
                                                                                                          
 
                                                                                                        
diff --git a/docs/dms/umn/kafka_ug_0046.html b/docs/dms/umn/kafka_ug_0046.html
index 50769fbf..3c19a518 100644
--- a/docs/dms/umn/kafka_ug_0046.html
+++ b/docs/dms/umn/kafka_ug_0046.html
@@ -1,34 +1,33 @@
 
 
 
                                                                                                        Deleting Kafka Messages
                                                                                                        
-
                                                                                                        Scenario
                                                                                                        This section describes how to delete messages on the console.
                                                                                                        
+
                                                                                                        This section describes how to delete messages stored in a topic on the console.
                                                                                                        
 
                                                                                                         
                                                                                                        Deleted messages cannot be recovered.
                                                                                                        
 
                                                                                                        
-
                                                                                                        
 
                                                                                                        Prerequisites
                                                                                                        Before deleting a message, set the auto.offset.reset parameter in the code of consumption. auto.offset.reset specifies the consumption policy of a consumer when there is no initial offset in Kafka or the current offset does not exist (for example, the current offset has been deleted). Options:
                                                                                                        
 
                                                                                                        • latest: The offset is automatically reset to the latest offset.
                                                                                                        • earliest: The offset is automatically reset to the earliest offset.
                                                                                                        • none: The system throws an exception to the consumer.
                                                                                                        
 
                                                                                                         
                                                                                                        If this parameter is set to latest, the producer may start to send messages to new partitions (if any) before the consumer resets to the initial offset. As a result, some messages will be lost.
                                                                                                        
 
                                                                                                        
 
                                                                                                        
-
                                                                                                        Deleting Kafka Messages
                                                                                                        1. Log in to the console.
                                                                                                        2. Click  in the upper left corner to select a region.
                                                                                                           
                                                                                                          Select the region where your Kafka instance is located.
                                                                                                          
+
                                                                                                          Procedure
                                                                                                          1. Log in to the console.
                                                                                                          2. Click  in the upper left corner to select a region.
                                                                                                             
                                                                                                            Select the region where your Kafka instance is located.
                                                                                                            
 
                                                                                                            
 
                                                                                                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                          4. Click the desired Kafka instance to view its details.
                                                                                                          5. In the navigation pane, choose Topics.
                                                                                                          6. Perform either of the following steps to display the Delete Message dialog box:
                                                                                                            • If ciphertext access has not been enabled for the instance, click Delete Messages in the row that contains the topic whose messages you want to delete.
                                                                                                            • If ciphertext access has been enabled for the instance, choose More > Delete Messages in the row that contains the topic whose messages you want to delete.
                                                                                                            
 
                                                                                                          7. Set the parameters for deleting messages, as shown in Table 1.
                                                                                                            Figure 1 Deleting messages
                                                                                                            
 
-
                                                                                                      Table 8 Replica distribution after reassignment
                                                                                                      Topic Name
                                                                                                      
+
                                                                                                      
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/dms/umn/kafka_ug_0024.html b/docs/dms/umn/kafka_ug_0024.html
index 43c99261..b04e5941 100644
--- a/docs/dms/umn/kafka_ug_0024.html
+++ b/docs/dms/umn/kafka_ug_0024.html
@@ -1,8 +1,8 @@
 
                                                                                                      Viewing Sample Code of Kafka Production and Consumption
                                                                                                      
-
                                                                                                      On the console, view sample code for creating and retrieving messages in Java, Go, and Python.
                                                                                                      
-
                                                                                                      Viewing Sample Code of Kafka Production and Consumption
                                                                                                      1. Log in to the console.
                                                                                                      2. Click  in the upper left corner to select a region.
                                                                                                         
                                                                                                        Select the region where your Kafka instance is located.
                                                                                                        
+
                                                                                                        Distributed Message Service allows you to view sample Java, Go, and Python code of producing and consuming messages on the console. You can quickly complete Kafka client integration.
                                                                                                        
+
                                                                                                        Procedure
                                                                                                        1. Log in to the console.
                                                                                                        2. Click  in the upper left corner to select a region.
                                                                                                           
                                                                                                          Select the region where your Kafka instance is located.
                                                                                                          
 
                                                                                                          
 
                                                                                                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                        4. Click the desired Kafka instance to view the instance details.
                                                                                                        5. In the navigation pane, choose Topics.
                                                                                                        6. Click View Sample Code. The Sample Code dialog box is displayed.
                                                                                                          View sample code for creating and retrieving messages in Java, Go, and Python. Set Access By to PlainText to view the sample code where SASL_SSL authentication is disabled. Set Access By to SASL_SSL to view the sample code where SASL_SSL authentication is enabled.
                                                                                                          
 
                                                                                                        
diff --git a/docs/dms/umn/kafka_ug_0027.html b/docs/dms/umn/kafka_ug_0027.html
index 977764a2..53ff39c6 100644
--- a/docs/dms/umn/kafka_ug_0027.html
+++ b/docs/dms/umn/kafka_ug_0027.html
@@ -4,7 +4,7 @@
 
                                                                                                        Export the topic list on the console. Batch export is supported.
                                                                                                        
 
                                                                                                        Prerequisites
                                                                                                        A topic has been created.
                                                                                                        
 
                                                                                                        
-
                                                                                                        Exporting the Topic List
                                                                                                        1. Log in to the console.
                                                                                                        2. Click  in the upper left corner to select a region.
                                                                                                           
                                                                                                          Select the region where your Kafka instance is located.
                                                                                                          
+
                                                                                                          Procedure
                                                                                                          1. Log in to the console.
                                                                                                          2. Click  in the upper left corner to select a region.
                                                                                                             
                                                                                                            Select the region where your Kafka instance is located.
                                                                                                            
 
                                                                                                            
 
                                                                                                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                          4. Click the desired Kafka instance to view the instance details.
                                                                                                          5. In the navigation pane, choose Topics.
                                                                                                          6. Click  in the upper right to export the topic list.
                                                                                                            The topic list contains the following information: topic name, number of partitions, number of replicas, aging time, message timestamp, max. message size, and whether synchronous replication and flushing are enabled.
                                                                                                            
 
                                                                                                          
diff --git a/docs/dms/umn/kafka_ug_0041.html b/docs/dms/umn/kafka_ug_0041.html
new file mode 100644
index 00000000..7690b25e
--- /dev/null
+++ b/docs/dms/umn/kafka_ug_0041.html
@@ -0,0 +1,23 @@
+
+
+
                                                                                                          Disabling Smart Connect
                                                                                                          
+
                                                                                                          Disable Smart Connect and resources can be freed.
                                                                                                          
+
                                                                                                          Disabling Smart Connect does not affect services.
                                                                                                          
+
                                                                                                           
                                                                                                          This function is unavailable for single-node instances. Kafka 3.x instances do not support this function.
                                                                                                          
+
                                                                                                          
+
                                                                                                          Impact
                                                                                                          • Brokers related to Smart Connect are automatically deleted.
                                                                                                          • If you disable Smart Connect and then enable it again, deleted Smart Connect tasks cannot be retrieved and need to be created again.
                                                                                                          
+
                                                                                                          
+
                                                                                                          Prerequisites
                                                                                                          • A Kafka instance has been created and is in the Running state.
                                                                                                          • All Smart Connect tasks must be deleted. This is to prevent running Smart Connect tasks from being lost after Smart Connect is disabled.
                                                                                                          
+
                                                                                                          
+
                                                                                                          Procedure
                                                                                                          1. Log in to the console.
                                                                                                          2. Click  in the upper left corner to select a region.
                                                                                                             
                                                                                                            Select the region where your Kafka instance is located.
                                                                                                            
+
                                                                                                            
+
                                                                                                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                          4. Disable Smart Connect using either of the following methods:
                                                                                                            • In the row containing the desired Kafka instance, choose More > Disable Smart Connect.
                                                                                                            • Click the desired Kafka instance to view its details. In the upper right corner, choose More > Disable Smart Connect.
                                                                                                            
+
                                                                                                          5. Click  to disable Smart Connect. Then click Next.
                                                                                                          6. Ensure that Smart Connect is disabled and click Submit.
                                                                                                          
+
                                                                                                          
+
                                                                                                          
+
+
diff --git a/docs/dms/umn/kafka_ug_0043.html b/docs/dms/umn/kafka_ug_0043.html
index 533d53cc..41012c91 100644
--- a/docs/dms/umn/kafka_ug_0043.html
+++ b/docs/dms/umn/kafka_ug_0043.html
@@ -1,8 +1,8 @@
 
 
 
                                                                                                          Configuring Automatic Topic Creation
                                                                                                          
-
                                                                                                          Automatic topic creation: A topic will be automatically created when a message is produced in or consumed from a topic that does not exist. By default, the topic has parameters listed in Table 1.
                                                                                                          
-
                                                                                                          After you change the value of the log.retention.hours, default.replication.factor, or num.partitions parameter, the value will be used in later topics that are automatically created. For example, assume that num.partitions is changed to 5, an automatically created topic has parameters listed in Table 1.
                                                                                                          
+
                                                                                                          Automatic Topic Creation indicates that a topic will be automatically created when a message is produced in or consumed from a topic that does not exist. By default, the topic has parameters listed in Table 1.
                                                                                                          
+
                                                                                                          After you change the value of the log.retention.hours (retention period), default.replication.factor (replica quantity), or num.partitions (partition quantity) parameter, the value will be used in later topics that are automatically created. For example, assume that num.partitions is changed to 5, an automatically created topic has parameters listed in Table 1.
                                                                                                          
 
 
                                                                                                      Table 8 Replica distribution after reassignment
                                                                                                      Topic Name
                                                                                                      
 
                                                                                                      Partition Name
                                                                                                      
+
                                                                                                      Partition Name
                                                                                                      
 
                                                                                                      Broker of Leader Replica
                                                                                                      
+
                                                                                                      Broker of Leader Replica
                                                                                                      
 
                                                                                                      Broker of Follower Replica
                                                                                                      
+
                                                                                                      Broker of Follower Replica
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Topic 1
                                                                                                      
+
                                                                                                      Topic 1
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 1, 2
                                                                                                      
+
                                                                                                      0, 1, 2
                                                                                                      
                                                                                                       		
 
                                                                                                      Topic 2
                                                                                                      
+
                                                                                                      Topic 2
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0
                                                                                                      
+
                                                                                                      0
                                                                                                      
 
                                                                                                      0, 1
                                                                                                      
+
                                                                                                      0, 1
                                                                                                      
                                                                                                       		
 
                                                                                                      
                                                                                                       
 
 
                                                                                                      
@@ -64,7 +64,7 @@
 
                                                                                                      Table 1 Topic parameters
                                                                                                      Parameter
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      
-
                                                                                                      Configuring Automatic Topic Creation
                                                                                                      1. Log in to the console.
                                                                                                      2. Click  in the upper left corner to select a region.
                                                                                                         
                                                                                                        Select the region where your Kafka instance is located.
                                                                                                        
+
                                                                                                        Procedure
                                                                                                        1. Log in to the console.
                                                                                                        2. Click  in the upper left corner to select a region.
                                                                                                           
                                                                                                          Select the region where your Kafka instance is located.
                                                                                                          
 
                                                                                                          
 
                                                                                                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                        4. Click the desired Kafka instance to view its details.
                                                                                                        5. In the Instance Information area, click  or  next to Automatic Topic Creation. The Confirm dialog box is displayed.
                                                                                                           
                                                                                                          Enabling or disabling automatic topic creation may cause instance restarts.
                                                                                                          
 
                                                                                                          
diff --git a/docs/dms/umn/kafka_ug_0044.html b/docs/dms/umn/kafka_ug_0044.html
index 40340bcd..8edf2fbf 100644
--- a/docs/dms/umn/kafka_ug_0044.html
+++ b/docs/dms/umn/kafka_ug_0044.html
@@ -83,6 +83,14 @@
 
                                                                                                          SCRAM-SHA-512 is enabled by default. To use PLAIN, enable SASL/PLAIN. SCRAM-SHA-512 authentication is recommended for plaintext transmission.
                                                                                                          
 
 
                                                                                                      Cross-VPC Access Protocol
                                                                                                      
+
                                                                                                      -
                                                                                                      
+
                                                                                                      • When Plaintext Access is enabled and Ciphertext Access is disabled, PLAINTEXT is used for Cross-VPC Access Protocol.
                                                                                                      • When Ciphertext Access is enabled and Security Protocol is SASL_SSL, SASL_SSL is used for Cross-VPC Access Protocol.
                                                                                                      • When Ciphertext Access is enabled and Security Protocol is SASL_PLAINTEXT, SASL_PLAINTEXT is used for Cross-VPC Access Protocol.
                                                                                                      
+
                                                                                                      Fixed once the instance is created.
                                                                                                      
+
                                                                                                      
 
                                                                                                      SASL/PLAIN
                                                                                                      
                                                                                                       		
 
                                                                                                      -
                                                                                                      
@@ -98,7 +106,7 @@
 
                                                                                                      Username and password used by the client to connect to the Kafka instance.
                                                                                                      
 
                                                                                                      A username should contain 4 to 64 characters, start with a letter, and contain only letters, digits, hyphens (-), and underscores (_).
                                                                                                      
 
                                                                                                      A password must meet the following requirements:
                                                                                                      
-
                                                                                                      • Contains 8 to 32 characters.
                                                                                                      • Contains at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters `~! @#$ %^&*()-_=+\|[{}];:'",<.>? and spaces, and cannot start with a hyphen (-).
                                                                                                      • Cannot be the username spelled forwards or backwards.
                                                                                                      
+
                                                                                                      • Contains 8 to 32 characters.
                                                                                                      • Cannot start with a hyphen (-) and must contain at least three of the following character types: uppercase letters, lowercase letters, digits, spaces, and special characters `~! @#$ %^&*()-_=+\|[{}];:'",<.>?
                                                                                                      • Cannot be the username spelled forwards or backwards.
                                                                                                      
 
                                                                                                      The username cannot be changed once ciphertext access is enabled.
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
 
                                                                                                      Table 1 Parameters for deleting a message
                                                                                                      Parameter
                                                                                                      
+
                                                                                                      
-
-
-
-
-
                                                                                                      Table 1 Parameters for deleting a message
                                                                                                      Parameter
                                                                                                      
 
                                                                                                      Description
                                                                                                      
+
                                                                                                      Description
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Partition
                                                                                                      
+
                                                                                                      Partition
                                                                                                      
 
                                                                                                      Select the ID of the partition where the message is located.
                                                                                                      
+
                                                                                                      Select the ID of the partition where the message is located.
                                                                                                      
                                                                                                       		
 
                                                                                                      Offset
                                                                                                      
+
                                                                                                      Offset
                                                                                                      
 
                                                                                                      Enter the offset. Data before this offset will be deleted.
                                                                                                      
+
                                                                                                      Enter an offset. The data after the earliest offset and before this offset will be deleted. For example, if the earliest offset is 2 and the entered offset is 5, the messages whose offset ranges from 2 to 4 will be deleted.
                                                                                                      
 
                                                                                                       NOTE: 
                                                                                                      • If Offset is set to -1, all messages in the partition will be deleted.
                                                                                                      • If the offset you entered is not between the earliest offset and the latest offset of the specified partition, no messages will be deleted.