From 190f09501cb1bcda3a128de48656175a48c9d6c5 Mon Sep 17 00:00:00 2001 From: chenjunjie Date: Mon, 6 Oct 2025 09:50:17 +0000 Subject: [PATCH] DMS UMN 20250314 version Reviewed-by: Liudmila Denisova Co-authored-by: chenjunjie Co-committed-by: chenjunjie --- docs/dms/umn/ALL_META.TXT.json | 674 +++++++++----- docs/dms/umn/CLASS.TXT.json | 807 +++++++++-------- docs/dms/umn/CreateUserAndGrantPolicy.html | 56 +- docs/dms/umn/Kafka-client-best-practice.html | 8 +- docs/dms/umn/Kafka-client-parameter.html | 111 ++- docs/dms/umn/Kafka-specification.html | 197 ++--- .../umn/ProductDescPrivilegeManagement.html | 2 +- docs/dms/umn/TagManagement.html | 18 +- docs/dms/umn/UserPrivilegeManagement.html | 4 +- docs/dms/umn/en-us_image_0000001093972624.png | Bin 348 -> 462 bytes docs/dms/umn/en-us_image_0000001160616010.png | Bin 401 -> 0 bytes docs/dms/umn/en-us_image_0000001206335999.png | Bin 762 -> 0 bytes docs/dms/umn/en-us_image_0000001427644729.png | Bin 407 -> 0 bytes docs/dms/umn/en-us_image_0000001453201733.png | Bin 188 -> 217 bytes docs/dms/umn/en-us_image_0000001540501562.png | Bin 416 -> 461 bytes docs/dms/umn/en-us_image_0000001707049736.png | Bin 416 -> 0 bytes docs/dms/umn/en-us_image_0000001921463342.png | Bin 47297 -> 47404 bytes docs/dms/umn/en-us_image_0000001998520149.png | Bin 42475 -> 42739 bytes docs/dms/umn/en-us_image_0000002063422361.png | Bin 23419 -> 0 bytes docs/dms/umn/en-us_image_0000002110644228.png | Bin 0 -> 179 bytes docs/dms/umn/en-us_image_0000002157871349.png | Bin 0 -> 222 bytes ...8.png => en-us_image_0000002281749220.png} | Bin ...8.png => en-us_image_0000002309000337.png} | Bin docs/dms/umn/en-us_image_0000002317148937.png | Bin 0 -> 485 bytes docs/dms/umn/en-us_image_0000002317222029.png | Bin 0 -> 485 bytes docs/dms/umn/kafka-bp-migration.html | 7 +- docs/dms/umn/kafka-dnat.html | 95 +- docs/dms/umn/kafka-faq-0001.html | 3 +- docs/dms/umn/kafka-faq-0005.html | 3 +- docs/dms/umn/kafka-faq-0033.html | 20 +- docs/dms/umn/kafka-faq-0035.html | 6 +- docs/dms/umn/kafka-faq-0038.html | 1 - docs/dms/umn/kafka-faq-0041.html | 5 +- docs/dms/umn/kafka-faq-0063.html | 11 + docs/dms/umn/kafka-faq-0064.html | 11 + docs/dms/umn/kafka-faq-0065.html | 12 + docs/dms/umn/kafka-faq-0066.html | 11 + docs/dms/umn/kafka-faq-0067.html | 15 + docs/dms/umn/kafka-faq-0068.html | 11 + docs/dms/umn/kafka-faq-0069.html | 12 + docs/dms/umn/kafka-faq-0070.html | 17 + docs/dms/umn/kafka-faq-180604024.html | 22 +- docs/dms/umn/kafka-faq-190416001.html | 2 + docs/dms/umn/kafka-faq-191030002.html | 2 + docs/dms/umn/kafka-faq-191030003.html | 4 +- docs/dms/umn/kafka-faq-191030004.html | 8 + docs/dms/umn/kafka-faq-200423001.html | 2 + docs/dms/umn/kafka-faq-200426003.html | 2 +- docs/dms/umn/kafka-faq-200426005.html | 4 +- docs/dms/umn/kafka-faq-200426007.html | 4 +- docs/dms/umn/kafka-faq-200426009.html | 2 +- docs/dms/umn/kafka-faq-200426014.html | 2 +- docs/dms/umn/kafka-faq-200426016.html | 82 +- docs/dms/umn/kafka-faq-200426024.html | 80 +- docs/dms/umn/kafka-faq-200426025.html | 80 +- docs/dms/umn/kafka-faq-200426026.html | 2 +- docs/dms/umn/kafka-faq-200426028.html | 12 - docs/dms/umn/kafka-faq-200426030.html | 2 +- docs/dms/umn/kafka-faq-200426032.html | 2 +- docs/dms/umn/kafka-faq-200426036.html | 12 +- docs/dms/umn/kafka-faq-200426100.html | 2 +- docs/dms/umn/kafka-pd-0052.html | 158 ++-- docs/dms/umn/kafka-pd-0053.html | 18 + docs/dms/umn/kafka-pd-0056.html | 79 ++ docs/dms/umn/kafka-pd-190605001.html | 2 +- docs/dms/umn/kafka-pd-190605002.html | 2 + docs/dms/umn/kafka-pd-190605003.html | 140 +-- docs/dms/umn/kafka-pd-200720001.html | 2 +- docs/dms/umn/kafka-qs-0409001.html | 52 +- docs/dms/umn/kafka-scenarios.html | 1 + docs/dms/umn/kafka-trouble-0001.html | 2 +- docs/dms/umn/kafka-ug-00001.html | 16 +- docs/dms/umn/kafka-ug-0001.html | 129 ++- docs/dms/umn/kafka-ug-0002.html | 19 +- docs/dms/umn/kafka-ug-0003.html | 50 +- docs/dms/umn/kafka-ug-0004.html | 8 +- docs/dms/umn/kafka-ug-0006.html | 110 ++- docs/dms/umn/kafka-ug-0007.html | 261 +++--- docs/dms/umn/kafka-ug-0012.html | 99 ++- docs/dms/umn/kafka-ug-0014.html | 141 ++- docs/dms/umn/kafka-ug-0015.html | 90 +- docs/dms/umn/kafka-ug-0034.html | 35 +- docs/dms/umn/kafka-ug-0035.html | 13 +- docs/dms/umn/kafka-ug-0038.html | 18 +- docs/dms/umn/kafka-ug-0041.html | 16 +- docs/dms/umn/kafka-ug-0053.html | 4 +- docs/dms/umn/kafka-ug-0056.html | 4 +- docs/dms/umn/kafka-ug-0058.html | 2 + docs/dms/umn/kafka-ug-0069.html | 2 +- docs/dms/umn/kafka-ug-0072.html | 104 +++ docs/dms/umn/kafka-ug-0075.html | 15 + docs/dms/umn/kafka-ug-0319001.html | 302 +++---- docs/dms/umn/kafka-ug-0723001.html | 6 +- docs/dms/umn/kafka-ug-0723006.html | 2 + docs/dms/umn/kafka-ug-180413002.html | 829 ++++++++++-------- docs/dms/umn/kafka-ug-180418002.html | 146 ++- docs/dms/umn/kafka-ug-180524001.html | 9 +- docs/dms/umn/kafka-ug-180604012.html | 24 +- docs/dms/umn/kafka-ug-180604013.html | 166 ++-- docs/dms/umn/kafka-ug-180604014.html | 65 +- docs/dms/umn/kafka-ug-180604015.html | 10 +- docs/dms/umn/kafka-ug-180604016.html | 11 +- docs/dms/umn/kafka-ug-180604018.html | 229 +++-- docs/dms/umn/kafka-ug-180604019.html | 97 +- docs/dms/umn/kafka-ug-180604020.html | 92 +- docs/dms/umn/kafka-ug-180801001.html | 308 ++++++- docs/dms/umn/kafka-ug-181221001.html | 50 +- docs/dms/umn/kafka-ug-190605001.html | 8 +- docs/dms/umn/kafka-ug-190904001.html | 71 +- docs/dms/umn/kafka-ug-200119002.html | 6 +- docs/dms/umn/kafka-ug-200506001.html | 14 +- docs/dms/umn/kafka_faq_0058.html | 2 +- docs/dms/umn/kafka_faq_0059.html | 2 +- docs/dms/umn/kafka_faq_0061.html | 2 +- docs/dms/umn/kafka_pd_0004.html | 148 ++++ docs/dms/umn/kafka_trouble_0007.html | 16 + docs/dms/umn/kafka_ug_0017.html | 17 +- docs/dms/umn/kafka_ug_0018.html | 28 +- docs/dms/umn/kafka_ug_0021.html | 62 +- docs/dms/umn/kafka_ug_0023.html | 37 +- docs/dms/umn/kafka_ug_0024.html | 5 +- docs/dms/umn/kafka_ug_0027.html | 4 +- docs/dms/umn/kafka_ug_0041.html | 11 +- docs/dms/umn/kafka_ug_0043.html | 78 +- docs/dms/umn/kafka_ug_0044.html | 122 ++- docs/dms/umn/kafka_ug_0045.html | 144 ++- docs/dms/umn/kafka_ug_0046.html | 20 +- 127 files changed, 4474 insertions(+), 2706 deletions(-) delete mode 100644 docs/dms/umn/en-us_image_0000001160616010.png delete mode 100644 docs/dms/umn/en-us_image_0000001206335999.png delete mode 100644 docs/dms/umn/en-us_image_0000001427644729.png delete mode 100644 docs/dms/umn/en-us_image_0000001707049736.png delete mode 100644 docs/dms/umn/en-us_image_0000002063422361.png create mode 100644 docs/dms/umn/en-us_image_0000002110644228.png create mode 100644 docs/dms/umn/en-us_image_0000002157871349.png rename docs/dms/umn/{en-us_image_0000001756508438.png => en-us_image_0000002281749220.png} (100%) rename docs/dms/umn/{en-us_image_0000001756853218.png => en-us_image_0000002309000337.png} (100%) create mode 100644 docs/dms/umn/en-us_image_0000002317148937.png create mode 100644 docs/dms/umn/en-us_image_0000002317222029.png create mode 100644 docs/dms/umn/kafka-faq-0063.html create mode 100644 docs/dms/umn/kafka-faq-0064.html create mode 100644 docs/dms/umn/kafka-faq-0065.html create mode 100644 docs/dms/umn/kafka-faq-0066.html create mode 100644 docs/dms/umn/kafka-faq-0067.html create mode 100644 docs/dms/umn/kafka-faq-0068.html create mode 100644 docs/dms/umn/kafka-faq-0069.html create mode 100644 docs/dms/umn/kafka-faq-0070.html delete mode 100644 docs/dms/umn/kafka-faq-200426028.html create mode 100644 docs/dms/umn/kafka-pd-0053.html create mode 100644 docs/dms/umn/kafka-pd-0056.html create mode 100644 docs/dms/umn/kafka-ug-0072.html create mode 100644 docs/dms/umn/kafka-ug-0075.html create mode 100644 docs/dms/umn/kafka_pd_0004.html create mode 100644 docs/dms/umn/kafka_trouble_0007.html diff --git a/docs/dms/umn/ALL_META.TXT.json b/docs/dms/umn/ALL_META.TXT.json index 277049d66..5d0f36cca 100644 --- a/docs/dms/umn/ALL_META.TXT.json +++ b/docs/dms/umn/ALL_META.TXT.json @@ -75,13 +75,13 @@ "githuburl":"" }, { - "uri":"Kafka-specification.html", - "node_id":"kafka-specification.xml", + "uri":"kafka-pd-0053.html", + "node_id":"kafka-pd-0053.xml", "product_code":"kafka", "code":"5", - "des":"Kafka instances are compatible with open-source Kafka v1.1.0, v2.3.0, v2.7, and v3.x. Kafka instances are classified into cluster and single-node types. A cluster instanc", + "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":"Specifications,Service Overview,User Guide", + "kw":"Kafka Instance Specifications", "search_title":"", "metedata":[ { @@ -89,14 +89,50 @@ "documenttype":"usermanual" } ], - "title":"Specifications", + "title":"Kafka Instance Specifications", + "githuburl":"" + }, + { + "uri":"kafka-pd-0056.html", + "node_id":"kafka-pd-0056.xml", + "product_code":"kafka", + "code":"6", + "des":"A single-node Kafka instance has one broker, is compatible with open-source Kafka 2.7, and is applicable to test scenarios. Do not use it for production services.In the f", + "doc_type":"usermanual", + "kw":"Single-node Kafka Instances,Kafka Instance Specifications,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Single-node Kafka Instances", + "githuburl":"" + }, + { + "uri":"Kafka-specification.html", + "node_id":"kafka-specification.xml", + "product_code":"kafka", + "code":"7", + "des":"A cluster Kafka instance has three or more brokers, and is compatible with open-source Kafka 2.3.0, 2.7, and 3.x.In the following table:For Kafka instances, the number of", + "doc_type":"usermanual", + "kw":"Cluster Kafka Instances,Kafka Instance Specifications,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Cluster Kafka Instances", "githuburl":"" }, { "uri":"kafka-pd-0052.html", "node_id":"kafka-pd-0052.xml", "product_code":"kafka", - "code":"6", + "code":"8", "des":"A single-node Kafka instance has only one broker. These instances do not guarantee performance or reliability and are for trial use or testing only. In the production env", "doc_type":"usermanual", "kw":"Comparing Single-node and Cluster Kafka Instances,Service Overview,User Guide", @@ -111,11 +147,29 @@ "title":"Comparing Single-node and Cluster Kafka Instances", "githuburl":"" }, + { + "uri":"kafka_pd_0004.html", + "node_id":"kafka_pd_0004.xml", + "product_code":"kafka", + "code":"9", + "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":"Comparing Kafka and RocketMQ,Service Overview,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Comparing Kafka and RocketMQ", + "githuburl":"" + }, { "uri":"kafka-pd-200720001.html", "node_id":"kafka-pd-200720001.xml", "product_code":"kafka", - "code":"7", + "code":"10", "des":"DMS is compatible with open-source Kafka and has customized and enhanced Kafka features. In addition to the advantages of open-source Kafka, DMS for Kafka provides more r", "doc_type":"usermanual", "kw":"Comparing DMS for Kafka and Open-Source Kafka,Service Overview,User Guide", @@ -133,8 +187,8 @@ "uri":"kafka-pd-190605003.html", "node_id":"kafka-pd-190605003.xml", "product_code":"kafka", - "code":"8", - "des":"This section describes the notes and constraints on DMS.", + "code":"11", + "des":"This section describes the notes and constraints on Distributed Message Service (DMS). Use your Kafka instances as prescribed to avoid program exceptions.Any instability ", "doc_type":"usermanual", "kw":"Notes and Constraints,Service Overview,User Guide", "search_title":"", @@ -151,7 +205,7 @@ "uri":"kafka-pd-190605002.html", "node_id":"kafka-pd-190605002.xml", "product_code":"kafka", - "code":"9", + "code":"12", "des":"Cloud Trace Service (CTS)CTS generates traces to provide you with a history of operations performed on cloud service resources. The traces include operation requests sent", "doc_type":"usermanual", "kw":"Related Services,Service Overview,User Guide", @@ -169,7 +223,7 @@ "uri":"glossary-kafka.html", "node_id":"glossary-kafka.xml", "product_code":"kafka", - "code":"10", + "code":"13", "des":"DMS for Kafka of the cloud service platform uses Kafka as the message engine. This chapter presents explanations of basic concepts of Kafka.A topic is a category for mess", "doc_type":"usermanual", "kw":"Basic Concepts,Service Overview,User Guide", @@ -187,10 +241,10 @@ "uri":"ProductDescPrivilegeManagement.html", "node_id":"productdescprivilegemanagement.xml", "product_code":"kafka", - "code":"11", + "code":"14", "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", + "kw":"Permissions,Service Overview,User Guide", "search_title":"", "metedata":[ { @@ -198,14 +252,14 @@ "documenttype":"usermanual" } ], - "title":"Permission", + "title":"Permissions", "githuburl":"" }, { "uri":"kafka-ug-00003.html", "node_id":"kafka-ug-00003.xml", "product_code":"kafka", - "code":"12", + "code":"15", "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":"Getting Started", @@ -223,7 +277,7 @@ "uri":"kafka-qs-0409001.html", "node_id":"kafka-qs-0409001.xml", "product_code":"kafka", - "code":"13", + "code":"16", "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", @@ -241,7 +295,7 @@ "uri":"kafka-ug-0069.html", "node_id":"kafka-ug-0069.xml", "product_code":"kafka", - "code":"14", + "code":"17", "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", @@ -259,10 +313,10 @@ "uri":"UserPrivilegeManagement.html", "node_id":"userprivilegemanagement.xml", "product_code":"kafka", - "code":"15", + "code":"18", "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":"Permission Management", + "kw":"Permissions Management", "search_title":"", "metedata":[ { @@ -271,17 +325,17 @@ "documenttype":"usermanual" } ], - "title":"Permission Management", + "title":"Permissions Management", "githuburl":"" }, { "uri":"CreateUserAndGrantPolicy.html", "node_id":"createuserandgrantpolicy.xml", "product_code":"kafka", - "code":"16", + "code":"19", "des":"This section describes how to use Identity and Access Management (IAM) for fine-grained permissions control for your Distributed Message Service (DMS) for Kafka resources", "doc_type":"usermanual", - "kw":"Creating a User and Granting DMS for Kafka Permissions,Permission Management,User Guide", + "kw":"Creating an IAM User and Granting DMS for Kafka Permissions,Permissions Management,User Guide", "search_title":"", "metedata":[ { @@ -290,14 +344,14 @@ "documenttype":"usermanual" } ], - "title":"Creating a User and Granting DMS for Kafka Permissions", + "title":"Creating an IAM User and Granting DMS for Kafka Permissions", "githuburl":"" }, { "uri":"kafka-ug-180604013.html", "node_id":"kafka-ug-180604013.xml", "product_code":"kafka", - "code":"17", + "code":"20", "des":"Kafka instances are tenant-exclusive, and physically isolated in deployment. You can customize the computing capabilities and storage space of a Kafka instance as require", "doc_type":"usermanual", "kw":"Creating a Kafka Instance,User Guide", @@ -316,7 +370,7 @@ "uri":"kafka-ug-0720001.html", "node_id":"kafka-ug-0720001.xml", "product_code":"kafka", - "code":"18", + "code":"21", "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":"Configuring Topics", @@ -335,7 +389,7 @@ "uri":"kafka-ug-180604018.html", "node_id":"kafka-ug-180604018.xml", "product_code":"kafka", - "code":"19", + "code":"22", "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", @@ -354,7 +408,7 @@ "uri":"kafka-ug-0002.html", "node_id":"kafka-ug-0002.xml", "product_code":"kafka", - "code":"20", + "code":"23", "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", @@ -373,7 +427,7 @@ "uri":"kafka-ug-0058.html", "node_id":"kafka-ug-0058.xml", "product_code":"kafka", - "code":"21", + "code":"24", "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":"Managing Topics", @@ -392,8 +446,8 @@ "uri":"kafka_ug_0045.html", "node_id":"kafka_ug_0045.xml", "product_code":"kafka", - "code":"22", - "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", + "code":"25", + "des":"On the Kafka console, you can view basic information, partition and producer information, and subscriptions of a topic.If an instance contains more than 10,000 consumer g", "doc_type":"usermanual", "kw":"Viewing Kafka Topic Details,Managing Topics,User Guide", "search_title":"", @@ -411,7 +465,7 @@ "uri":"kafka-ug-0038.html", "node_id":"kafka-ug-0038.xml", "product_code":"kafka", - "code":"23", + "code":"26", "des":"This section describes how to modify configurations in Table 1 of a Kafka topic on the console.Modifying Synchronous Replication, Synchronous Flushing, Message Timestamp,", "doc_type":"usermanual", "kw":"Modifying Kafka Topic Configurations,Managing Topics,User Guide", @@ -430,8 +484,8 @@ "uri":"kafka-ug-0006.html", "node_id":"kafka-ug-0006.xml", "product_code":"kafka", - "code":"24", - "des":"After creating a topic, you can increase the number of partitions as required.Changing the number of partitions does not restart the instance or affect services.Methods f", + "code":"27", + "des":"After creating a topic, you can change the number of partitions as required. Changing the number of partitions does not restart the instance or affect services.Methods fo", "doc_type":"usermanual", "kw":"Changing Kafka Partition Quantity,Managing Topics,User Guide", "search_title":"", @@ -445,12 +499,30 @@ "title":"Changing Kafka Partition Quantity", "githuburl":"" }, + { + "uri":"kafka-ug-0072.html", + "node_id":"kafka-ug-0072.xml", + "product_code":"kafka", + "code":"28", + "des":"The replicas of a Kafka topic can be modified as required.Reassigning partitions can modify replicas automatically or manually on the Kafka console. For more information,", + "doc_type":"usermanual", + "kw":"Modifying Kafka Topic Replicas,Managing Topics,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Modifying Kafka Topic Replicas", + "githuburl":"" + }, { "uri":"kafka_ug_0027.html", "node_id":"kafka_ug_0027.xml", "product_code":"kafka", - "code":"25", - "des":"Export the topic list on the console. Batch export is supported.A topic has been created.Select the region where your Kafka instance is located.The topic list contains th", + "code":"29", + "des":"Export the topic list on the console. Batch export is supported.A topic has been created.The topic list contains the following information: topic name, number of partitio", "doc_type":"usermanual", "kw":"Exporting the Kafka Topic List,Managing Topics,User Guide", "search_title":"", @@ -468,7 +540,7 @@ "uri":"kafka_ug_0023.html", "node_id":"kafka_ug_0023.xml", "product_code":"kafka", - "code":"26", + "code":"30", "des":"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 th", "doc_type":"usermanual", "kw":"Reassigning Kafka Partitions,Managing Topics,User Guide", @@ -487,7 +559,7 @@ "uri":"kafka_ug_0043.html", "node_id":"kafka_ug_0043.xml", "product_code":"kafka", - "code":"27", + "code":"31", "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", @@ -506,8 +578,8 @@ "uri":"kafka-ug-180604019.html", "node_id":"kafka-ug-180604019.xml", "product_code":"kafka", - "code":"28", - "des":"Delete a topic using either of the following methods:Deleting a Kafka Topic (Console)Deleting a Kafka Topic on the ClientA Kafka instance has been created, and a topic ha", + "code":"32", + "des":"This document describes how to delete a topic.Deleting a Kafka Topic (Console)Deleting a Kafka Topic on the ClientDeleting a topic clears the topic data permanently.For a", "doc_type":"usermanual", "kw":"Deleting a Kafka Topic,Managing Topics,User Guide", "search_title":"", @@ -525,7 +597,7 @@ "uri":"kafka-ug190605003.html", "node_id":"kafka-ug190605003.xml", "product_code":"kafka", - "code":"29", + "code":"33", "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":"Connecting to an Instance", @@ -544,7 +616,7 @@ "uri":"kafka-ug-0059.html", "node_id":"kafka-ug-0059.xml", "product_code":"kafka", - "code":"30", + "code":"34", "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":"Configuring Kafka Network Connections", @@ -563,7 +635,7 @@ "uri":"kafka-ug-180604012.html", "node_id":"kafka-ug-180604012.xml", "product_code":"kafka", - "code":"31", + "code":"35", "des":"A client can connect to a Kafka instance over a public or private network. Notes before using a private network:By default, a client and a Kafka instance are interconnect", "doc_type":"usermanual", "kw":"Kafka Network Connection Conditions,Configuring Kafka Network Connections,User Guide", @@ -582,8 +654,8 @@ "uri":"kafka-ug-0319001.html", "node_id":"kafka-ug-0319001.xml", "product_code":"kafka", - "code":"32", - "des":"Clients can use IPv4 or IPv6 addresses to access a Kafka instance over a public network.By IPv4: On the Kafka console, enable public access and configure EIPs for the ins", + "code":"36", + "des":"A client can use IPv4 or IPv6 addresses to access a Kafka instance over a public network.By IPv4: On the Kafka console, enable public access and configure EIPs for the in", "doc_type":"usermanual", "kw":"Configuring Kafka Public Access,Configuring Kafka Network Connections,User Guide", "search_title":"", @@ -601,7 +673,7 @@ "uri":"kafka-ug-0001.html", "node_id":"kafka-ug-0001.xml", "product_code":"kafka", - "code":"33", + "code":"37", "des":"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 thi", "doc_type":"usermanual", "kw":"Accessing Kafka Using a VPC Endpoint Across VPCs,Configuring Kafka Network Connections,User Guide", @@ -620,7 +692,7 @@ "uri":"kafka-dnat.html", "node_id":"kafka-dnat.xml", "product_code":"kafka", - "code":"34", + "code":"38", "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", @@ -639,7 +711,7 @@ "uri":"kafka-ug-0061.html", "node_id":"kafka-ug-0061.xml", "product_code":"kafka", - "code":"35", + "code":"39", "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":"Configuring Kafka Access Control", @@ -658,7 +730,7 @@ "uri":"kafka_ug_0044.html", "node_id":"kafka_ug_0044.xml", "product_code":"kafka", - "code":"36", + "code":"40", "des":"You can access a Kafka instance in plaintext or ciphertext. This section describes how to change the access mode on the console.Plaintext access: Clients connect to the K", "doc_type":"usermanual", "kw":"Configuring Plaintext or Ciphertext Access to Kafka Instances,Configuring Kafka Access Control,User ", @@ -677,7 +749,7 @@ "uri":"kafka-ug-0003.html", "node_id":"kafka-ug-0003.xml", "product_code":"kafka", - "code":"37", + "code":"41", "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 ACL Users,Configuring Kafka Access Control,User Guide", @@ -696,7 +768,7 @@ "uri":"kafka-ug-0062.html", "node_id":"kafka-ug-0062.xml", "product_code":"kafka", - "code":"38", + "code":"42", "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":"Configuring the Kafka Client", @@ -714,7 +786,7 @@ "uri":"Kafka-client-parameter.html", "node_id":"kafka-client-parameter.xml", "product_code":"kafka", - "code":"39", + "code":"43", "des":"This section provides recommendations on configuring common parameters for Kafka producers and consumers. Kafka clients in different versions may have different parameter", "doc_type":"usermanual", "kw":"Setting Parameters for Kafka Clients,Configuring the Kafka Client,User Guide", @@ -732,7 +804,7 @@ "uri":"Kafka-client-best-practice.html", "node_id":"kafka-client-best-practice.xml", "product_code":"kafka", - "code":"40", + "code":"44", "des":"Ensure that the owner thread does not exit abnormally. Otherwise, the client may fail to initiate consumption requests and the consumption will be blocked.Commit messages", "doc_type":"usermanual", "kw":"Suggestions on Using the Kafka Client,Configuring the Kafka Client,User Guide", @@ -750,7 +822,7 @@ "uri":"kafka-ug-180604020.html", "node_id":"kafka-ug-180604020.xml", "product_code":"kafka", - "code":"41", + "code":"45", "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", @@ -769,7 +841,7 @@ "uri":"kafka-ug-180801001.html", "node_id":"kafka-ug-180801001.xml", "product_code":"kafka", - "code":"42", + "code":"46", "des":"This section describes how to access a Kafka instance in ciphertext on an open-source Kafka client. The client connects to the Kafka instance with SASL authentication. If", "doc_type":"usermanual", "kw":"Connecting to Kafka Using the Client (Ciphertext Access),Connecting to an Instance,User Guide", @@ -788,7 +860,7 @@ "uri":"kafka-ug-0720002.html", "node_id":"kafka-ug-0720002.xml", "product_code":"kafka", - "code":"43", + "code":"47", "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":"Managing Messages", @@ -807,8 +879,8 @@ "uri":"kafka-ug-190904001.html", "node_id":"kafka-ug-190904001.xml", "product_code":"kafka", - "code":"44", - "des":"You can view the offset of different partitions, the message size, creation time, and body of messages in topics.Select the region where your Kafka instance is located.If", + "code":"48", + "des":"When messages are lost or fail to be consumed, you can query the content and attributes of specific messages for troubleshooting.You can view the offset of different part", "doc_type":"usermanual", "kw":"Viewing Kafka Messages,Managing Messages,User Guide", "search_title":"", @@ -826,7 +898,7 @@ "uri":"kafka-ug-200506001.html", "node_id":"kafka-ug-200506001.xml", "product_code":"kafka", - "code":"45", + "code":"49", "des":"Aging time is a period that messages in a topic are retained for. Consumers must consume messages before this period ends. Otherwise, the messages will be deleted and can", "doc_type":"usermanual", "kw":"Changing Kafka Message Retention Period,Managing Messages,User Guide", @@ -845,8 +917,8 @@ "uri":"kafka_ug_0046.html", "node_id":"kafka_ug_0046.xml", "product_code":"kafka", - "code":"46", - "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", + "code":"50", + "des":"This section describes how to delete messages stored in a topic on the console.Deleting messages takes effect permanently.Before deleting a message, set the auto.offset.r", "doc_type":"usermanual", "kw":"Deleting Kafka Messages,Managing Messages,User Guide", "search_title":"", @@ -864,7 +936,7 @@ "uri":"kafka-ug-0011.html", "node_id":"kafka-ug-0011.xml", "product_code":"kafka", - "code":"47", + "code":"51", "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":"Managing Consumer Groups", @@ -883,7 +955,7 @@ "uri":"kafka-ug-0041.html", "node_id":"kafka-ug-0041.xml", "product_code":"kafka", - "code":"48", + "code":"52", "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", @@ -902,8 +974,8 @@ "uri":"kafka_ug_0021.html", "node_id":"kafka_ug_0021.xml", "product_code":"kafka", - "code":"49", - "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", + "code":"53", + "des":"After a consumer group is created, you can view its configuration and status.The consumer group name, status, and Coordinator (ID) are displayed. Coordinator (ID) indicat", "doc_type":"usermanual", "kw":"Querying the Kafka Consumer Group List,Managing Consumer Groups,User Guide", "search_title":"", @@ -921,7 +993,7 @@ "uri":"kafka-ug-0015.html", "node_id":"kafka-ug-0015.xml", "product_code":"kafka", - "code":"50", + "code":"54", "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 Information,Managing Consumer Groups,User Guide", @@ -940,8 +1012,8 @@ "uri":"kafka-ug-0014.html", "node_id":"kafka-ug-0014.xml", "product_code":"kafka", - "code":"51", - "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", + "code":"55", + "des":"A consumption offset indicates the consumption progress of a consumer. This section describes how to view and reset consumption offsets.Messages may be consumed more than", "doc_type":"usermanual", "kw":"Viewing and Resetting Kafka Consumption Offsets,Managing Consumer Groups,User Guide", "search_title":"", @@ -959,8 +1031,8 @@ "uri":"kafka-ug-0056.html", "node_id":"kafka-ug-0056.xml", "product_code":"kafka", - "code":"52", - "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 >", + "code":"56", + "des":"You can export a list of consumer groups in a Kafka instance.Select the desired consumer groups and choose Export > Export selected data to an XLSX file to export specifi", "doc_type":"usermanual", "kw":"Exporting Kafka Consumer Groups,Managing Consumer Groups,User Guide", "search_title":"", @@ -978,7 +1050,7 @@ "uri":"kafka-ug-0012.html", "node_id":"kafka-ug-0012.xml", "product_code":"kafka", - "code":"53", + "code":"57", "des":"You can delete a consumer group in either of the following ways:On the console.Use Kafka CLI. (Ensure that the Kafka instance version is the same as the CLI version.)If a", "doc_type":"usermanual", "kw":"Deleting a Kafka Consumer Group,Managing Consumer Groups,User Guide", @@ -997,7 +1069,7 @@ "uri":"kafka-ug-180604011.html", "node_id":"kafka-ug-180604011.xml", "product_code":"kafka", - "code":"54", + "code":"58", "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":"Managing Instances", @@ -1016,7 +1088,7 @@ "uri":"kafka-ug-180604014.html", "node_id":"kafka-ug-180604014.xml", "product_code":"kafka", - "code":"55", + "code":"59", "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", @@ -1035,8 +1107,8 @@ "uri":"kafka-ug-0004.html", "node_id":"kafka-ug-0004.xml", "product_code":"kafka", - "code":"56", - "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", + "code":"60", + "des":"This section describes how to view the disk usage of each broker of a Kafka instance on the console.Unavailable for single-node instances.You can query topics that use th", "doc_type":"usermanual", "kw":"Viewing Kafka Disk Usage,Managing Instances,User Guide", "search_title":"", @@ -1054,7 +1126,7 @@ "uri":"kafka-ug-200119002.html", "node_id":"kafka-ug-200119002.xml", "product_code":"kafka", - "code":"57", + "code":"61", "des":"After you initiate certain instance operations listed in Table 1, a background task will start for each operation. On the console, you can view the background task status", "doc_type":"usermanual", "kw":"Viewing Kafka Background Tasks,Managing Instances,User Guide", @@ -1073,7 +1145,7 @@ "uri":"kafka_ug_0024.html", "node_id":"kafka_ug_0024.xml", "product_code":"kafka", - "code":"58", + "code":"62", "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", @@ -1092,7 +1164,7 @@ "uri":"kafka-ug-0007.html", "node_id":"kafka-ug-0007.xml", "product_code":"kafka", - "code":"59", + "code":"63", "des":"Your Kafka instances, topics, and consumers come with default configuration parameter settings. You can modify common parameters on the DMS console. For details about par", "doc_type":"usermanual", "kw":"Modifying Kafka Instance Configuration Parameters,Managing Instances,User Guide", @@ -1111,8 +1183,8 @@ "uri":"TagManagement.html", "node_id":"tagmanagement.xml", "product_code":"kafka", - "code":"60", - "des":"Tags facilitate Kafka instance identification and management.You can add tags to a Kafka instance when creating the instance or add tags on the Tags tab page of the creat", + "code":"64", + "des":"Tags facilitate Kafka instance identification and management.You can add tags to a Kafka instance when creating the instance or add tags on the Tags page of the created i", "doc_type":"usermanual", "kw":"Configuring Kafka Instance Tags,Managing Instances,User Guide", "search_title":"", @@ -1130,8 +1202,8 @@ "uri":"kafka-ug-0053.html", "node_id":"kafka-ug-0053.xml", "product_code":"kafka", - "code":"61", - "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", + "code":"65", + "des":"You can export a list of instances on the DMS console.Select the desired instances and choose Export > Export selected data to an XLSX file to export specified instances.", "doc_type":"usermanual", "kw":"Exporting the Kafka Instance List,Managing Instances,User Guide", "search_title":"", @@ -1149,8 +1221,8 @@ "uri":"kafka-ug-180604015.html", "node_id":"kafka-ug-180604015.xml", "product_code":"kafka", - "code":"62", - "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", + "code":"66", + "des":"You can restart one or more Kafka instances in batches on the DMS console.When a Kafka instance is being restarted, message consumption and production requests of clients", "doc_type":"usermanual", "kw":"Restarting a Kafka Instance,Managing Instances,User Guide", "search_title":"", @@ -1168,8 +1240,8 @@ "uri":"kafka-ug-180604016.html", "node_id":"kafka-ug-180604016.xml", "product_code":"kafka", - "code":"63", - "des":"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 p", + "code":"67", + "des":"Delete one or more Kafka instances at a time on the DMS console.Deleting a Kafka instance will clear the instance data without any backup. Exercise caution.The status of ", "doc_type":"usermanual", "kw":"Deleting Kafka Instances,Managing Instances,User Guide", "search_title":"", @@ -1183,14 +1255,32 @@ "title":"Deleting Kafka Instances", "githuburl":"" }, + { + "uri":"kafka-ug-0075.html", + "node_id":"kafka-ug-0075.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":"Modifying Instance Specifications", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Modifying Instance Specifications", + "githuburl":"" + }, { "uri":"kafka-ug-181221001.html", "node_id":"kafka-ug-181221001.xml", "product_code":"kafka", - "code":"64", + "code":"69", "des":"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 ", "doc_type":"usermanual", - "kw":"Modifying Kafka Instance Specifications,User Guide", + "kw":"Modifying Cluster Kafka Instance Specifications,Modifying Instance Specifications,User Guide", "search_title":"", "metedata":[ { @@ -1199,14 +1289,14 @@ "documenttype":"usermanual" } ], - "title":"Modifying Kafka Instance Specifications", + "title":"Modifying Cluster Kafka Instance Specifications", "githuburl":"" }, { "uri":"kafka_ug_0016.html", "node_id":"kafka_ug_0016.xml", "product_code":"kafka", - "code":"65", + "code":"70", "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", @@ -1225,7 +1315,7 @@ "uri":"kafka-bp-migration.html", "node_id":"kafka-bp-migration.xml", "product_code":"kafka", - "code":"66", + "code":"71", "des":"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. K", "doc_type":"usermanual", "kw":"Kafka Data Migration Overview,Migrating Data,User Guide", @@ -1243,7 +1333,7 @@ "uri":"kafka-ug-0065.html", "node_id":"kafka-ug-0065.xml", "product_code":"kafka", - "code":"67", + "code":"72", "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", @@ -1261,7 +1351,7 @@ "uri":"kafka_ug_0017.html", "node_id":"kafka_ug_0017.xml", "product_code":"kafka", - "code":"68", + "code":"73", "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", @@ -1280,7 +1370,7 @@ "uri":"kafka-ug-0034.html", "node_id":"kafka-ug-0034.xml", "product_code":"kafka", - "code":"69", + "code":"74", "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", @@ -1299,7 +1389,7 @@ "uri":"kafka-ug-0035.html", "node_id":"kafka-ug-0035.xml", "product_code":"kafka", - "code":"70", + "code":"75", "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", @@ -1318,8 +1408,8 @@ "uri":"kafka_ug_0018.html", "node_id":"kafka_ug_0018.xml", "product_code":"kafka", - "code":"71", - "des":"View, delete, start, pause, or restart a Smart Connect task.This function is unavailable for single-node instances.A Smart Connect task has been created.Select the region", + "code":"76", + "des":"View, delete, start, pause, or restart a Smart Connect task.Unavailable for single-node instances.A Smart Connect task has been created.The source and target are displaye", "doc_type":"usermanual", "kw":"Managing Smart Connect Tasks,Migrating Data Using Smart Connect,User Guide", "search_title":"", @@ -1337,8 +1427,8 @@ "uri":"kafka_ug_0041.html", "node_id":"kafka_ug_0041.xml", "product_code":"kafka", - "code":"72", - "des":"Disable Smart Connect and resources can be freed.Disabling Smart Connect does not affect services.This function is unavailable for single-node instances.Brokers related t", + "code":"77", + "des":"Disable Smart Connect and resources can be freed.Disabling Smart Connect does not affect services.Brokers related to Smart Connect are automatically deleted.If you disabl", "doc_type":"usermanual", "kw":"Disabling Smart Connect,Migrating Data Using Smart Connect,User Guide", "search_title":"", @@ -1356,7 +1446,7 @@ "uri":"kafka-ug-180413001.html", "node_id":"kafka-ug-180413001.xml", "product_code":"kafka", - "code":"73", + "code":"78", "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", @@ -1375,7 +1465,7 @@ "uri":"kafka-ug-190605001.html", "node_id":"kafka-ug-190605001.xml", "product_code":"kafka", - "code":"74", + "code":"79", "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 Metrics,Monitoring and Alarms,User Guide", @@ -1394,7 +1484,7 @@ "uri":"kafka-ug-180413002.html", "node_id":"kafka-ug-180413002.xml", "product_code":"kafka", - "code":"75", + "code":"80", "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", @@ -1413,7 +1503,7 @@ "uri":"kafka-ug-180524001.html", "node_id":"kafka-ug-180524001.xml", "product_code":"kafka", - "code":"76", + "code":"81", "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", @@ -1432,7 +1522,7 @@ "uri":"kafka-ug-180418002.html", "node_id":"kafka-ug-180418002.xml", "product_code":"kafka", - "code":"77", + "code":"82", "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", @@ -1451,7 +1541,7 @@ "uri":"kafka-ug-0723004.html", "node_id":"kafka-ug-0723004.xml", "product_code":"kafka", - "code":"78", + "code":"83", "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", @@ -1469,7 +1559,7 @@ "uri":"kafka-faq-191030002.html", "node_id":"kafka-faq-191030002.xml", "product_code":"kafka", - "code":"79", + "code":"84", "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", @@ -1487,7 +1577,7 @@ "uri":"kafka-faq-200426002.html", "node_id":"kafka-faq-200426002.xml", "product_code":"kafka", - "code":"80", + "code":"85", "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", @@ -1505,8 +1595,8 @@ "uri":"kafka-faq-200426003.html", "node_id":"kafka-faq-200426003.xml", "product_code":"kafka", - "code":"81", - "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 ", + "code":"86", + "des":"The possible cause is that you do not have the Server Administrator and VPC Administrator permissions. For details about how to add permissions to a user group, see Viewi", "doc_type":"usermanual", "kw":"Why Can't I View the Subnet and Security Group Information When Creating a DMS Instance?,Instances,U", "search_title":"", @@ -1523,7 +1613,7 @@ "uri":"kafka-faq-200426005.html", "node_id":"kafka-faq-200426005.xml", "product_code":"kafka", - "code":"82", + "code":"87", "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", @@ -1541,7 +1631,7 @@ "uri":"kafka-faq-200426006.html", "node_id":"kafka-faq-200426006.xml", "product_code":"kafka", - "code":"83", + "code":"88", "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", @@ -1559,7 +1649,7 @@ "uri":"kafka-faq-200426007.html", "node_id":"kafka-faq-200426007.xml", "product_code":"kafka", - "code":"84", + "code":"89", "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", @@ -1577,7 +1667,7 @@ "uri":"kafka-faq-200426008.html", "node_id":"kafka-faq-200426008.xml", "product_code":"kafka", - "code":"85", + "code":"90", "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", @@ -1595,7 +1685,7 @@ "uri":"kafka-faq-200426009.html", "node_id":"kafka-faq-200426009.xml", "product_code":"kafka", - "code":"86", + "code":"91", "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", @@ -1613,7 +1703,7 @@ "uri":"kafka-faq-200426010.html", "node_id":"kafka-faq-200426010.xml", "product_code":"kafka", - "code":"87", + "code":"92", "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", @@ -1631,7 +1721,7 @@ "uri":"kafka-faq-200426011.html", "node_id":"kafka-faq-200426011.xml", "product_code":"kafka", - "code":"88", + "code":"93", "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 usin", "doc_type":"usermanual", "kw":"Can I Modify the Port for Accessing a Kafka Instance?,Instances,User Guide", @@ -1649,7 +1739,7 @@ "uri":"kafka-faq-200426012.html", "node_id":"kafka-faq-200426012.xml", "product_code":"kafka", - "code":"89", + "code":"94", "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", @@ -1667,7 +1757,7 @@ "uri":"kafka-faq-200426013.html", "node_id":"kafka-faq-200426013.xml", "product_code":"kafka", - "code":"90", + "code":"95", "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", @@ -1685,8 +1775,8 @@ "uri":"kafka-faq-200426014.html", "node_id":"kafka-faq-200426014.xml", "product_code":"kafka", - "code":"91", - "des":"The SASL_SSL setting can be changed for cluster instances. For details, see Configuring Plaintext or Ciphertext Access to Kafka Instances.A single-node instance does not ", + "code":"96", + "des":"The SASL_SSL setting of a cluster Kafka instance can be changed after instance creation. For details, see Configuring Plaintext or Ciphertext Access to Kafka Instances.A ", "doc_type":"usermanual", "kw":"How Do I Change the SASL_SSL Setting of a Kafka Instance?,Instances,User Guide", "search_title":"", @@ -1703,7 +1793,7 @@ "uri":"kafka_faq_0052.html", "node_id":"kafka_faq_0052.xml", "product_code":"kafka", - "code":"92", + "code":"97", "des":"There are two SASL authentication mechanisms for Kafka instances: SCRAM-SHA-512 and PLAIN.For instances with IPv6 disabled, the mechanism cannot be modified after ciphert", "doc_type":"usermanual", "kw":"How Do I Modify the SASL Mechanism?,Instances,User Guide", @@ -1721,7 +1811,7 @@ "uri":"kafka_faq_0062.html", "node_id":"kafka_faq_0062.xml", "product_code":"kafka", - "code":"93", + "code":"98", "des":"There are two security protocols for Kafka instances: SASL_SSL and SASL_PLAINTEXT.For instances with IPv6 disabled, the security protocol can be changed on the console. I", "doc_type":"usermanual", "kw":"How Do I Change the Security Protocol?,Instances,User Guide", @@ -1739,7 +1829,7 @@ "uri":"kafka-faq-0008.html", "node_id":"kafka-faq-0008.xml", "product_code":"kafka", - "code":"94", + "code":"99", "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", @@ -1757,7 +1847,7 @@ "uri":"kafka-faq-0015.html", "node_id":"kafka-faq-0015.xml", "product_code":"kafka", - "code":"95", + "code":"100", "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", @@ -1775,7 +1865,7 @@ "uri":"kafka-faq-0020.html", "node_id":"kafka-faq-0020.xml", "product_code":"kafka", - "code":"96", + "code":"101", "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", @@ -1793,7 +1883,7 @@ "uri":"kafka-faq-0023.html", "node_id":"kafka-faq-0023.xml", "product_code":"kafka", - "code":"97", + "code":"102", "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", @@ -1811,7 +1901,7 @@ "uri":"kafka-faq-0025.html", "node_id":"kafka-faq-0025.xml", "product_code":"kafka", - "code":"98", + "code":"103", "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", @@ -1829,7 +1919,7 @@ "uri":"kafka-faq-0030.html", "node_id":"kafka-faq-0030.xml", "product_code":"kafka", - "code":"99", + "code":"104", "des":"Yes.", "doc_type":"usermanual", "kw":"Do Kafka Instances Support Disk Encryption?,Instances,User Guide", @@ -1847,7 +1937,7 @@ "uri":"kafka-faq-0036.html", "node_id":"kafka-faq-0036.xml", "product_code":"kafka", - "code":"100", + "code":"105", "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", @@ -1865,7 +1955,7 @@ "uri":"kafka-faq-0037.html", "node_id":"kafka-faq-0037.xml", "product_code":"kafka", - "code":"101", + "code":"106", "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", @@ -1883,7 +1973,7 @@ "uri":"kafka-faq-0040.html", "node_id":"kafka-faq-0040.xml", "product_code":"kafka", - "code":"102", + "code":"107", "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", @@ -1901,7 +1991,7 @@ "uri":"kafka_faq_0046.html", "node_id":"kafka_faq_0046.xml", "product_code":"kafka", - "code":"103", + "code":"108", "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", @@ -1915,11 +2005,29 @@ "title":"How Do I Bind an EIP Again?", "githuburl":"" }, + { + "uri":"kafka-faq-0070.html", + "node_id":"kafka-faq-0070.xml", + "product_code":"kafka", + "code":"109", + "des":"Each broker of a Kafka instance has a 100 GB disk. The automatic deletion policy has been configured and a topic with 180 partitions has been created. The earliest messag", + "doc_type":"usermanual", + "kw":"Why Are the Earliest Messages Not Automatically Deleted When the Disk Capacity Reaches 95%?,Instance", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Why Are the Earliest Messages Not Automatically Deleted When the Disk Capacity Reaches 95%?", + "githuburl":"" + }, { "uri":"kafka_faq_0053.html", "node_id":"kafka_faq_0053.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":"Specification Modification", @@ -1937,8 +2045,8 @@ "uri":"kafka-faq-0035.html", "node_id":"kafka-faq-0035.xml", "product_code":"kafka", - "code":"105", - "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", + "code":"111", + "des":"Table 1 describes the impact of increasing specifications.", "doc_type":"usermanual", "kw":"Does Specification Modification Affect Services?,Specification Modification,User Guide", "search_title":"", @@ -1955,7 +2063,7 @@ "uri":"kafka_faq_0054.html", "node_id":"kafka_faq_0054.xml", "product_code":"kafka", - "code":"106", + "code":"112", "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", @@ -1973,7 +2081,7 @@ "uri":"kafka_faq_0056.html", "node_id":"kafka_faq_0056.xml", "product_code":"kafka", - "code":"107", + "code":"113", "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", @@ -1991,7 +2099,7 @@ "uri":"kafka_faq_0057.html", "node_id":"kafka_faq_0057.xml", "product_code":"kafka", - "code":"108", + "code":"114", "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", @@ -2009,7 +2117,7 @@ "uri":"kafka-faq-191030001.html", "node_id":"kafka-faq-191030001.xml", "product_code":"kafka", - "code":"109", + "code":"115", "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", @@ -2027,7 +2135,7 @@ "uri":"kafka-faq-180604024.html", "node_id":"kafka-faq-180604024.xml", "product_code":"kafka", - "code":"110", + "code":"116", "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", @@ -2045,7 +2153,7 @@ "uri":"kafka-faq-200426015.html", "node_id":"kafka-faq-200426015.xml", "product_code":"kafka", - "code":"111", + "code":"117", "des":"Yes. For details, see the Connecting to an Instance.", "doc_type":"usermanual", "kw":"Can I Access a Kafka Instance Over a Public Network?,Connections,User Guide", @@ -2063,7 +2171,7 @@ "uri":"kafka-faq-200426016.html", "node_id":"kafka-faq-200426016.xml", "product_code":"kafka", - "code":"112", + "code":"118", "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", @@ -2081,7 +2189,7 @@ "uri":"kafka-faq-200426017.html", "node_id":"kafka-faq-200426017.xml", "product_code":"kafka", - "code":"113", + "code":"119", "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", @@ -2099,7 +2207,7 @@ "uri":"kafka-faq-200426019.html", "node_id":"kafka-faq-200426019.xml", "product_code":"kafka", - "code":"114", + "code":"120", "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", @@ -2117,7 +2225,7 @@ "uri":"kafka-faq-200426020.html", "node_id":"kafka-faq-200426020.xml", "product_code":"kafka", - "code":"115", + "code":"121", "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", @@ -2135,7 +2243,7 @@ "uri":"kafka-faq-200426023.html", "node_id":"kafka-faq-200426023.xml", "product_code":"kafka", - "code":"116", + "code":"122", "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", @@ -2153,7 +2261,7 @@ "uri":"kafka-faq-200708002.html", "node_id":"kafka-faq-200708002.xml", "product_code":"kafka", - "code":"117", + "code":"123", "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", @@ -2171,8 +2279,8 @@ "uri":"kafka-faq-0001.html", "node_id":"kafka-faq-0001.xml", "product_code":"kafka", - "code":"118", - "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", + "code":"124", + "des":"Click the name of your Kafka instance. In the Connection section on the Basic Information page, view Instance Address (Public Network).For details about how to connect to", "doc_type":"usermanual", "kw":"How Do I Obtain the Public Access Address After Public Access Is Enabled?,Connections,User Guide", "search_title":"", @@ -2189,7 +2297,7 @@ "uri":"kafka-faq-0026.html", "node_id":"kafka-faq-0026.xml", "product_code":"kafka", - "code":"119", + "code":"125", "des":"No.", "doc_type":"usermanual", "kw":"Does DMS for Kafka Support Authentication on Clients by the Server?,Connections,User Guide", @@ -2207,7 +2315,7 @@ "uri":"kafka-faq-0027.html", "node_id":"kafka-faq-0027.xml", "product_code":"kafka", - "code":"120", + "code":"126", "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,", @@ -2225,7 +2333,7 @@ "uri":"kafka-faq-0028.html", "node_id":"kafka-faq-0028.xml", "product_code":"kafka", - "code":"121", + "code":"127", "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", @@ -2243,7 +2351,7 @@ "uri":"kafka-faq-0029.html", "node_id":"kafka-faq-0029.xml", "product_code":"kafka", - "code":"122", + "code":"128", "des":"TLS 1.2.", "doc_type":"usermanual", "kw":"Which TLS Version Does DMS for Kafka Support?,Connections,User Guide", @@ -2261,7 +2369,7 @@ "uri":"kafka-faq-0033.html", "node_id":"kafka-faq-0033.xml", "product_code":"kafka", - "code":"123", + "code":"129", "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", @@ -2279,7 +2387,7 @@ "uri":"kafka-faq-0034.html", "node_id":"kafka-faq-0034.xml", "product_code":"kafka", - "code":"124", + "code":"130", "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", @@ -2297,7 +2405,7 @@ "uri":"kafka_faq_0048.html", "node_id":"kafka_faq_0048.xml", "product_code":"kafka", - "code":"125", + "code":"131", "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", @@ -2315,7 +2423,7 @@ "uri":"kafka_faq_0051.html", "node_id":"kafka_faq_0051.xml", "product_code":"kafka", - "code":"126", + "code":"132", "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", @@ -2333,7 +2441,7 @@ "uri":"kafka_faq_0061.html", "node_id":"kafka_faq_0061.xml", "product_code":"kafka", - "code":"127", + "code":"133", "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", @@ -2351,7 +2459,7 @@ "uri":"kafka-faq-191030003.html", "node_id":"kafka-faq-191030003.xml", "product_code":"kafka", - "code":"128", + "code":"134", "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", @@ -2369,7 +2477,7 @@ "uri":"kafka-faq-200426024.html", "node_id":"kafka-faq-200426024.xml", "product_code":"kafka", - "code":"129", + "code":"135", "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", @@ -2387,7 +2495,7 @@ "uri":"kafka-faq-200426025.html", "node_id":"kafka-faq-200426025.xml", "product_code":"kafka", - "code":"130", + "code":"136", "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", @@ -2405,7 +2513,7 @@ "uri":"kafka-faq-200426101.html", "node_id":"kafka-faq-200426101.xml", "product_code":"kafka", - "code":"131", + "code":"137", "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", @@ -2423,8 +2531,8 @@ "uri":"kafka-faq-200426026.html", "node_id":"kafka-faq-200426026.xml", "product_code":"kafka", - "code":"132", - "des":"Possible cause: The aggregate number of partitions of created topics has reached the upper limit. The maximum number of partitions varies by instance specifications. For ", + "code":"138", + "des":"Possible cause: The aggregate number of partitions of created topics has reached the upper limit. The limit varies with instance specifications. For details, see Single-n", "doc_type":"usermanual", "kw":"Why Do I Fail to Create Topics?,Topics and Partitions,User Guide", "search_title":"", @@ -2441,7 +2549,7 @@ "uri":"kafka-faq-200426027.html", "node_id":"kafka-faq-200426027.xml", "product_code":"kafka", - "code":"133", + "code":"139", "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", @@ -2455,29 +2563,11 @@ "title":"Do Kafka Instances Support Batch Importing Topics or Automatic Topic Creation?", "githuburl":"" }, - { - "uri":"kafka-faq-200426028.html", - "node_id":"kafka-faq-200426028.xml", - "product_code":"kafka", - "code":"134", - "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", - "search_title":"", - "metedata":[ - { - "prodname":"kafka", - "documenttype":"usermanual" - } - ], - "title":"Why Do Deleted Topics Still Exist?", - "githuburl":"" - }, { "uri":"kafka-faq-200426030.html", "node_id":"kafka-faq-200426030.xml", "product_code":"kafka", - "code":"135", + "code":"140", "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", @@ -2495,8 +2585,8 @@ "uri":"kafka-faq-200426032.html", "node_id":"kafka-faq-200426032.xml", "product_code":"kafka", - "code":"136", - "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", + "code":"141", + "des":"If you have enabled SASL_SSL for your Kafka instance, you can configure ACL permissions for your topics. On the Topics page of the Kafka console, click Grant User Permiss", "doc_type":"usermanual", "kw":"Can I Add ACL Permissions for Topics?,Topics and Partitions,User Guide", "search_title":"", @@ -2513,7 +2603,7 @@ "uri":"kafka-faq-0003.html", "node_id":"kafka-faq-0003.xml", "product_code":"kafka", - "code":"137", + "code":"142", "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", @@ -2531,8 +2621,8 @@ "uri":"kafka-faq-0005.html", "node_id":"kafka-faq-0005.xml", "product_code":"kafka", - "code":"138", - "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", + "code":"143", + "des":"You can increase the partition quantity by increasing broker flavors or adding brokers. For details, see Modifying Cluster Kafka Instance Specifications.", "doc_type":"usermanual", "kw":"How Do I Increase the Partition Quantity?,Topics and Partitions,User Guide", "search_title":"", @@ -2549,7 +2639,7 @@ "uri":"kafka-faq-0010.html", "node_id":"kafka-faq-0010.xml", "product_code":"kafka", - "code":"139", + "code":"144", "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", @@ -2567,7 +2657,7 @@ "uri":"kafka-faq-0038.html", "node_id":"kafka-faq-0038.xml", "product_code":"kafka", - "code":"140", + "code":"145", "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?", @@ -2581,11 +2671,29 @@ "title":"What Can I Do If a Consumer Fails to Retrieve Messages from a Topic Due to Insufficient Permissions?", "githuburl":"" }, + { + "uri":"kafka-faq-0068.html", + "node_id":"kafka-faq-0068.xml", + "product_code":"kafka", + "code":"146", + "des":"No. However, you can increase the total number of partitions by increasing the broker quantity or flavor. For details, see Modifying Cluster Kafka Instance Specifications", + "doc_type":"usermanual", + "kw":"Can I Purchase Partitions Separately?,Topics and Partitions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Can I Purchase Partitions Separately?", + "githuburl":"" + }, { "uri":"kafka-faq-200423001.html", "node_id":"kafka-faq-200423001.xml", "product_code":"kafka", - "code":"141", + "code":"147", "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", @@ -2603,7 +2711,7 @@ "uri":"kafka-faq-200426033.html", "node_id":"kafka-faq-200426033.xml", "product_code":"kafka", - "code":"142", + "code":"148", "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", @@ -2621,7 +2729,7 @@ "uri":"kafka-faq-0043.html", "node_id":"kafka-faq-0043.xml", "product_code":"kafka", - "code":"143", + "code":"149", "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,", @@ -2639,7 +2747,7 @@ "uri":"kafka_faq_0059.html", "node_id":"kafka_faq_0059.xml", "product_code":"kafka", - "code":"144", + "code":"150", "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", @@ -2657,7 +2765,7 @@ "uri":"kafka_faq_0060.html", "node_id":"kafka_faq_0060.xml", "product_code":"kafka", - "code":"145", + "code":"151", "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", @@ -2675,7 +2783,7 @@ "uri":"kafka-faq-0031.html", "node_id":"kafka-faq-0031.xml", "product_code":"kafka", - "code":"146", + "code":"152", "des":"Just simply unsubscribe from them on the Kafka client.", "doc_type":"usermanual", "kw":"Can I Delete Unnecessary Topics in a Consumer Group?,Consumer Groups,User Guide", @@ -2689,11 +2797,29 @@ "title":"Can I Delete Unnecessary Topics in a Consumer Group?", "githuburl":"" }, + { + "uri":"kafka-faq-0069.html", + "node_id":"kafka-faq-0069.xml", + "product_code":"kafka", + "code":"153", + "des":"If you cannot find a consumer group from the console, the possible causes are as follows:auto.create.groups.enable is set to true, the consumer group status is EMPTY, and", + "doc_type":"usermanual", + "kw":"Why Are Consumer Groups Missing?,Consumer Groups,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Why Are Consumer Groups Missing?", + "githuburl":"" + }, { "uri":"kafka-faq-190416001.html", "node_id":"kafka-faq-190416001.xml", "product_code":"kafka", - "code":"147", + "code":"154", "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", @@ -2711,7 +2837,7 @@ "uri":"kafka-faq-200426035.html", "node_id":"kafka-faq-200426035.xml", "product_code":"kafka", - "code":"148", + "code":"155", "des":"10 MB.", "doc_type":"usermanual", "kw":"What Is the Maximum Size of a Message that Can be Created?,Messages,User Guide", @@ -2729,7 +2855,7 @@ "uri":"kafka-faq-200426036.html", "node_id":"kafka-faq-200426036.xml", "product_code":"kafka", - "code":"149", + "code":"156", "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", @@ -2747,7 +2873,7 @@ "uri":"kafka-faq-200426037.html", "node_id":"kafka-faq-200426037.xml", "product_code":"kafka", - "code":"150", + "code":"157", "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", @@ -2765,7 +2891,7 @@ "uri":"kafka-faq-200426100.html", "node_id":"kafka-faq-200426100.xml", "product_code":"kafka", - "code":"151", + "code":"158", "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", @@ -2783,7 +2909,7 @@ "uri":"kafka-faq-200708001.html", "node_id":"kafka-faq-200708001.xml", "product_code":"kafka", - "code":"152", + "code":"159", "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", @@ -2801,7 +2927,7 @@ "uri":"kafka-faq-0018.html", "node_id":"kafka-faq-0018.xml", "product_code":"kafka", - "code":"153", + "code":"160", "des":"No.", "doc_type":"usermanual", "kw":"Do Kafka Instances Support Delayed Message Delivery?,Messages,User Guide", @@ -2819,7 +2945,7 @@ "uri":"kafka-faq-0041.html", "node_id":"kafka-faq-0041.xml", "product_code":"kafka", - "code":"154", + "code":"161", "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", @@ -2837,7 +2963,7 @@ "uri":"kafka-faq-0045.html", "node_id":"kafka-faq-0045.xml", "product_code":"kafka", - "code":"155", + "code":"162", "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", @@ -2855,8 +2981,8 @@ "uri":"kafka_faq_0058.html", "node_id":"kafka_faq_0058.xml", "product_code":"kafka", - "code":"156", - "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", + "code":"163", + "des":"message.max.bytes can be modified on the Parameters page on the Kafka console. For details, see Modifying Kafka Instance Configuration Parameters.The maximum value of mes", "doc_type":"usermanual", "kw":"How Do I Modify message.max.bytes?,Messages,User Guide", "search_title":"", @@ -2869,11 +2995,29 @@ "title":"How Do I Modify message.max.bytes?", "githuburl":"" }, + { + "uri":"kafka-faq-0065.html", + "node_id":"kafka-faq-0065.xml", + "product_code":"kafka", + "code":"164", + "des":"If you have enabled idempotence or transactions on the producer client, and produced messages, message offsets are not continuous on the consumer client or on the Message", + "doc_type":"usermanual", + "kw":"Why Are Offsets Not Continuous?,Messages,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Why Are Offsets Not Continuous?", + "githuburl":"" + }, { "uri":"kafka-faq-191030004.html", "node_id":"kafka-faq-191030004.xml", "product_code":"kafka", - "code":"157", + "code":"165", "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", @@ -2891,7 +3035,7 @@ "uri":"kafka-faq-200426041.html", "node_id":"kafka-faq-200426041.xml", "product_code":"kafka", - "code":"158", + "code":"166", "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", @@ -2909,7 +3053,7 @@ "uri":"kafka-faq-0007.html", "node_id":"kafka-faq-0007.xml", "product_code":"kafka", - "code":"159", + "code":"167", "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", @@ -2927,7 +3071,7 @@ "uri":"kafka-faq-0022.html", "node_id":"kafka-faq-0022.xml", "product_code":"kafka", - "code":"160", + "code":"168", "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", @@ -2941,11 +3085,83 @@ "title":"Why Is a Consumer Group Still on the Monitoring Page After Being Deleted?", "githuburl":"" }, + { + "uri":"kafka-faq-0063.html", + "node_id":"kafka-faq-0063.xml", + "product_code":"kafka", + "code":"169", + "des":"Metrics including Disk Read Speed, Disk Write Speed, Average Disk Read Time, Average Disk Write Time, and CPU Usage output instantaneous values. These metrics are for ref", + "doc_type":"usermanual", + "kw":"Why Do Metrics Fluctuate Significantly (Disk Read/Write Speed, Average Disk Read/Write Time, and CPU", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Why Do Metrics Fluctuate Significantly (Disk Read/Write Speed, Average Disk Read/Write Time, and CPU Usage)?", + "githuburl":"" + }, + { + "uri":"kafka-faq-0064.html", + "node_id":"kafka-faq-0064.xml", + "product_code":"kafka", + "code":"170", + "des":"It is normal that JVM Heap Memory Usage of JVM is displayed in a sawtooth shape on the monitoring page. The maximum value may further increase or the fluctuation may be g", + "doc_type":"usermanual", + "kw":"Why Does JVM Heap Memory Usage of JVM Fluctuate Significantly?,Monitoring & Alarm,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Why Does JVM Heap Memory Usage of JVM Fluctuate Significantly?", + "githuburl":"" + }, + { + "uri":"kafka-faq-0066.html", + "node_id":"kafka-faq-0066.xml", + "product_code":"kafka", + "code":"171", + "des":"The metric data of the message production rate is reported once every minute. Message production rate = Number of messages produced per minute/60. The value is rounded do", + "doc_type":"usermanual", + "kw":"Why Is Production Rate Still 0 When There Are Produced Messages?,Monitoring & Alarm,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Why Is Production Rate Still 0 When There Are Produced Messages?", + "githuburl":"" + }, + { + "uri":"kafka-faq-0067.html", + "node_id":"kafka-faq-0067.xml", + "product_code":"kafka", + "code":"172", + "des":"On the Consumer Offset tab page of the consumer group details page, there are stacked messages in a topic (total stack ≠ 0), whereas the Consumer Available Messages on th", + "doc_type":"usermanual", + "kw":"Why Is the Number of Stacked Messages Monitored as 0 when Messages Are Stacked?,Monitoring & Alarm,U", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Why Is the Number of Stacked Messages Monitored as 0 when Messages Are Stacked?", + "githuburl":"" + }, { "uri":"kafka-ug-0723006.html", "node_id":"kafka-ug-0723006.xml", "product_code":"kafka", - "code":"161", + "code":"173", "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", @@ -2963,7 +3179,7 @@ "uri":"kafka-faq-0604001.html", "node_id":"kafka-faq-0604001.xml", "product_code":"kafka", - "code":"162", + "code":"174", "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", @@ -2981,7 +3197,7 @@ "uri":"kafka-trouble-0709001.html", "node_id":"kafka-trouble-0709001.xml", "product_code":"kafka", - "code":"163", + "code":"175", "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", @@ -2999,7 +3215,7 @@ "uri":"kafka-trouble-0001.html", "node_id":"kafka-trouble-0001.xml", "product_code":"kafka", - "code":"164", + "code":"176", "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", @@ -3017,7 +3233,7 @@ "uri":"kafka-trouble-0002.html", "node_id":"kafka-trouble-0002.xml", "product_code":"kafka", - "code":"165", + "code":"177", "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", @@ -3035,7 +3251,7 @@ "uri":"kafka-trouble-0004.html", "node_id":"kafka-trouble-0004.xml", "product_code":"kafka", - "code":"166", + "code":"178", "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", @@ -3049,11 +3265,29 @@ "title":"Troubleshooting Error \"Topic {{topic_name}} not present in metadata after 60000 ms\" During Message Production or Consumption", "githuburl":"" }, + { + "uri":"kafka_trouble_0007.html", + "node_id":"kafka_trouble_0007.xml", + "product_code":"kafka", + "code":"179", + "des":"To consume Kafka messages in Flink 1.15, the consumption progress fails to be submitted, and the error messages \"COORDINATOR_NOT_AVAILABLE\" are thrown.Bug on the Kafka cl", + "doc_type":"usermanual", + "kw":"Flink 1.15 Consumption Progress Submission Failure,Troubleshooting,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"kafka", + "documenttype":"usermanual" + } + ], + "title":"Flink 1.15 Consumption Progress Submission Failure", + "githuburl":"" + }, { "uri":"kafka-ug-00001.html", "node_id":"kafka-ug-00001.xml", "product_code":"kafka", - "code":"167", + "code":"180", "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", @@ -3071,7 +3305,7 @@ "uri":"kafka-ug-00002.html", "node_id":"kafka-ug-00002.xml", "product_code":"dms", - "code":"168", + "code":"181", "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", @@ -3089,7 +3323,7 @@ "uri":"dms-ug-0312114.html", "node_id":"dms-ug-0312114.xml", "product_code":"dms", - "code":"169", + "code":"182", "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 10bb45743..0f75efd6c 100644 --- a/docs/dms/umn/CLASS.TXT.json +++ b/docs/dms/umn/CLASS.TXT.json @@ -36,14 +36,32 @@ "code":"4" }, { - "desc":"Kafka instances are compatible with open-source Kafka v1.1.0, v2.3.0, v2.7, and v3.x. Kafka instances are classified into cluster and single-node types. A cluster instanc", + "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":"Specifications", - "uri":"Kafka-specification.html", + "title":"Kafka Instance Specifications", + "uri":"kafka-pd-0053.html", "doc_type":"usermanual", "p_code":"1", "code":"5" }, + { + "desc":"A single-node Kafka instance has one broker, is compatible with open-source Kafka 2.7, and is applicable to test scenarios. Do not use it for production services.In the f", + "product_code":"dms", + "title":"Single-node Kafka Instances", + "uri":"kafka-pd-0056.html", + "doc_type":"usermanual", + "p_code":"5", + "code":"6" + }, + { + "desc":"A cluster Kafka instance has three or more brokers, and is compatible with open-source Kafka 2.3.0, 2.7, and 3.x.In the following table:For Kafka instances, the number of", + "product_code":"dms", + "title":"Cluster Kafka Instances", + "uri":"Kafka-specification.html", + "doc_type":"usermanual", + "p_code":"5", + "code":"7" + }, { "desc":"A single-node Kafka instance has only one broker. These instances do not guarantee performance or reliability and are for trial use or testing only. In the production env", "product_code":"dms", @@ -51,7 +69,16 @@ "uri":"kafka-pd-0052.html", "doc_type":"usermanual", "p_code":"1", - "code":"6" + "code":"8" + }, + { + "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":"Comparing Kafka and RocketMQ", + "uri":"kafka_pd_0004.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"9" }, { "desc":"DMS is compatible with open-source Kafka and has customized and enhanced Kafka features. In addition to the advantages of open-source Kafka, DMS for Kafka provides more r", @@ -60,16 +87,16 @@ "uri":"kafka-pd-200720001.html", "doc_type":"usermanual", "p_code":"1", - "code":"7" + "code":"10" }, { - "desc":"This section describes the notes and constraints on DMS.", + "desc":"This section describes the notes and constraints on Distributed Message Service (DMS). Use your Kafka instances as prescribed to avoid program exceptions.Any instability ", "product_code":"dms", "title":"Notes and Constraints", "uri":"kafka-pd-190605003.html", "doc_type":"usermanual", "p_code":"1", - "code":"8" + "code":"11" }, { "desc":"Cloud Trace Service (CTS)CTS generates traces to provide you with a history of operations performed on cloud service resources. The traces include operation requests sent", @@ -78,7 +105,7 @@ "uri":"kafka-pd-190605002.html", "doc_type":"usermanual", "p_code":"1", - "code":"9" + "code":"12" }, { "desc":"DMS for Kafka of the cloud service platform uses Kafka as the message engine. This chapter presents explanations of basic concepts of Kafka.A topic is a category for mess", @@ -87,16 +114,16 @@ "uri":"glossary-kafka.html", "doc_type":"usermanual", "p_code":"1", - "code":"10" + "code":"13" }, { "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", + "title":"Permissions", "uri":"ProductDescPrivilegeManagement.html", "doc_type":"usermanual", "p_code":"1", - "code":"11" + "code":"14" }, { "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.", @@ -105,7 +132,7 @@ "uri":"kafka-ug-00003.html", "doc_type":"usermanual", "p_code":"", - "code":"12" + "code":"15" }, { "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", @@ -113,8 +140,8 @@ "title":"Getting Started with Kafka for Message Production and Consumption", "uri":"kafka-qs-0409001.html", "doc_type":"usermanual", - "p_code":"12", - "code":"13" + "p_code":"15", + "code":"16" }, { "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 ", @@ -123,25 +150,25 @@ "uri":"kafka-ug-0069.html", "doc_type":"usermanual", "p_code":"", - "code":"14" + "code":"17" }, { "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":"Permission Management", + "title":"Permissions Management", "uri":"UserPrivilegeManagement.html", "doc_type":"usermanual", "p_code":"", - "code":"15" + "code":"18" }, { "desc":"This section describes how to use Identity and Access Management (IAM) for fine-grained permissions control for your Distributed Message Service (DMS) for Kafka resources", "product_code":"dms", - "title":"Creating a User and Granting DMS for Kafka Permissions", + "title":"Creating an IAM User and Granting DMS for Kafka Permissions", "uri":"CreateUserAndGrantPolicy.html", "doc_type":"usermanual", - "p_code":"15", - "code":"16" + "p_code":"18", + "code":"19" }, { "desc":"Kafka instances are tenant-exclusive, and physically isolated in deployment. You can customize the computing capabilities and storage space of a Kafka instance as require", @@ -150,7 +177,7 @@ "uri":"kafka-ug-180604013.html", "doc_type":"usermanual", "p_code":"", - "code":"17" + "code":"20" }, { "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.", @@ -159,7 +186,7 @@ "uri":"kafka-ug-0720001.html", "doc_type":"usermanual", "p_code":"", - "code":"18" + "code":"21" }, { "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", @@ -167,8 +194,8 @@ "title":"Creating a Kafka Topic", "uri":"kafka-ug-180604018.html", "doc_type":"usermanual", - "p_code":"18", - "code":"19" + "p_code":"21", + "code":"22" }, { "desc":"Kafka instances with ciphertext access enabled support access control list (ACL) for topics. You can differentiate user permissions by granting users different permission", @@ -176,8 +203,8 @@ "title":"Configuring Kafka Topic Permissions", "uri":"kafka-ug-0002.html", "doc_type":"usermanual", - "p_code":"18", - "code":"20" + "p_code":"21", + "code":"23" }, { "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.", @@ -185,17 +212,17 @@ "title":"Managing Topics", "uri":"kafka-ug-0058.html", "doc_type":"usermanual", - "p_code":"18", - "code":"21" + "p_code":"21", + "code":"24" }, { - "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", + "desc":"On the Kafka console, you can view basic information, partition and producer information, and subscriptions of a topic.If an instance contains more than 10,000 consumer g", "product_code":"dms", "title":"Viewing Kafka Topic Details", "uri":"kafka_ug_0045.html", "doc_type":"usermanual", - "p_code":"21", - "code":"22" + "p_code":"24", + "code":"25" }, { "desc":"This section describes how to modify configurations in Table 1 of a Kafka topic on the console.Modifying Synchronous Replication, Synchronous Flushing, Message Timestamp,", @@ -203,26 +230,35 @@ "title":"Modifying Kafka Topic Configurations", "uri":"kafka-ug-0038.html", "doc_type":"usermanual", - "p_code":"21", - "code":"23" + "p_code":"24", + "code":"26" }, { - "desc":"After creating a topic, you can increase the number of partitions as required.Changing the number of partitions does not restart the instance or affect services.Methods f", + "desc":"After creating a topic, you can change the number of partitions as required. Changing the number of partitions does not restart the instance or affect services.Methods fo", "product_code":"dms", "title":"Changing Kafka Partition Quantity", "uri":"kafka-ug-0006.html", "doc_type":"usermanual", - "p_code":"21", - "code":"24" + "p_code":"24", + "code":"27" }, { - "desc":"Export the topic list on the console. Batch export is supported.A topic has been created.Select the region where your Kafka instance is located.The topic list contains th", + "desc":"The replicas of a Kafka topic can be modified as required.Reassigning partitions can modify replicas automatically or manually on the Kafka console. For more information,", + "product_code":"dms", + "title":"Modifying Kafka Topic Replicas", + "uri":"kafka-ug-0072.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"28" + }, + { + "desc":"Export the topic list on the console. Batch export is supported.A topic has been created.The topic list contains the following information: topic name, number of partitio", "product_code":"dms", "title":"Exporting the Kafka Topic List", "uri":"kafka_ug_0027.html", "doc_type":"usermanual", - "p_code":"21", - "code":"25" + "p_code":"24", + "code":"29" }, { "desc":"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 th", @@ -230,8 +266,8 @@ "title":"Reassigning Kafka Partitions", "uri":"kafka_ug_0023.html", "doc_type":"usermanual", - "p_code":"21", - "code":"26" + "p_code":"24", + "code":"30" }, { "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 ", @@ -239,17 +275,17 @@ "title":"Configuring Automatic Topic Creation", "uri":"kafka_ug_0043.html", "doc_type":"usermanual", - "p_code":"21", - "code":"27" + "p_code":"24", + "code":"31" }, { - "desc":"Delete a topic using either of the following methods:Deleting a Kafka Topic (Console)Deleting a Kafka Topic on the ClientA Kafka instance has been created, and a topic ha", + "desc":"This document describes how to delete a topic.Deleting a Kafka Topic (Console)Deleting a Kafka Topic on the ClientDeleting a topic clears the topic data permanently.For a", "product_code":"dms", "title":"Deleting a Kafka Topic", "uri":"kafka-ug-180604019.html", "doc_type":"usermanual", - "p_code":"21", - "code":"28" + "p_code":"24", + "code":"32" }, { "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.", @@ -258,7 +294,7 @@ "uri":"kafka-ug190605003.html", "doc_type":"usermanual", "p_code":"", - "code":"29" + "code":"33" }, { "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.", @@ -266,8 +302,8 @@ "title":"Configuring Kafka Network Connections", "uri":"kafka-ug-0059.html", "doc_type":"usermanual", - "p_code":"29", - "code":"30" + "p_code":"33", + "code":"34" }, { "desc":"A client can connect to a Kafka instance over a public or private network. Notes before using a private network:By default, a client and a Kafka instance are interconnect", @@ -275,17 +311,17 @@ "title":"Kafka Network Connection Conditions", "uri":"kafka-ug-180604012.html", "doc_type":"usermanual", - "p_code":"30", - "code":"31" + "p_code":"34", + "code":"35" }, { - "desc":"Clients can use IPv4 or IPv6 addresses to access a Kafka instance over a public network.By IPv4: On the Kafka console, enable public access and configure EIPs for the ins", + "desc":"A client can use IPv4 or IPv6 addresses to access a Kafka instance over a public network.By IPv4: On the Kafka console, enable public access and configure EIPs for the in", "product_code":"dms", "title":"Configuring Kafka Public Access", "uri":"kafka-ug-0319001.html", "doc_type":"usermanual", - "p_code":"30", - "code":"32" + "p_code":"34", + "code":"36" }, { "desc":"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 thi", @@ -293,8 +329,8 @@ "title":"Accessing Kafka Using a VPC Endpoint Across VPCs", "uri":"kafka-ug-0001.html", "doc_type":"usermanual", - "p_code":"30", - "code":"33" + "p_code":"34", + "code":"37" }, { "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", @@ -302,8 +338,8 @@ "title":"Accessing Kafka in a Public Network Using DNAT", "uri":"kafka-dnat.html", "doc_type":"usermanual", - "p_code":"30", - "code":"34" + "p_code":"34", + "code":"38" }, { "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.", @@ -311,8 +347,8 @@ "title":"Configuring Kafka Access Control", "uri":"kafka-ug-0061.html", "doc_type":"usermanual", - "p_code":"29", - "code":"35" + "p_code":"33", + "code":"39" }, { "desc":"You can access a Kafka instance in plaintext or ciphertext. This section describes how to change the access mode on the console.Plaintext access: Clients connect to the K", @@ -320,8 +356,8 @@ "title":"Configuring Plaintext or Ciphertext Access to Kafka Instances", "uri":"kafka_ug_0044.html", "doc_type":"usermanual", - "p_code":"35", - "code":"36" + "p_code":"39", + "code":"40" }, { "desc":"Kafka instances with ciphertext access enabled support access control list (ACL) for topics. You can differentiate user permissions by granting users different permission", @@ -329,8 +365,8 @@ "title":"Configuring Kafka ACL Users", "uri":"kafka-ug-0003.html", "doc_type":"usermanual", - "p_code":"35", - "code":"37" + "p_code":"39", + "code":"41" }, { "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.", @@ -338,8 +374,8 @@ "title":"Configuring the Kafka Client", "uri":"kafka-ug-0062.html", "doc_type":"usermanual", - "p_code":"29", - "code":"38" + "p_code":"33", + "code":"42" }, { "desc":"This section provides recommendations on configuring common parameters for Kafka producers and consumers. Kafka clients in different versions may have different parameter", @@ -347,8 +383,8 @@ "title":"Setting Parameters for Kafka Clients", "uri":"Kafka-client-parameter.html", "doc_type":"usermanual", - "p_code":"38", - "code":"39" + "p_code":"42", + "code":"43" }, { "desc":"Ensure that the owner thread does not exit abnormally. Otherwise, the client may fail to initiate consumption requests and the consumption will be blocked.Commit messages", @@ -356,8 +392,8 @@ "title":"Suggestions on Using the Kafka Client", "uri":"Kafka-client-best-practice.html", "doc_type":"usermanual", - "p_code":"38", - "code":"40" + "p_code":"42", + "code":"44" }, { "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", @@ -365,8 +401,8 @@ "title":"Connecting to Kafka Using the Client (Plaintext Access)", "uri":"kafka-ug-180604020.html", "doc_type":"usermanual", - "p_code":"29", - "code":"41" + "p_code":"33", + "code":"45" }, { "desc":"This section describes how to access a Kafka instance in ciphertext on an open-source Kafka client. The client connects to the Kafka instance with SASL authentication. If", @@ -374,8 +410,8 @@ "title":"Connecting to Kafka Using the Client (Ciphertext Access)", "uri":"kafka-ug-180801001.html", "doc_type":"usermanual", - "p_code":"29", - "code":"42" + "p_code":"33", + "code":"46" }, { "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.", @@ -384,16 +420,16 @@ "uri":"kafka-ug-0720002.html", "doc_type":"usermanual", "p_code":"", - "code":"43" + "code":"47" }, { - "desc":"You can view the offset of different partitions, the message size, creation time, and body of messages in topics.Select the region where your Kafka instance is located.If", + "desc":"When messages are lost or fail to be consumed, you can query the content and attributes of specific messages for troubleshooting.You can view the offset of different part", "product_code":"dms", "title":"Viewing Kafka Messages", "uri":"kafka-ug-190904001.html", "doc_type":"usermanual", - "p_code":"43", - "code":"44" + "p_code":"47", + "code":"48" }, { "desc":"Aging time is a period that messages in a topic are retained for. Consumers must consume messages before this period ends. Otherwise, the messages will be deleted and can", @@ -401,17 +437,17 @@ "title":"Changing Kafka Message Retention Period", "uri":"kafka-ug-200506001.html", "doc_type":"usermanual", - "p_code":"43", - "code":"45" + "p_code":"47", + "code":"49" }, { - "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", + "desc":"This section describes how to delete messages stored in a topic on the console.Deleting messages takes effect permanently.Before deleting a message, set the auto.offset.r", "product_code":"dms", "title":"Deleting Kafka Messages", "uri":"kafka_ug_0046.html", "doc_type":"usermanual", - "p_code":"43", - "code":"46" + "p_code":"47", + "code":"50" }, { "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.", @@ -420,7 +456,7 @@ "uri":"kafka-ug-0011.html", "doc_type":"usermanual", "p_code":"", - "code":"47" + "code":"51" }, { "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", @@ -428,17 +464,17 @@ "title":"Creating a Kafka Consumer Group", "uri":"kafka-ug-0041.html", "doc_type":"usermanual", - "p_code":"47", - "code":"48" + "p_code":"51", + "code":"52" }, { - "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", + "desc":"After a consumer group is created, you can view its configuration and status.The consumer group name, status, and Coordinator (ID) are displayed. Coordinator (ID) indicat", "product_code":"dms", "title":"Querying the Kafka Consumer Group List", "uri":"kafka_ug_0021.html", "doc_type":"usermanual", - "p_code":"47", - "code":"49" + "p_code":"51", + "code":"53" }, { "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", @@ -446,26 +482,26 @@ "title":"Viewing Kafka Consumer Information", "uri":"kafka-ug-0015.html", "doc_type":"usermanual", - "p_code":"47", - "code":"50" + "p_code":"51", + "code":"54" }, { - "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", + "desc":"A consumption offset indicates the consumption progress of a consumer. This section describes how to view and reset consumption offsets.Messages may be consumed more than", "product_code":"dms", "title":"Viewing and Resetting Kafka Consumption Offsets", "uri":"kafka-ug-0014.html", "doc_type":"usermanual", - "p_code":"47", - "code":"51" + "p_code":"51", + "code":"55" }, { - "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 >", + "desc":"You can export a list of consumer groups in a Kafka instance.Select the desired consumer groups and choose Export > Export selected data to an XLSX file to export specifi", "product_code":"dms", "title":"Exporting Kafka Consumer Groups", "uri":"kafka-ug-0056.html", "doc_type":"usermanual", - "p_code":"47", - "code":"52" + "p_code":"51", + "code":"56" }, { "desc":"You can delete a consumer group in either of the following ways:On the console.Use Kafka CLI. (Ensure that the Kafka instance version is the same as the CLI version.)If a", @@ -473,8 +509,8 @@ "title":"Deleting a Kafka Consumer Group", "uri":"kafka-ug-0012.html", "doc_type":"usermanual", - "p_code":"47", - "code":"53" + "p_code":"51", + "code":"57" }, { "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.", @@ -483,7 +519,7 @@ "uri":"kafka-ug-180604011.html", "doc_type":"usermanual", "p_code":"", - "code":"54" + "code":"58" }, { "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", @@ -491,17 +527,17 @@ "title":"Viewing and Modifying Basic Information of a Kafka Instance", "uri":"kafka-ug-180604014.html", "doc_type":"usermanual", - "p_code":"54", - "code":"55" + "p_code":"58", + "code":"59" }, { - "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", + "desc":"This section describes how to view the disk usage of each broker of a Kafka instance on the console.Unavailable for single-node instances.You can query topics that use th", "product_code":"dms", "title":"Viewing Kafka Disk Usage", "uri":"kafka-ug-0004.html", "doc_type":"usermanual", - "p_code":"54", - "code":"56" + "p_code":"58", + "code":"60" }, { "desc":"After you initiate certain instance operations listed in Table 1, a background task will start for each operation. On the console, you can view the background task status", @@ -509,8 +545,8 @@ "title":"Viewing Kafka Background Tasks", "uri":"kafka-ug-200119002.html", "doc_type":"usermanual", - "p_code":"54", - "code":"57" + "p_code":"58", + "code":"61" }, { "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 ", @@ -518,8 +554,8 @@ "title":"Viewing Sample Code of Kafka Production and Consumption", "uri":"kafka_ug_0024.html", "doc_type":"usermanual", - "p_code":"54", - "code":"58" + "p_code":"58", + "code":"62" }, { "desc":"Your Kafka instances, topics, and consumers come with default configuration parameter settings. You can modify common parameters on the DMS console. For details about par", @@ -527,53 +563,62 @@ "title":"Modifying Kafka Instance Configuration Parameters", "uri":"kafka-ug-0007.html", "doc_type":"usermanual", - "p_code":"54", - "code":"59" + "p_code":"58", + "code":"63" }, { - "desc":"Tags facilitate Kafka instance identification and management.You can add tags to a Kafka instance when creating the instance or add tags on the Tags tab page of the creat", + "desc":"Tags facilitate Kafka instance identification and management.You can add tags to a Kafka instance when creating the instance or add tags on the Tags page of the created i", "product_code":"dms", "title":"Configuring Kafka Instance Tags", "uri":"TagManagement.html", "doc_type":"usermanual", - "p_code":"54", - "code":"60" + "p_code":"58", + "code":"64" }, { - "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", + "desc":"You can export a list of instances on the DMS console.Select the desired instances and choose Export > Export selected data to an XLSX file to export specified instances.", "product_code":"dms", "title":"Exporting the Kafka Instance List", "uri":"kafka-ug-0053.html", "doc_type":"usermanual", - "p_code":"54", - "code":"61" + "p_code":"58", + "code":"65" }, { - "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", + "desc":"You can restart one or more Kafka instances in batches on the DMS console.When a Kafka instance is being restarted, message consumption and production requests of clients", "product_code":"dms", "title":"Restarting a Kafka Instance", "uri":"kafka-ug-180604015.html", "doc_type":"usermanual", - "p_code":"54", - "code":"62" + "p_code":"58", + "code":"66" }, { - "desc":"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 p", + "desc":"Delete one or more Kafka instances at a time on the DMS console.Deleting a Kafka instance will clear the instance data without any backup. Exercise caution.The status of ", "product_code":"dms", "title":"Deleting Kafka Instances", "uri":"kafka-ug-180604016.html", "doc_type":"usermanual", - "p_code":"54", - "code":"63" + "p_code":"58", + "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":"Modifying Instance Specifications", + "uri":"kafka-ug-0075.html", + "doc_type":"usermanual", + "p_code":"", + "code":"68" }, { "desc":"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 ", "product_code":"dms", - "title":"Modifying Kafka Instance Specifications", + "title":"Modifying Cluster Kafka Instance Specifications", "uri":"kafka-ug-181221001.html", "doc_type":"usermanual", - "p_code":"", - "code":"64" + "p_code":"68", + "code":"69" }, { "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.", @@ -582,7 +627,7 @@ "uri":"kafka_ug_0016.html", "doc_type":"usermanual", "p_code":"", - "code":"65" + "code":"70" }, { "desc":"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. K", @@ -590,8 +635,8 @@ "title":"Kafka Data Migration Overview", "uri":"kafka-bp-migration.html", "doc_type":"usermanual", - "p_code":"65", - "code":"66" + "p_code":"70", + "code":"71" }, { "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.", @@ -599,8 +644,8 @@ "title":"Migrating Data Using Smart Connect", "uri":"kafka-ug-0065.html", "doc_type":"usermanual", - "p_code":"65", - "code":"67" + "p_code":"70", + "code":"72" }, { "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", @@ -608,8 +653,8 @@ "title":"Enabling Smart Connect", "uri":"kafka_ug_0017.html", "doc_type":"usermanual", - "p_code":"67", - "code":"68" + "p_code":"72", + "code":"73" }, { "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", @@ -617,8 +662,8 @@ "title":"Replicating Kafka Instance Data", "uri":"kafka-ug-0034.html", "doc_type":"usermanual", - "p_code":"67", - "code":"69" + "p_code":"72", + "code":"74" }, { "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.", @@ -626,26 +671,26 @@ "title":"Dumping Kafka Data to Object Storage Service (OBS)", "uri":"kafka-ug-0035.html", "doc_type":"usermanual", - "p_code":"67", - "code":"70" + "p_code":"72", + "code":"75" }, { - "desc":"View, delete, start, pause, or restart a Smart Connect task.This function is unavailable for single-node instances.A Smart Connect task has been created.Select the region", + "desc":"View, delete, start, pause, or restart a Smart Connect task.Unavailable for single-node instances.A Smart Connect task has been created.The source and target are displaye", "product_code":"dms", "title":"Managing Smart Connect Tasks", "uri":"kafka_ug_0018.html", "doc_type":"usermanual", - "p_code":"67", - "code":"71" + "p_code":"72", + "code":"76" }, { - "desc":"Disable Smart Connect and resources can be freed.Disabling Smart Connect does not affect services.This function is unavailable for single-node instances.Brokers related t", + "desc":"Disable Smart Connect and resources can be freed.Disabling Smart Connect does not affect services.Brokers related to Smart Connect are automatically deleted.If you disabl", "product_code":"dms", "title":"Disabling Smart Connect", "uri":"kafka_ug_0041.html", "doc_type":"usermanual", - "p_code":"67", - "code":"72" + "p_code":"72", + "code":"77" }, { "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 +699,7 @@ "uri":"kafka-ug-180413001.html", "doc_type":"usermanual", "p_code":"", - "code":"73" + "code":"78" }, { "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", @@ -662,8 +707,8 @@ "title":"Viewing Kafka Metrics", "uri":"kafka-ug-190605001.html", "doc_type":"usermanual", - "p_code":"73", - "code":"74" + "p_code":"78", + "code":"79" }, { "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", @@ -671,8 +716,8 @@ "title":"Kafka Metrics", "uri":"kafka-ug-180413002.html", "doc_type":"usermanual", - "p_code":"73", - "code":"75" + "p_code":"78", + "code":"80" }, { "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", @@ -680,8 +725,8 @@ "title":"Configuring a Kafka Alarm Rule", "uri":"kafka-ug-180524001.html", "doc_type":"usermanual", - "p_code":"73", - "code":"76" + "p_code":"78", + "code":"81" }, { "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", @@ -690,7 +735,7 @@ "uri":"kafka-ug-180418002.html", "doc_type":"usermanual", "p_code":"", - "code":"77" + "code":"82" }, { "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.", @@ -699,7 +744,7 @@ "uri":"kafka-ug-0723004.html", "doc_type":"usermanual", "p_code":"", - "code":"78" + "code":"83" }, { "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.", @@ -707,8 +752,8 @@ "title":"Instances", "uri":"kafka-faq-191030002.html", "doc_type":"usermanual", - "p_code":"78", - "code":"79" + "p_code":"83", + "code":"84" }, { "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", @@ -716,17 +761,17 @@ "title":"Why Can't I Select Two AZs?", "uri":"kafka-faq-200426002.html", "doc_type":"usermanual", - "p_code":"79", - "code":"80" + "p_code":"84", + "code":"85" }, { - "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 ", + "desc":"The possible cause is that you do not have the Server Administrator and VPC Administrator permissions. For details about how to add permissions to a user group, see Viewi", "product_code":"dms", "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":"79", - "code":"81" + "p_code":"84", + "code":"86" }, { "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", @@ -734,8 +779,8 @@ "title":"How Do I Select Storage Space for a Kafka Instance?", "uri":"kafka-faq-200426005.html", "doc_type":"usermanual", - "p_code":"79", - "code":"82" + "p_code":"84", + "code":"87" }, { "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", @@ -743,8 +788,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":"79", - "code":"83" + "p_code":"84", + "code":"88" }, { "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 ", @@ -752,8 +797,8 @@ "title":"Which Capacity Threshold Policy Should I Use?", "uri":"kafka-faq-200426007.html", "doc_type":"usermanual", - "p_code":"79", - "code":"84" + "p_code":"84", + "code":"89" }, { "desc":"Kafka v2.3.0, v2.7, and v3.x.For details about how to create a Kafka instance, see Creating a Kafka Instance.", @@ -761,8 +806,8 @@ "title":"Which Kafka Versions Are Supported?", "uri":"kafka-faq-200426008.html", "doc_type":"usermanual", - "p_code":"79", - "code":"85" + "p_code":"84", + "code":"90" }, { "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", @@ -770,8 +815,8 @@ "title":"What Is the ZooKeeper Address of a Kafka Instance?", "uri":"kafka-faq-200426009.html", "doc_type":"usermanual", - "p_code":"79", - "code":"86" + "p_code":"84", + "code":"91" }, { "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", @@ -779,8 +824,8 @@ "title":"Are Kafka Instances in Cluster Mode?", "uri":"kafka-faq-200426010.html", "doc_type":"usermanual", - "p_code":"79", - "code":"87" + "p_code":"84", + "code":"92" }, { "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 usin", @@ -788,8 +833,8 @@ "title":"Can I Modify the Port for Accessing a Kafka Instance?", "uri":"kafka-faq-200426011.html", "doc_type":"usermanual", - "p_code":"79", - "code":"88" + "p_code":"84", + "code":"93" }, { "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", @@ -797,8 +842,8 @@ "title":"How Long Are Kafka SSL Certificates Valid for?", "uri":"kafka-faq-200426012.html", "doc_type":"usermanual", - "p_code":"79", - "code":"89" + "p_code":"84", + "code":"94" }, { "desc":"On the Kafka console, you can create a Smart Connect task for instance data replication. For details, see Replicating Kafka Instance Data.", @@ -806,17 +851,17 @@ "title":"How Do I Synchronize Data from One Kafka Instance to Another?", "uri":"kafka-faq-200426013.html", "doc_type":"usermanual", - "p_code":"79", - "code":"90" + "p_code":"84", + "code":"95" }, { - "desc":"The SASL_SSL setting can be changed for cluster instances. For details, see Configuring Plaintext or Ciphertext Access to Kafka Instances.A single-node instance does not ", + "desc":"The SASL_SSL setting of a cluster Kafka instance can be changed after instance creation. For details, see Configuring Plaintext or Ciphertext Access to Kafka Instances.A ", "product_code":"dms", "title":"How Do I Change the SASL_SSL Setting of a Kafka Instance?", "uri":"kafka-faq-200426014.html", "doc_type":"usermanual", - "p_code":"79", - "code":"91" + "p_code":"84", + "code":"96" }, { "desc":"There are two SASL authentication mechanisms for Kafka instances: SCRAM-SHA-512 and PLAIN.For instances with IPv6 disabled, the mechanism cannot be modified after ciphert", @@ -824,8 +869,8 @@ "title":"How Do I Modify the SASL Mechanism?", "uri":"kafka_faq_0052.html", "doc_type":"usermanual", - "p_code":"79", - "code":"92" + "p_code":"84", + "code":"97" }, { "desc":"There are two security protocols for Kafka instances: SASL_SSL and SASL_PLAINTEXT.For instances with IPv6 disabled, the security protocol can be changed on the console. I", @@ -833,8 +878,8 @@ "title":"How Do I Change the Security Protocol?", "uri":"kafka_faq_0062.html", "doc_type":"usermanual", - "p_code":"79", - "code":"93" + "p_code":"84", + "code":"98" }, { "desc":"No. A Kafka instance will not be restarted if you modify its enterprise project.", @@ -842,8 +887,8 @@ "title":"Will a Kafka Instance Be Restarted After Its Enterprise Project Is Modified?", "uri":"kafka-faq-0008.html", "doc_type":"usermanual", - "p_code":"79", - "code":"94" + "p_code":"84", + "code":"99" }, { "desc":"Kafka brokers and ZooKeeper are deployed on the same VM.", @@ -851,8 +896,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":"79", - "code":"95" + "p_code":"84", + "code":"100" }, { "desc":"For security purposes, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is supported.", @@ -860,8 +905,8 @@ "title":"Which Cipher Suites Are Supported by Kafka?", "uri":"kafka-faq-0020.html", "doc_type":"usermanual", - "p_code":"79", - "code":"96" + "p_code":"84", + "code":"101" }, { "desc":"No. The AZ cannot be changed once the instance is created. To use multiple AZs, create another instance.", @@ -869,8 +914,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":"79", - "code":"97" + "p_code":"84", + "code":"102" }, { "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", @@ -878,8 +923,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":"79", - "code":"98" + "p_code":"84", + "code":"103" }, { "desc":"Yes.", @@ -887,8 +932,8 @@ "title":"Do Kafka Instances Support Disk Encryption?", "uri":"kafka-faq-0030.html", "doc_type":"usermanual", - "p_code":"79", - "code":"99" + "p_code":"84", + "code":"104" }, { "desc":"No. Once an instance is created, its VPC and subnet cannot be changed.", @@ -896,8 +941,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":"79", - "code":"100" + "p_code":"84", + "code":"105" }, { "desc":"You can find Kafka Streams use cases on the official Kafka website.", @@ -905,8 +950,8 @@ "title":"Where Can I Find Kafka Streams Use Cases?", "uri":"kafka-faq-0037.html", "doc_type":"usermanual", - "p_code":"79", - "code":"101" + "p_code":"84", + "code":"106" }, { "desc":"No. Kafka instances cannot be upgraded once they are created. To use a higher Kafka version, create another Kafka instance.", @@ -914,8 +959,8 @@ "title":"Can I Upgrade Kafka Instances?", "uri":"kafka-faq-0040.html", "doc_type":"usermanual", - "p_code":"79", - "code":"102" + "p_code":"84", + "code":"107" }, { "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", @@ -923,8 +968,17 @@ "title":"How Do I Bind an EIP Again?", "uri":"kafka_faq_0046.html", "doc_type":"usermanual", - "p_code":"79", - "code":"103" + "p_code":"84", + "code":"108" + }, + { + "desc":"Each broker of a Kafka instance has a 100 GB disk. The automatic deletion policy has been configured and a topic with 180 partitions has been created. The earliest messag", + "product_code":"dms", + "title":"Why Are the Earliest Messages Not Automatically Deleted When the Disk Capacity Reaches 95%?", + "uri":"kafka-faq-0070.html", + "doc_type":"usermanual", + "p_code":"84", + "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,17 +986,17 @@ "title":"Specification Modification", "uri":"kafka_faq_0053.html", "doc_type":"usermanual", - "p_code":"78", - "code":"104" + "p_code":"83", + "code":"110" }, { - "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", + "desc":"Table 1 describes the impact of increasing specifications.", "product_code":"dms", "title":"Does Specification Modification Affect Services?", "uri":"kafka-faq-0035.html", "doc_type":"usermanual", - "p_code":"104", - "code":"105" + "p_code":"110", + "code":"111" }, { "desc":"No. Data will not be migrated when you increase specifications.", @@ -950,8 +1004,8 @@ "title":"Will Data Migration Be Involved When I Increase Specifications?", "uri":"kafka_faq_0054.html", "doc_type":"usermanual", - "p_code":"104", - "code":"106" + "p_code":"110", + "code":"112" }, { "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", @@ -959,8 +1013,8 @@ "title":"Why Does Message Production Fail During Scaling?", "uri":"kafka_faq_0056.html", "doc_type":"usermanual", - "p_code":"104", - "code":"107" + "p_code":"110", + "code":"113" }, { "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", @@ -968,8 +1022,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":"104", - "code":"108" + "p_code":"110", + "code":"114" }, { "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.", @@ -977,8 +1031,8 @@ "title":"Connections", "uri":"kafka-faq-191030001.html", "doc_type":"usermanual", - "p_code":"78", - "code":"109" + "p_code":"83", + "code":"115" }, { "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", @@ -986,8 +1040,8 @@ "title":"How Do I Select and Configure a Security Group?", "uri":"kafka-faq-180604024.html", "doc_type":"usermanual", - "p_code":"109", - "code":"110" + "p_code":"115", + "code":"116" }, { "desc":"Yes. For details, see the Connecting to an Instance.", @@ -995,8 +1049,8 @@ "title":"Can I Access a Kafka Instance Over a Public Network?", "uri":"kafka-faq-200426015.html", "doc_type":"usermanual", - "p_code":"109", - "code":"111" + "p_code":"115", + "code":"117" }, { "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", @@ -1004,8 +1058,8 @@ "title":"How Many Connection Addresses Does a Kafka Instance Have by Default?", "uri":"kafka-faq-200426016.html", "doc_type":"usermanual", - "p_code":"109", - "code":"112" + "p_code":"115", + "code":"118" }, { "desc":"Yes. You can access a Kafka instance across regions over a public network or by using direct connections.", @@ -1013,8 +1067,8 @@ "title":"Do Kafka Instances Support Cross-Region Access?", "uri":"kafka-faq-200426017.html", "doc_type":"usermanual", - "p_code":"109", - "code":"113" + "p_code":"115", + "code":"119" }, { "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. ", @@ -1022,8 +1076,8 @@ "title":"Do Kafka Instances Support Cross-VPC Access?", "uri":"kafka-faq-200426019.html", "doc_type":"usermanual", - "p_code":"109", - "code":"114" + "p_code":"115", + "code":"120" }, { "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.", @@ -1031,8 +1085,8 @@ "title":"Do Kafka Instances Support Cross-Subnet Access?", "uri":"kafka-faq-200426020.html", "doc_type":"usermanual", - "p_code":"109", - "code":"115" + "p_code":"115", + "code":"121" }, { "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", @@ -1040,8 +1094,8 @@ "title":"Does DMS for Kafka Support Authentication with Kerberos?", "uri":"kafka-faq-200426023.html", "doc_type":"usermanual", - "p_code":"109", - "code":"116" + "p_code":"115", + "code":"122" }, { "desc":"Yes. No password is required when accessing a Kafka instance in plaintext. For details, see Connecting to Kafka Using the Client (Plaintext Access).", @@ -1049,17 +1103,17 @@ "title":"Does DMS for Kafka Support Password-Free Access?", "uri":"kafka-faq-200708002.html", "doc_type":"usermanual", - "p_code":"109", - "code":"117" + "p_code":"115", + "code":"123" }, { - "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", + "desc":"Click the name of your Kafka instance. In the Connection section on the Basic Information page, view Instance Address (Public Network).For details about how to connect to", "product_code":"dms", "title":"How Do I Obtain the Public Access Address After Public Access Is Enabled?", "uri":"kafka-faq-0001.html", "doc_type":"usermanual", - "p_code":"109", - "code":"118" + "p_code":"115", + "code":"124" }, { "desc":"No.", @@ -1067,8 +1121,8 @@ "title":"Does DMS for Kafka Support Authentication on Clients by the Server?", "uri":"kafka-faq-0026.html", "doc_type":"usermanual", - "p_code":"109", - "code":"119" + "p_code":"115", + "code":"125" }, { "desc":"No. You can only use JKS certificates for connecting to instances in Java.", @@ -1076,8 +1130,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":"109", - "code":"120" + "p_code":"115", + "code":"126" }, { "desc":"JKS certificates are used for connecting to instances in Java and CRT certificates are used for connecting to instances in Python.", @@ -1085,8 +1139,8 @@ "title":"What Are the Differences Between JKS and CRT Certificates?", "uri":"kafka-faq-0028.html", "doc_type":"usermanual", - "p_code":"109", - "code":"121" + "p_code":"115", + "code":"127" }, { "desc":"TLS 1.2.", @@ -1094,8 +1148,8 @@ "title":"Which TLS Version Does DMS for Kafka Support?", "uri":"kafka-faq-0029.html", "doc_type":"usermanual", - "p_code":"109", - "code":"122" + "p_code":"115", + "code":"128" }, { "desc":"Yes. The maximum allowed number of client connections varies by instance specifications.", @@ -1103,8 +1157,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":"109", - "code":"123" + "p_code":"115", + "code":"129" }, { "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", @@ -1112,8 +1166,8 @@ "title":"How Many Connections Are Allowed from Each IP Address?", "uri":"kafka-faq-0034.html", "doc_type":"usermanual", - "p_code":"109", - "code":"124" + "p_code":"115", + "code":"130" }, { "desc":"No, and you cannot specify the IP addresses.", @@ -1121,8 +1175,8 @@ "title":"Can I Change the Private Network Addresses of a Kafka Instance?", "uri":"kafka_faq_0048.html", "doc_type":"usermanual", - "p_code":"109", - "code":"125" + "p_code":"115", + "code":"131" }, { "desc":"Yes. All Kafka instances and users use the same SSL certificate.To obtain the SSL certificate, perform the following steps:", @@ -1130,8 +1184,8 @@ "title":"Is the Same SSL Certificate Used for Different Instances?", "uri":"kafka_faq_0051.html", "doc_type":"usermanual", - "p_code":"109", - "code":"126" + "p_code":"115", + "code":"132" }, { "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", @@ -1139,8 +1193,8 @@ "title":"Why Is It Not Recommended to Use a Sarama Client for Messaging?", "uri":"kafka_faq_0061.html", "doc_type":"usermanual", - "p_code":"109", - "code":"127" + "p_code":"115", + "code":"133" }, { "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.", @@ -1148,8 +1202,8 @@ "title":"Topics and Partitions", "uri":"kafka-faq-191030003.html", "doc_type":"usermanual", - "p_code":"78", - "code":"128" + "p_code":"83", + "code":"134" }, { "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", @@ -1157,8 +1211,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":"128", - "code":"129" + "p_code":"134", + "code":"135" }, { "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", @@ -1166,8 +1220,8 @@ "title":"Why Is Partition Quantity Limited?", "uri":"kafka-faq-200426025.html", "doc_type":"usermanual", - "p_code":"128", - "code":"130" + "p_code":"134", + "code":"136" }, { "desc":"No. If you want to use fewer partitions, delete the corresponding topic, create another one, and specify the desired number of partitions.", @@ -1175,17 +1229,17 @@ "title":"Can I Reduce the Partition Quantity?", "uri":"kafka-faq-200426101.html", "doc_type":"usermanual", - "p_code":"128", - "code":"131" + "p_code":"134", + "code":"137" }, { - "desc":"Possible cause: The aggregate number of partitions of created topics has reached the upper limit. The maximum number of partitions varies by instance specifications. For ", + "desc":"Possible cause: The aggregate number of partitions of created topics has reached the upper limit. The limit varies with instance specifications. For details, see Single-n", "product_code":"dms", "title":"Why Do I Fail to Create Topics?", "uri":"kafka-faq-200426026.html", "doc_type":"usermanual", - "p_code":"128", - "code":"132" + "p_code":"134", + "code":"138" }, { "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", @@ -1193,17 +1247,8 @@ "title":"Do Kafka Instances Support Batch Importing Topics or Automatic Topic Creation?", "uri":"kafka-faq-200426027.html", "doc_type":"usermanual", - "p_code":"128", - "code":"133" - }, - { - "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 ", - "product_code":"dms", - "title":"Why Do Deleted Topics Still Exist?", - "uri":"kafka-faq-200426028.html", - "doc_type":"usermanual", - "p_code":"128", - "code":"134" + "p_code":"134", + "code":"139" }, { "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", @@ -1211,17 +1256,17 @@ "title":"Can I View the Disk Space Used by a Topic?", "uri":"kafka-faq-200426030.html", "doc_type":"usermanual", - "p_code":"128", - "code":"135" + "p_code":"134", + "code":"140" }, { - "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", + "desc":"If you have enabled SASL_SSL for your Kafka instance, you can configure ACL permissions for your topics. On the Topics page of the Kafka console, click Grant User Permiss", "product_code":"dms", "title":"Can I Add ACL Permissions for Topics?", "uri":"kafka-faq-200426032.html", "doc_type":"usermanual", - "p_code":"128", - "code":"136" + "p_code":"134", + "code":"141" }, { "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.", @@ -1229,17 +1274,17 @@ "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":"128", - "code":"137" + "p_code":"134", + "code":"142" }, { - "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", + "desc":"You can increase the partition quantity by increasing broker flavors or adding brokers. For details, see Modifying Cluster Kafka Instance Specifications.", "product_code":"dms", "title":"How Do I Increase the Partition Quantity?", "uri":"kafka-faq-0005.html", "doc_type":"usermanual", - "p_code":"128", - "code":"138" + "p_code":"134", + "code":"143" }, { "desc":"Enabling or disabling automatic topic creation may cause instance restarts. For details, see the information displayed on the Kafka console.", @@ -1247,8 +1292,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":"128", - "code":"139" + "p_code":"134", + "code":"144" }, { "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", @@ -1256,8 +1301,17 @@ "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":"128", - "code":"140" + "p_code":"134", + "code":"145" + }, + { + "desc":"No. However, you can increase the total number of partitions by increasing the broker quantity or flavor. For details, see Modifying Cluster Kafka Instance Specifications", + "product_code":"dms", + "title":"Can I Purchase Partitions Separately?", + "uri":"kafka-faq-0068.html", + "doc_type":"usermanual", + "p_code":"134", + "code":"146" }, { "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.", @@ -1265,8 +1319,8 @@ "title":"Consumer Groups", "uri":"kafka-faq-200423001.html", "doc_type":"usermanual", - "p_code":"78", - "code":"141" + "p_code":"83", + "code":"147" }, { "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", @@ -1274,8 +1328,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":"141", - "code":"142" + "p_code":"147", + "code":"148" }, { "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", @@ -1283,8 +1337,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":"141", - "code":"143" + "p_code":"147", + "code":"149" }, { "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", @@ -1292,8 +1346,8 @@ "title":"Why Does a Deleted Consumer Group Still Exist?", "uri":"kafka_faq_0059.html", "doc_type":"usermanual", - "p_code":"141", - "code":"144" + "p_code":"147", + "code":"150" }, { "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", @@ -1301,8 +1355,8 @@ "title":"Why Can't I View Consumers When Instance Consumption Is Normal?", "uri":"kafka_faq_0060.html", "doc_type":"usermanual", - "p_code":"141", - "code":"145" + "p_code":"147", + "code":"151" }, { "desc":"Just simply unsubscribe from them on the Kafka client.", @@ -1310,8 +1364,17 @@ "title":"Can I Delete Unnecessary Topics in a Consumer Group?", "uri":"kafka-faq-0031.html", "doc_type":"usermanual", - "p_code":"141", - "code":"146" + "p_code":"147", + "code":"152" + }, + { + "desc":"If you cannot find a consumer group from the console, the possible causes are as follows:auto.create.groups.enable is set to true, the consumer group status is EMPTY, and", + "product_code":"dms", + "title":"Why Are Consumer Groups Missing?", + "uri":"kafka-faq-0069.html", + "doc_type":"usermanual", + "p_code":"147", + "code":"153" }, { "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.", @@ -1319,8 +1382,8 @@ "title":"Messages", "uri":"kafka-faq-190416001.html", "doc_type":"usermanual", - "p_code":"78", - "code":"147" + "p_code":"83", + "code":"154" }, { "desc":"10 MB.", @@ -1328,8 +1391,8 @@ "title":"What Is the Maximum Size of a Message that Can be Created?", "uri":"kafka-faq-200426035.html", "doc_type":"usermanual", - "p_code":"147", - "code":"148" + "p_code":"154", + "code":"155" }, { "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", @@ -1337,8 +1400,8 @@ "title":"Why Does Message Poll Often Fail During Rebalancing?", "uri":"kafka-faq-200426036.html", "doc_type":"usermanual", - "p_code":"147", - "code":"149" + "p_code":"154", + "code":"156" }, { "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", @@ -1346,8 +1409,8 @@ "title":"Why Can't I Query Messages on the Console?", "uri":"kafka-faq-200426037.html", "doc_type":"usermanual", - "p_code":"147", - "code":"150" + "p_code":"154", + "code":"157" }, { "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", @@ -1355,8 +1418,8 @@ "title":"What Can I Do If Kafka Messages Are Accumulated?", "uri":"kafka-faq-200426100.html", "doc_type":"usermanual", - "p_code":"147", - "code":"151" + "p_code":"154", + "code":"158" }, { "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", @@ -1364,8 +1427,8 @@ "title":"Why Do Messages Still Exist After the Retention Period Elapses?", "uri":"kafka-faq-200708001.html", "doc_type":"usermanual", - "p_code":"147", - "code":"152" + "p_code":"154", + "code":"159" }, { "desc":"No.", @@ -1373,8 +1436,8 @@ "title":"Do Kafka Instances Support Delayed Message Delivery?", "uri":"kafka-faq-0018.html", "doc_type":"usermanual", - "p_code":"147", - "code":"153" + "p_code":"154", + "code":"160" }, { "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", @@ -1382,8 +1445,8 @@ "title":"How Do I View the Number of Accumulated Messages?", "uri":"kafka-faq-0041.html", "doc_type":"usermanual", - "p_code":"147", - "code":"154" + "p_code":"154", + "code":"161" }, { "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 ", @@ -1391,17 +1454,26 @@ "title":"Why Is the Message Creation Time Displayed as Year 1970?", "uri":"kafka-faq-0045.html", "doc_type":"usermanual", - "p_code":"147", - "code":"155" + "p_code":"154", + "code":"162" }, { - "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", + "desc":"message.max.bytes can be modified on the Parameters page on the Kafka console. For details, see Modifying Kafka Instance Configuration Parameters.The maximum value of mes", "product_code":"dms", "title":"How Do I Modify message.max.bytes?", "uri":"kafka_faq_0058.html", "doc_type":"usermanual", - "p_code":"147", - "code":"156" + "p_code":"154", + "code":"163" + }, + { + "desc":"If you have enabled idempotence or transactions on the producer client, and produced messages, message offsets are not continuous on the consumer client or on the Message", + "product_code":"dms", + "title":"Why Are Offsets Not Continuous?", + "uri":"kafka-faq-0065.html", + "doc_type":"usermanual", + "p_code":"154", + "code":"164" }, { "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.", @@ -1409,8 +1481,8 @@ "title":"Monitoring & Alarm", "uri":"kafka-faq-191030004.html", "doc_type":"usermanual", - "p_code":"78", - "code":"157" + "p_code":"83", + "code":"165" }, { "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 (", @@ -1418,8 +1490,8 @@ "title":"Why Can't I View the Monitoring Data?", "uri":"kafka-faq-200426041.html", "doc_type":"usermanual", - "p_code":"157", - "code":"158" + "p_code":"165", + "code":"166" }, { "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", @@ -1427,8 +1499,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":"157", - "code":"159" + "p_code":"165", + "code":"167" }, { "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", @@ -1436,8 +1508,44 @@ "title":"Why Is a Consumer Group Still on the Monitoring Page After Being Deleted?", "uri":"kafka-faq-0022.html", "doc_type":"usermanual", - "p_code":"157", - "code":"160" + "p_code":"165", + "code":"168" + }, + { + "desc":"Metrics including Disk Read Speed, Disk Write Speed, Average Disk Read Time, Average Disk Write Time, and CPU Usage output instantaneous values. These metrics are for ref", + "product_code":"dms", + "title":"Why Do Metrics Fluctuate Significantly (Disk Read/Write Speed, Average Disk Read/Write Time, and CPU Usage)?", + "uri":"kafka-faq-0063.html", + "doc_type":"usermanual", + "p_code":"165", + "code":"169" + }, + { + "desc":"It is normal that JVM Heap Memory Usage of JVM is displayed in a sawtooth shape on the monitoring page. The maximum value may further increase or the fluctuation may be g", + "product_code":"dms", + "title":"Why Does JVM Heap Memory Usage of JVM Fluctuate Significantly?", + "uri":"kafka-faq-0064.html", + "doc_type":"usermanual", + "p_code":"165", + "code":"170" + }, + { + "desc":"The metric data of the message production rate is reported once every minute. Message production rate = Number of messages produced per minute/60. The value is rounded do", + "product_code":"dms", + "title":"Why Is Production Rate Still 0 When There Are Produced Messages?", + "uri":"kafka-faq-0066.html", + "doc_type":"usermanual", + "p_code":"165", + "code":"171" + }, + { + "desc":"On the Consumer Offset tab page of the consumer group details page, there are stacked messages in a topic (total stack ≠ 0), whereas the Consumer Available Messages on th", + "product_code":"dms", + "title":"Why Is the Number of Stacked Messages Monitored as 0 when Messages Are Stacked?", + "uri":"kafka-faq-0067.html", + "doc_type":"usermanual", + "p_code":"165", + "code":"172" }, { "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.", @@ -1446,7 +1554,7 @@ "uri":"kafka-ug-0723006.html", "doc_type":"usermanual", "p_code":"", - "code":"161" + "code":"173" }, { "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", @@ -1454,8 +1562,8 @@ "title":"Troubleshooting Kafka Connection Exceptions", "uri":"kafka-faq-0604001.html", "doc_type":"usermanual", - "p_code":"161", - "code":"162" + "p_code":"173", + "code":"174" }, { "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", @@ -1463,8 +1571,8 @@ "title":"Troubleshooting 6-Min Latency Between Message Creation and Retrieval", "uri":"kafka-trouble-0709001.html", "doc_type":"usermanual", - "p_code":"161", - "code":"163" + "p_code":"173", + "code":"175" }, { "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 ", @@ -1472,8 +1580,8 @@ "title":"Troubleshooting Message Creation Failures", "uri":"kafka-trouble-0001.html", "doc_type":"usermanual", - "p_code":"161", - "code":"164" + "p_code":"173", + "code":"176" }, { "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", @@ -1481,8 +1589,8 @@ "title":"Troubleshooting Topic Deletion Failures", "uri":"kafka-trouble-0002.html", "doc_type":"usermanual", - "p_code":"161", - "code":"165" + "p_code":"173", + "code":"177" }, { "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", @@ -1490,8 +1598,17 @@ "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":"161", - "code":"166" + "p_code":"173", + "code":"178" + }, + { + "desc":"To consume Kafka messages in Flink 1.15, the consumption progress fails to be submitted, and the error messages \"COORDINATOR_NOT_AVAILABLE\" are thrown.Bug on the Kafka cl", + "product_code":"dms", + "title":"Flink 1.15 Consumption Progress Submission Failure", + "uri":"kafka_trouble_0007.html", + "doc_type":"usermanual", + "p_code":"173", + "code":"179" }, { "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.", @@ -1500,7 +1617,7 @@ "uri":"kafka-ug-00001.html", "doc_type":"usermanual", "p_code":"", - "code":"167" + "code":"180" }, { "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.", @@ -1509,7 +1626,7 @@ "uri":"kafka-ug-00002.html", "doc_type":"usermanual", "p_code":"", - "code":"168" + "code":"181" }, { "desc":"See Glossary.", @@ -1518,6 +1635,6 @@ "uri":"dms-ug-0312114.html", "doc_type":"usermanual", "p_code":"", - "code":"169" + "code":"182" } ] \ No newline at end of file diff --git a/docs/dms/umn/CreateUserAndGrantPolicy.html b/docs/dms/umn/CreateUserAndGrantPolicy.html index 4c8c09abe..5a21c929d 100644 --- a/docs/dms/umn/CreateUserAndGrantPolicy.html +++ b/docs/dms/umn/CreateUserAndGrantPolicy.html @@ -1,26 +1,25 @@ -

Creating a User and Granting DMS for Kafka Permissions

+

Creating an IAM User and Granting DMS for Kafka Permissions

This section describes how to use Identity and Access Management (IAM) for fine-grained permissions control for your Distributed Message Service (DMS) for Kafka resources. With IAM, you can:

-

  • Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing DMS for Kafka resources.
  • Grant users only the permissions required to perform a given task based on their job responsibilities.
  • Entrust another account or cloud service to perform efficient O&M on your DMS for Kafka resources.

If your account meets your permissions requirements, you can skip this section.

-

This section describes the procedure for granting permissions (see Figure 1).

-

Prerequisites

Learn about the permissions (see System-defined roles and policies supported by DMS for Kafka) supported by DMS for Kafka and choose policies according to your requirements. For the permissions of other services, see Permissions.

+

This section describes the procedure for granting user permissions. Figure 1 shows the process flow.

+

Prerequisites

Learn about the permissions (see System-defined roles and policies supported by DMS for Kafka) supported by DMS for Kafka and choose policies according to your requirements. For the permissions of other services, see Permissions.

+

DMS for Kafka permissions policies are based on DMS. Therefore, when assigning permissions for user groups, select DMS permissions policies.

Process Flow

Figure 1 Process for granting DMS for Kafka permissions

-

  1. For the following example, create a user group on the IAM console and assign the DMS ReadOnlyAccess policy to the group.

    -
  2. Create an IAM user and add it to the created user group.
  3. Log in as the IAM user and verify permissions.

    In the authorized region, perform the following operations:

    -
    • 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.
    +

    1. For the following example, create a user group on the IAM console and assign the DMS ReadOnlyAccess to the group.

      +

    2. Create an IAM user and add it to the created user group.

      +
    3. Log in as the IAM user and verify permissions.

      In the authorized region, perform the following operations:

      +
      • 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"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

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.

-
  • DMS for Kafka permissions policies are based on DMS. Therefore, when assigning permissions, select DMS permissions policies.
  • Due to data caching, a policy involving Object Storage Service (OBS) actions will take effect five minutes after it is attached to a user, user group, or project.
-
+

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

  • Example 1: Grant permission to delete and restart instances.
    {
     "Version": "1.1",
     "Statement": [
@@ -34,8 +33,7 @@
     ]
 }
  • Example 2: Grant permission to deny instance deletion.

    A policy with only "Deny" permissions must be used together with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

    -

    Assume that you want to grant the permissions of the DMS FullAccess policy to a user but want to prevent them from deleting instances. You can create a custom policy for denying instance deletion, and attach this policy together with the DMS FullAccess policy to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on DMS for Kafka excepting deleting instances.

    -

    Example policy denying instance deletion:

    +

    For example, if you want to assign all of the permissions of the DMS FullAccess policy to a user, except for deleting instances, you can create a custom policy to deny only instance deletion. When you apply both the DMS FullAccess policy and the custom policy denying instance deletion, since "Deny" always takes precedence over "Allow", the "Deny" will be applied for that one conflicting permission. The user will then be able to perform all operations on instances except deleting instances. The following is an example of a deny policy:

    {
         "Version": "1.1",
         "Statement": [
@@ -51,19 +49,19 @@

DMS for Kafka Resources

A resource is an object that exists within a service. DMS for Kafka resources include kafka. To select these resources, specify their paths.

-
Table 1 DMS for Kafka resources and their paths

Resource

+
- - - - -
Table 1 DMS for Kafka resources and their paths

Resource

Resource Name

+

Resource Name

Path

+

Path

kafka

+

kafka

Instance

+

Instance

[Format]

+

[Format]

DMS:*:*: kafka:instance ID

[Notes]

For instance resources, IAM automatically generates the prefix (DMS:*:*:kafka:) of the resource path.

@@ -78,26 +76,26 @@

DMS for Kafka Request Conditions

Request conditions are useful in determining when a custom policy is in effect. A request condition consists of condition keys and operators. Condition keys are either global or service-level and are used in the Condition element of a policy statement. Global condition keys (starting with g:) are available for operations of all services, while service-specific condition keys (starting with a service name such as dms:) are available only for operations of specific services. An operator must be used together with a condition key to form a complete condition statement.

DMS for Kafka has a group of predefined condition keys that can be used in IAM. For example, to define an "Allow" permission, use the condition dms:ssl to filter instances by SASL configurations. The following table lists the DMS for Kafka predefined condition keys.

-
- - @@ -96,9 +105,9 @@ - - @@ -106,21 +115,65 @@ - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/dms/umn/Kafka-specification.html b/docs/dms/umn/Kafka-specification.html index ee729afbd..632a3bbfe 100644 --- a/docs/dms/umn/Kafka-specification.html +++ b/docs/dms/umn/Kafka-specification.html @@ -1,189 +1,129 @@ -

Specifications

-

Kafka Instance Specifications

Kafka instances are compatible with open-source Kafka v1.1.0, v2.3.0, v2.7, and v3.x. Kafka instances are classified into cluster and single-node types. A cluster instance consists of three or more brokers and a single-node one has one broker.

-

Kafka instances are classified based on instance ECS flavors as follows:

-
  • Cluster
    • kafka.2u4g.cluster.small
    • kafka.2u4g.cluster
    • kafka.4u8g.cluster
    • kafka.8u16g.cluster
    • kafka.12u24g.cluster
    • kafka.16u32g.cluster
    -
  • Single-node
    • kafka.2u4g.single.small
    • kafka.2u4g.single
    -
-

For Kafka instances, the number of transactions per second (TPS) is the maximum number of messages that can be written per second. In the following table, transactions per second (TPS) are calculated assuming that the size of a message is 1 KB. The test scenario is private access in plaintext. The disk type is ultra-high I/O.

-

Cluster Kafka instances support v2.3.0, v2.7, and v3.x. Single-node Kafka instances support v2.7.

+

Cluster Kafka Instances

+

Instance Specifications

A cluster Kafka instance has three or more brokers, and is compatible with open-source Kafka 2.3.0, 2.7, and 3.x.

+

In the following table:

+
  • For Kafka instances, the number of transactions per second (TPS) is the maximum number of messages that can be written per second.
  • TPS performance: number of messages processed per second assuming that the size of a message is 1 KB.
  • Test scenario: private access in plaintext. The disk type is ultra-high I/O.
-
Table 2 Predefined condition keys of DMS for Kafka

Condition Key

+
- - - - - - - - @@ -107,7 +105,7 @@
-
Parent topic: Permission Management
+
Parent topic: Permissions Management
diff --git a/docs/dms/umn/Kafka-client-best-practice.html b/docs/dms/umn/Kafka-client-best-practice.html index 8b886d9f2..ff40f7bbb 100644 --- a/docs/dms/umn/Kafka-client-best-practice.html +++ b/docs/dms/umn/Kafka-client-best-practice.html @@ -1,12 +1,14 @@

Suggestions on Using the Kafka Client

-

Consumers

  1. Ensure that the owner thread does not exit abnormally. Otherwise, the client may fail to initiate consumption requests and the consumption will be blocked.
  2. Commit messages only after they have been processed. Otherwise, the messages may fail to be processed and cannot be polled again.
  3. Generally, do not commit every message. Otherwise, there will be many OFFSET_COMMIT requests, causing high CPU usage. For example, if a consumption request pulls 1000 messages and commits every one of them, TPS of the commit requests is 1000 times that of consumption. The smaller the message size, the larger the ratio. You can commit a specific number of messages in batches or enable enable.auto.commit. However, if the client is faulty, some cached consumption offset may be lost, resulting in repeated consumption. Therefore, you are advised to commit messages in batches based on service requirements.
  4. A consumer cannot frequently join or leave a group. Otherwise, the consumer will frequently perform rebalancing, which blocks consumption.
  5. The number of consumers cannot be greater than the number of partitions in the topic. Otherwise, some consumers may fail to poll for messages.
  6. Ensure that the consumer polls at regular intervals to keep sending heartbeats to the server. If the consumer stops sending heartbeats for long enough, the consumer session will time out and the consumer will be considered to have stopped. This will also block consumption.
  7. Ensure that there is a limitation on the size of messages buffered locally to avoid an out-of-memory (OOM) situation.
  8. Set the timeout for the consumer session to 30 seconds: session.timeout.ms=30000.
  9. Kafka supports exactly-once delivery. Therefore, ensure the idempotency of processing messages for services.
  10. Always close the consumer before exiting. Otherwise, consumers in the same group may be blocked within the timeout set by session.timeout.ms.
  11. Do not start a consumer group name with a special character, such as a number sign (#). Otherwise, monitoring data of the consumer group cannot be displayed.
+

Consumers

  1. Ensure that the owner thread does not exit abnormally. Otherwise, the client may fail to initiate consumption requests and the consumption will be blocked.
  2. Commit messages only after they have been processed. Otherwise, the messages may fail to be processed and cannot be polled again.
  3. Generally, do not commit every message. Otherwise, there will be many OFFSET_COMMIT requests, causing high CPU usage. For example, if a consumption request pulls 1000 messages and commits every one of them, TPS of the commit requests is 1000 times that of consumption. The smaller the message size, the larger the ratio. You can commit a specific number of messages in batches or enable enable.auto.commit. However, if the client is faulty, some cached consumption offset may be lost, resulting in repeated consumption. Therefore, you are advised to commit messages in batches based on service requirements.
  4. A consumer cannot frequently join or leave a group. Otherwise, the consumer will frequently perform rebalancing, which blocks consumption.
  5. The number of consumers in a consumer group must be within the total partitions subscribed by the consumer group. Otherwise, some consumers cannot pull messages.
  6. Ensure that the consumer polls at regular intervals to keep sending heartbeats to the server. If the consumer stops sending heartbeats for long enough, the consumer session will time out and the consumer will be considered to have stopped. This will also block consumption.
  7. Ensure that there is a limitation on the size of messages buffered locally to avoid an out-of-memory (OOM) situation.
  8. Set the timeout for the consumer session to 30 seconds: session.timeout.ms=30000.
  9. Kafka supports exactly-once delivery. Therefore, ensure the idempotency of processing messages for services.
  10. Always close the consumer before exiting. Otherwise, consumers in the same group may be blocked within the timeout set by session.timeout.ms.
  11. Do not start a consumer group name with a special character, such as a number sign (#). Otherwise, monitoring data of the consumer group cannot be displayed.
  12. Handle AuthorizationException in the consumption logic and set consumption retry. For example, in SpringKafka, add the following configuration.
    # Set the authorization exception retry interval to 10 seconds.
+spring.kafka.listener.authorizationExceptionRetryInterval=10000
    +
-

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.
+

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.
  6. Try reusing producers. Do not create producers frequently. When idempotence is enabled (default for producer clients 3.0 and later), producing messages creates producer state objects on the server. Frequent creation results in too many objects to be reclaimed in time, causing server memory surges and performance deterioration. Set enable.idempotence to false if the idempotence is not required.
  7. Catch exception AuthorizationException. You are advised to retry message production on the service side. Self-healing can be implemented through limited retry and backoff policies.

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 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.

+

You can enable or disable automatic topic creation. Enabling this function automatically creates a topic when a message is produced in or consumed from a topic that does not exist.

Others

Maximum number of connections: 3000

Maximum size of a message: 10 MB

diff --git a/docs/dms/umn/Kafka-client-parameter.html b/docs/dms/umn/Kafka-client-parameter.html index 4a5818312..d00d9ef06 100644 --- a/docs/dms/umn/Kafka-client-parameter.html +++ b/docs/dms/umn/Kafka-client-parameter.html @@ -7,9 +7,9 @@
- - @@ -17,10 +17,10 @@ - - - - - - - @@ -51,33 +51,42 @@ - - - - - - - - + + + + +
Table 2 Predefined condition keys of DMS for Kafka

Condition Key

Operator

+

Operator

Description

+

Description

dms:publicIP

+

dms:publicIP

Bool

+

Bool

Whether public access is enabled

+

Whether public access is enabled

dms:ssl

+

dms:ssl

Bool

+

Bool

Whether SSL is enabled

+

Whether SSL is enabled

Default Value

Recommended Value

+

Recommended Value

Description

+

Description

1

all or –1 (if high reliability mode is selected)

+

all or –1 (if high reliability mode is selected)

1 (if high throughput mode is selected)

Indicates the number of acknowledgments the producer requires the server to return before considering a request complete. This controls the durability of records that are sent. The value of this parameter can be any of the following:

+

Number of acknowledgments the producer requires the server to return before considering a request complete. This controls the durability of records that are sent. The value of this parameter can be any of the following:

0: The producer will not wait for any acknowledgment from the server at all. The record will be immediately added to the socket buffer and considered sent. No guarantee can be made that the server has received the record, and the retries configuration will not take effect (as the client generally does not know of any failures). The offset given back for each record will always be set to –1.

1: The leader will write the record to its local log but will respond without waiting until receiving full acknowledgement from all followers. If the leader fails immediately after acknowledging the record but before the followers have replicated it, the record will be lost.

all or -1: The leader needs to wait until all backups in the ISR are written into logs. As long as any backup survives, data will not be lost. min.insync.replicas specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful.

@@ -30,20 +30,20 @@

0

/

+

/

Number of times that the client resends a message. Setting this parameter to a value greater than zero will cause the client to resend any record that failed to be sent.

+

Number of times that the client resends a message. Setting this parameter to a value greater than zero will cause the client to resend any record that failed to be sent.

Note that this retry is no different than if the client re-sent the record upon receiving the error. Allowing retries will potentially change the ordering of records because if two batches are sent to the same partition, and the first fails and is retried but the second succeeds, then the records in the second batch may appear first.

You are advised to configure producers so that they can be able to retry in case of network disconnections. Set retries to 3 and the retry interval retry.backoff.ms to 1000.

request.timeout.ms

30000

+

30,000

/

+

/

Maximum amount of time (in ms) the client will wait for the response of a request. If the response is not received before the timeout elapses, the client will throw a timeout exception.

+

Maximum amount of time (in ms) the client will wait for the response of a request. If the response is not received before the timeout elapses, the client will throw a timeout exception.

Setting this parameter to a large value, for example, 127000 (127s), can prevent records from failing to be sent in high-concurrency scenarios.

TRUE

TRUE

+

TRUE

Setting this parameter to TRUE indicates that when buffer memory is exhausted, the producer must stop receiving new message records or throw an exception.

+

Setting this parameter to TRUE indicates that when buffer memory is exhausted, the producer must stop receiving new message records or throw an exception.

By default, this parameter is set to TRUE. However, in some cases, non-blocking usage is desired and it is better to throw an exception immediately. Setting this parameter to FALSE will cause the producer to instead throw "BufferExhaustedException" when buffer memory is exhausted.

batch.size

16384

+

16,384

262144

+

262,144

Default maximum number of bytes of messages that can be processed at a time. The producer will attempt to batch records together into fewer requests whenever multiple records are being sent to the same partition. This helps improve performance of both the client and the server. No attempt will be made to batch records larger than this size.

+

Default maximum number of bytes of messages that can be processed at a time. The producer will attempt to batch records together into fewer requests whenever multiple records are being sent to the same partition. This helps improve performance of both the client and the server. No attempt will be made to batch records larger than this size.

Requests sent to brokers will contain multiple batches, one for each partition with data available to be sent.

A smaller batch size will make batching less common and may reduce throughput (a batch size of zero will disable batching entirely). A larger batch size may use more memory as a buffer of the specified batch size will always be allocated in anticipation of additional records.

buffer.memory

33554432

+

33,554,432

67108864

+

67,108,864

Total bytes of memory the producer can use to buffer records waiting to be sent to the server. If records are sent faster than they can be delivered to the broker, the producer will stop sending records or throw a "block.on.buffer.full" exception.

+

Total bytes of memory the producer can use to buffer records waiting to be sent to the server. If records are sent faster than they can be delivered to the broker, the producer will stop sending records or throw a "block.on.buffer.full" exception.

This setting should correspond roughly to the total memory the producer will use, but is not a rigid bound since not all memory the producer uses is used for buffering. Some additional memory will be used for compression (if compression is enabled) as well as for maintaining in-flight requests.

enable.idempotence

+
  • Earlier than v3.0: false
  • v3.0 and later: true
+

If idempotence is not required, you are advised to set this parameter to false.

+

If you have enabled idempotence on the producer client, and produced messages, message offsets are not continuous on the consumer client or on the Message Query page on the Kafka console. This is because enabling idempotence generates some metadata control messages during message production. These control messages are produced to topics, and are invisible to consumers.

+
@@ -86,9 +95,9 @@

Default Value

Recommended Value

+

Recommended Value

Description

+

Description

TRUE

FALSE

+

FALSE

If this parameter is set to TRUE, the offset of messages already fetched by the consumer will be periodically committed to ZooKeeper. This committed offset will be used when the process fails as the position from which the new consumer will begin.

+

If this parameter is set to TRUE, the offset of messages already fetched by the consumer will be periodically committed to ZooKeeper. This committed offset will be used when the process fails as the position from which the new consumer will begin.

Constraints: If this parameter is set to FALSE, to avoid message loss, an offset must be committed to ZooKeeper after the messages are successfully consumed.

latest

earliest

+

earliest

Indicates what to do when there is no initial offset in ZooKeeper or if the current offset has been deleted. Options:

-
  • earliest: Automatically reset to the smallest offset.
  • latest: The offset is automatically reset to the largest offset.
  • none: The system throws an exception to the consumer if no offset is available.
  • anything else: The system throws an exception to the consumer.
-
NOTE:

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.

-
+

Indicates what to do when there is no initial offset in ZooKeeper or if the current offset has been deleted. Options:

+
  • earliest: Automatically reset to the smallest offset.
  • latest: Automatically reset to the largest offset.
  • none: The system throws an exception to the consumer if no offset is available.
  • anything else: 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.

connections.max.idle.ms

600000

+

600,000

30000

+

30,000

Timeout interval (in ms) for an idle connection. The server closes the idle connection after this period of time ends. Setting this parameter to 30000 can reduce the server response failures when the network condition is poor.

+

Timeout interval (in ms) for an idle connection. The server closes the idle connection after this period of time ends. Setting this parameter to 30000 can reduce the server response failures when the network condition is poor.

+

max.poll.records

+

500

+

Must be less than the value of max.poll.interval.ms.

+

The maximum number of messages that a consumer can pull from a broker at a time.

+

max.poll.interval.ms

+

300,000

+

Increase this parameter if complex and time-consuming logic exists between two polls.

+

The maximum interval between consumer polls, in milliseconds. If this parameter is exceeded, the consumption fails and the consumer is removed from the consumer group, triggering rebalance.

+

heartbeat.interval.ms

+

3,000

+

≥ 3000

+

Heartbeat interval between a consumer and Kafka, in milliseconds.

+

session.timeout.ms

+

10,000

+

Set this parameter to at least 3 times the value of heartbeat.interval.ms.

+

The consumer-broker session timeout when the offset is managed by consumer group, in milliseconds.

+

fetch.max.bytes

+

1,000,000

+

max.request.size < message.max.bytes < fetch.max.bytes

+

The maximum bytes of a message that a consumer can pull from a broker at a time.
- - @@ -41,42 +41,42 @@ - - - - - - - - diff --git a/docs/dms/umn/kafka-faq-0035.html b/docs/dms/umn/kafka-faq-0035.html index 37c7bed98..e078520b1 100644 --- a/docs/dms/umn/kafka-faq-0035.html +++ b/docs/dms/umn/kafka-faq-0035.html @@ -1,7 +1,7 @@

Does Specification Modification Affect Services?

-

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 modification takes.

+

Table 1 describes the impact of increasing specifications.

Table 1 Kafka instance specifications (cluster)

Flavor

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 1 Cluster Kafka instance specifications

Flavor

Brokers

+

Brokers

Maximum TPS per Broker

+

Maximum TPS per Broker

Maximum Partitions per Broker

+

Maximum Partitions per Broker

Recommended Consumer Groups per Broker

+

Recommended Consumer Groups per Broker

Maximum Client Connections per Broker

+

Maximum Client Connections per Broker

Storage Space

+

Storage Space (GB)

Traffic per Broker (MB/s)

+

Traffic per Broker (MB/s)

kafka.2u4g.cluster.small

+

kafka.2u4g.cluster.small

3–30

+

3–30

20,000

+

20,000

100

+

100

15

+

15

2000

+

2,000

300 GB–300,000 GB

+

300–300,000

40

+

40

kafka.2u4g.cluster

+

kafka.2u4g.cluster

3–30

+

3–30

30,000

+

30,000

250

+

250

20

+

20

2000

+

2,000

300 GB–300,000 GB

+

300–300,000

100

+

100

kafka.4u8g.cluster

+

kafka.4u8g.cluster

3–30

+

3–30

100,000

+

100,000

500

+

500

100

+

100

4000

+

4,000

300 GB–600,000 GB

+

300–600,000

200

+

200

kafka.8u16g.cluster

+

kafka.8u16g.cluster

3–50

+

3–50

150,000

+

150,000

1000

+

1000

150

+

150

4000

+

4,000

300 GB–1,500,000 GB

+

300–1,500,000

375

+

375

kafka.12u24g.cluster

+

kafka.12u24g.cluster

3–50

+

3–50

200,000

+

200,000

1500

+

1,500

200

+

200

4000

+

4,000

300 GB–1,500,000 GB

+

300–1,500,000

625

+

625

kafka.16u32g.cluster

+

kafka.16u32g.cluster

3–50

+

3–50

250,000

+

250,000

2000

+

2,000

200

+

200

4000

+

4,000

300 GB–1,500,000 GB

+

300–1,500,000

750

-
-
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - @@ -199,9 +139,9 @@

Assume that the current flavor is kafka.2u4g.cluster, the traffic per broker is 100 MB/s, and the number of brokers is 3. What are the total network traffic, maximum read traffic, and maximum write traffic of the instance?

  1. Total network traffic = Traffic per broker x Broker quantity = 100 MB/s x 3 = 300 MB/s
  2. Maximum read traffic = Total instance network traffic/Default number of replicas/2 = 300 MB/s/3/2= 50 MB/s
  3. Maximum write traffic = Total instance network traffic/Default number of replicas/2 = 300 MB/s/3/2 = 50 MB/s
-

Mapping Between Old and New Flavors

Table 3 compares the old and new Kafka instance flavors.

+

Mapping Between Old and New Flavors

Table 2 compares the old and new Kafka instance flavors.

-
Table 2 Kafka instance specifications (single-node)

Flavor

-

Brokers

-

TPS per Broker

-

Maximum Partitions per Broker

-

Recommended Consumer Groups per Broker

-

Maximum Client Connections per Broker

-

Storage Space

-

Traffic per Broker (MB/s)

-

kafka.2u4g.single.small

-

1

-

20,000

-

100

-

15

-

2000

-

100 GB–10,000 GB

-

40

-

kafka.2u4g.single

-

1

-

30,000

-

250

-

20

-

2000

-

100 GB–10,000 GB

-

100

+

750
- @@ -38,7 +38,7 @@ - @@ -56,8 +56,7 @@

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.

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.

-
  1. Start new consumer clients, set the Kafka connection addresses to that of the new Kafka instance, and consume data from the new Kafka instance.

    Original consumer clients must continue running. Messages are consumed from both the original and new Kafka instances.

    -
    +
    1. Start new consumer clients, set the Kafka connection addresses to that of the new Kafka instance, and consume data from the new Kafka instance.

      Original consumer clients must continue running. Messages are consumed from both the original and new Kafka instances.

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

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.

diff --git a/docs/dms/umn/kafka-dnat.html b/docs/dms/umn/kafka-dnat.html index ad6d9e303..2338b537b 100644 --- a/docs/dms/umn/kafka-dnat.html +++ b/docs/dms/umn/kafka-dnat.html @@ -6,32 +6,105 @@

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.

    -
    -

  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 Connection area on the Basic Information tab page, view and record the private network access addresses of the Kafka instance. In the Network area, view and record the VPC and subnet where the Kafka instance is located.

    Figure 1 Kafka instance information
    +

    Step 1: Obtain Information About the Kafka Instance

    1. Log in to the console.
    2. Click in the upper left corner to select the region where your instance is located.
    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
    4. Click the desired instance to go to the instance details page.
    5. In the Connection area on the Basic Information page, view and record the private network access addresses of the Kafka instance. In the Network area, view and record the VPC and subnet where the Kafka instance is located.

      Figure 1 Kafka instance information

    -

    Step 2: Create a Public NAT Gateway

    1. Click Service List and choose Network > NAT Gateway.
    2. Click Create Public NAT Gateway.
    3. Set the following parameters:

      • Region: Select the region that the Kafka instance is in.
      • Name: Enter a name for the public NAT gateway.
      • VPC: Select the VPC recorded in 5.
      • Subnet: Select the subnet recorded in 5.
      -

      Set other parameters as required. For details, see Creating a NAT Gateway.

      -
      Figure 2 Create Public NAT Gateway
      +

      Step 2: Create a Public NAT Gateway

      1. Click Service List and choose Network > NAT Gateway.
      2. Click Create Public NAT Gateway.
      3. Set parameters by referring to Table 1 and other parameters as required. For details, see Creating a Public NAT Gateway.

        Figure 2 Create Public NAT Gateway
        + +
Table 3 Mapping between old and new Kafka instance flavors

Old Flavor

+
@@ -243,20 +183,20 @@ - - -
Table 2 Mapping between old and new Kafka instance flavors

Old Flavor

New Flavor

600 MB/s

1200 MB/s

+

1,200 MB/s

1200 MB/s

+

1,200 MB/s

kafka.4u8g.cluster * 6

1250 MB/s

+

1,250 MB/s

Instances with new flavors have the following features:

-
  • Better performance and cost effectiveness: They use exclusive resources (except for kafka.2u4g.cluster.small). By contrast, old flavors use non-exclusive resources. If the load is heavy, resources conflicts will occur.
  • Latest functions, for example, reassigning partitions and changing the SSL setting.
  • Flexible flavor changes: For example, you can increase the broker flavor.
  • Flexible disk capacity: Only related to the broker quantity, and not to the flavor.
  • More specification options: A wider range of combinations of broker flavor (over 10,000 MB/s) and quantity are available.
+
  • Better performance and cost effectiveness: They use exclusive resources (except for kafka.2u4g.cluster.small). By contrast, old flavors use non-exclusive resources. If the load is heavy, resources conflicts will occur.
  • Latest functions, for example, reassigning partitions and changing the SSL setting.
  • Flexible flavor changes: For example, you can increase the broker flavor.
  • Flexible disk capacity: Only related to the broker quantity, and not to the flavor.
  • More specification options: A wider range of combinations of broker flavor (over 10,000 MB/s) and quantity are available.
  • More disk type options: General Purpose SSD and Extreme SSD are now available, in addition to the original disk types.

Flavor Selection

  • kafka.2u4g.cluster.small with 3 brokers

    Recommended for up to 6000 client connections, 45 consumer groups, and 60,000 TPS

  • kafka.2u4g.cluster with 3 brokers

    Recommended for up to 6000 client connections, 60 consumer groups, and 90,000 TPS

    @@ -271,15 +211,14 @@

    The storage space can be expanded as your service grows.

Topic Quantity

There are limits on the topic quantity and the aggregate number of partitions in the topics. When the partition quantity limit is reached, you can no longer create topics.

-

The number of topics is related to the maximum number of partitions allowed (see Table 1 and Table 2) and the specified number of partitions in each topic (see Figure 1).

-
Figure 1 Setting the number of partitions
+

The number of topics is related to the maximum number of partitions allowed (see Table 1) and the specified number of partitions in each topic.

The maximum number of partitions allowed for an instance with kafka.2u4g.cluster and 3 brokers is 750.

  • If the number of partitions of each topic in the instance is 3, the maximum number of topics is 750/3 = 250.
  • If the number of partitions of each topic in the instance is 1, the maximum number of topics is 750/1 = 750.
-
Parent topic: Service Overview
+
Parent topic: Kafka Instance Specifications
diff --git a/docs/dms/umn/ProductDescPrivilegeManagement.html b/docs/dms/umn/ProductDescPrivilegeManagement.html index da4a6ec68..4c91d6e65 100644 --- a/docs/dms/umn/ProductDescPrivilegeManagement.html +++ b/docs/dms/umn/ProductDescPrivilegeManagement.html @@ -1,6 +1,6 @@ -

Permission

+

Permissions

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.

diff --git a/docs/dms/umn/TagManagement.html b/docs/dms/umn/TagManagement.html index 79d70be80..b83d0ce18 100644 --- a/docs/dms/umn/TagManagement.html +++ b/docs/dms/umn/TagManagement.html @@ -2,7 +2,7 @@

Configuring Kafka Instance Tags

Tags facilitate Kafka instance identification and management.

-

You can add tags to a Kafka instance when creating the instance or add tags on the Tags tab page of the created instance. Up to 20 tags can be added to an instance. Tags can be deleted.

+

You can add tags to a Kafka instance when creating the instance or add tags on the Tags page of the created instance. Tags can be deleted.

A tag consists of a tag key and a tag value. Table 1 lists the tag key and value requirements.

- -
Table 1 Tag key and value requirements

Parameter

@@ -13,22 +13,26 @@

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 start with _sys_.
+
  • 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 in instance creation.
+
  • Can contain 0 to 255 characters.
  • Can contain letters, digits, spaces, and special characters _.:=+-@
  • Cannot start or end with a space in instance creation.
-

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:

9094

0.0.0.0/0

+

IP address or IP address group of the Kafka client

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

9095

0.0.0.0/0

+

IP address or IP address group of the Kafka client

Accessing a Kafka instance in a public network (in ciphertext)
+ + + + + + + + + + + + + + + + +
Table 1 Public NAT gateway creation parameters

Parameter

+

Description

+

Region

+

Region where the public NAT gateway is located. Select the region that the Kafka instance is in.

+

Name

+

Enter a name for the public NAT gateway. Enter up to 64 characters. Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed.

+

VPC

+

VPC where the public NAT gateway resides. Select the VPC recorded in 5.

+

Subnet

+

Subnet in the VPC where the public NAT gateway resides. Select the subnet recorded in 5.

+
+

  • Click Create Now.
  • Confirm the specifications and click Submit.

    • Step 3: Add a DNAT Rule

    1. On Public NAT Gateways page, locate the row containing the newly created public NAT gateway and click Add Rule in the Operation column.
    2. On the DNAT Rules tab page, click Add DNAT Rule.

      Figure 3 Public NAT gateway details
      -

    3. Set the following parameters:

      • Scenario: Select VPC.
      • Port Type: Select Specific port.
      • Protocol: Select TCP.
      • EIP: Select an EIP.
      • Outside Port: Enter 9011.
      • Instance Type: Select Custom.
      • Private IP Address: Enter one of the private network addresses of the Kafka instance recorded in 5.
      • Inside Port: Enter 9011.
      -

      For details about more parameters, see Adding a DNAT Rule.

      -
      Figure 4 Adding a DNAT rule
      +

    4. Set parameters by referring to Table 2. For details about more parameters, see Adding a DNAT Rule.

      Figure 4 Adding a DNAT rule
      + +
      + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      Table 2 Adding a DNAT rule

      Parameter

      +

      Description

      +

      Scenario

      +

      Select VPC. The servers in a VPC will share an EIP to provide services accessible from the Internet through the DNAT rule.

      +

      Port Type

      +

      Select Specific port. The public NAT gateway forwards requests to your servers only from the outside port and to the inside port configured here, and only if they use the right protocol.

      +

      Protocol

      +

      Select TCP.

      +

      EIP

      +

      Select the created EIP.

      +

      Outside Port

      +

      Enter 9011.

      +

      Instance Type

      +

      Instance type for providing services over external public networks. Select Custom.

      +

      Private IP Address

      +

      Enter one of the private network addresses of the Kafka instance recorded in 5.

      +

      Inside Port

      +

      Enter 9011.

      +
      +

    5. Click OK.

      View the DNAT rule status in the DNAT rule list. If Status is Running, the rule has been added successfully.

    6. 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.

    7. 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: 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 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 area on the Basic Information page, click Modify.
      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).

      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 5 are 100.xxx.xxx.20:9011,100.xxx.xxx.21:9011,100.xxx.xxx.23:9011.
      • Configure security group rules for the Kafka instance to allow inbound access over port 9011.
      • Public access must be enabled on the client connected to the Kafka instance.
      -

    diff --git a/docs/dms/umn/kafka-faq-0001.html b/docs/dms/umn/kafka-faq-0001.html index 3f9338d29..011f1b9bd 100644 --- a/docs/dms/umn/kafka-faq-0001.html +++ b/docs/dms/umn/kafka-faq-0001.html @@ -1,9 +1,8 @@

    How Do I Obtain the Public Access Address After Public Access Is Enabled?

    -

    Click the name of your Kafka instance. In the Connection section on the Basic Information tab page, view Instance Address (Public Network).

    +

    Click the name of your Kafka instance. In the Connection section on the Basic Information page, view Instance Address (Public Network).

    For details about how to connect to a Kafka instance, see Connecting to an Instance.

    -

    diff --git a/docs/dms/umn/kafka-faq-0005.html b/docs/dms/umn/kafka-faq-0005.html index 4b7e605bb..9d915bd8f 100644 --- a/docs/dms/umn/kafka-faq-0005.html +++ b/docs/dms/umn/kafka-faq-0005.html @@ -1,8 +1,7 @@

    How Do I Increase the Partition Quantity?

    -

    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 Specifications. On the page that is displayed, add brokers as required. For details, see Modifying Kafka Instance Specifications.

    +

    You can increase the partition quantity by increasing broker flavors or adding brokers. For details, see Modifying Cluster Kafka Instance Specifications.

    diff --git a/docs/dms/umn/kafka-faq-0033.html b/docs/dms/umn/kafka-faq-0033.html index 182eae736..8b8cd1bb3 100644 --- a/docs/dms/umn/kafka-faq-0033.html +++ b/docs/dms/umn/kafka-faq-0033.html @@ -11,7 +11,7 @@

    100 MB/s

    3000

    +

    3,000

    300 MB/s

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

    20,000

    1200 MB/s

    +

    1,200 MB/s

    20,000

    kafka.2u4g.cluster.small

    2000

    +

    2,000

    kafka.2u4g.single.small

    2000

    +

    2,000

    kafka.2u4g.cluster

    2000

    +

    2,000

    kafka.2u4g.single

    2000

    +

    2,000

    kafka.4u8g.cluster

    4000

    +

    4,000

    kafka.8u16g.cluster

    4000

    +

    4,000

    kafka.12u24g.cluster

    4000

    +

    4,000

    kafka.16u32g.cluster

    4000

    +

    4,000
    @@ -11,7 +11,7 @@ - diff --git a/docs/dms/umn/kafka-faq-0038.html b/docs/dms/umn/kafka-faq-0038.html index aba39f09b..b39a7d9a9 100644 --- a/docs/dms/umn/kafka-faq-0038.html +++ b/docs/dms/umn/kafka-faq-0038.html @@ -8,7 +8,6 @@
    Figure 1 Consumer access permissions

    Solution:

    • If all consumers must be in the same consumer group (group.id is the same), grant the same topic access permissions to all the consumers.
    • If the consumers do not need to be in the same consumer group, change the value of group.id to ensure that each consumer is in a separate consumer group.
    -

    diff --git a/docs/dms/umn/kafka-faq-0041.html b/docs/dms/umn/kafka-faq-0041.html index 18cb176aa..39f17761d 100644 --- a/docs/dms/umn/kafka-faq-0041.html +++ b/docs/dms/umn/kafka-faq-0041.html @@ -2,9 +2,8 @@

    How Do I View the Number of Accumulated Messages?

    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 accumulated messages are to be viewed. The consumer group details page is displayed. On the Consumer Offset tab page, view the number of messages accumulated in each topic of your target consumer group. For details, see Viewing Consumer Offsets.
    • On the Monitoring tab page of an instance, click the By Consumer Group tab. Select the desired consumer group for Consumer Group and All topics for Topic. The Consumer Available Messages metric reflects the number of messages accumulated in all topics of this consumer group. For details about viewing the monitoring data, see Viewing Kafka Metrics.
    • On the Consumer Groups tab page of the Cloud Eye console, click the By Consumer Group tab. Select the desired consumer group for Consumer Group and All topics for Topic. The Consumer Available Messages metric reflects the number of messages accumulated in all topics of this consumer group. For details about viewing the monitoring data, see Viewing Kafka Metrics.
    • In the /bin directory on the Kafka client, run command kafka-consumer-groups.sh --bootstrap-server ${connection-address} --describe --group ${consumer-group-name} to check number of accumulated messages of each topic in a consumer group. LAG indicates the total number of messages accumulated in each topic.
      Figure 1 Viewing the total number of messages accumulated in each topic
      -

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

      -
      +
      • On the Consumer Groups page of an instance, click the name of the consumer group whose accumulated messages are to be viewed. The consumer group details page is displayed. On the Consumer Offset tab page, view the number of messages accumulated in each topic of your target consumer group. For details, see Viewing Consumer Offsets.
      • On the Monitoring page of an instance, click the By Consumer Group tab. Select the desired consumer group for Consumer Group and All topics for Topic. The Consumer Available Messages metric reflects the number of messages accumulated in all topics of this consumer group. For details about viewing the monitoring data, see Viewing Kafka Metrics.
      • On the Consumer Groups tab page of the Cloud Eye console, click the By Consumer Group tab. Select the desired consumer group for Consumer Group and All topics for Topic. The Consumer Available Messages metric reflects the number of messages accumulated in all topics of this consumer group. For details about viewing the monitoring data, see Viewing Kafka Metrics.
      • In the /bin directory on the Kafka client, run command kafka-consumer-groups.sh --bootstrap-server ${connection-address} --describe --group ${consumer-group-name} to check number of accumulated messages of each topic in a consumer group. LAG indicates the total number of messages accumulated in each topic.
        Figure 1 Viewing the total number of messages accumulated in each topic
        +

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

    diff --git a/docs/dms/umn/kafka-faq-0063.html b/docs/dms/umn/kafka-faq-0063.html new file mode 100644 index 000000000..d882f2512 --- /dev/null +++ b/docs/dms/umn/kafka-faq-0063.html @@ -0,0 +1,11 @@ + + +

    Why Do Metrics Fluctuate Significantly (Disk Read/Write Speed, Average Disk Read/Write Time, and CPU Usage)?

    +

    Metrics including Disk Read Speed, Disk Write Speed, Average Disk Read Time, Average Disk Write Time, and CPU Usage output instantaneous values. These metrics are for reference only. Generally, flushing Kafka data asynchronously to disk consumes disk I/O and CPU usage, causing fluctuations. They do not affect services.

    +
    +
    +
    +
    Parent topic: Monitoring & Alarm
    +
    +
    + diff --git a/docs/dms/umn/kafka-faq-0064.html b/docs/dms/umn/kafka-faq-0064.html new file mode 100644 index 000000000..ee2d1e760 --- /dev/null +++ b/docs/dms/umn/kafka-faq-0064.html @@ -0,0 +1,11 @@ + + +

    Why Does JVM Heap Memory Usage of JVM Fluctuate Significantly?

    +

    It is normal that JVM Heap Memory Usage of JVM is displayed in a sawtooth shape on the monitoring page. The maximum value may further increase or the fluctuation may be greater after scale-out or an engine upgrade. Such fluctuations are caused by normal JVM heap memory reclamation, and do not affect services.

    +
    +
    +
    +
    Parent topic: Monitoring & Alarm
    +
    +
    + diff --git a/docs/dms/umn/kafka-faq-0065.html b/docs/dms/umn/kafka-faq-0065.html new file mode 100644 index 000000000..ebbcd65c9 --- /dev/null +++ b/docs/dms/umn/kafka-faq-0065.html @@ -0,0 +1,12 @@ + + +

    Why Are Offsets Not Continuous?

    +

    If you have enabled idempotence or transactions on the producer client, and produced messages, message offsets are not continuous on the consumer client or on the Message Query page on the Kafka console. This is because enabling idempotence or transactions generates some metadata control messages during message production. These control messages are produced to topics, and are invisible to consumers.

    +

    By default, idempotence is enabled for Kafka 3.0 and later producer clients. To disable it, set the parameter enable.idempotence to false.

    +
    +
    +
    +
    Parent topic: Messages
    +
    +
    + diff --git a/docs/dms/umn/kafka-faq-0066.html b/docs/dms/umn/kafka-faq-0066.html new file mode 100644 index 000000000..1025557e3 --- /dev/null +++ b/docs/dms/umn/kafka-faq-0066.html @@ -0,0 +1,11 @@ + + +

    Why Is Production Rate Still 0 When There Are Produced Messages?

    +

    The metric data of the message production rate is reported once every minute. Message production rate = Number of messages produced per minute/60. The value is rounded down. The production rate is displayed as 0 if the number of messages produced within a minute is less than 60.

    +
    +
    +
    +
    Parent topic: Monitoring & Alarm
    +
    +
    + diff --git a/docs/dms/umn/kafka-faq-0067.html b/docs/dms/umn/kafka-faq-0067.html new file mode 100644 index 000000000..4e96978f7 --- /dev/null +++ b/docs/dms/umn/kafka-faq-0067.html @@ -0,0 +1,15 @@ + + +

    Why Is the Number of Stacked Messages Monitored as 0 when Messages Are Stacked?

    +

    Symptom

    On the Consumer Offset tab page of the consumer group details page, there are stacked messages in a topic (total stack ≠ 0), whereas the Consumer Available Messages on the consumer group monitoring page is 0.

    +
    +

    Conclusion

    The total stack on the Consumer Offset tab page and the Consumer Available Messages are not synchronously updated.

    +

    The total stack is sampled immediately. The Consumer Available Messages is sampled every minute. You see the stack number at your time. When a consumer consumes all the stacked messages within 1 minute, Consumer Available Messages displays 0.

    +
    +
    +
    +
    +
    Parent topic: Monitoring & Alarm
    +
    +
    + diff --git a/docs/dms/umn/kafka-faq-0068.html b/docs/dms/umn/kafka-faq-0068.html new file mode 100644 index 000000000..8aa07c2ae --- /dev/null +++ b/docs/dms/umn/kafka-faq-0068.html @@ -0,0 +1,11 @@ + + +

    Can I Purchase Partitions Separately?

    +

    No. However, you can increase the total number of partitions by increasing the broker quantity or flavor. For details, see Modifying Cluster Kafka Instance Specifications.

    +
    +
    +
    +
    Parent topic: Topics and Partitions
    +
    +
    + diff --git a/docs/dms/umn/kafka-faq-0069.html b/docs/dms/umn/kafka-faq-0069.html new file mode 100644 index 000000000..4fb9b1a0a --- /dev/null +++ b/docs/dms/umn/kafka-faq-0069.html @@ -0,0 +1,12 @@ + + +

    Why Are Consumer Groups Missing?

    +

    If you cannot find a consumer group from the console, the possible causes are as follows:

    +
    • 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 after it is created.
    • If the consumer group has never committed an offset, it will be deleted after the Kafka instance restarts.
    +
    +
    +
    +
    Parent topic: Consumer Groups
    +
    +
    + diff --git a/docs/dms/umn/kafka-faq-0070.html b/docs/dms/umn/kafka-faq-0070.html new file mode 100644 index 000000000..01aced255 --- /dev/null +++ b/docs/dms/umn/kafka-faq-0070.html @@ -0,0 +1,17 @@ + + +

    Why Are the Earliest Messages Not Automatically Deleted When the Disk Capacity Reaches 95%?

    +

    Symptom

    Each broker of a Kafka instance has a 100 GB disk. The automatic deletion policy has been configured and a topic with 180 partitions has been created. The earliest messages are not automatically deleted when the disk usage reaches 95%.

    +
    +

    Possible Cause

    Each broker of a Kafka instance uses a 33 GB disk to store logs and ZooKeeper data. Such a disk was formatted during instance creation and certain space is used. As a result, the data storage space is approximately 66 GB. Several segment files constitute each partition of a topic. Each segment file has maximum storage of 500 MB. To delete a message, Kafka deletes segment files instead of a message. Kafka reserves at least one segment file in each partition for message storage. In this way, at least one segment file is kept. Increasing partitions to 132 (66 GB/500 MB = 132) may cause the disk usage to reach the upper limit.

    +

    When the disk usage reaches 95% (62.7 GB), the messages might be stored in one of those kept segment files. In this case, the messages are not deleted.

    +
    +

    Solution

    Expand the storage. For details, see Modifying Cluster Kafka Instance Specifications

    +
    +
    +
    +
    +
    Parent topic: Instances
    +
    +
    + diff --git a/docs/dms/umn/kafka-faq-180604024.html b/docs/dms/umn/kafka-faq-180604024.html index cd4cc558c..aec8df3b6 100644 --- a/docs/dms/umn/kafka-faq-180604024.html +++ b/docs/dms/umn/kafka-faq-180604024.html @@ -25,7 +25,7 @@
    - @@ -38,7 +38,7 @@ - @@ -51,7 +51,7 @@ - @@ -64,7 +64,7 @@ - @@ -155,7 +155,7 @@ - @@ -166,7 +166,7 @@ - @@ -177,7 +177,7 @@ - @@ -210,7 +210,7 @@ - @@ -223,7 +223,7 @@ - @@ -236,7 +236,7 @@ - @@ -249,7 +249,7 @@ - diff --git a/docs/dms/umn/kafka-faq-190416001.html b/docs/dms/umn/kafka-faq-190416001.html index 99a73e17c..7184b5bf5 100644 --- a/docs/dms/umn/kafka-faq-190416001.html +++ b/docs/dms/umn/kafka-faq-190416001.html @@ -22,6 +22,8 @@
  • How Do I Modify message.max.bytes?
    • +
  • Why Are Offsets Not Continuous?
    +
    • diff --git a/docs/dms/umn/kafka-faq-191030002.html b/docs/dms/umn/kafka-faq-191030002.html index 9e366e539..a16b04765 100644 --- a/docs/dms/umn/kafka-faq-191030002.html +++ b/docs/dms/umn/kafka-faq-191030002.html @@ -52,6 +52,8 @@
  • How Do I Bind an EIP Again?
    • +
  • Why Are the Earliest Messages Not Automatically Deleted When the Disk Capacity Reaches 95%?
    +
    • diff --git a/docs/dms/umn/kafka-faq-191030003.html b/docs/dms/umn/kafka-faq-191030003.html index 1fd2e76b7..43a3140d4 100644 --- a/docs/dms/umn/kafka-faq-191030003.html +++ b/docs/dms/umn/kafka-faq-191030003.html @@ -14,8 +14,6 @@
  • Do Kafka Instances Support Batch Importing Topics or Automatic Topic Creation?
    • -
  • Why Do Deleted Topics Still Exist?
    -
  • Can I View the Disk Space Used by a Topic?
  • Can I Add ACL Permissions for Topics?
    @@ -28,6 +26,8 @@
  • What Can I Do If a Consumer Fails to Retrieve Messages from a Topic Due to Insufficient Permissions?
    • +
  • Can I Purchase Partitions Separately?
    +
    • diff --git a/docs/dms/umn/kafka-faq-191030004.html b/docs/dms/umn/kafka-faq-191030004.html index 30720d734..97763b035 100644 --- a/docs/dms/umn/kafka-faq-191030004.html +++ b/docs/dms/umn/kafka-faq-191030004.html @@ -10,6 +10,14 @@
  • Why Is a Consumer Group Still on the Monitoring Page After Being Deleted?
    • +
  • Why Do Metrics Fluctuate Significantly (Disk Read/Write Speed, Average Disk Read/Write Time, and CPU Usage)?
    +
    • +
  • Why Does JVM Heap Memory Usage of JVM Fluctuate Significantly?
    +
    • +
  • Why Is Production Rate Still 0 When There Are Produced Messages?
    +
    • +
  • Why Is the Number of Stacked Messages Monitored as 0 when Messages Are Stacked?
    +
    • diff --git a/docs/dms/umn/kafka-faq-200423001.html b/docs/dms/umn/kafka-faq-200423001.html index d4bb36e1e..a78c9f626 100644 --- a/docs/dms/umn/kafka-faq-200423001.html +++ b/docs/dms/umn/kafka-faq-200423001.html @@ -14,6 +14,8 @@
  • Can I Delete Unnecessary Topics in a Consumer Group?
    • +
  • Why Are Consumer Groups Missing?
    +
    • diff --git a/docs/dms/umn/kafka-faq-200426003.html b/docs/dms/umn/kafka-faq-200426003.html index 62c2460fc..2adeb8ffd 100644 --- a/docs/dms/umn/kafka-faq-200426003.html +++ b/docs/dms/umn/kafka-faq-200426003.html @@ -1,7 +1,7 @@

    Why Can't I View the Subnet and Security Group Information When Creating a DMS Instance?

    -

    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 Modifying User Group Information.

    +

    The possible cause is that 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 Modifying User Group Information.

    diff --git a/docs/dms/umn/kafka-faq-200426005.html b/docs/dms/umn/kafka-faq-200426005.html index 5ad0b37e4..497c71fe9 100644 --- a/docs/dms/umn/kafka-faq-200426005.html +++ b/docs/dms/umn/kafka-faq-200426005.html @@ -2,8 +2,8 @@

    How Do I Select Storage Space for a Kafka Instance?

    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. For more information, see Disk Types and Performance.

    -

    For example, if the required disk size to store data for the retention period is 100 GB, the disk capacity must be at least: 100 GB x Number of replicas + 100 GB (reserved space). In a Kafka cluster, each node uses a 33 GB disk to store logs and ZooKeeper data. Therefore, the actual available storage space is less than the created storage space.

    -

    The number of replicas (3 by default) can be configured when you create a topic. If automatic topic creation has been enabled, each automatically created topic has three replicas by default. You can change this quantity by setting default.replication.factor on the Parameters tab page.

    +

    For example, if the required disk size to store data for the retention period is 100 GB, the disk capacity must be at least: 100 GB × Number of replicas + 100 GB (reserved space). In a Kafka cluster, each node uses a 33 GB disk to store logs and ZooKeeper data. Therefore, the actual available storage space is less than the created storage space.

    +

    The number of replicas (3 by default) can be configured when you create a topic. If automatic topic creation has been enabled, each automatically created topic has three replicas by default. You can change this quantity by setting default.replication.factor on the Parameters page.

    diff --git a/docs/dms/umn/kafka-faq-200426007.html b/docs/dms/umn/kafka-faq-200426007.html index f6a011185..559cc7878 100644 --- a/docs/dms/umn/kafka-faq-200426007.html +++ b/docs/dms/umn/kafka-faq-200426007.html @@ -3,9 +3,9 @@

    Which Capacity Threshold Policy Should I Use?

    The following policies are supported:

    • Stop production

      When the memory usage reaches the disk capacity threshold (95%), new messages will no longer be created, but existing messages can still be retrieved until they are discarded. The default retention time is three days. This policy is suitable for scenarios where no data losses can be tolerated.

      -
    • Automatically delete

      When the memory usage reaches the disk capacity threshold (95%), 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.

      +
    • Automatically delete

      When the memory usage reaches the disk capacity threshold (95%), messages can be produced and consumed, 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.

    -

    Select a proper policy based on requirements for data and service reliability. Both policies are only used for handling extreme scenarios. To avoid extreme scenarios, create sufficient disk space in the first place.

    +

    Select a proper policy as required for data and service reliability. Both policies are only used for handling extreme scenarios. To avoid extreme scenarios, create sufficient disk space in the first place.

    diff --git a/docs/dms/umn/kafka-faq-200426009.html b/docs/dms/umn/kafka-faq-200426009.html index 554d0f67e..b43d3f4ad 100644 --- a/docs/dms/umn/kafka-faq-200426009.html +++ b/docs/dms/umn/kafka-faq-200426009.html @@ -2,7 +2,7 @@

    What Is the ZooKeeper Address of a Kafka Instance?

    Kafka instances are managed using ZooKeeper. Opening ZooKeeper may cause misoperations and service losses. ZooKeeper is used only within Kafka clusters and does not provide services externally.

    -

    You can use open-source Kafka clients to connect to Kafka instances and call the native APIs to create and retrieve messages.

    +

    You can use open-source Kafka clients to connect to Kafka instances and call the native APIs to produce and consume messages.

    diff --git a/docs/dms/umn/kafka-faq-200426014.html b/docs/dms/umn/kafka-faq-200426014.html index 06e6a9d1a..a2159fa3b 100644 --- a/docs/dms/umn/kafka-faq-200426014.html +++ b/docs/dms/umn/kafka-faq-200426014.html @@ -1,7 +1,7 @@

    How Do I Change the SASL_SSL Setting of a Kafka Instance?

    -
    +
    diff --git a/docs/dms/umn/kafka-faq-200426016.html b/docs/dms/umn/kafka-faq-200426016.html index 1c767e461..e4b980652 100644 --- a/docs/dms/umn/kafka-faq-200426016.html +++ b/docs/dms/umn/kafka-faq-200426016.html @@ -1,9 +1,9 @@

    How Many Connection Addresses Does a Kafka Instance Have by Default?

    -

    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 to each flavor.

    +

    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 to each flavor.

    -
    Table 1 Impact of specification modification

    Modified Object

    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 2,000 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

    @@ -24,7 +24,7 @@
    • 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)));
      -
    +
  • It takes 5 to 10 minutes to modify specifications on one broker. The more brokers, the longer time the modification takes.
    		•

    9092

    0.0.0.0/0

    +

    IP address or IP address group of the Kafka client

    Accessing a Kafka instance over a private network within a VPC (in plaintext)

    9192

    ::/0

    +

    IP address or IP address group of the Kafka client

    Accessing a Kafka instance within a VPC (with SSL encryption disabled)

    9093

    0.0.0.0/0

    +

    IP address or IP address group of the Kafka client

    Accessing a Kafka instance over a private network within a VPC (in ciphertext)

    9193

    ::/0

    +

    IP address or IP address group of the Kafka client

    Accessing a Kafka instance within a VPC (with SSL encryption enabled)

    9011

    0.0.0.0/0

    +

    IP address or IP address group of the Kafka client

    Accessing a Kafka instance using DNAT (in cipher- or plaintext)

    9092

    0.0.0.0/0

    +

    IP address or IP address group of the Kafka client

    Accessing a Kafka instance using a peering connection across VPCs (in plaintext)

    9093

    0.0.0.0/0

    +

    IP address or IP address group of the Kafka client

    Accessing a Kafka instance using a peering connection across VPCs (in ciphertext)

    9094

    0.0.0.0/0

    +

    IP address or IP address group of the Kafka client

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

    9095

    0.0.0.0/0

    +

    IP address or IP address group of the Kafka client

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

    9192

    ::/0

    +

    IP address or IP address group of the Kafka client

    Accessing a Kafka instance over a public network (without SSL)

    9193

    ::/0

    +

    IP address or IP address group of the Kafka client

    Accessing a Kafka instance over a public network (with SSL)
    Table 1 Kafka instance specifications (cluster)

    Flavor

    +
    @@ -15,7 +15,7 @@ - @@ -31,9 +31,9 @@ - - @@ -48,9 +48,9 @@ - - @@ -65,9 +65,9 @@ - - @@ -82,9 +82,9 @@ - - @@ -95,13 +95,13 @@ - - - @@ -112,13 +112,13 @@ - - - @@ -127,56 +127,56 @@
    Table 1 Cluster Kafka instance specifications

    Flavor

    Brokers

    Maximum Client Connections per Broker

    Storage Space

    +

    Storage Space (GB)

    Traffic per Broker (MB/s)

    15

    2000

    +

    2,000

    300 GB–300,000 GB

    +

    300–300,000

    40

    20

    2000

    +

    2,000

    300 GB–300,000 GB

    +

    300–300,000

    100

    100

    4000

    +

    4,000

    300 GB–600,000 GB

    +

    300–600,000

    200

    150

    4000

    +

    4,000

    300 GB–1,500,000 GB

    +

    300–1,500,000

    375

    200,000

    1500

    +

    1,500

    200

    4000

    +

    4,000

    300 GB–1,500,000 GB

    +

    300–1,500,000

    625

    250,000

    2000

    +

    2,000

    200

    4000

    +

    4,000

    300 GB–1,500,000 GB

    +

    300–1,500,000

    750

    -
    Table 2 Kafka instance specifications (single-node)

    Flavor

    +
    - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/dms/umn/kafka-faq-200426024.html b/docs/dms/umn/kafka-faq-200426024.html index 2e7ae79e4..0f3611b52 100644 --- a/docs/dms/umn/kafka-faq-200426024.html +++ b/docs/dms/umn/kafka-faq-200426024.html @@ -4,7 +4,7 @@

    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 partitions of topics. When this limit is reached, no more topics can be created.

    The partition limit varies depending on the flavor, as shown in the following table.

    -
    Table 2 Single-node Kafka instance specifications

    Flavor

    Brokers

    +

    Brokers

    TPS per Broker

    +

    Max. TPS per Broker

    Maximum Partitions per Broker

    +

    Max. Partitions per Broker

    Recommended Consumer Groups per Broker

    +

    Recommended Consumer Groups per Broker

    Maximum Client Connections per Broker

    +

    Max. Client Connections per Broker

    Storage Space

    +

    Storage Space (GB)

    Traffic per Broker (MB/s)

    +

    Traffic Limit per Broker (MB/s)

    kafka.2u4g.single.small

    +

    kafka.2u4g.single.small

    1

    +

    1

    20,000

    +

    20,000

    100

    +

    100

    15

    +

    15

    2000

    +

    2,000

    100 GB–10,000 GB

    +

    100–10,000

    40

    +

    40

    kafka.2u4g.single

    +

    kafka.2u4g.single

    1

    +

    1

    30,000

    +

    30,000

    250

    +

    250

    20

    +

    20

    2000

    +

    2,000

    100 GB–10,000 GB

    +

    100–10,000

    100

    +

    100
    Table 1 Kafka instance specifications (cluster)

    Flavor

    +
    @@ -16,7 +16,7 @@ - @@ -32,9 +32,9 @@ - - @@ -49,9 +49,9 @@ - - @@ -66,9 +66,9 @@ - - @@ -83,9 +83,9 @@ - - @@ -96,13 +96,13 @@ - - - @@ -113,13 +113,13 @@ - - - @@ -128,56 +128,56 @@
    Table 1 Cluster Kafka instance specifications

    Flavor

    Brokers

    Maximum Client Connections per Broker

    Storage Space

    +

    Storage Space (GB)

    Traffic per Broker (MB/s)

    15

    2000

    +

    2,000

    300 GB–300,000 GB

    +

    300–300,000

    40

    20

    2000

    +

    2,000

    300 GB–300,000 GB

    +

    300–300,000

    100

    100

    4000

    +

    4,000

    300 GB–600,000 GB

    +

    300–600,000

    200

    150

    4000

    +

    4,000

    300 GB–1,500,000 GB

    +

    300–1,500,000

    375

    200,000

    1500

    +

    1,500

    200

    4000

    +

    4,000

    300 GB–1,500,000 GB

    +

    300–1,500,000

    625

    250,000

    2000

    +

    2,000

    200

    4000

    +

    4,000

    300 GB–1,500,000 GB

    +

    300–1,500,000

    750

    -
    Table 2 Kafka instance specifications (single-node)

    Flavor

    +
    - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/dms/umn/kafka-faq-200426025.html b/docs/dms/umn/kafka-faq-200426025.html index c687f6cce..4b32d6bc8 100644 --- a/docs/dms/umn/kafka-faq-200426025.html +++ b/docs/dms/umn/kafka-faq-200426025.html @@ -4,7 +4,7 @@

    Kafka manages messages by partition. If there are too many partitions, message creation, storage, and retrieval will be fragmented, affecting the performance and stability. If the total number of partitions of topics reaches the upper limit, you cannot create more topics.

    The partition limit varies depending on the flavor, as shown in the following table.

    -
    Table 2 Single-node Kafka instance specifications

    Flavor

    Brokers

    +

    Brokers

    TPS per Broker

    +

    Max. TPS per Broker

    Maximum Partitions per Broker

    +

    Max. Partitions per Broker

    Recommended Consumer Groups per Broker

    +

    Recommended Consumer Groups per Broker

    Maximum Client Connections per Broker

    +

    Max. Client Connections per Broker

    Storage Space

    +

    Storage Space (GB)

    Traffic per Broker (MB/s)

    +

    Traffic Limit per Broker (MB/s)

    kafka.2u4g.single.small

    +

    kafka.2u4g.single.small

    1

    +

    1

    20,000

    +

    20,000

    100

    +

    100

    15

    +

    15

    2000

    +

    2,000

    100 GB–10,000 GB

    +

    100–10,000

    40

    +

    40

    kafka.2u4g.single

    +

    kafka.2u4g.single

    1

    +

    1

    30,000

    +

    30,000

    250

    +

    250

    20

    +

    20

    2000

    +

    2,000

    100 GB–10,000 GB

    +

    100–10,000

    100

    +

    100
    Table 1 Kafka instance specifications (cluster)

    Flavor

    +
    @@ -16,7 +16,7 @@ - @@ -32,9 +32,9 @@ - - @@ -49,9 +49,9 @@ - - @@ -66,9 +66,9 @@ - - @@ -83,9 +83,9 @@ - - @@ -96,13 +96,13 @@ - - - @@ -113,13 +113,13 @@ - - - @@ -128,56 +128,56 @@
    Table 1 Cluster Kafka instance specifications

    Flavor

    Brokers

    Maximum Client Connections per Broker

    Storage Space

    +

    Storage Space (GB)

    Traffic per Broker (MB/s)

    15

    2000

    +

    2,000

    300 GB–300,000 GB

    +

    300–300,000

    40

    20

    2000

    +

    2,000

    300 GB–300,000 GB

    +

    300–300,000

    100

    100

    4000

    +

    4,000

    300 GB–600,000 GB

    +

    300–600,000

    200

    150

    4000

    +

    4,000

    300 GB–1,500,000 GB

    +

    300–1,500,000

    375

    200,000

    1500

    +

    1,500

    200

    4000

    +

    4,000

    300 GB–1,500,000 GB

    +

    300–1,500,000

    625

    250,000

    2000

    +

    2,000

    200

    4000

    +

    4,000

    300 GB–1,500,000 GB

    +

    300–1,500,000

    750

    -
    Table 2 Kafka instance specifications (single-node)

    Flavor

    +
    - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/dms/umn/kafka-faq-200426026.html b/docs/dms/umn/kafka-faq-200426026.html index 8530897ed..f81404dc7 100644 --- a/docs/dms/umn/kafka-faq-200426026.html +++ b/docs/dms/umn/kafka-faq-200426026.html @@ -1,7 +1,7 @@

    Why Do I Fail to Create Topics?

    -

    Possible cause: The aggregate number of partitions of created topics has reached the upper limit. The maximum number of partitions varies by instance specifications. For details, see Specifications.

    +

    Possible cause: The aggregate number of partitions of created topics has reached the upper limit. The limit varies with instance specifications. For details, see Single-node Kafka Instances and Cluster Kafka Instances.

    Solution: Scale up the instance or delete unnecessary topics.

    diff --git a/docs/dms/umn/kafka-faq-200426028.html b/docs/dms/umn/kafka-faq-200426028.html deleted file mode 100644 index aab07dfa9..000000000 --- a/docs/dms/umn/kafka-faq-200426028.html +++ /dev/null @@ -1,12 +0,0 @@ - - -

    Why Do Deleted Topics Still Exist?

    -

    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 will be automatically created.

    -

    Solution: Disable automatic topic creation.

    -
    -
    -
    -
    Parent topic: Topics and Partitions
    -
    -
    - diff --git a/docs/dms/umn/kafka-faq-200426030.html b/docs/dms/umn/kafka-faq-200426030.html index de04616e0..65eb4f50f 100644 --- a/docs/dms/umn/kafka-faq-200426030.html +++ b/docs/dms/umn/kafka-faq-200426030.html @@ -2,7 +2,7 @@

    Can I View the Disk Space Used by a Topic?

    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 Eye console. On the By Topic tab page, set Topic to the name of the desired topic, and Monitoring Type to Basic monitoring. The Message Size metric reflects the message size of the selected topic.
    • Click the desired Kafka instance to view its details. Choose Monitoring in the navigation pane. On the By Topic tab page, set Topic to the name of the topic whose disk space you want to view and Monitoring Type to Basic monitoring. The Message Size metric reflects the message size of the selected topic.
    +
    • In the row containing the desired Kafka instance, click View Metric to go to the Cloud Eye console. On the By Topic tab page, set Topic to the name of the desired topic, and Monitoring Type to Basic monitoring. The Message Size metric reflects the message size of the selected topic.
    • Click the desired Kafka instance to go to the instance details page. In the navigation pane, choose Monitoring. On the By Topic tab page, set Topic to the name of the topic whose disk space you want to view and Monitoring Type to Basic monitoring. The Message Size metric reflects the message size of the selected topic.
    diff --git a/docs/dms/umn/kafka-faq-200426032.html b/docs/dms/umn/kafka-faq-200426032.html index a3da359c3..9204594c0 100644 --- a/docs/dms/umn/kafka-faq-200426032.html +++ b/docs/dms/umn/kafka-faq-200426032.html @@ -1,7 +1,7 @@

    Can I Add ACL Permissions for Topics?

    -

    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 Permission in the row that contains the topic for which you want to configure user permissions.

    +

    If you have enabled SASL_SSL for your Kafka instance, you can configure ACL permissions for your topics. On the Topics page of the Kafka console, click Grant User Permission in the row that contains the topic for which you want to configure user permissions.

    For details, see Configuring Kafka Topic Permissions.

    diff --git a/docs/dms/umn/kafka-faq-200426036.html b/docs/dms/umn/kafka-faq-200426036.html index a0bc91e48..f17627499 100644 --- a/docs/dms/umn/kafka-faq-200426036.html +++ b/docs/dms/umn/kafka-faq-200426036.html @@ -2,19 +2,19 @@

    Why Does Message Poll Often Fail During Rebalancing?

    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 removed from a consumer group. However, if a consumer is regarded as abnormal and removed from the consumer group, message retrieval may fail.

    +

    In normal cases, rebalancing occurs inevitably when a consumer is added to or removed from a consumer group. However, if a consumer is regarded as abnormal by the server and removed from the consumer group, message consumption may fail.

    This may happen in the following scenarios:

    1. Heartbeat requests are not sent in time.

      A consumer sends heartbeat requests to the broker at the interval specified by heartbeat.interval.ms. If the broker does not receive any heartbeat request from the consumer within the period specified by session.timeout.ms, the broker considers that the consumer is abnormal and removes the consumer from the consumer group, triggering rebalancing.

      -
    2. The interval between retrievals is too long.

      The maximum number of messages that a consumer can retrieve at a time is specified by max.poll.records. In most cases, a client processes the retrieved data before starting the next retrieval. The processing may be prolonged when a large number of messages are retrieved at a time and cannot be processed within the time specified by max.poll.interval.ms, or when an exception occurs during the process (for example, data needs to be written to the backend database, but the backend database pressure is too high, resulting in high latency). If the consumer does not send the next retrieval request within the time specified by max.poll.interval.ms, the broker considers that the consumer is inactive and removes it from the consumer group, triggering rebalancing.

      +
    3. The interval between retrievals is too long.

      The maximum number of messages that a consumer can consume at a time is specified by max.poll.records. In most cases, a client processes the consumed data before starting the next consumption. The processing may be prolonged when a large number of messages are consumed at a time and cannot be processed within the time specified by max.poll.interval.ms, or when an exception occurs during the process (for example, data needs to be written to the backend database, but the backend database pressure is too high, resulting in slow SQL and high latency). If the consumer does not send the next consumption request within the time specified by max.poll.interval.ms, the broker considers that the consumer is inactive and removes it from the consumer group, triggering rebalancing.

    Solutions and Troubleshooting Methods

    Scenario 1: Heartbeat requests are not sent in time.

    -

    Solution: On the consumer client, set the value of session.timeout.ms to three times the value of heartbeat.interval.ms.

    +

    Locating: If the client is in Java, check GC logs to see whether FullGC takes a long time. If yes, the heartbeat thread may be blocked. As a result, the server fails to check heartbeats and starts rebalancing.

    +

    Solution: Check for client issues. FullGC indicates that memory leakage may have occurred on the client.

    Scenario 2: The interval between retrievals is too long.

    Troubleshooting methods:

    -
    1. Check the time required for processing a single message and whether the time required for processing a specified number (max.poll.records) of messages exceeds the time specified by max.poll.interval.ms.
    2. Check whether message processing requires network connections, such as writing data to the database and calling backend APIs, and whether the backend is normal in rebalancing scenarios.
    -

    Solution: On the consumer client, decrease the value of max.poll.records.

    +
    1. Check the time required for processing a single message and whether the time required for processing a specified number (max.poll.records) of messages exceeds the time specified by max.poll.interval.ms.
    2. Check whether message processing requires network connections, such as writing data to the database and calling backend APIs, and whether the downstream consumer system is normal in rebalancing scenarios.
    +

    Solution: On the consumer client, decrease the value of max.poll.records. If message processing takes longer, increase the value of max.poll.interval.ms.

    -

    diff --git a/docs/dms/umn/kafka-faq-200426100.html b/docs/dms/umn/kafka-faq-200426100.html index 9050c2b73..ad93d2159 100644 --- a/docs/dms/umn/kafka-faq-200426100.html +++ b/docs/dms/umn/kafka-faq-200426100.html @@ -3,7 +3,7 @@

    What Can I Do If Kafka Messages Are Accumulated?

    Symptom: An alarm is generated for the Accumulated Messages metric.

    Solution:

    -
    1. Log in to the Kafka console and click the instance for which the alarm is generated. The instance details page is displayed.
    2. Choose Monitoring in the navigation pane.
    3. On the By Consumer Group tab page, view Consumer Available Messages to find the consumer group with accumulated messages.
    4. In the navigation pane, choose Consumer Groups.
    5. Check whether there are consumers in the consumer group where messages are accumulated. If yes, contact the service party to accelerate their consumption. If no, contact the customer to delete unused consumer groups.
    +
    1. Log in to the Kafka console and click the instance for which the alarm is generated. The instance details page is displayed.
    2. In the navigation pane, choose Monitoring.
    3. On the By Consumer Group tab page, view Consumer Available Messages to find the consumer group with accumulated messages.
    4. In the navigation pane, choose Consumer Groups.
    5. Check whether there are consumers in the consumer group where messages are accumulated. If yes, contact the service party to accelerate their consumption. If no, contact the customer to delete unused consumer groups.
    diff --git a/docs/dms/umn/kafka-pd-0052.html b/docs/dms/umn/kafka-pd-0052.html index c895a08ee..ec13b5ce0 100644 --- a/docs/dms/umn/kafka-pd-0052.html +++ b/docs/dms/umn/kafka-pd-0052.html @@ -2,120 +2,104 @@

    Comparing Single-node and Cluster Kafka Instances

    A single-node Kafka instance has only one broker. These instances do not guarantee performance or reliability and are for trial use or testing only. In the production environment, use cluster instances.

    -

    Parameters for Creation

    Parameter settings that are unique to single-node instances are listed in Table 1.

    +

    Table 1 compares single-node and cluster instances by features and functions.

    -
    Table 2 Single-node Kafka instance specifications

    Flavor

    Brokers

    +

    Brokers

    TPS per Broker

    +

    Max. TPS per Broker

    Maximum Partitions per Broker

    +

    Max. Partitions per Broker

    Recommended Consumer Groups per Broker

    +

    Recommended Consumer Groups per Broker

    Maximum Client Connections per Broker

    +

    Max. Client Connections per Broker

    Storage Space

    +

    Storage Space (GB)

    Traffic per Broker (MB/s)

    +

    Traffic Limit per Broker (MB/s)

    kafka.2u4g.single.small

    +

    kafka.2u4g.single.small

    1

    +

    1

    20,000

    +

    20,000

    100

    +

    100

    15

    +

    15

    2000

    +

    2,000

    100 GB–10,000 GB

    +

    100–10,000

    40

    +

    40

    kafka.2u4g.single

    +

    kafka.2u4g.single

    1

    +

    1

    30,000

    +

    30,000

    250

    +

    250

    20

    +

    20

    2000

    +

    2,000

    100 GB–10,000 GB

    +

    100–10,000

    100

    +

    100
    Table 1 Parameters of a single-node instance

    Parameter

    +
    - + - - + - - + - - + - - + - - + - - + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Comparing single-node and cluster instances

    Item

    Description

    +

    Single-node

    +

    Cluster

    AZ

    +

    Version

    Only one AZ

    +

    2.7

    +

    1.1.0, 2.3.0, 2.7, and 3.x

    Version

    +

    AZ

    Only v2.7

    +

    Single

    +

    1, or 3 or more

    Broker Flavor

    +

    Brokers

    kafka.2u4g.single.small and kafka.2u4g.single

    +

    1

    +

    3 and more

    Brokers

    +

    Access mode

    Only one

    +

    Plaintext access

    +

    Plaintext and ciphertext access

    Storage space per broker

    +

    Modifying instance specifications

    Disk types: high I/O and ultra-high I/O; Disk size: 100–10,000 GB

    +

    ×

    +

    √

    Ciphertext Access

    +

    Resetting Kafka password

    Not supported

    +

    ×

    +

    √

    +

    Viewing disk usage

    +

    ×

    +

    √

    +

    Reassigning partitions

    +

    ×

    +

    √

    +

    Configuring topic permissions

    +

    ×

    +

    √

    +

    Managing users

    +

    ×

    +

    √

    +

    Smart Connect

    +

    ×

    +

    √

    +

    Modifying configuration parameters

    +

    ×

    +

    √
    -

    Comparing Instance Functions

    Table 2 compares the functions of single-node and cluster instances.

    - -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 2 Comparing functions

    Function

    -

    Single-node Instance

    -

    Cluster Instance

    -

    Modifying instance specifications

    -

    ×

    -

    √

    -

    Changing the instance access mode

    -

    Only enabling/disabling public plaintext access

    -

    Options:

    -
    • Enabling private ciphertext access
    • Enabling/Disabling private plaintext access
    • Enabling/Disabling public plaintext access
    • Enabling/Disabling public ciphertext access
    -

    Resetting Kafka password

    -

    ×

    -

    √

    -

    Viewing disk usage

    -

    ×

    -

    √

    -

    Reassigning partitions

    -

    ×

    -

    √

    -

    Configuring topic permissions

    -

    ×

    -

    √

    -

    Managing users

    -

    ×

    -

    √

    -

    Modifying configuration parameters

    -

    ×

    -

    √

    -
    -
    -
    -
    Parent topic: Service Overview
    diff --git a/docs/dms/umn/kafka-pd-0053.html b/docs/dms/umn/kafka-pd-0053.html new file mode 100644 index 000000000..30b640454 --- /dev/null +++ b/docs/dms/umn/kafka-pd-0053.html @@ -0,0 +1,18 @@ + + +

    Kafka Instance Specifications

    +

    +
    + + diff --git a/docs/dms/umn/kafka-pd-0056.html b/docs/dms/umn/kafka-pd-0056.html new file mode 100644 index 000000000..d135a3abf --- /dev/null +++ b/docs/dms/umn/kafka-pd-0056.html @@ -0,0 +1,79 @@ + + +

    Single-node Kafka Instances

    +

    Instance Specifications

    A single-node Kafka instance has one broker, is compatible with open-source Kafka 2.7, and is applicable to test scenarios. Do not use it for production services.

    +

    In the following table:

    +
    • For Kafka instances, the number of transactions per second (TPS) is the maximum number of messages that can be written per second.
    • TPS performance: number of messages processed per second assuming that the size of a message is 1 KB.
    • Test scenario: private access in plaintext. The disk type is ultra-high I/O.
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Single-node Kafka instance specifications

    Flavor

    +

    Brokers

    +

    Max. TPS per Broker

    +

    Max. Partitions per Broker

    +

    Recommended Consumer Groups per Broker

    +

    Max. Client Connections per Broker

    +

    Storage Space (GB)

    +

    Traffic Limit per Broker (MB/s)

    +

    kafka.2u4g.single.small

    +

    1

    +

    20,000

    +

    100

    +

    15

    +

    2,000

    +

    100–10,000

    +

    40

    +

    kafka.2u4g.single

    +

    1

    +

    30,000

    +

    250

    +

    20

    +

    2,000

    +

    100–10,000

    +

    100

    +
    +
    +
    +

    Storage Space Estimation

    Kafka instances can store messages in multiple replicas. The storage space is consumed by message replicas, logs, and metadata. When creating an instance, specify its storage space based on the expected service message size, the number of replicas, and reserved disk space. Each Kafka broker reserves 33 GB disk space for storing logs and metadata.

    +

    For example, if the expected service message size is 100 GB, the number of replicas is 2, and the number of brokers is 1, the disk size should be at least 233 GB (100 GB × 2 + 33 GB × 1).

    +
    +

    Topic Quantity Calculation

    There are limits on the topic quantity and the aggregate number of partitions in the topics. When the partition quantity limit is reached, you can no longer create topics.

    +

    The number of topics is related to the maximum number of partitions allowed and the specified number of partitions in each topic (see Table 1).

    +

    The maximum number of partitions allowed for an instance with kafka.2u4g.single is 250.

    +
    • If the number of partitions of each topic in the instance is 2, the maximum number of topics is 250/2 = 125.
    • If the number of partitions of each topic in the instance is 1, the maximum number of topics is 250/1 = 250.
    +
    +
    +
    +
    +
    Parent topic: Kafka Instance Specifications
    +
    +
    + diff --git a/docs/dms/umn/kafka-pd-190605001.html b/docs/dms/umn/kafka-pd-190605001.html index c856a0e97..aaef23cee 100644 --- a/docs/dms/umn/kafka-pd-190605001.html +++ b/docs/dms/umn/kafka-pd-190605001.html @@ -4,7 +4,7 @@

    Apache Kafka is distributed message middleware that features high throughput, data persistence, horizontal scalability, and stream data processing. It adopts the publish-subscribe pattern and is widely used for log collection, data streaming, online/offline system analytics, and real-time monitoring.

    DMS is a message queuing service based on Apache Kafka. It provides Kafka instances with isolated compute, storage, and bandwidth resources. DMS allows you to apply and configure resources based on service requirements. It can be used out of the box and frees you from deployment and O&M so that you can focus on the agile development of your applications.

    -

    Readers' Guide

    This documentation introduces DMS for Kafka and its differences from Apache Kafka. You will learn about the detailed information about the specifications, console operations, and client access to instances of DMS for Kafka.

    +

    Readers' Guide

    This documentation introduces DMS for Kafka and its differences from Apache Kafka. You will learn about the detailed information about the specifications, console operations, and client access to instances of DMS for Kafka.

    For more information about the basic knowledge of Kafka or technical details about creating and retrieving messages, please go to the official Apache Kafka website.

    diff --git a/docs/dms/umn/kafka-pd-190605002.html b/docs/dms/umn/kafka-pd-190605002.html index d31c925b2..545984929 100644 --- a/docs/dms/umn/kafka-pd-190605002.html +++ b/docs/dms/umn/kafka-pd-190605002.html @@ -15,6 +15,8 @@
  • Tag Management Service (TMS)

    TMS is a visualized service for fast and unified cross-region tagging and categorization of cloud services.

    Tags facilitate Kafka instance identification and management.

  • Key Management Service (KMS)

    When creating a Kafka instance, you can specify whether to enable disk encryption. Enabling disk encryption improves data security. Disk encryption depends on the keys provided by KMS.

    +
  • VPC Endpoint

    A client can access a Kafka instance over a private network: When a client and a Kafka instance are deployed across VPCs in one region, connect the client and the Kafka instance across VPCs using a VPC endpoint.

    +
  • NAT Gateway

    A Kafka instance can communicate with a client over a public network: Configure port mapping from EIPs to specified instance ports using destination NAT (DNAT) of NAT Gateway.

    • diff --git a/docs/dms/umn/kafka-pd-190605003.html b/docs/dms/umn/kafka-pd-190605003.html index c36145930..aa7ae9c80 100644 --- a/docs/dms/umn/kafka-pd-190605003.html +++ b/docs/dms/umn/kafka-pd-190605003.html @@ -1,57 +1,59 @@

    Notes and Constraints

    -

    This section describes the notes and constraints on DMS.

    +

    This section describes the notes and constraints on Distributed Message Service (DMS). Use your Kafka instances as prescribed to avoid program exceptions.

    +

    Any instability caused by ignorance of the notes and constraints is not covered by the SLA.

    +

    Instance

    -
    Table 1 Instance notes and constraints

    Item

    +
    - - - - - - - - - - - - - - - - - - - @@ -59,71 +61,71 @@

    Topic

    -
    Table 1 Instance notes and constraints

    Item

    Notes and Constraints

    +

    Notes and Constraints

    Kafka ZooKeeper

    +

    Kafka ZooKeeper

    Kafka clusters are managed using ZooKeeper. Opening ZooKeeper may cause misoperations and service losses. Currently, ZooKeeper is used only within Kafka clusters and does not provide services externally.

    +

    Kafka clusters are managed using ZooKeeper. Opening ZooKeeper may cause misoperations and service losses. Currently, ZooKeeper is used only within Kafka clusters and does not provide services externally.

    Version

    +

    Version

    • The service version can be 2.3.0, 2.7, or 3.x. Kafka instances cannot be upgraded once they are created.
    • Clients later than version 0.10 are supported. Use a version that is consistent with the service version.
    +
    • The service version can be 2.3.0, 2.7, or 3.x. Kafka instances cannot be upgraded once they are created.
    • Clients later than version 0.10 are supported. Use a version that is consistent with the service version.

    Logging in to the VM where the Kafka brokers reside

    +

    Logging in to the VM where the Kafka brokers reside

    Not supported

    +

    Not supported

    Storage

    +

    Storage

    • The storage space can be expanded but cannot be reduced.
    • You can expand the storage space up to 20 times.
    +
    • The storage space of cluster instances can be expanded but cannot be reduced.
    • You can expand the storage space up to 20 times.
    • The storage space of single-node instances cannot be changed.

    Broker quantity

    +

    Brokers

    The broker quantity can be increased but cannot be decreased.

    +

    The broker quantity of cluster instances can be increased but cannot be decreased. The broker quantity of single-node instances cannot be changed.

    Broker flavor

    +

    Broker flavor

    • The broker flavor can be increased but cannot be decreased.
    • Single-replica topics do not support message production during this period. Services will be interrupted.
    • If a topic has multiple replicas, scaling up 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.
    +
    • The broker flavor of cluster instances can be increased but cannot be decreased.
    • Single-replica topics do not support message production during this period. Services will be interrupted.
    • If a topic has multiple replicas, scaling up 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.
    • The broker flavor of single-node instances cannot be changed.

    VPC, subnet, and AZ

    +

    VPC, subnet, and AZ

    After an instance is created, its VPC, subnet, and AZ cannot be modified.

    +

    After an instance is created, its VPC, subnet, and AZ cannot be modified.

    Kerberos authentication

    +

    Kerberos authentication

    Not supported

    +

    Not supported

    Client connections from each IP address

    +

    Client connections from each IP address

    Each Kafka broker allows a maximum of 1000 connections from each IP address by default. Excess connections will be rejected.

    +

    Each Kafka broker allows a maximum of 1000 connections from each IP address by default. Excess connections will be rejected.
    Table 2 Topic notes and constraints

    Item

    +
    - - - - - - - - - - - - - - - - - - - - - - - @@ -131,30 +133,30 @@

    Consumer Group

    -
    Table 2 Topic notes and constraints

    Item

    Notes and Constraints

    +

    Notes and Constraints

    Total number of topic partitions

    +

    Total number of topic partitions

    The total number of topic partitions is related to the instance specifications. For details, see Specifications.

    +

    The total number of topic partitions is related to the instance specifications. For details, see Cluster Kafka Instances.

    Kafka manages messages by partition. If there are too many partitions, message creation, storage, and retrieval will be fragmented, affecting the performance and stability. If the total number of partitions of topics reaches the upper limit, you cannot create more topics.

    Number of partitions in a topic

    +

    Number of partitions in a topic

    • Based on the open-source Kafka constraints, the number of partitions in a topic can be increased but cannot be decreased.
    • To ensure performance, a partition number within 200 is recommended for each topic.
    +
    • Based on the open-source Kafka constraints, the number of partitions in a topic can be increased but cannot be decreased.
    • To ensure performance, a partition number within 200 is recommended for each topic.

    Topic quantity

    +

    Topic quantity

    The topic quantity is related to the total number of topic partitions and number of partitions in each topic. For details, see Specifications.

    +

    The topic quantity is related to the total number of topic partitions and number of partitions in each topic. For details, see Cluster Kafka Instances.

    Automatic topic creation

    +

    Automatic topic creation

    Supported. 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 the following parameters:

    -
    • Partitions: 3
    • Replicas: 3
    • Aging Time: 72
    • Synchronous Replication and Synchronous Flushing disabled
    • Message Timestamp: CreateTime
    • Max.Message Size (bytes): 10,485,760
    -

    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.

    +

    Supported. 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 the following parameters:

    +
    • Partitions: 1 for single-node instances and 3 for cluster instances
    • Replicas: 1 for single-node instances and 3 for cluster instances
    • Aging Time: 72
    • Synchronous Replication and Synchronous Flushing disabled
    • Message Timestamp: CreateTime
    • Max. Message Size (bytes): 10,485,760
    +

    For cluster instances, 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. These parameters cannot be changed for single-node instances.

    For example, assume that num.partitions is changed to 5, an automatically created topic has the following parameters:

    -
    • Partitions: 5
    • Replicas: 3
    • Aging Time: 72
    • Synchronous Replication and Synchronous Flushing disabled
    • Message Timestamp: CreateTime
    • Max.Message Size (bytes): 10,485,760
    +
    • Partitions: 5
    • Replicas: 3
    • Aging Time: 72
    • Synchronous Replication and Synchronous Flushing disabled
    • Message Timestamp: CreateTime
    • Max. Message Size (bytes): 10,485,760

    Synchronous replication

    +

    Synchronous replication

    If a topic has only one replica, synchronous replication cannot be enabled.

    +

    If a topic has only one replica, synchronous replication cannot be enabled.

    Replica quantity

    +

    Replica quantity

    Single-replica topics are not recommended. 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 to use a topic with only one replica.

    +

    Single-replica topics are not recommended for cluster instances. 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 to use a topic with only one replica.

    Aging time

    +

    Aging time

    The value of the log.retention.hours parameter takes effect only if the aging time has not been set for the topic.

    -

    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.

    +

    The log.retention.hours parameter takes effect only when the aging time has not been set for the topic.

    +

    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.

    Batch importing and exporting topics

    +

    Batch importing and exporting topics

    Batch export is supported, but batch import is not supported.

    +

    Batch export is supported, but batch import is not supported.

    Topic name

    +

    Topic name

    If a topic name starts with a special character, for example, an underscore (_) or a number sign (#), monitoring data cannot be displayed.

    +

    If a topic name starts with a special character, for example, an underscore (_) or a number sign (#), monitoring data cannot be displayed.

    Delay queues

    +

    Delay queues

    Not supported

    +

    Not supported

    Broker faults

    +

    Broker faults

    When some brokers of an instance are faulty, topics cannot be created, modified, or deleted, but can be queried.

    +

    When some brokers of an instance are faulty, topics cannot be created, modified, or deleted, but can be queried.
    Table 3 Consumer group notes and constraints

    Item

    +
    - - - - - - - - - @@ -162,15 +164,15 @@

    Message

    -
    Table 3 Consumer group notes and constraints

    Item

    Notes and Constraints

    +

    Notes and Constraints

    Creating consumer groups, consumers, and producers

    +

    Creating consumer groups, consumers, and producers

    Consumer groups, consumers, and producers are generated automatically when you use the instance.

    +
    • 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 you use the instance.
    • When parameter auto.create.groups.enable is set to false, you need to create a consumer group, but do not need to create a producer or consumer.

    Resetting the consumer offset

    +

    Resetting the consumer offset

    Messages may be retrieved more than once after the offset is reset.

    +

    Messages may be retrieved more than once after the offset is reset.

    Consumer group name

    +

    Consumer group name

    If a consumer group name starts with a special character, for example, an underscore (_) or a number sign (#), monitoring data cannot be displayed.

    +

    If a consumer group name starts with a special character, for example, an underscore (_) or a number sign (#), monitoring data cannot be displayed.

    Broker faults

    +

    Broker faults

    When some instance brokers are faulty, consumer groups cannot be created or deleted, or consumption progress cannot be reset, but consumer groups can be queried.

    +

    When some instance brokers are faulty, consumer groups cannot be created or deleted, or consumption progress cannot be reset, but consumer groups can be queried.
    Table 4 Message notes and constraints

    Item

    +
    - - - @@ -178,20 +180,20 @@

    User

    -
    Table 4 Message notes and constraints

    Item

    Notes and Constraints

    +

    Notes and Constraints

    Message size

    +

    Message size

    The maximum length of a message is 10 MB. If the length exceeds 10 MB, the production fails.

    +

    The maximum length of a message is 10 MB. If the length exceeds 10 MB, the production fails.
    Table 5 User notes and constraints

    Item

    +
    - - - - - diff --git a/docs/dms/umn/kafka-pd-200720001.html b/docs/dms/umn/kafka-pd-200720001.html index 145a9b9e2..02fd0534e 100644 --- a/docs/dms/umn/kafka-pd-200720001.html +++ b/docs/dms/umn/kafka-pd-200720001.html @@ -57,7 +57,7 @@ - diff --git a/docs/dms/umn/kafka-qs-0409001.html b/docs/dms/umn/kafka-qs-0409001.html index f64c7c4ff..1998dcc1f 100644 --- a/docs/dms/umn/kafka-qs-0409001.html +++ b/docs/dms/umn/kafka-qs-0409001.html @@ -11,33 +11,33 @@

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

  • 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. 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.

      +

      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 an IAM 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.

        -
        +

        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.

        +

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

        To connect to Kafka instances, add the security group rules described in Table 1. Other rules can be added based on site requirements. -
    Table 5 User notes and constraints

    Item

    Notes and Constraints

    +

    Notes and Constraints

    Number of users

    +

    Number of users

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

    +

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

    Broker faults

    +

    Broker faults

    When some instance brokers are faulty, users cannot be created or deleted, or password cannot be reset, but users can be queried.

    +

    When some instance brokers are faulty, users cannot be created or deleted, or password cannot be reset, but users can be queried.

    Feature-rich

    While maintaining 100% open-source compatibility, DMS further optimizes open-source code to improve performance and reliability, and provides message querying, and many other features.

    +

    While maintaining 100% open-source compatibility, DMS further optimizes open-source code to improve performance and reliability, and provides message querying, migration, and many other features.

    Functionality is limited and requires self-development.
    @@ -286,11 +280,11 @@ password="**********"; sasl.mechanism=PLAIN security.protocol=SASL_SSL -ssl.truststore.location={ssl_truststore_path} +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 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.
    +
    • 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.

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

    cd ../bin

  • Produce messages.

    ./kafka-console-producer.sh --broker-list ${connection address} --topic ${topic name} --producer.config ../config/producer.properties
    diff --git a/docs/dms/umn/kafka-scenarios.html b/docs/dms/umn/kafka-scenarios.html index 68cccf92f..38a465650 100644 --- a/docs/dms/umn/kafka-scenarios.html +++ b/docs/dms/umn/kafka-scenarios.html @@ -2,6 +2,7 @@

    Application Scenarios

    Kafka is popular message-oriented middleware that features highly reliable, asynchronous message delivery. It is widely used for transmitting data between different systems in many industries, including enterprise application, payment, telecommunications, e-commerce, social networking, instant messaging, video, Internet of Things, and Internet of Vehicle.

    +

    For synchronization links that require real-time results, Remote Procedure Call (RPC) is recommended.

    Asynchronous Communication

    Non-core or less important messages are sent asynchronously to receiving systems, so that the main service process is not kept waiting for the results of other systems, allowing for faster responses.

    For example, Kafka can be used to send a notification email and SMS message after a user has registered with a website, providing fast responses throughout the registration process.

    Figure 1 Serial registration and notification
    diff --git a/docs/dms/umn/kafka-trouble-0001.html b/docs/dms/umn/kafka-trouble-0001.html index 229417eaf..23c470755 100644 --- a/docs/dms/umn/kafka-trouble-0001.html +++ b/docs/dms/umn/kafka-trouble-0001.html @@ -5,7 +5,7 @@

    Root Cause

    The disk usage of the broker is too high.

    -

    Solution

    Expand the disk space by referring to Modifying Instance Specifications.

    +

    Solution

    Expand the disk space by referring to Modifying Cluster Kafka Instance Specifications.

    diff --git a/docs/dms/umn/kafka-ug-00001.html b/docs/dms/umn/kafka-ug-00001.html index 0c02ef001..5e16a9a50 100644 --- a/docs/dms/umn/kafka-ug-00001.html +++ b/docs/dms/umn/kafka-ug-00001.html @@ -8,12 +8,18 @@
    • - + + +
    Table 1 Security group rules

    Direction

    +
    - - - - - - - - - @@ -47,13 +47,13 @@

  • 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. 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=/root/jdk1.8.0_321 
-export PATH=$JAVA_HOME/bin:$PATH
          +
        5. Press i and add the following content.
          export JAVA_HOME=/root/jdk1.8.0_321 
+export PATH=$JAVA_HOME/bin:$PATH

          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
          @@ -61,7 +61,7 @@ export PATH=$JAVA_HOME/bin:$PATH
          If the following message is returned, the JDK is installed.
          java version "1.8.0_321"
        -
      4. Download an open-source Kafka client.
        wget https://archive.apache.org/dist/kafka/2.7.2/kafka_2.12-2.7.2.tgz
        +
      5. Download an open-source Kafka client.
        wget https://archive.apache.org/dist/kafka/2.7.2/kafka_2.12-2.7.2.tgz
      6. Run the following command to decompress the package:
        tar -zxf kafka_2.12-2.7.2.tgz
    @@ -77,7 +77,7 @@ export PATH=$JAVA_HOME/bin:$PATH
    • - - - @@ -209,7 +203,7 @@ export PATH=$JAVA_HOME/bin:$PATH
    Table 1 Security group rules

    Direction

    Protocol

    +

    Protocol

    Port

    +

    Port

    Source address

    +

    Source address

    Description

    +

    Description

    Inbound

    +

    Inbound

    TCP

    +

    TCP

    9093

    +

    9093

    0.0.0.0/0

    +

    0.0.0.0/0

    Accessing a Kafka instance over a private network within a VPC (in ciphertext)

    +

    Accessing a Kafka instance over a private network within a VPC (in ciphertext)

    Region

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

    -

    +

    Select eu-de.

    Project

    @@ -115,12 +115,6 @@ export PATH=$JAVA_HOME/bin:$PATH

    Select 2.7.

    CPU Architecture

    -

    x86

    -

    Retain the default value.

    -

    Broker Flavor

    Select a broker flavor as required.

    @@ -195,7 +189,7 @@ export PATH=$JAVA_HOME/bin:$PATH

    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. 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.
      +
      • 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.
    -

  • 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.

    +

  • Skip Advanced Settings.
  • Click Create.
  • Confirm the instance information and then submit the request.
  • Return to the Kafka Instances 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 Failed state, delete it and try creating another one. If the instance creation fails again, contact customer service.

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

    @@ -227,7 +221,7 @@ export PATH=$JAVA_HOME/bin:$PATH

    • 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
    • __dms_dial_test

    Cannot be changed once the topic is created.

    Enter topic-01.

    2024-09-25

    +

    2025-07-01

    +

    Added:

    + +

    2024-09-25

    Added:

    Modified:

    - +

    2024-07-19

    @@ -25,9 +31,9 @@

    2024-06-14

    Added the following content:

    - +

    Modified the following content:

    - +

    2022-12-01

    @@ -68,7 +74,7 @@

    2019-11-30

    This release incorporates the following changes:

    -
    • Optimized description about Kafka premium instances in section What Is DMS?.
    • Added description about DMS functions in section "Functions".
    • Added description about the differences between Kafka queues and Kafka premium instances in section "Comparing Kafka Queues and Kafka Premium Instances".
    • Added description about the specifications of Kafka queues and Kafka premium instances in section Specifications.
    • Added explanation of the relationship between Kafka premium instances and VPCs in section Related Services.
    • Optimized description about DMS queues and added description about Kafka premium instances in section Basic Concepts.
    • Added recommendations on Kafka client configurations in Best Practices.
    • Removed the Region parameter in section "Creating a Queue".
    • Optimized description about queue policy parameters in section "Managing Queue Policies".
    • Optimized description about Kafka premium instance operations and parameters in chapter "Managing Kafka Premium Instances".
    • Optimized description about DMS metrics in section Kafka Metrics.
    • Added description about Kafka premium instance operations supported by CTS in section Viewing Kafka Audit Logs.
    +
    • Optimized description about Kafka premium instances in section What Is DMS?.
    • Added description about DMS functions in section "Functions".
    • Added description about the differences between Kafka queues and Kafka premium instances in section "Comparing Kafka Queues and Kafka Premium Instances".
    • Added description about the specifications of Kafka queues and Kafka premium instances in section Cluster Kafka Instances.
    • Added explanation of the relationship between Kafka premium instances and VPCs in section Related Services.
    • Optimized description about DMS queues and added description about Kafka premium instances in section Basic Concepts.
    • Added recommendations on Kafka client configurations in Best Practices.
    • Removed the Region parameter in section "Creating a Queue".
    • Optimized description about queue policy parameters in section "Managing Queue Policies".
    • Optimized description about Kafka premium instance operations and parameters in chapter "Managing Kafka Premium Instances".
    • Optimized description about DMS metrics in section Kafka Metrics.
    • Added description about Kafka premium instance operations supported by CTS in section Viewing Kafka Audit Logs.

    2019-11-08

    diff --git a/docs/dms/umn/kafka-ug-0001.html b/docs/dms/umn/kafka-ug-0001.html index 7a4be1bb4..1690657ba 100644 --- a/docs/dms/umn/kafka-ug-0001.html +++ b/docs/dms/umn/kafka-ug-0001.html @@ -11,30 +11,133 @@

    Options:

    • PLAINTEXT: There is no authentication required in such a connection and data is transmitted in plaintext.
    • SASL_SSL: Clients can connect to a Kafka instance with SASL and the data will be encrypted using the SSL certificate.
    • SASL_PLAINTEXT: Clients can connect to a Kafka instance with SASL and the data will be transmitted in plaintext.
    -

    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 2 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 3 Viewing the VPC to which the Kafka instance belongs
      +

      Creating a VPC Endpoint Service

      1. Log in to the console.
      2. Click in the upper left corner to select the region where your instance is located.
      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
      4. Click the desired instance to go to the instance details page.
      5. In the Advanced Settings area on the Basic Information 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
        +

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

        Figure 3 Viewing the VPC to which the Kafka instance belongs

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

        Figure 4 Obtaining the VPC ID
        -

      8. 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.
        +

      9. 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 request parameters by referring to Table 1, and other parameters as required.

        + +
        + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        Table 1 VPC Endpoint service creation parameters

        Parameter

        +

        Description

        +

        port_id

        +

        ID of the backend resource.

        +

        Enter a port ID obtained in 5.

        +

        vpc_id

        +

        ID of the VPC of the backend resource.

        +

        Enter a VPC ID obtained in 7.

        +

        server_type

        +

        Resource type.

        +

        Enter VM.

        +

        client_port

        +

        Access port.

        +

        Enter 9011.

        +

        server_port

        +

        Service port.

        +

        Enter 9011.

        +

        protocol

        +

        Port mapping protocol.

        +

        Enter TCP.

        +

        approval_enabled

        +

        Whether approval is required.

        +

        Entering false indicates that no approval is required and the connected VPC endpoint will be in the accepted state.

        +

        service_type

        +

        Service type.

        +

        Enter 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.

        +
        +

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

      10. 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

      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 5 Checking the VPC endpoint status
        +

        Creating a VPC Endpoint

        1. Click Service List. Then choose Network > VPC Endpoint.
        2. Click Create VPC Endpoint.
        3. Set parameters by referring to Table 2. Retain the default values for other parameters. For details, see Creating a VPC Endpoint.

          + +
          + + + + + + + + + + + + + + + + + + + + + + +
          Table 2 VPC endpoint creation parameters

          Parameter

          +

          Description

          +

          Region

          +

          Region where the endpoint is located. Select the region that the Kafka instance is in.

          +

          Service Category

          +
          • Cloud services: Select this option if the VPC endpoint service to be accessed is a cloud service.
          • Find a service by name: Select this option if the VPC endpoint service to be accessed is a private service of your own.
          +

          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

          +

          VPC where the endpoint is located. Select the VPC that the Kafka client is in.

          +

          Subnet

          +

          Subnet where the endpoint is located. Select the subnet that the Kafka client is in.

          +

          Private IP Address

          +

          IPv4 address of the endpoint. Select Automatic.

          +
          +
          +

        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 5 Checking the VPC endpoint status

        7. 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 6 Viewing the private IP address

        8. 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.
        -

        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 7 Changing the advertised.listeners IP addresses
          +

          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. In the Advanced Settings area on the Basic Information 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. Each IP address must match the corresponding port ID. Otherwise, the network will be disconnected. After the modification, click Save.

            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).

          diff --git a/docs/dms/umn/kafka-ug-0002.html b/docs/dms/umn/kafka-ug-0002.html index c7c972b2a..d1c6c3e9a 100644 --- a/docs/dms/umn/kafka-ug-0002.html +++ b/docs/dms/umn/kafka-ug-0002.html @@ -2,27 +2,22 @@

          Configuring Kafka Topic Permissions

          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.

          -

          This function is unavailable for single-node instances.

          -
          -

          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.
          +

          This section describes how to grant topic permissions to users after ciphertext access is enabled for a Kafka instance.

          +

          Notes and 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 have 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 initial user (set when ciphertext access is enabled for the first time) and other authorized users have the permission to subscribe to or publish messages to topics. 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.
          • Unavailable for single-node instances.
          • Permissions may be temporarily invalid during the configuration, throwing client error message "AuthorizationException". In this case, set a retry mechanism on the client. For details, see Suggestions on Using the Kafka Client.

          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 the instance details.
          5. In the navigation pane, choose Topics.
          6. In the row containing the desired topic, click Grant User Permission.
          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. 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
              +

              Setting Permissions for a Topic

              1. Log in to the console.
              2. Click in the upper left corner to select the region where your 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. 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.

                +

                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, while other users can only publish messages to this topic.

                Figure 3 Granting topic permissions to users

              8. Click OK.

                On the Topics tab page, click next to the topic name to view the authorized users and their permissions.

                Figure 4 Viewing authorized users and their permissions

              -

              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.
              +

              Deleting Permissions for a Topic

              1. Log in to the console.
              2. Click in the upper left corner to select the region where your 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 containing the user whose permissions are to be removed, click Delete, and click OK.

                To check whether the user permission has been deleted, click before the topic on the topic list page. Deleted users are no longer displayed.

                +

              diff --git a/docs/dms/umn/kafka-ug-0003.html b/docs/dms/umn/kafka-ug-0003.html index 5eb238113..0802eed6e 100644 --- a/docs/dms/umn/kafka-ug-0003.html +++ b/docs/dms/umn/kafka-ug-0003.html @@ -3,60 +3,50 @@

              Configuring Kafka ACL 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 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:

              - -

              Prerequisites

              • Ciphertext access has been enabled for the Kafka instance.
              • Kafka users can be configured only for Kafka instances in the Running state.
              + +

              Notes and Constraints

              • Single-node instances do not support user creation, user password reset, or user deletion.
              • The initial user set when ciphertext access is enabled for the first time cannot be deleted.
              • Resetting a user password will interrupt services. Change the user password in the client configuration file or code as soon as possible.
              • The maximum number of users that can be created for a Kafka instance is 20 or 500. Check the console for the actual limit.
              -

              Constraints

              • Single-node instances do not support user creation, user password reset, or user deletion.
              • Resetting a user password will interrupt services. Change the user password in the client configuration file or code as soon as possible.
              +

              Prerequisites

              • Ciphertext access has been enabled for the Kafka instance.
              • The Kafka instance is in the Running state.
              -

              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 instance to go to the instance details page.
              5. On the Users page, click Create User.
              6. Set user information by referring to Configuring Kafka ACL Users.

                -

                Table 1 User creation parameters

                Parameter

                +

                Creating a User

                1. Log in to the console.
                2. Click in the upper left corner to select the region where your instance is located.
                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                4. Click the desired instance to go to the instance details page.
                5. In the navigation pane, choose Users.
                6. Click Create User in the upper left corner.
                7. Set user information by referring to Table 1.

                  +

                  - - - - -
                  Table 1 User creation parameters

                  Parameter

                  Description

                  +

                  Description

                  Username

                  +

                  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 (_).

                  +

                  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

                  +

                  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.
                  +

                  The password used to access a Kafka instance. 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 forward or backward.
                  -

                8. Click OK.

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

                  +

                9. Click OK.

                  View the new user on the user list page.

                  +

                  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.

                  -
                  -

                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                4. Reset the password for the initial user in either of the following ways.

                  • Choose More > Reset Kafka Password in the row containing the desired Kafka instance.
                  • Click the desired Kafka instance to view its details. Choose More > Reset Kafka Password in the upper left corner.
                  • Click the desired Kafka instance to view its details. On the Basic Information page, click Reset Password next to Username in the Connection section.
                  • Click the desired Kafka instance to view its details. On the Users page, click Reset Password in the row containing the desired user.
                  -

                5. 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.

                  -
                  +

                  Resetting the Password (for the Initial User)

                  1. Log in to the console.
                  2. Click in the upper left corner to select the region where your instance is located.
                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                  4. Reset the password for the initial user in either of the following ways.

                    • Choose More > Reset Kafka Password in the row containing the desired Kafka instance.
                    • Click the desired Kafka instance to go to the instance details page. Choose More > Reset Kafka Password in the upper right corner.
                    • Click the desired Kafka instance to go to the instance details page. On the Basic Information page, click Reset Password next to Username in the Connection section.
                    • Click the desired Kafka instance to go to the instance details page. On the Users page, click Reset Password in the row containing the desired user.
                    +

                  5. 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.

                      +

                  -

                  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.
                    +

                    Resetting the Password (for Non-initial Users)

                    1. Log in to the console.
                    2. Click in the upper left corner to select the region where your 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 go to the instance details page.
                    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.

                      -
                      -

                    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 Users.
                    6. 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.

                      -
                      -

                    7. In the displayed Delete User dialog box, click OK to delete the user.
                    +

                    Deleting a User

                    1. Log in to the console.
                    2. Click in the upper left corner to select the region where your instance is located.
                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                    4. Click the desired instance to go to the instance details page.
                    5. In the navigation pane, choose Users.
                    6. 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.
                      +

                    7. In the displayed Delete User dialog box, click OK to delete the user.

                      The user is deleted if it is not displayed in the user list.

                      +

                    diff --git a/docs/dms/umn/kafka-ug-0004.html b/docs/dms/umn/kafka-ug-0004.html index 71be31fb0..cc9902256 100644 --- a/docs/dms/umn/kafka-ug-0004.html +++ b/docs/dms/umn/kafka-ug-0004.html @@ -2,11 +2,9 @@

                    Viewing Kafka Disk Usage

                    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.

                    -
                    -

                    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.

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

                      +

                      Notes and Constraints

                      Unavailable for single-node instances.

                      +
                      +

                      Procedure

                      1. Log in to the console.
                      2. Click in the upper left corner to select the region where your instance is located.
                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                      4. Click the name of the desired Kafka instance to go to the Basic Information page.
                      5. Go to the Monitoring > 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 9e150d319..298faa4d3 100644 --- a/docs/dms/umn/kafka-ug-0006.html +++ b/docs/dms/umn/kafka-ug-0006.html @@ -1,59 +1,79 @@

                      Changing Kafka Partition Quantity

                      -

                      After creating a topic, you can increase the number of partitions as required.

                      -

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

                      -
                      +

                      After creating a topic, you can change the number of partitions as required. Changing the number of partitions does not restart the instance or affect services.

                      Methods for changing the partition quantity:

                      - -

                      Modifying Topic Partitions 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 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 partitions of all topics cannot exceed the maximum partitions of an instance. The maximum partitions of an instance vary by instance specifications. For details, see Specifications.
                        -
                        + +

                        Notes and Constraints

                        • The number of partitions can only be increased.
                        • The partition quantity of topics of a single-node or cluster Kafka instance is limited. When the partition quantity limit is reached, you can no longer create topics. The quantity varies with instance specifications. For details, see Cluster Kafka Instances and Single-node Kafka Instances.
                        • For an instance with ciphertext access enabled, if allow.everyone.if.no.acl.found is set to false, the topic partition quantity can be modified on the client only by the initial user (set in first ciphertext access enablement).
                        +
                        +

                        Repartitioning a Topic on the Console

                        1. Log in to the console.
                        2. Click in the upper left corner to select the region where your instance is located.
                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                        4. Click the desired instance to go to the instance details page.
                        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.

                          To ensure performance, a maximum of 200 partitions is allowed for each topic on the Kafka console.

                          +

                          View the partition quantity on the Topics page.

                        Modifying Topic Partitions on the 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}
                          -
                          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. To ensure performance, a partition number within 200 is recommended for each topic.
                          +
                          • 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}
                            + +
                            + + + + + + + + + + + + + +
                            Table 1 Topic partition quantity parameters

                            Parameter

                            +

                            Description

                            +

                            connection-address

                            +

                            Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.

                            +

                            topic-name

                            +

                            Topic name.

                            +

                            number-of-partitions

                            +

                            Number of partitions in the topic.

                            +

                            To ensure performance, 200 or less partitions are recommended for each 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]#
                            -
                          • 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 and go to 2 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 and go to 2 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. To ensure performance, a partition number within 200 is recommended for each topic.
                              +
                            3. For a Kafka instance with ciphertext access enabled, do as follows:
                              1. (Optional) If the username and password, and the SSL certificate has been configured, skip this step and go to 2. Otherwise, do as follows:

                                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}
                                + +
                                + + + + + + + + + + + + + + + + +
                                Table 2 Topic partition quantity parameters

                                Parameter

                                +

                                Description

                                +

                                connection-address

                                +

                                Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.

                                +

                                topic-name

                                +

                                Topic name.

                                +

                                number-of-partitions

                                +

                                Number of partitions in the topic.

                                +

                                To ensure performance, 200 or less partitions are recommended for each topic.

                                +

                                ssl-user-config.properties

                                +

                                Configuration file name. This file contains username, password, and SSL certificate information.

                                +

                                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
diff --git a/docs/dms/umn/kafka-ug-0007.html b/docs/dms/umn/kafka-ug-0007.html
index 8f9da0c34..0cd81bb7e 100644
--- a/docs/dms/umn/kafka-ug-0007.html
+++ b/docs/dms/umn/kafka-ug-0007.html
@@ -4,329 +4,328 @@
 
                                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.
                                
-
                                
+
                                Notes and Constraints
                                • 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.
                                
 
                                
-
                                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 1 and Table 2. Parameters of v2.3.0/v2.7/3.x instances are described in Table 3 and Table 4.
                                  
+
                                  Procedure
                                  1. Log in to the console.
                                  2. Click  in the upper left corner to select the region where your instance is located.
                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                  4. Click the desired instance to go to the instance details page.
                                  5. Choose Parameters.
                                    • To modify a specific parameter, locate the row containing it, and click Edit.
                                    • To modify parameters in batches, click Modify.
                                    • To restore parameters to their default values, choose Edit > Restore Default or Modify > Restore Default.
                                    
+
                                    Parameters of v1.1.0 instances are described in Table 1 and Table 2. Parameters of v2.3.0/v2.7/v3.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 or 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 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
                                    
+
                                    1,440–30,240
                                    
 
                                    Unit: minute
                                    
 
                                    20160
                                    
+
                                    20,160
                                    
                                     		
 
                                    
                                     
 
                                    
 
                                    
 
-
                                    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.
                                    
+
                                    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
                                    
+
                                    5,000–600,000
                                    
 
                                    Unit: millisecond
                                    
 
                                    600,000
                                    
+
                                    600,000
                                    
                                     		
 
                                    log.retention.hours
                                    
+
                                    log.retention.hours
                                    
 
                                    Maximum duration for storing log files.
                                    
+
                                    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
                                    
 
                                    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.
                                    
+
                                    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
                                    
+
                                    6,000–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.
                                    
-
                                    This parameter is displayed only when  is enabled for the instance or ciphertext access is used.
                                    
+
                                    • When this parameter is set to true, all users can access resources without ACL rules.
                                    • When this parameter is set to false, the initial user has all the permissions and other users require authorization.
                                      All the permissions cover modifying a topic, creating and deleting a topic, and changing the number of topic partitions.
                                      
+
                                    
+
                                    This parameter is displayed only when ciphertext access is enabled for the instance.
                                    
 
                                    This parameter of some earlier instances cannot be modified.
                                    
 
                                    true/false
                                    
+
                                    true or 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
                                    
 
                                    Minimum session timeout 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
                                    
+
                                    6,000–300,000
                                    
 
                                    Unit: millisecond
                                    
 
                                    6000
                                    
+
                                    6,000
                                    
                                     		
 
                                    
                                     
 
                                    
 
                                    
 
-
                                    Table 3 Dynamic parameters (v2.3.0/v2.7/v3.x)
                                    Parameter
                                    
+
                                    
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                    Table 3 Dynamic parameters (v2.3.0/v2.7/v3.x)
                                    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.
                                    
+
                                    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 or 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 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
                                    
+
                                    1,440–30,240
                                    
 
                                    Unit: minute
                                    
 
                                    20160
                                    
+
                                    20,160
                                    
                                     		
 
                                    
                                     
 
                                    
 
                                    
 
-
                                    Table 4 Static parameters (v2.3.0/v2.7/v3.x)
                                    Parameter
                                    
+
                                    
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                    Table 4 Static parameters (v2.3.0/v2.7/v3.x)
                                    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
                                    
+
                                    5,000–600,000
                                    
 
                                    Unit: millisecond
                                    
 
                                    600,000
                                    
+
                                    600,000
                                    
                                     		
 
                                    log.retention.hours
                                    
+
                                    log.retention.hours
                                    
 
                                    Maximum duration for storing log files.
                                    
+
                                    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
                                    
 
                                    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.
                                    
+
                                    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
                                    
+
                                    6,000–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.
                                    
-
                                    This parameter is displayed only when  is enabled for the instance or ciphertext access is used.
                                    
+
                                    • When this parameter is set to true, all users can access resources without ACL rules.
                                    • When this parameter is set to false, the initial user has all the permissions and other users require authorization.
                                      All the permissions cover modifying a topic, creating and deleting a topic, and changing the number of topic partitions.
                                      
+
                                    
+
                                    This parameter is displayed only when ciphertext access is enabled for the instance.
                                    
 
                                    This parameter of some earlier instances cannot be modified.
                                    
 
                                    true/false
                                    
+
                                    true or 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
                                    
 
                                    Minimum session timeout 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
                                    
+
                                    6,000–300,000
                                    
 
                                    Unit: millisecond
                                    
 
                                    6000
                                    
+
                                    6,000
                                    
                                     		
 
                                    
                                     
 
                                    
 
                                    
-
                                     
                                    • To modify multiple dynamic or static parameters at a time, click Modify above the parameter list.
                                    • If you want to restore the default values, click Restore Default in the row containing the desired parameter.
                                    
-
                                    
-
                                  6. Click Save.
                                     
                                    Modifying dynamic parameters will not restart the instance. Static parameter modification requires manual restart of the instance.
                                    
-
                                    
+
                                  7. Click Save.
                                    Modifying dynamic parameters will not restart the instance. Static parameter modification requires manual restart of the instance.
                                    
+
                                    On the Parameters page, view the new parameter values in the Current Value column.
                                    
 
                                    8. 
 
 
diff --git a/docs/dms/umn/kafka-ug-0012.html b/docs/dms/umn/kafka-ug-0012.html
index 1305d6053..14a176f31 100644
--- a/docs/dms/umn/kafka-ug-0012.html
+++ b/docs/dms/umn/kafka-ug-0012.html
@@ -3,60 +3,67 @@
 
                                    Deleting a Kafka Consumer Group
                                    
 
                                    You can delete a consumer group in either of the following ways:
                                    
 
                                    • On the console.
                                    • Use Kafka CLI. (Ensure that the Kafka instance version is the same as the CLI version.)
                                    
-
                                    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.
                                    
+
                                    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.
                                    • Deleting a consumer group loses the consumption offset. Re-consumption or repeated consumption may occur.
                                    
 
                                    
-
                                    Prerequisites
                                    The status of the consumer group to be deleted is EMPTY.
                                    
+
                                    Prerequisite
                                    The status of the consumer group to be deleted is EMPTY.
                                    
 
                                    
-
                                    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.
                                      
-
                                       
                                      A consumer group can be deleted only when its status is EMPTY.
                                      
-
                                      
-
                                      Consumer group statuses include:
                                      
-
                                      • DEAD: The consumer group has no member or metadata.
                                      • EMPTY: The consumer group has metadata but has no member.
                                      • PREPARING_REBALANCE: The consumer group is to be rebalanced.
                                      • COMPLETING_REBALANCE: All members have joined the consumer group.
                                      • STABLE: Members in the consumer group can consume messages normally.
                                      
-
                                    7. In the displayed Delete Consumer Group dialog box, click OK.
                                    
+
                                    Deleting a Consumer Group (Console)
                                    1. Log in to the console.
                                    2. Click  in the upper left corner to select the region where your instance is located.
                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                    4. Click the desired instance to go to the instance details page.
                                    5. In the navigation pane, choose Consumer Groups.
                                    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 to be deleted, click Delete.
                                      • Click the consumer group to be deleted. The consumer group details page is displayed. Click Delete in the upper right corner.
                                      
+
                                    7. In the displayed Delete Consumer Group dialog box, click OK.
                                      The consumer groups are deleted when they are no longer displayed in the consumer group list.
                                      
+
                                    
+
                                    
+
                                    Deleting a Consumer Group (Kafka Client)
                                    The following uses Linux as an example.
                                    
+
                                    • 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 {group-name}
                                      
+
+
                                      
+
+
+
+
+
+
+
+
+
+
+
                                      Table 1 Consumer group deletion parameters
                                      Parameter
                                      
+
                                      Description
                                      
+
                                      connection-address
                                      
+
                                      Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                      
+
                                      group-name
                                      
+
                                      Consumer group name.
                                      
+
                                      
 
                                      
-
                                      Using the CLI to Delete a Consumer Group
                                      The following uses Linux as an example.
                                      
-
                                      • 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 and go to 2 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 and go to 2 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. For a Kafka instance with ciphertext access enabled, do as follows:
                                          1. (Optional) If the SSL certificate has been configured, skip this step and go to 2. Otherwise, do as follows:
                                            Create the ssl-user-config.properties file in the /config directory of the Kafka client and add the SSL certificate configurations by referring to 3.
                                            
+
                                          2. In the /bin directory of the Kafka client, run the following command:
                                            ./kafka-consumer-groups.sh --bootstrap-server {connection-address} --delete --group {group-name} --command-config ../config/{ssl-user-config.properties}
                                            
+
+
                                            
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                            Table 2 Consumer group deletion parameters
                                            Parameter
                                            
+
                                            Description
                                            
+
                                            connection-address
                                            
+
                                            Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                            
+
                                            group-name
                                            
+
                                            Consumer group name.
                                            
+
                                            ssl-user-config.properties
                                            
+
                                            Configuration file name. This file contains username, password, and SSL certificate information.
                                            
+
                                            
 
                                            
-
                                          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} --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.
diff --git a/docs/dms/umn/kafka-ug-0014.html b/docs/dms/umn/kafka-ug-0014.html
index 432fa3deb..b3098b65e 100644
--- a/docs/dms/umn/kafka-ug-0014.html
+++ b/docs/dms/umn/kafka-ug-0014.html
@@ -2,17 +2,74 @@
 
 
                                            Viewing and Resetting Kafka Consumption Offsets
                                            
 
                                            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.
                                            
-
                                             
                                            After a client is stopped, the server considers the client offline only after the time period specified in ConsumerConfig.SESSION_TIMEOUT_MS_CONFIG (1000 ms by default).
                                            
-
                                            
+
                                            Notes and Constraints
                                            Messages may be consumed more than once after the offset is reset. Exercise caution when performing this operation.
                                            
 
                                            
-
                                            Viewing Consumer Offsets (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 Consumer Offset tab page, view the list of topics that the consumer group has subscribed to, total number of messages accumulated in the topic, consumption progress in each partition of the topic (number of accumulated messages, offset, latest offset, consumer ID, consumer address, and client ID).
                                            8. (Optional) To query the consumer offsets of a specific topic, enter the topic name in the search box and press Enter.
                                            
+
                                            Prerequisites
                                            The consumer offset cannot be reset on the fly. You must first stop consumption of the desired consumer group. After a client is stopped, the server considers the client offline only after the time period specified in ConsumerConfig.SESSION_TIMEOUT_MS_CONFIG (1000 ms by default).
                                            
 
                                            
-
                                            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
                                              
+
                                              Viewing Consumer Offsets (Console)
                                              1. Log in to the console.
                                              2. Click  in the upper left corner to select the region where your instance is located.
                                              3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                              4. Click the desired instance to go to the instance details page.
                                              5. In the navigation pane, choose Consumer Groups.
                                              6. Click the name of the desired consumer group.
                                              7. On the Consumer Offset tab page, view the list of topics that the consumer group has subscribed to, topic quantity, total number of messages accumulated in the topic, and offset of each partition.
                                                
+
                                                
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                Table 1 Consumer offset parameters
                                                Parameter
                                                
+
                                                Description
                                                
+
                                                Topic Name
                                                
+
                                                Name of a topic that the consumer group has subscribed to
                                                
+
                                                Partitions
                                                
+
                                                Number of partitions in a topic
                                                
+
                                                Cumulative Messages
                                                
+
                                                Number of messages that are not consumed by the consumer group in a topic
                                                
+
                                                This parameter indicates the instantaneous value at the sampling. The value of its corresponding metric in monitoring is sampled every minute. These values may vary. For more information, see Why Is the Number of Stacked Messages Monitored as 0 when Messages Are Stacked?.
                                                
+
                                                Partition
                                                
+
                                                Partition number in a topic
                                                
+
                                                Accumulated Messages
                                                
+
                                                Number of messages that are not consumed by the consumer group in a partition
                                                
+
                                                Offset
                                                
+
                                                Offset of this partition
                                                
+
                                                Latest Offset
                                                
+
                                                Maximum message position of a partition
                                                
+
                                                ID
                                                
+
                                                ID of the consumer who consumes messages in this partition
                                                
+
                                                Address
                                                
+
                                                Address of the consumer who consumes messages in this partition
                                                
+
                                                Client ID
                                                
+
                                                Client identifier. This client is used to connect to a Kafka instance and consume messages in this partition.
                                                
+
                                                
+
                                                
+
                                              8. (Optional) To query the consumer offsets of a specific topic, enter the topic name in the search box and press Enter.
                                              
+
                                              
+
                                              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
                                                
 
                                                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
@@ -31,38 +88,28 @@ 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]#
                                                
-
                                              • 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 and go to 2 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 and go to 2 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. For a Kafka instance with ciphertext access enabled, do as follows:
                                                  1. (Optional) If the username and password, and the SSL certificate has been configured, skip this step and go to 2. Otherwise, do as follows:
                                                    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} 
                                                    
+
+
                                                    
+
+
+
+
+
+
+
+
+
+
+
                                                    Table 2 Consumer offset query parameters
                                                    Parameter
                                                    
+
                                                    Description
                                                    
+
                                                    connection-address
                                                    
+
                                                    Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                                    
+
                                                    ssl-user-config.properties
                                                    
+
                                                    Configuration file name. This file contains username, password, and SSL certificate information.
                                                    
+
                                                    
 
                                                    
-
                                                  3. 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
 
@@ -83,11 +130,9 @@ test            topic-01        2          10              10              0
 
                                                  
 
                                              
 
                                              
-
                                              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. In the displayed Reset Consumer Offset dialog box, set the parameters by referring to Table 1.
                                                
-
                                                Table 1 Parameters for resetting the consumer offset
                                                Parameter
                                                
+
                                                Resetting Consumer Offsets
                                                1. Log in to the console.
                                                2. Click  in the upper left corner to select the region where your instance is located.
                                                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                4. Click the desired instance to go to the instance details page.
                                                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.
                                                  
+
                                                8. In the displayed Reset Consumer Offset dialog box, set the parameters by referring to Table 3.
                                                  
+
                                                  
@@ -97,7 +142,7 @@ test            topic-01        2          10              10              0
 
                                                  Table 3 Parameters for resetting the consumer offset
                                                  Parameter
                                                  
                                                   		
 
                                                  Description
                                                  
                                                   		
 
                                                  You can reset an offset by:
                                                  
 
                                                  • Time: Reset the offset to the specified time.
                                                  • Offset: Reset the offset to the specified position.
                                                  
-
                                                  If you reset offsets in batches, they can only be reset to the specified time.
                                                  
+
                                                  Reset Consumer Offset works with a specific time.
                                                  
                                                   		
 
                                                  
 
                                                  Time
                                                  
@@ -116,9 +161,9 @@ test            topic-01        2          10              10              0
 
 
                                                  
 
                                                  
-
                                                9. Click OK.
                                                10. Click Yes in the confirmation dialog box. The consumer offset is reset.
                                                
+
                                              9. Click OK.
                                              10. Click Yes in the confirmation dialog box. The consumer offset is reset.
                                                On the Consumer Offset tab page, click  before the topic whose consumer offset has been reset, and view the new value in the Offset column.
                                                
+
                                                11. 
 
                                                
-
                                                
 
 
                                                
 
                                                
diff --git a/docs/dms/umn/kafka-ug-0015.html b/docs/dms/umn/kafka-ug-0015.html
index d72f50367..fcb48eaf2 100644
--- a/docs/dms/umn/kafka-ug-0015.html
+++ b/docs/dms/umn/kafka-ug-0015.html
@@ -4,53 +4,63 @@
 
                                                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 a Kafka instance name to go to the instance details page.
                                                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.
                                                  
+
                                                  Viewing the Consumer List (Console)
                                                  1. Log in to the console.
                                                  2. Click  in the upper left corner to select the region where your instance is located.
                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                  4. Click the desired instance to go to the instance details page.
                                                  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. (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
                                                    
-
                                                    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.
                                                    
+
                                                    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
                                                      
+
+
                                                      
+
+
+
+
+
+
+
+
+
+
+
                                                      Table 1 Consumer list query parameters
                                                      Parameter
                                                      
+
                                                      Description
                                                      
+
                                                      connection-address
                                                      
+
                                                      Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                                      
+
                                                      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]#
                                                      
-
                                                    • 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 and go to 2 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 and go to 2 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. For a Kafka instance with ciphertext access enabled, do as follows:
                                                        1. (Optional) If the username and password, and the SSL certificate has been configured, skip this step and go to 2. Otherwise, do as follows:
                                                          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} 
                                                          
+
+
                                                          
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                          Table 2 Consumer list query parameters
                                                          Parameter
                                                          
+
                                                          Description
                                                          
+
                                                          connection-address
                                                          
+
                                                          Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                                          
+
                                                          group-name
                                                          
+
                                                          Consumer group name.
                                                          
+
                                                          ssl-user-config.properties
                                                          
+
                                                          Configuration file name. This file contains username, password, and SSL certificate information.
                                                          
+
                                                          
 
                                                          
-
                                                        3. 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
 
@@ -60,9 +70,7 @@ test            console-consumer-566d0c82-07d3-4d87-9a6e-f57a9bc9fc69 /192.168.0
 
                                                        
 
                                                    
 
                                                    
-
                                                    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.
                                                    
+
                                                    Viewing Consumer Connection Addresses (Console)
                                                    1. Log in to the console.
                                                    2. Click  in the upper left corner to select the region where your instance is located.
                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                    4. Click the desired instance to go to the instance details page.
                                                    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
index 43fd37d8e..fd07c6b2c 100644
--- a/docs/dms/umn/kafka-ug-0034.html
+++ b/docs/dms/umn/kafka-ug-0034.html
@@ -2,15 +2,12 @@
 
 
                                                    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 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.
                                                    
+
                                                    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 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.
                                                    • Data can be synchronized only when Max. Message Size of the target topic is greater than or equal to 524,288 bytes. If no topic is available in the target Kafka instance, a topic will be automatically created with the same Max. Message Size as that of the source Kafka instance topic during data synchronization. In this case, ensure the Max. Message Size to be used is greater than or equal to 524,288 bytes. To modify Max. Message Size, see Modifying Kafka Topic Configurations.
                                                    
 
                                                    
 
                                                    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:
                                                      
+
                                                      Procedure
                                                      1. Log in to the console.
                                                      2. Click  in the upper left corner to select the region where your instance is located.
                                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                      4. Click the desired instance to go to the instance details page.
                                                      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 Peer Kafka parameters
                                                        Parameter
                                                        
@@ -29,21 +26,20 @@
 
                                                        Config Type
                                                        
                                                         		
 
                                                        Options:
                                                        
-
                                                        • Kafka address: Enter Kafka instance addresses.
                                                        • Instance name: Select an existing Kafka instance.
                                                        
+
                                                        • Kafka address: Enter Kafka instance addresses. To replicate data to a target Kafka instance in another VPC, use this type.
                                                        • Instance name: Select an existing Kafka instance. To replicate data to a target Kafka instance in the same VPC, use this type.
                                                        
                                                         		
 
                                                        
 
                                                        Instance Name
                                                        
 
                                                        Set this parameter when Config Type is set to Instance name.
                                                        
+
                                                        Mandatory when Instance name is used for Config Type and the Kafka instances are within a VPC.
                                                        
 
                                                        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.
                                                        
+
                                                        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
                                                        
@@ -73,8 +69,7 @@
 
 
                                                        
 
                                                        
-
                                                         
                                                        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.
                                                        
-
                                                        
+
                                                        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 Smart Connect task and create another one.
                                                        
 
                                                      12. In the Rules area, configure the following parameters.
                                                        
 
                                                        
@@ -92,8 +87,7 @@
 
                                                        Table 2 Parameters for configuring data replication rules
                                                        Parameter
                                                        
                                                         		
 
                                                        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.
                                                        
-
                                                        
+
                                                        Data of topics whose names end with "internal" (for example, topic.internal) will not be synchronized.
                                                        
                                                         		
 
                                                        
 
                                                        Tasks
                                                        
@@ -117,9 +111,8 @@
 
                                                        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.
                                                        
-
                                                        
+
                                                        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
                                                        
@@ -148,11 +141,11 @@
 
 
                                                        
 
                                                        
-
                                                         
                                                        • 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.
                                                        
-
                                                        
+
                                                        Precautions:
                                                        
+
                                                        • 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.
                                                        
 
                                                      13. (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.
                                                        
-
                                                      14. 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.
                                                        
-
                                                        
+
                                                      15. 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, Kafka automatically creates the following topics:
                                                        
+
                                                        • 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.
                                                        
 
                                                      
 
                                                      
 
                                                    
diff --git a/docs/dms/umn/kafka-ug-0035.html b/docs/dms/umn/kafka-ug-0035.html
index 38d410713..c06866a59 100644
--- a/docs/dms/umn/kafka-ug-0035.html
+++ b/docs/dms/umn/kafka-ug-0035.html
@@ -2,15 +2,12 @@
 
 
                                                    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 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.
                                                    
+
                                                    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 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.
                                                      
+
                                                      Procedure
                                                      1. Log in to the console.
                                                      2. Click  in the upper left corner to select the region where your instance is located.
                                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                      4. Click the desired instance to go to the instance details page.
                                                      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
                                                        
@@ -74,7 +71,7 @@
 
                                                        
 
                                                        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.
                                                        
+
                                                        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/topic-name/year/month/day.
                                                        
                                                         		
 
                                                        
 
                                                        Record Separator
                                                        
@@ -90,7 +87,7 @@
 
 
                                                        
 
                                                        
-
                                                         
                                                        Do not use the key of a message as the dumping file name.
                                                        
+
                                                         
                                                        • Do not use the key of a message as the dumping file name.
                                                        • OBS file directory format: bucket-name/file-directory/topic-name/time. For example, obs-kafka/smartconnect/topic01/2025/01/01.
                                                        • OBS file name format: topic-name+partition No.+start offset, for example, topic01+0+0000000004.
                                                        • OBS file generation rule: One file is generated for each specified data dump period.
                                                        
 
                                                        
 
                                                      12. 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 1ae7e2758..e3ed036af 100644
--- a/docs/dms/umn/kafka-ug-0038.html
+++ b/docs/dms/umn/kafka-ug-0038.html
@@ -2,8 +2,7 @@
 
 
                                                      Modifying Kafka Topic Configurations
                                                      
 
                                                      This section describes how to modify configurations in Table 1 of a Kafka topic on the console.
                                                      
-
                                                       
                                                      Modifying Synchronous Replication, Synchronous Flushing, Message Timestamp, or Max. Message Size does not require instance restart.
                                                      
-
                                                      
+
                                                      Modifying Synchronous Replication, Synchronous Flushing, Message Timestamp, or Max. Message Size does not require instance restart.
                                                      
 
 
                                                      
@@ -21,6 +20,11 @@
 
+
+
+
                                                      Table 1 Kafka topic configuration parameters
                                                      Parameter
                                                      
 
                                                      Maximum message retention. For details about how to change, see Changing Kafka Message Retention Period.
                                                      
                                                       		
 
                                                      Replicas
                                                      
+
                                                      Number of replicas of each topic partition. To modify it, see Modifying Kafka Topic Replicas.
                                                      
+
                                                      
 
                                                      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.
                                                      
@@ -46,14 +50,12 @@
 
 
                                                      
 
                                                      
-
                                                      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.
                                                        
-
                                                        
+
                                                        Notes and Constraints
                                                        • 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.
                                                        
+
                                                        
+
                                                        Modifying a Topic
                                                        1. Log in to the console.
                                                        2. Click  in the upper left corner to select the region where your instance is located.
                                                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                        4. Click the desired instance to go to the instance details page.
                                                        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.
                                                          View the reconfiguration on the Topics page.
                                                          
 
                                                        
 
                                                        
-
                                                        
 
                                                      
 
                                                      
 
                                                      
diff --git a/docs/dms/umn/kafka-ug-0041.html b/docs/dms/umn/kafka-ug-0041.html
index e07af3ab7..65f5f9512 100644
--- a/docs/dms/umn/kafka-ug-0041.html
+++ b/docs/dms/umn/kafka-ug-0041.html
@@ -5,23 +5,19 @@
 
                                                      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.
                                                      
-
                                                      
+
                                                      This section describes how to create a consumer group on the console. This operation does not restart the Kafka instance.
                                                      
 
                                                      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
                                                        
+
                                                        Procedure
                                                        1. Log in to the console.
                                                        2. Click  in the upper left corner to select the region where your instance is located.
                                                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                        4. Click the desired instance to go to the instance details page.
                                                        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.
                                                          
+
                                                          
-
-
-
diff --git a/docs/dms/umn/kafka-ug-0053.html b/docs/dms/umn/kafka-ug-0053.html
index a8018aeae..494251112 100644
--- a/docs/dms/umn/kafka-ug-0053.html
+++ b/docs/dms/umn/kafka-ug-0053.html
@@ -2,9 +2,7 @@
 
 
                                                          Exporting the Kafka Instance List
                                                          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.
                                                            
+
                                                            Procedure
                                                            1. Log in to the console.
                                                            2. Click  in the upper left corner to select the region where your instance is located.
                                                            3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                            4. Export the instance list in either of the following ways:
                                                              • 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 6772212bb..f071131d3 100644
--- a/docs/dms/umn/kafka-ug-0056.html
+++ b/docs/dms/umn/kafka-ug-0056.html
@@ -2,9 +2,7 @@
 
 
                                                          Exporting Kafka Consumer Groups
                                                          
 
                                                          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.
                                                            
+
                                                            Procedure
                                                            1. Log in to the console.
                                                            2. Click  in the upper left corner to select the region where your instance is located.
                                                            3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                            4. Click the desired instance to go to the instance details page.
                                                            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-0058.html b/docs/dms/umn/kafka-ug-0058.html
index 346165226..56f00e7ff 100644
--- a/docs/dms/umn/kafka-ug-0058.html
+++ b/docs/dms/umn/kafka-ug-0058.html
@@ -14,6 +14,8 @@
 
 
                                                        8. Changing Kafka Partition Quantity
                                                          
 
                                                          9. 
+
                                                        9. Modifying Kafka Topic Replicas
                                                          
+
                                                          10. 
 
                                                        10. Exporting the Kafka Topic List
                                                          
 
                                                          11. 
 
                                                        11. Reassigning Kafka Partitions
                                                          
diff --git a/docs/dms/umn/kafka-ug-0069.html b/docs/dms/umn/kafka-ug-0069.html
index 7d9444ae6..90c6f8efd 100644
--- a/docs/dms/umn/kafka-ug-0069.html
+++ b/docs/dms/umn/kafka-ug-0069.html
@@ -3,7 +3,7 @@
 
                                                          Process of Using Kafka
                                                          
 
                                                          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.
                                                            
+
                                                            1. Creating an IAM 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.
                                                              
diff --git a/docs/dms/umn/kafka-ug-0072.html b/docs/dms/umn/kafka-ug-0072.html
new file mode 100644
index 000000000..f8653fa4f
--- /dev/null
+++ b/docs/dms/umn/kafka-ug-0072.html
@@ -0,0 +1,104 @@
+
+
+
                                                              Modifying Kafka Topic Replicas
                                                              
+
                                                              The replicas of a Kafka topic can be modified as required.
                                                              
+
                                                              Reassigning partitions can modify replicas automatically or manually on the Kafka console. For more information, see Modifying Replicas by Automatic Reassignment and Modifying Replicas by Manual Reassignment.
                                                              
+
                                                              Notes and Constraints
                                                              • Unavailable for single-node instances.
                                                              • 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.
                                                              
+
                                                              
+
                                                              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.
                                                              • 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 longer for a topic with a large data volume. To check the volume, see the Message Size metric on the monitoring page by referring to Viewing Kafka Metrics. 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.
                                                              
+
                                                              
+
                                                              Prerequisite
                                                              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.
                                                              
+
                                                              
+
                                                              Modifying Replicas by Automatic Reassignment
                                                              1. Log in to the console.
                                                              2. Click  in the upper left corner to select the region where your instance is located.
                                                              3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                              4. Click the desired instance to go to the instance details page.
                                                              5. In the navigation pane, choose Topics.
                                                              6. Go to the Auto page in either of the following ways:
                                                                • Select one or more topics and choose Reassign > Auto above the topic list.
                                                                • In the row containing the desired topic, choose More > Reassign > Auto.
                                                                
+
                                                              7. Modify the replicas.
                                                                
+
                                                          12. 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 1 Parameters of automatic reassignment
                                                          Parameter
                                                          
+
                                                          Description
                                                          
+
                                                          Broker Name
                                                          
+
                                                          Select the brokers to assign the topic's partition replicas to.
                                                          
+
                                                          Replicas
                                                          
+
                                                          Enter the number of replicas. This number must be less than or equal to the number of brokers.
                                                          
+
                                                          Max. Bandwidth
                                                          
+
                                                          Specify throttle. The default value is -1, indicating that there is no throttle.
                                                          
+
                                                          If the instance has low workload (for example, only 30 of 300 MB/s is used), you are not advised to limit the bandwidth. Otherwise, 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.
                                                          
+
                                                          Execute
                                                          
+
                                                          Specify when to execute the reassignment.
                                                          
+
                                                          • Now means to execute it immediately.
                                                          • As scheduled means to execute it at the scheduled time.
                                                          
+
                                                          
+
                                                          
+
                                                        12. (Optional) Click Calculate. Time Required indicates how long automatic balancing will take.
                                                          The one-click calculation function does not affect the performance of Kafka instances.
                                                          
+
                                                        13. Click OK.
                                                          The following table lists how to check whether reassignment is complete (scheduled and non-scheduled tasks):
                                                          
+
+
                                                          
+
+
+
+
+
+
+
+
+
+
+
                                                          Table 2 Checking the reassignment result
                                                          Task Type
                                                          
+
                                                          Reassignment Result
                                                          
+
                                                          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, which means that the replicas are modified.
                                                          
+
                                                          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.
                                                            
+
                                                          2. Click Background tasks. When the task status is Successful, reassignment has completed, which means that the replicas are modified.
                                                          
+
                                                          
+
                                                          
+
                                                        
+
                                                        
+
                                                        Modifying Replicas by Manual Reassignment
                                                        1. Log in to the console.
                                                        2. Click  in the upper left corner to select the region where your instance is located.
                                                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                        4. Click the desired instance to go to the instance details page.
                                                        5. In the navigation pane, choose Topics.
                                                        6. Go to the Manual page in either of the following ways:
                                                          • Select a topic and choose Reassign > Manual above the topic list. Manual reassignment does not support batch operations.
                                                          • In the row containing the desired topic, choose More > Reassign > Manual.
                                                          
+
                                                        7. Modify the replicas.
                                                          • 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 of 300 MB/s is used), you are not advised to limit the bandwidth. Otherwise, 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.
                                                          
+
                                                        8. (Optional) Click Calculate. Time Required indicates how long manual balancing will take.
                                                          The one-click calculation function does not affect the performance of Kafka instances.
                                                          
+
                                                        9. Click OK.
                                                          The following table lists how to check whether reassignment is complete (scheduled and non-scheduled tasks):
                                                          
+
+
                                                          
+
+
+
+
+
+
+
+
+
+
+
                                                          Table 3 Checking the reassignment result
                                                          Task Type
                                                          
+
                                                          Reassignment Result
                                                          
+
                                                          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, which means that the replicas are modified.
                                                          
+
                                                          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.
                                                            
+
                                                          2. Click Background tasks. When the task status is Successful, reassignment has completed, which means that the replicas are modified.
                                                          
+
                                                          
+
                                                          
+
                                                        
+
                                                        
+
+
                                                        
+
                                                        
+
                                                        Parent topic: Managing Topics
                                                        
+
                                                        
+
                                                        
+
diff --git a/docs/dms/umn/kafka-ug-0075.html b/docs/dms/umn/kafka-ug-0075.html
new file mode 100644
index 000000000..23101ba75
--- /dev/null
+++ b/docs/dms/umn/kafka-ug-0075.html
@@ -0,0 +1,15 @@
+
+
+
+  
                                                        Modifying Instance Specifications
                                                        
+
+  
                                                        
+
                                                        
+
+
+
diff --git a/docs/dms/umn/kafka-ug-0319001.html b/docs/dms/umn/kafka-ug-0319001.html
index bf96e41c6..18b74d4f7 100644
--- a/docs/dms/umn/kafka-ug-0319001.html
+++ b/docs/dms/umn/kafka-ug-0319001.html
@@ -1,18 +1,16 @@
 
 
 
                                                        Configuring Kafka Public Access
                                                        
-
                                                        Clients can use IPv4 or IPv6 addresses to access a Kafka instance over a public network.
                                                        
+
                                                        A client can use IPv4 or IPv6 addresses to access a Kafka instance over a public network.
                                                        
 
                                                        • By IPv4: On the Kafka console, enable public access and configure EIPs for the instance.
                                                        • By IPv6: Enable IPv6 in Kafka instance creation and add IPv6 addresses to the shared bandwidth to support both private and public IPv6 access.
                                                        
 
                                                        On the Kafka console, the procedures for configuring public IPv4 access vary depending on the content displayed in the Connection area on the Basic Information page.
                                                        
-
-
                                                        Prerequisites
                                                        • You can change the public access setting only when the Kafka instance is in the Running state.
                                                        • (Optional) To access a Kafka instance using IPv6 addresses, ensure that IPv6 is enabled for the Kafka instance.
                                                        
-
                                                        
+
 
                                                        Notes and Constraints
                                                        Kafka instances only support IPv4 EIPs. IPv6 EIPs are not supported.
                                                        
 
                                                        
-
                                                        Enabling Public IPv4 Access (SASL Cannot Be Changed)
                                                        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 EIPs are insufficient, do as follows to set them.
                                                          
-
                                                          1. Click Create Elastic IP to go to the Create EIP page and create EIPs. For details, see Assigning an EIP
                                                          2. After the creation is complete, return to the public access enabling page.
                                                          3. Click  after Elastic IP Address, select an EIP for each broker and then click .
                                                          4. You can view the operation progress on the Background Tasks page. If the task status is Successful, the modification has succeeded.
                                                          
+
                                                          Prerequisites
                                                          • You can change the public access setting only when the Kafka instance is in the Running state.
                                                          • (Optional) To access a Kafka instance using IPv6 addresses, ensure that IPv6 is enabled for the Kafka instance.
                                                          
+
                                                          
+
                                                          Enabling Public IPv4 Access (SASL Cannot Be Changed)
                                                          1. Log in to the console.
                                                          2. Click  in the upper left corner to select the region where your instance is located.
                                                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                          4. Click the name of 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 EIPs are insufficient, do as follows to set them.
                                                            
+
                                                            1. Click Create Elastic IP to go to the Create EIP page and create EIPs. For details, see Assigning an EIP.
                                                            2. After the creation is complete, return to the public access enabling page.
                                                            3. Click  after Elastic IP Address, select an EIP for each broker and then click .
                                                            4. You can view the operation progress on the Background Tasks page. If the task status is Successful, the modification has succeeded.
                                                            
 
                                                            After public access is enabled, configure security group rules listed in Table 1 before attempting to access Kafka. For details about accessing Kafka, see Connecting to an Instance.
                                                            
 
 
                                                            
-
@@ -50,7 +48,7 @@
 
-
@@ -60,237 +58,229 @@
 
                                                            
-
                                                            Disabling Public IPv4 Access (SASL Cannot Be Changed)
                                                            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.
                                                              You can view the operation progress on the Background Tasks page. If the task status is Successful, the modification has succeeded.
                                                              
-
                                                              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.
                                                              
+
                                                              Enabling Public IPv4 Access (Plaintext or Ciphertext Access Can Be Changed)
                                                              1. Log in to the console.
                                                              2. Click  in the upper left corner to select the region where your instance is located.
                                                              3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                              4. Click the name of 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 EIPs are insufficient, do as follows to set them.
                                                                
+
                                                                1. Click Create Elastic IP to go to the Create EIP page and create EIPs. For details, see Assigning an EIP.
                                                                2. After the creation is complete, return to the public access enabling page.
                                                                3. Click  after Elastic IP Address, select an EIP for each broker and then click . The Background Tasks page is displayed.
                                                                4. If the status of the task turns to Successful, public access is successfully enabled.
                                                                
+
                                                                Figure 1 Enabling public access
                                                                
+
                                                                After public access is enabled, configure the access mode (plaintext or ciphertext) and security group rules listed in Table 2 before attempting to access Kafka. For details about accessing Kafka, see Connecting to an Instance.
                                                                
 
-
                                                            Table 1 Kafka instance security group rules (public IPv4 access)
                                                            Direction
                                                            
@@ -37,7 +35,7 @@
 
 
                                                            9094
                                                            
 
                                                            0.0.0.0/0
                                                            
+
                                                            IP address or IP address group of the Kafka client
                                                            
                                                             		
 
                                                            Accessing Kafka over a public network (without SSL)
                                                            
                                                             		
 
                                                            9095
                                                            
 
                                                            0.0.0.0/0
                                                            
+
                                                            IP address or IP address group of the Kafka client
                                                            
                                                             		
 
                                                            Accessing Kafka over a public network (with SSL)
                                                            
                                                             		
 
 
                                                            Table 2 Kafka instance security group rules (private access)
                                                            Direction
                                                            
+
                                                            
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                            Table 2 Kafka instance security group rules (public IPv4 access)
                                                            Direction
                                                            
 
                                                            Protocol
                                                            
+
                                                            Protocol
                                                            
 
                                                            Type
                                                            
+
                                                            Type
                                                            
 
                                                            Port
                                                            
+
                                                            Port
                                                            
 
                                                            Source
                                                            
+
                                                            Source
                                                            
 
                                                            Description
                                                            
+
                                                            Description
                                                            
                                                             		
 
                                                            
 
                                                            Inbound
                                                            
+
                                                            Inbound
                                                            
 
                                                            TCP
                                                            
+
                                                            TCP
                                                            
 
                                                            IPv4
                                                            
+
                                                            IPv4
                                                            
 
                                                            9092
                                                            
+
                                                            9094
                                                            
 
                                                            0.0.0.0/0
                                                            
+
                                                            IP address or IP address group of the Kafka client
                                                            
 
                                                            Accessing a Kafka instance over a private network within a VPC (without SSL)
                                                            
+
                                                            Public plaintext access to Kafka
                                                            
                                                             		
 
                                                            Inbound
                                                            
+
                                                            Inbound
                                                            
 
                                                            TCP
                                                            
+
                                                            TCP
                                                            
 
                                                            IPv4
                                                            
+
                                                            IPv4
                                                            
 
                                                            9093
                                                            
+
                                                            9095
                                                            
 
                                                            0.0.0.0/0
                                                            
+
                                                            IP address or IP address group of the Kafka client
                                                            
 
                                                            Accessing a Kafka instance over a private network within a VPC (with SSL)
                                                            
+
                                                            Public ciphertext access to Kafka
                                                            
                                                             		
 
                                                            
                                                             
 
                                                            
 
                                                            
-
                                                             
                                                            After a security group is created, its default inbound rule allows communication among ECSs within the security group and its default outbound rule allows all outbound traffic. In this case, you can access a Kafka instance within a VPC, and do not need to add rules according to Table 2.
                                                            
-
                                                            
 
                                                            
 
-
                                                            Enabling Public IPv4 Access (Plaintext or Ciphertext Access Can Be Changed)
                                                            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 EIPs are insufficient, do as follows to set them.
                                                              
-
                                                              1. Click Create Elastic IP to go to the Create EIP page and create EIPs. For details, see Assigning an EIP
                                                              2. After the creation is complete, return to the public access enabling page.
                                                              3. Click  after Elastic IP Address, select an EIP for each broker and then click . The Background Tasks page is displayed.
                                                              4. If the status of the task turns to Successful, public access is successfully enabled.
                                                              
-
                                                              Figure 1 Enabling public access
                                                              
-
                                                              After public access is enabled, configure the access mode (plaintext or ciphertext) and security group rules listed in Table 3 before attempting to access Kafka. For details about accessing Kafka, see Connecting to an Instance.
                                                              
+
                                                              Enabling IPv6 Public Network Access
                                                              1. Log in to the console.
                                                              2. Click  in the upper left corner to select the region where your 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 Connection area, obtain IPv6 Instance Address (Private Network). In the Network area, view and record the VPC and subnet.
                                                              6. Click  in the upper left corner of the management console and choose Network > Elastic IP. The EIPs page is displayed.
                                                              7. Choose Shared Bandwidths in the navigation pane.
                                                              8. Apply for a shared bandwidth. For details, see Assigning a Shared Bandwidth.
                                                                If a shared bandwidth already exists, you do not need to apply for one again.
                                                                
+
                                                              9. In the row containing the shared bandwidth, click Add Public IP Address.
                                                              10. Set the parameters as described in Table 3 and click OK.
                                                                
+
                                                                
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                Table 3 Adding public IP parameters
                                                                Parameter
                                                                
+
                                                                Description
                                                                
+
                                                                Public IP Address
                                                                
+
                                                                Select IPv6 Address.
                                                                
+
                                                                VPC
                                                                
+
                                                                Select the VPC in 5 from the drop-down list.
                                                                
+
                                                                Subnet
                                                                
+
                                                                Select the subnet in 5 from the drop-down list. Select all IPv6 addresses in 5.
                                                                
+
                                                                
+
                                                                
+
                                                              11. After the shared bandwidth is configured, set a Kafka instance security group with the rules described in Table 4.
                                                                
+
                                                                
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                Table 4 Kafka instance security group rules (IPv6 access)
                                                                Direction
                                                                
+
                                                                Protocol
                                                                
+
                                                                Type
                                                                
+
                                                                Port
                                                                
+
                                                                Source
                                                                
+
                                                                Description
                                                                
+
                                                                Inbound
                                                                
+
                                                                TCP
                                                                
+
                                                                IPv6
                                                                
+
                                                                9192
                                                                
+
                                                                ::/0
                                                                
+
                                                                Accessing a Kafka instance using IPv6 addresses (without SSL encryption)
                                                                
+
                                                                Inbound
                                                                
+
                                                                TCP
                                                                
+
                                                                IPv6
                                                                
+
                                                                9193
                                                                
+
                                                                ::/0
                                                                
+
                                                                Accessing a Kafka instance using IPv6 addresses (with SSL encryption)
                                                                
+
                                                                
+
                                                                
+
                                                                When a client is connected to a Kafka instance over an IPv6 public network:
                                                                
+
                                                                • The Kafka connection addresses are the IPv6 addresses in Instance Address (Private Network).
                                                                • The client NIC must be added to shard bandwidth. Shared bandwidth is using a connected network. The shared bandwidth of the client NIC and that of the Kafka instance can be different.
                                                                
+
                                                              
+
                                                              
+
                                                              Disabling Public IPv4 Access (SASL Cannot Be Changed)
                                                              1. Log in to the console.
                                                              2. Click  in the upper left corner to select the region where your instance is located.
                                                              3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                              4. Click the name of a Kafka instance to go to the Basic Information page.
                                                              5. Click  next to Public Access.
                                                                You can view the operation progress on the Background Tasks page. If the task status is Successful, the modification has succeeded.
                                                                
+
                                                                After public access is disabled, configure security group rules listed in Table 5 before attempting to access Kafka in a VPC. For details about accessing Kafka, see Connecting to an Instance.
                                                                
 
-
                                                                Table 3 Kafka instance security group rules (public IPv4 access)
                                                                Direction
                                                                
+
                                                                
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                Table 5 Kafka instance security group rules (private access)
                                                                Direction
                                                                
 
                                                                Protocol
                                                                
+
                                                                Protocol
                                                                
 
                                                                Type
                                                                
+
                                                                Type
                                                                
 
                                                                Port
                                                                
+
                                                                Port
                                                                
 
                                                                Source
                                                                
+
                                                                Source
                                                                
 
                                                                Description
                                                                
+
                                                                Description
                                                                
                                                                 		
 
                                                                
 
                                                                Inbound
                                                                
+
                                                                Inbound
                                                                
 
                                                                TCP
                                                                
+
                                                                TCP
                                                                
 
                                                                IPv4
                                                                
+
                                                                IPv4
                                                                
 
                                                                9094
                                                                
+
                                                                9092
                                                                
 
                                                                0.0.0.0/0
                                                                
+
                                                                IP address or IP address group of the Kafka client
                                                                
 
                                                                Public plaintext access to Kafka
                                                                
+
                                                                Accessing a Kafka instance over a private network within a VPC (without SSL)
                                                                
                                                                 		
 
                                                                Inbound
                                                                
+
                                                                Inbound
                                                                
 
                                                                TCP
                                                                
+
                                                                TCP
                                                                
 
                                                                IPv4
                                                                
+
                                                                IPv4
                                                                
 
                                                                9095
                                                                
+
                                                                9093
                                                                
 
                                                                0.0.0.0/0
                                                                
+
                                                                IP address or IP address group of the Kafka client
                                                                
 
                                                                Public ciphertext access to Kafka
                                                                
+
                                                                Accessing a Kafka instance over a private network within a VPC (with SSL)
                                                                
                                                                 		
 
                                                                
                                                                 
 
                                                                
 
                                                                
+
                                                                 
                                                                After a security group is created, its default inbound rule allows communication among ECSs within the security group and its default outbound rule allows all outbound traffic. In this case, you can access a Kafka instance within a VPC, and do not need to add rules according to Table 5.
                                                                
+
                                                                
 
                                                                
 
-
                                                                Disabling Public IPv4 Access (Plaintext or Ciphertext Access Can Be Changed)
                                                                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 IPv4 Access (Plaintext or Ciphertext Access Can Be Changed)
                                                                  1. Log in to the console.
                                                                  2. Click  in the upper left corner to select the region where your instance is located.
                                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                  4. Click the name of 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 6 before attempting to access Kafka in a VPC. For details about accessing Kafka, see Connecting to an Instance.
                                                                     
                                                                    After a security group is created, its default inbound rule allows communication among ECSs within the security group and its default outbound rule allows all outbound traffic. In this case, you can access a Kafka instance within a VPC, and do not need to add rules according to Table 6.
                                                                    
 
                                                                    
-
                                                                  7. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                  8. Click a Kafka instance to go to the Basic Information page.
                                                                  9. Before disabling public access, disable Plaintext Access and Ciphertext Access next to Public Network Access. Then click  next to Public Access.
                                                                  10. 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 4 before attempting to access Kafka in a VPC. For details about accessing Kafka, see Connecting to an Instance.
-
                                                                    Table 4 Kafka instance security group rules (private access)
                                                                    Direction
                                                                    
+
+
                                                                    
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                    Table 6 Kafka instance security group rules (private access)
                                                                    Direction
                                                                    
 
                                                                    Protocol
                                                                    
+
                                                                    Protocol
                                                                    
 
                                                                    Type
                                                                    
+
                                                                    Type
                                                                    
 
                                                                    Port
                                                                    
+
                                                                    Port
                                                                    
 
                                                                    Source
                                                                    
+
                                                                    Source
                                                                    
 
                                                                    Description
                                                                    
+
                                                                    Description
                                                                    
                                                                     		
 
                                                                    
 
                                                                    Inbound
                                                                    
+
                                                                    Inbound
                                                                    
 
                                                                    TCP
                                                                    
+
                                                                    TCP
                                                                    
 
                                                                    IPv4
                                                                    
+
                                                                    IPv4
                                                                    
 
                                                                    9092
                                                                    
+
                                                                    9092
                                                                    
 
                                                                    0.0.0.0/0
                                                                    
+
                                                                    IP address or IP address group of the Kafka client
                                                                    
 
                                                                    Accessing a Kafka instance over a private network within a VPC (in plaintext)
                                                                    
+
                                                                    Accessing a Kafka instance over a private network within a VPC (in plaintext)
                                                                    
                                                                     		
 
                                                                    Inbound
                                                                    
+
                                                                    Inbound
                                                                    
 
                                                                    TCP
                                                                    
+
                                                                    TCP
                                                                    
 
                                                                    IPv4
                                                                    
+
                                                                    IPv4
                                                                    
 
                                                                    9093
                                                                    
+
                                                                    9093
                                                                    
 
                                                                    0.0.0.0/0
                                                                    
+
                                                                    IP address or IP address group of the Kafka client
                                                                    
 
                                                                    Accessing a Kafka instance over a private network within a VPC (in ciphertext)
                                                                    
+
                                                                    Accessing a Kafka instance over a private network within a VPC (in ciphertext)
                                                                    
                                                                     		
 
                                                                    
                                                                     
 
                                                                    
 
                                                                    
-
                                                                     
                                                                    After a security group is created, its default inbound rule allows communication among ECSs within the security group and its default outbound rule allows all outbound traffic. In this case, you can access a Kafka instance within a VPC, and do not need to add rules according to Table 4.
                                                                    
-
                                                                    
 
 
                                                                    
 
-
                                                                    Enabling IPv6 Public Network 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. In the Connection area, obtain IPv6 Instance Address (Private Network). In the Network area, view and record the VPC and subnet.
                                                                    6. Click  in the upper left corner of the management console and choose Network > Elastic IP. The EIPs page is displayed.
                                                                    7. Choose Shared Bandwidths in the navigation pane.
                                                                    8. Apply for a shared bandwidth. For details, see Assigning a Shared Bandwidth.
                                                                      If a shared bandwidth already exists, you do not need to apply for one again.
                                                                      
-
                                                                    9. In the row containing the shared bandwidth, click Add Public IP Address.
                                                                    10. Set the parameters as described in Table 5 and click OK.
                                                                      
-
                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                      Table 5 Adding public IP parameters
                                                                      Parameter
                                                                      
-
                                                                      Description
                                                                      
-
                                                                      Public IP Address
                                                                      
-
                                                                      Select IPv6 Address.
                                                                      
-
                                                                      VPC
                                                                      
-
                                                                      Select the VPC in 5 from the drop-down list.
                                                                      
-
                                                                      Subnet
                                                                      
-
                                                                      Select the subnet in 5 from the drop-down list. Select all IPv6 addresses in 5.
                                                                      
-
                                                                      
-
                                                                      
-
                                                                    11. After the shared bandwidth is configured, set a Kafka instance security group with the rules described in Table 6.
                                                                      
-
                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                      Table 6 Kafka instance security group rules (IPv6 access)
                                                                      Direction
                                                                      
-
                                                                      Protocol
                                                                      
-
                                                                      Type
                                                                      
-
                                                                      Port
                                                                      
-
                                                                      Source
                                                                      
-
                                                                      Description
                                                                      
-
                                                                      Inbound
                                                                      
-
                                                                      TCP
                                                                      
-
                                                                      IPv6
                                                                      
-
                                                                      9192
                                                                      
-
                                                                      ::/0
                                                                      
-
                                                                      Accessing a Kafka instance using IPv6 addresses (without SSL encryption)
                                                                      
-
                                                                      Inbound
                                                                      
-
                                                                      TCP
                                                                      
-
                                                                      IPv6
                                                                      
-
                                                                      9193
                                                                      
-
                                                                      ::/0
                                                                      
-
                                                                      Accessing a Kafka instance using IPv6 addresses (with SSL encryption)
                                                                      
-
                                                                      
-
                                                                      
-
                                                                       
                                                                      • When a client is connected to a Kafka instance over an IPv6 public network, the Kafka connection addresses are the IPv6 addresses in Instance Address (Private Network).
                                                                      • To access a Kafka instance over an IPv6 public network, add the client NIC to the shared bandwidth. Shared bandwidths are using a connected network. The shared bandwidth of the client NIC and that of the Kafka instance can be different.
                                                                      
-
                                                                      
-
                                                                    
-
                                                                    
 
                                                                    Disabling IPv6 Public Access
                                                                    Remove the IPv6 addresses of a Kafka instance from the shared bandwidth. For details, see Removing EIPs from a Shared Bandwidth.
                                                                    
 
                                                                    
 
diff --git a/docs/dms/umn/kafka-ug-0723001.html b/docs/dms/umn/kafka-ug-0723001.html
index b0a346425..4fe12cd18 100644
--- a/docs/dms/umn/kafka-ug-0723001.html
+++ b/docs/dms/umn/kafka-ug-0723001.html
@@ -11,10 +11,12 @@
 
 
                                                                  11. Application Scenarios
                                                                    
 
                                                                    12. 
-
                                                                  12. Specifications
                                                                    
+
                                                                  13. Kafka Instance Specifications
                                                                    
 
                                                                    14. 
 
                                                                  14. Comparing Single-node and Cluster Kafka Instances
                                                                    
 
                                                                    15. 
+
                                                                  15. Comparing Kafka and RocketMQ
                                                                    
+
                                                                    16. 
 
                                                                  16. Comparing DMS for Kafka and Open-Source Kafka
                                                                    
 
                                                                    17. 
 
                                                                  17. Notes and Constraints
                                                                    
@@ -23,7 +25,7 @@
 
                                                                    18. 
 
                                                                  18. Basic Concepts
                                                                    
 
                                                                    19. 
-
                                                                  19. Permission
                                                                    
+
                                                                  20. Permissions
                                                                    
 
                                                                    21. 
 
 
diff --git a/docs/dms/umn/kafka-ug-0723006.html b/docs/dms/umn/kafka-ug-0723006.html
index ddfaeafc5..f4ddd1391 100644
--- a/docs/dms/umn/kafka-ug-0723006.html
+++ b/docs/dms/umn/kafka-ug-0723006.html
@@ -18,6 +18,8 @@
 
 
                                                                  21. Troubleshooting Error "Topic {{topic_name}} not present in metadata after 60000 ms" During Message Production or Consumption
                                                                    
 
                                                                    22. 
+
                                                                  22. Flink 1.15 Consumption Progress Submission Failure
                                                                    
+
                                                                    23. 
 
 
 
diff --git a/docs/dms/umn/kafka-ug-180413002.html b/docs/dms/umn/kafka-ug-180413002.html
index ca6a59e8c..1b61c667c 100644
--- a/docs/dms/umn/kafka-ug-180413002.html
+++ b/docs/dms/umn/kafka-ug-180413002.html
@@ -1,66 +1,79 @@
 
 
 
                                                                    Kafka Metrics
                                                                    
-
                                                                    Introduction
                                                                    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 metrics and alarms, or view Kafka instance metrics on the Monitoring page of the DMS console.
                                                                    
+
                                                                    Introduction
                                                                    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 metrics and alarms, or view Kafka instance metrics on the Monitoring page of the DMS console.
                                                                    
 
                                                                    For example, you can call the API to query the monitoring data of the Disk Capacity Usage metric.
                                                                    
 
                                                                    
 
                                                                    Namespace
                                                                    SYS.DMS
                                                                    
 
                                                                    
 
                                                                    Instance Metrics
                                                                    
-
                                                                    Table 1 Instance metrics
                                                                    Metric ID
                                                                    
+
                                                                    
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
@@ -70,315 +83,381 @@
 
                                                                    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.
                                                                    
 
-
                                                                    Table 1 Instance metrics
                                                                    Metric ID
                                                                    
 
                                                                    Metric Name
                                                                    
+
                                                                    Metric Name
                                                                    
 
                                                                    Description
                                                                    
+
                                                                    Description
                                                                    
 
                                                                    Value Range
                                                                    
+
                                                                    Value Range
                                                                    
 
                                                                    Monitored Object
                                                                    
+
                                                                    Unit
                                                                    
 
                                                                    Monitoring Period (Raw Data)
                                                                    
+
                                                                    Conversion Rule
                                                                    
+
                                                                    Monitored Object (Dimension)
                                                                    
+
                                                                    Monitoring Period (Raw Data)
                                                                    
                                                                     		
 
                                                                    
 
                                                                    current_partitions
                                                                    
+
                                                                    current_partitions
                                                                    
 
                                                                    Partitions
                                                                    
+
                                                                    Partitions
                                                                    
 
                                                                    Number of used partitions in the instance
                                                                    
-
                                                                    Unit: Count
                                                                    
+
                                                                    Number of used partitions in the instance
                                                                    
 
                                                                    0–100,000
                                                                    
+
                                                                    0–100,000
                                                                    
 
                                                                    Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    current_topics
                                                                    
+
                                                                    current_topics
                                                                    
 
                                                                    Topics
                                                                    
+
                                                                    Topics
                                                                    
 
                                                                    Number of created topics in the instance
                                                                    
-
                                                                    Unit: Count
                                                                    
+
                                                                    Number of created topics in the instance
                                                                    
 
                                                                    0–100,000
                                                                    
+
                                                                    0–100,000
                                                                    
 
                                                                    Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    group_msgs
                                                                    
+
                                                                    group_msgs
                                                                    
 
                                                                    Accumulated Messages
                                                                    
+
                                                                    Accumulated Messages
                                                                    
 
                                                                    Total number of accumulated messages in all consumer groups of the instance
                                                                    
-
                                                                    Unit: Count
                                                                    
+
                                                                    Total number of accumulated messages in all consumer groups of the instance
                                                                    
 
                                                                    0–1,000,000,000
                                                                    
+
                                                                    0–1,000,000,000
                                                                    
 
                                                                    Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    
 
                                                                    Table 2 Broker metrics
                                                                    Metric ID
                                                                    
+
                                                                    
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
@@ -386,130 +465,148 @@
 
                                                                    Topic Metrics
                                                                    
-
                                                                    Table 2 Broker metrics
                                                                    Metric ID
                                                                    
 
                                                                    Metric Name
                                                                    
+
                                                                    Metric Name
                                                                    
 
                                                                    Description
                                                                    
+
                                                                    Description
                                                                    
 
                                                                    Value Range
                                                                    
+
                                                                    Value Range
                                                                    
 
                                                                    Monitored Object
                                                                    
+
                                                                    Unit
                                                                    
 
                                                                    Monitoring Period (Raw Data)
                                                                    
+
                                                                    Conversion Rule
                                                                    
+
                                                                    Monitored Object (Dimension)
                                                                    
+
                                                                    Monitoring Period (Raw Data)
                                                                    
                                                                     		
 
                                                                    
 
                                                                    broker_data_size
                                                                    
+
                                                                    broker_data_size
                                                                    
 
                                                                    Message Size
                                                                    
+
                                                                    Message Size
                                                                    
 
                                                                    Total size of messages in the broker
                                                                    
-
                                                                    Unit: byte, KB, MB, GB, TB or PB
                                                                    
+
                                                                    Total size of messages in the broker
                                                                    
 
                                                                    0–5,000,000,000,000
                                                                    
+
                                                                    0–5,000,000,000,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Byte
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_messages_in_rate
                                                                    
+
                                                                    broker_messages_in_rate
                                                                    
 
                                                                    Message Creation Rate
                                                                    
+
                                                                    Message Creation Rate
                                                                    
 
                                                                    Number of messages created per second
                                                                    
-
                                                                    Unit: count/s
                                                                    
+
                                                                    Number of messages created per second
                                                                    
 
                                                                    0–500,000
                                                                    
+
                                                                    0–500,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Count/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_bytes_out_rate
                                                                    
+
                                                                    broker_bytes_out_rate
                                                                    
 
                                                                    Message Retrieval
                                                                    
+
                                                                    Message Retrieval
                                                                    
 
                                                                    Number of bytes retrieved per second
                                                                    
-
                                                                    Unit: byte/s, KB/s, MB/s, or GB/s
                                                                    
+
                                                                    Number of bytes retrieved per second
                                                                    
 
                                                                    0–500,000,000
                                                                    
+
                                                                    0–500,000,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_bytes_in_rate
                                                                    
+
                                                                    broker_bytes_in_rate
                                                                    
 
                                                                    Message Creation
                                                                    
+
                                                                    Message Creation
                                                                    
 
                                                                    Number of bytes created per second
                                                                    
-
                                                                    Unit: byte/s, KB/s, MB/s, or GB/s
                                                                    
+
                                                                    Number of bytes created per second
                                                                    
 
                                                                    0–500,000,000
                                                                    
+
                                                                    0–500,000,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    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
                                                                    
-
                                                                    Unit: byte/s, KB/s, MB/s, or GB/s
                                                                    
-
                                                                     NOTE: 
                                                                    You can view this metric if public access has been enabled and EIPs have been assigned to the instance.
                                                                    
-
                                                                    
+
                                                                    Inbound traffic over public networks per second
                                                                    
+
                                                                    You can view this metric if public access has been enabled for the instance.
                                                                    
 
                                                                    0–500,000,000
                                                                    
+
                                                                    0–500,000,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    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
                                                                    
-
                                                                    Unit: byte/s, KB/s, MB/s, or GB/s
                                                                    
-
                                                                     NOTE: 
                                                                    You can view this metric if public access has been enabled and EIPs have been assigned to the instance.
                                                                    
-
                                                                    
+
                                                                    Outbound traffic over public networks per second
                                                                    
+
                                                                    You can view this metric if public access has been enabled for the instance.
                                                                    
 
                                                                    0–500,000,000
                                                                    
+
                                                                    0–500,000,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    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
                                                                    
-
                                                                    Unit: ms
                                                                    
+
                                                                    Average time that the broker spends processing message retrieval requests
                                                                    
 
                                                                    0–10,000
                                                                    
+
                                                                    0–10,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    ms
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    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
                                                                    
-
                                                                    Unit: ms
                                                                    
+
                                                                    Average time that the broker spends processing message creation requests
                                                                    
 
                                                                    0–10,000
                                                                    
+
                                                                    0–10,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    ms
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    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
                                                                    
-
                                                                    Unit: %
                                                                    
+
                                                                    Average load of each CPU core of the Kafka VM
                                                                    
 
                                                                    0–20
                                                                    
+
                                                                    0–20
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    N/A
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_disk_usage
                                                                    
+
                                                                    broker_disk_usage
                                                                    
 
                                                                    Disk Capacity Usage
                                                                    
+
                                                                    Disk Capacity Usage
                                                                    
 
                                                                    Disk usage of the Kafka VM
                                                                    
-
                                                                    Unit: %
                                                                    
+
                                                                    Disk usage of the Kafka VM
                                                                    
 
                                                                    0–100
                                                                    
+
                                                                    0–100
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    %
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_memory_usage
                                                                    
+
                                                                    broker_memory_usage
                                                                    
 
                                                                    Memory Usage
                                                                    
+
                                                                    Memory Usage
                                                                    
 
                                                                    Memory usage of the Kafka VM 
                                                                    
-
                                                                    Unit: %
                                                                    
+
                                                                    Memory usage of the Kafka VM 
                                                                    
 
                                                                    0–100
                                                                    
+
                                                                    0–100
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    %
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_heap_usage
                                                                    
+
                                                                    broker_heap_usage
                                                                    
 
                                                                    JVM Heap Memory Usage of Kafka
                                                                    
+
                                                                    JVM Heap Memory Usage of JVM
                                                                    
 
                                                                    Heap memory usage of the Kafka JVM
                                                                    
-
                                                                    Unit: %
                                                                    
+
                                                                    Heap memory usage of the Kafka JVM
                                                                    
 
                                                                    0–100
                                                                    
+
                                                                    0–100
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    %
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    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
                                                                    
+
                                                                    N/A
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_connections
                                                                    
+
                                                                    broker_connections
                                                                    
 
                                                                    Connections
                                                                    
+
                                                                    Connections
                                                                    
 
                                                                    Total number of TCP connections on the Kafka broker
                                                                    
-
                                                                    Unit: count
                                                                    
+
                                                                    Total number of TCP connections on the Kafka broker
                                                                    
 
                                                                    0–65,535
                                                                    
+
                                                                    0–65,535
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_cpu_usage
                                                                    
+
                                                                    broker_cpu_usage
                                                                    
 
                                                                    CPU Usage
                                                                    
+
                                                                    CPU Usage
                                                                    
 
                                                                    CPU usage of the Kafka VM
                                                                    
-
                                                                    Unit: %
                                                                    
+
                                                                    CPU usage of the Kafka VM
                                                                    
 
                                                                    0–100
                                                                    
+
                                                                    0–100
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    %
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    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
                                                                    
-
                                                                    Unit: ms
                                                                    
+
                                                                    Average time for each disk I/O read in the monitoring period
                                                                    
 
                                                                    > 0
                                                                    
+
                                                                    > 0
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    ms
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    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
                                                                    
-
                                                                    Unit: ms
                                                                    
+
                                                                    Average time for each disk I/O write in the monitoring period
                                                                    
 
                                                                    > 0
                                                                    
+
                                                                    > 0
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    ms
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_total_bytes_in_rate
                                                                    
+
                                                                    broker_total_bytes_in_rate
                                                                    
 
                                                                    Inbound Traffic
                                                                    
+
                                                                    Inbound Traffic
                                                                    
 
                                                                    Inbound traffic per second
                                                                    
-
                                                                    Unit: byte/s
                                                                    
+
                                                                    Inbound traffic per second
                                                                    
 
                                                                    0–1,000,000,000
                                                                    
+
                                                                    0–1,000,000,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_total_bytes_out_rate
                                                                    
+
                                                                    broker_total_bytes_out_rate
                                                                    
 
                                                                    Outbound Traffic
                                                                    
+
                                                                    Outbound Traffic
                                                                    
 
                                                                    Outbound traffic per second
                                                                    
-
                                                                    Unit: byte/s
                                                                    
+
                                                                    Outbound traffic per second
                                                                    
 
                                                                    0–1,000,000,000
                                                                    
+
                                                                    0–1,000,000,000
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_disk_read_rate
                                                                    
+
                                                                    broker_disk_read_rate
                                                                    
 
                                                                    Disk Read Speed
                                                                    
+
                                                                    Disk Read Speed
                                                                    
 
                                                                    Read traffic on the disk
                                                                    
-
                                                                    Unit: byte/s, KB/s, MB/s, or GB/s
                                                                    
+
                                                                    Read traffic on the disk
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    broker_disk_write_rate
                                                                    
+
                                                                    broker_disk_write_rate
                                                                    
 
                                                                    Disk Write Speed
                                                                    
+
                                                                    Disk Write Speed
                                                                    
 
                                                                    Write traffic on the disk
                                                                    
-
                                                                    Unit: byte/s, KB/s, MB/s, or GB/s
                                                                    
+
                                                                    Write traffic on the disk
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Kafka instance broker
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Kafka instance broker
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    
                                                                     
 
 
                                                                    Table 3 Topic metrics
                                                                    Metric ID
                                                                    
+
                                                                    
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
@@ -517,195 +614,229 @@
 
                                                                    Consumer Group Metrics
                                                                    
-
                                                                    Table 3 Topic metrics
                                                                    Metric ID
                                                                    
 
                                                                    Metric Name
                                                                    
+
                                                                    Metric Name
                                                                    
 
                                                                    Description
                                                                    
+
                                                                    Description
                                                                    
 
                                                                    Value Range
                                                                    
+
                                                                    Value Range
                                                                    
 
                                                                    Monitored Object
                                                                    
+
                                                                    Unit
                                                                    
 
                                                                    Monitoring Period (Raw Data)
                                                                    
+
                                                                    Conversion Rule
                                                                    
+
                                                                    Monitored Object (Dimension)
                                                                    
+
                                                                    Monitoring Period (Raw Data)
                                                                    
                                                                     		
 
                                                                    
 
                                                                    topic_bytes_in_rate
                                                                    
+
                                                                    topic_bytes_in_rate
                                                                    
 
                                                                    Message Creation
                                                                    
+
                                                                    Message Creation
                                                                    
 
                                                                    Number of bytes created per second
                                                                    
-
                                                                    Unit: byte/s, KB/s, MB/s, or GB/s
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
-
                                                                    
+
                                                                    Number of bytes created per second
                                                                    
+
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
 
                                                                    0–500,000,000
                                                                    
+
                                                                    0–500,000,000
                                                                    
 
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    topic_bytes_out_rate
                                                                    
+
                                                                    topic_bytes_out_rate
                                                                    
 
                                                                    Message Retrieval
                                                                    
+
                                                                    Message Retrieval
                                                                    
 
                                                                    Number of bytes retrieved per second
                                                                    
-
                                                                    Unit: byte/s, KB/s, MB/s, or GB/s
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
-
                                                                    
+
                                                                    Number of bytes retrieved per second
                                                                    
+
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
 
                                                                    0–500,000,000
                                                                    
+
                                                                    0–500,000,000
                                                                    
 
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    Byte/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    topic_data_size
                                                                    
+
                                                                    topic_data_size
                                                                    
 
                                                                    Message Size
                                                                    
+
                                                                    Message Size
                                                                    
 
                                                                    Total size of messages in the queue
                                                                    
-
                                                                    Unit: byte, KB, MB, GB, TB or PB
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
-
                                                                    
+
                                                                    Total size of messages in the queue
                                                                    
+
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
 
                                                                    0–5,000,000,000,000
                                                                    
+
                                                                    0–5,000,000,000,000
                                                                    
 
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    Byte
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    1024(IEC)
                                                                    
+
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    topic_messages
                                                                    
+
                                                                    topic_messages
                                                                    
 
                                                                    Total Messages
                                                                    
+
                                                                    Total Messages
                                                                    
 
                                                                    Total number of messages in the queue
                                                                    
-
                                                                    Unit: count
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
-
                                                                    
+
                                                                    Total number of messages in the queue
                                                                    
+
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    topic_messages_in_rate
                                                                    
+
                                                                    topic_messages_in_rate
                                                                    
 
                                                                    Message Creation Rate
                                                                    
+
                                                                    Message Creation Rate
                                                                    
 
                                                                    Number of messages created per second
                                                                    
-
                                                                    Unit: count/s
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
-
                                                                    
+
                                                                    Number of messages created per second
                                                                    
+
                                                                    This metric is available only when Monitoring Type is set to Basic monitoring on the By Topic tab page.
                                                                    
 
                                                                    0–500,000
                                                                    
+
                                                                    0–500,000
                                                                    
 
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    Count/s
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    partition_messages
                                                                    
+
                                                                    partition_messages
                                                                    
 
                                                                    Partition Messages
                                                                    
+
                                                                    Partition Messages
                                                                    
 
                                                                    Total number of messages in the partition
                                                                    
-
                                                                    Unit: count
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Monitoring Type is set to Partition monitoring on the By Topic tab page.
                                                                    
-
                                                                    
+
                                                                    Total number of messages in the partition
                                                                    
+
                                                                    This metric is available only when Monitoring Type is set to Partition monitoring on the By Topic tab page.
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    produced_messages
                                                                    
+
                                                                    produced_messages
                                                                    
 
                                                                    Created Messages
                                                                    
+
                                                                    Created Messages
                                                                    
 
                                                                    Number of messages that have been created
                                                                    
-
                                                                    Unit: count
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Monitoring Type is set to Partition monitoring on the By Topic tab page.
                                                                    
-
                                                                    
+
                                                                    Number of messages that have been created
                                                                    
+
                                                                    This metric is available only when Monitoring Type is set to Partition monitoring on the By Topic tab page.
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Topic in a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    
                                                                     
 
 
                                                                    Table 4 Consumer group metrics
                                                                    Metric ID
                                                                    
+
                                                                    
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
                                                                    Table 4 Consumer group metrics
                                                                    Metric ID
                                                                    
 
                                                                    Metric Name
                                                                    
+
                                                                    Metric Name
                                                                    
 
                                                                    Description
                                                                    
+
                                                                    Description
                                                                    
 
                                                                    Value Range
                                                                    
+
                                                                    Value Range
                                                                    
 
                                                                    Monitored Object
                                                                    
+
                                                                    Unit
                                                                    
 
                                                                    Monitoring Period (Raw Data)
                                                                    
+
                                                                    Conversion Rule
                                                                    
+
                                                                    Monitored Object (Dimension)
                                                                    
+
                                                                    Monitoring Period (Raw Data)
                                                                    
                                                                     		
 
                                                                    
 
                                                                    messages_consumed
                                                                    
+
                                                                    messages_consumed
                                                                    
 
                                                                    Retrieved Messages
                                                                    
+
                                                                    Retrieved Messages
                                                                    
 
                                                                    Number of messages that have been retrieved in the consumer group
                                                                    
-
                                                                    Unit: count
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Topic is set to a specific topic name and Monitoring Type is set to Partition monitoring on the By Consumer Group tab page.
                                                                    
-
                                                                    
+
                                                                    Number of messages that have been retrieved in the consumer group
                                                                    
+
                                                                    This metric is available only when Topic is set to a specific topic name and Monitoring Type is set to Partition monitoring on the By Consumer Group tab page.
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    messages_remained
                                                                    
+
                                                                    messages_remained
                                                                    
 
                                                                    Available Messages
                                                                    
+
                                                                    Available Messages
                                                                    
 
                                                                    Number of messages that can be retrieved in the consumer group
                                                                    
-
                                                                    Unit: count
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Topic is set to a specific topic name and Monitoring Type is set to Partition monitoring on the By Consumer Group tab page.
                                                                    
-
                                                                    
+
                                                                    Number of messages that can be retrieved in the consumer group
                                                                    
+
                                                                    This metric is available only when Topic is set to a specific topic name and Monitoring Type is set to Partition monitoring on the By Consumer Group tab page.
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    topic_messages_remained
                                                                    
+
                                                                    topic_messages_remained
                                                                    
 
                                                                    Topic Available Messages
                                                                    
+
                                                                    Topic Available Messages
                                                                    
 
                                                                    Number of remaining messages that can be retrieved from the specified topic in the consumer group
                                                                    
-
                                                                    Unit: Count
                                                                    
-
                                                                     NOTE: 
                                                                    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.
                                                                    
-
                                                                    
+
                                                                    Number of remaining messages that can be retrieved from the specified topic in the consumer group
                                                                    
+
                                                                    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.
                                                                    
 
                                                                    0 to 263–1
                                                                    
+
                                                                    0 to 263–1
                                                                    
 
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    topic_messages_consumed
                                                                    
+
                                                                    topic_messages_consumed
                                                                    
 
                                                                    Topic Retrieved Messages
                                                                    
+
                                                                    Topic Retrieved Messages
                                                                    
 
                                                                    Number of messages that have been retrieved from the specified topic in the consumer group
                                                                    
-
                                                                    Unit: Count
                                                                    
-
                                                                     NOTE: 
                                                                    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.
                                                                    
-
                                                                    
+
                                                                    Number of messages that have been retrieved from the specified topic in the consumer group
                                                                    
+
                                                                    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.
                                                                    
 
                                                                    0 to 263–1
                                                                    
+
                                                                    0 to 263–1
                                                                    
 
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    consumer_messages_remained
                                                                    
+
                                                                    consumer_messages_remained
                                                                    
 
                                                                    Consumer Available Messages
                                                                    
+
                                                                    Consumer Available Messages
                                                                    
 
                                                                    Number of remaining messages that can be retrieved in the consumer group
                                                                    
-
                                                                    Unit: Count
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Topic is set to All topics on the By Consumer Group tab page.
                                                                    
-
                                                                    
+
                                                                    Number of remaining messages that can be retrieved in the consumer group
                                                                    
+
                                                                    This metric is available only when Topic is set to All topics on the By Consumer Group tab page.
                                                                    
 
                                                                    0 to 263–1
                                                                    
+
                                                                    0 to 263–1
                                                                    
 
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    consumer_messages_consumed
                                                                    
+
                                                                    consumer_messages_consumed
                                                                    
 
                                                                    Consumer Retrieved Messages
                                                                    
+
                                                                    Consumer Retrieved Messages
                                                                    
 
                                                                    Number of messages that have been retrieved in the consumer group
                                                                    
-
                                                                    Unit: Count
                                                                    
-
                                                                     NOTE: 
                                                                    This metric is available only when Topic is set to All topics on the By Consumer Group tab page.
                                                                    
-
                                                                    
+
                                                                    Number of messages that have been retrieved in the consumer group
                                                                    
+
                                                                    This metric is available only when Topic is set to All topics on the By Consumer Group tab page.
                                                                    
 
                                                                    0 to 263–1
                                                                    
+
                                                                    0 to 263–1
                                                                    
 
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Consumer group of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    
                                                                     
 
                                                                    
 
                                                                    
 
-
                                                                    Smart Connect Metrics
                                                                    
-
                                                                    Table 5 Smart Connect metrics
                                                                    Metric ID
                                                                    
+
                                                                    Smart Connect Metrics
                                                                    Smart Connect metrics are only available for cluster instances.
                                                                    
+
+
                                                                    
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
-
-
-
-
-
-
+
+
                                                                    Table 5 Smart Connect metrics
                                                                    Metric ID
                                                                    
 
                                                                    Metric Name
                                                                    
+
                                                                    Metric Name
                                                                    
 
                                                                    Description
                                                                    
+
                                                                    Description
                                                                    
 
                                                                    Value Range
                                                                    
+
                                                                    Value Range
                                                                    
 
                                                                    Monitored Object
                                                                    
+
                                                                    Unit
                                                                    
 
                                                                    Monitoring Period (Raw Data)
                                                                    
+
                                                                    Conversion Rule
                                                                    
+
                                                                    Monitored Object (Dimension)
                                                                    
+
                                                                    Monitoring Period (Raw Data)
                                                                    
                                                                     		
 
                                                                    
 
                                                                    kafka_wait_synchronize_data
                                                                    
+
                                                                    kafka_wait_synchronize_data
                                                                    
 
                                                                    Kafka Data to Sync
                                                                    
+
                                                                    Kafka Data to Sync
                                                                    
 
                                                                    Data to synchronize in the Kafka migration task
                                                                    
-
                                                                    Unit: count
                                                                    
+
                                                                    Data to synchronize in the Kafka migration task
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Smart Connect task of a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Smart Connect task of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    kafka_synchronize_rate
                                                                    
+
                                                                    kafka_synchronize_rate
                                                                    
 
                                                                    Kafka Data Synced per Minute
                                                                    
+
                                                                    Kafka Data Synced per Minute
                                                                    
 
                                                                    Data synchronized per minute in the Kafka migration task
                                                                    
-
                                                                    Unit: count
                                                                    
+
                                                                    Data synchronized per minute in the Kafka migration task
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Smart Connect task of a Kafka instance
                                                                    
+
                                                                    Count
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Smart Connect task of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    task_status
                                                                    
+
                                                                    task_status
                                                                    
 
                                                                    Task Status
                                                                    
+
                                                                    Task Status
                                                                    
 
                                                                    Status of the current task
                                                                    
+
                                                                    Status of the current task
                                                                    
 
                                                                    • 0: abnormal
                                                                    • 1: normal
                                                                    
+
                                                                    • 0: abnormal
                                                                    • 1: normal
                                                                    
 
                                                                    Smart Connect task of a Kafka instance
                                                                    
+
                                                                    N/A
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Smart Connect task of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    message_delay
                                                                    
+
                                                                    message_delay
                                                                    
 
                                                                    Message Delay
                                                                    
+
                                                                    Message Delay
                                                                    
 
                                                                    Time elapsed between when a message is sent from the source and received by the target
                                                                    
-
                                                                    Unit: ms
                                                                    
+
                                                                    Time elapsed between when a message is sent from the source and received by the target
                                                                    
 
                                                                    ≥ 0
                                                                    
+
                                                                    ≥ 0
                                                                    
 
                                                                    Smart Connect task of a Kafka instance
                                                                    
+
                                                                    ms
                                                                    
 
                                                                    1 minute
                                                                    
+
                                                                    N/A
                                                                    
+
                                                                    Smart Connect task of a Kafka instance
                                                                    
+
                                                                    1 minute
                                                                    
                                                                     		
 
                                                                    
                                                                     
 
                                                                    
 
                                                                    
-
                                                                     
                                                                    • 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.
                                                                    
-
                                                                    
+
                                                                    Precautions:
                                                                    
+
                                                                    • 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
                                                                    
 
                                                                    
-
+
+
+
+
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
@@ -125,10 +125,9 @@
 
                                                                    Key
                                                                    
diff --git a/docs/dms/umn/kafka-ug-180418002.html b/docs/dms/umn/kafka-ug-180418002.html
index 523b978b8..20ecbfaec 100644
--- a/docs/dms/umn/kafka-ug-180418002.html
+++ b/docs/dms/umn/kafka-ug-180418002.html
@@ -234,28 +234,154 @@
 
 
                                                                    kafka
                                                                    
 
                                                                    createConnectorTaskSuccess
                                                                    
+
                                                                    CreateConnectorSuccess
                                                                    
+
                                                                    Failing to enable Smart Connect
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    createConnectorFailure
                                                                    
                                                                     		
 
                                                                    
 
                                                                    Successfully creating a Smart Connect task
                                                                    
                                                                     		
 
                                                                    kafka
                                                                    
 
                                                                    createConnectorSinkTaskSuccess
                                                                    
-
                                                                    Failing to enable Smart Connect
                                                                    
-
                                                                    kafka
                                                                    
-
                                                                    createConnectorTaskFailure
                                                                    
+
                                                                    createConnectorTaskSuccess
                                                                    
                                                                     		
 
                                                                    
 
                                                                    Failing to create a Smart Connect task
                                                                    
                                                                     		
 
                                                                    kafka
                                                                    
 
                                                                    createConnectorSinkTaskFailure
                                                                    
+
                                                                    createConnectorTaskFailure
                                                                    
+
                                                                    Successfully modifying a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    putConnectorTaskSuccess
                                                                    
+
                                                                    Failing to modify a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    putConnectorTaskFailure
                                                                    
+
                                                                    Successfully deleting a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    deleteConnectorTaskSuccess
                                                                    
+
                                                                    Failing to delete a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    deleteConnectorTaskFailure
                                                                    
+
                                                                    Successfully restarting a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    restartConnectorSuccess
                                                                    
+
                                                                    Failing to restart a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    restartConnectorFailure
                                                                    
+
                                                                    Successfully pausing a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    pauseConnectorSuccess
                                                                    
+
                                                                    Failing to pause a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    pauseConnectorFailure
                                                                    
+
                                                                    Successfully starting a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    resumeConnectorSuccess
                                                                    
+
                                                                    Failing to start a Smart Connect task
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    resumeConnectorFailure
                                                                    
+
                                                                    Connectivity check succeeded
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    ValidateConnectorConnectivitySuccess
                                                                    
+
                                                                    Connectivity check failed
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    ValidateConnectorConnectivityFailure
                                                                    
+
                                                                    Successfully disabling Smart Connect
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    DeleteConnectorSuccess
                                                                    
+
                                                                    Failing to disable Smart Connect
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    DeleteConnectorFailure
                                                                    
+
                                                                    Successfully creating a connector
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    createConnectorNodeTaskSuccess
                                                                    
+
                                                                    Failing to create a connector
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    createConnectorNodeTaskFailure
                                                                    
+
                                                                    Successfully deleting a connector
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    deleteConnectorNodeTaskSuccess
                                                                    
+
                                                                    Failing to delete a connector
                                                                    
+
                                                                    kafka
                                                                    
+
                                                                    deleteConnectorNodeTaskFailure
                                                                    
                                                                     		
 
                                                                    
 
                                                                    Successfully creating a topic for a Kafka instance
                                                                    
diff --git a/docs/dms/umn/kafka-ug-180524001.html b/docs/dms/umn/kafka-ug-180524001.html
index 48433c9e9..1a282fa1d 100644
--- a/docs/dms/umn/kafka-ug-180524001.html
+++ b/docs/dms/umn/kafka-ug-180524001.html
@@ -68,7 +68,7 @@
                                                                     		
 
                                                                    Instance
                                                                    
 
                                                                    Alarm threshold: original value > 90% of the maximum allowed number of partitions. The partition limit varies depending on instance specifications. For details, see Specifications.
                                                                    
+
                                                                    Alarm threshold: original value > 90% of the maximum allowed number of partitions. The partition limit varies depending on instance specifications. For details, see Cluster Kafka Instances.
                                                                    
 
                                                                    Number of consecutive periods: 1
                                                                    
 
                                                                    Alarm severity: major
                                                                    
                                                                     		
 
                                                                    
 
                                                                    
-
                                                                    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. 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.
                                                                      
+
                                                                      Configuring Kafka Alarm Rules
                                                                      The following section describes how to configure alarm rules for a specified Kafka instance.
                                                                      
+
                                                                      1. Log in to the console.
                                                                      2. Click  in the upper left corner to select the region where your instance is located.
                                                                      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 Alarm Rules.
                                                                        
 
                                                                        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.
                                                                          
diff --git a/docs/dms/umn/kafka-ug-180604012.html b/docs/dms/umn/kafka-ug-180604012.html
index 4212ba46d..c5d949b3f 100644
--- a/docs/dms/umn/kafka-ug-180604012.html
+++ b/docs/dms/umn/kafka-ug-180604012.html
@@ -3,7 +3,7 @@
 
                                                                          Kafka Network Connection Conditions
                                                                          
 
                                                                          A client can connect to a Kafka instance over a public or private network. Notes before using a private network:
                                                                          
 
                                                                          • By default, a client and a Kafka instance are interconnected when they are deployed in a VPC.
                                                                          • If they are not, you need to interconnect them because of isolation among VPCs.
                                                                          
-
                                                                          Table 1 lists how a client can connect to a Kafka instance.
                                                                          
+
                                                                          Table 1 lists how to access a Kafka instance on a client.
                                                                          
 
 
                                                                          
@@ -45,8 +45,8 @@
 
                                                                          Table 1 Access modes
                                                                          Mode
                                                                          
                                                                           		
 
                                                                          
 
                                                                          
-
                                                                          Before connecting a client to a Kafka instance, allow accesses for the following security groups.
                                                                          
-
                                                                           
                                                                          After a security group is created, its default inbound rule allows communication among ECSs within the security group and its default outbound rule allows all outbound traffic. In this case, you can access a Kafka instance within a VPC, and do not need to add rules according to Table 2.
                                                                          
+
                                                                          Before accessing a Kafka instance on a client, configure the following rules in the security group of the instance.
                                                                          
+
                                                                           
                                                                          After a security group is created, its default inbound rule allows communication among ECSs within the security group and its default outbound rule allows all outbound traffic. In this case, you can access a Kafka instance within a VPC, and do not need to add rules according to Table 2.
                                                                          
 
                                                                          
 
 
                                                                          
-
@@ -84,7 +84,7 @@
 
-
@@ -97,7 +97,7 @@
 
-
@@ -110,7 +110,7 @@
 
-
@@ -123,7 +123,7 @@
 
-
@@ -136,7 +136,7 @@
 
-
@@ -151,7 +151,7 @@
 
-
-
-
diff --git a/docs/dms/umn/kafka-ug-180604013.html b/docs/dms/umn/kafka-ug-180604013.html
index dd6b097f5..1447c215b 100644
--- a/docs/dms/umn/kafka-ug-180604013.html
+++ b/docs/dms/umn/kafka-ug-180604013.html
@@ -16,7 +16,7 @@
 
@@ -24,6 +24,7 @@
 
                                                                          Table 2 Security group rules
                                                                          Direction
                                                                          
@@ -71,7 +71,7 @@
 
 
                                                                          9094
                                                                          
 
                                                                          0.0.0.0/0
                                                                          
+
                                                                          IP address or IP address group of the Kafka client
                                                                          
                                                                           		
 
                                                                          Accessing a Kafka instance over a public network (in plaintext)
                                                                          
                                                                           		
 
                                                                          9092
                                                                          
 
                                                                          0.0.0.0/0
                                                                          
+
                                                                          IP address or IP address group of the Kafka client
                                                                          
                                                                           		
 
                                                                          • Accessing a Kafka instance over a private network within a VPC (in plaintext)
                                                                          • Accessing a Kafka instance using a peering connection across VPCs (in plaintext)
                                                                          
                                                                           		
 
                                                                          9192
                                                                          
 
                                                                          ::/0
                                                                          
+
                                                                          IP address or IP address group of the Kafka client
                                                                          
                                                                           		
 
                                                                          Accessing a Kafka instance using IPv6 addresses (without SSL) (private or public network)
                                                                          
                                                                           		
 
                                                                          9095
                                                                          
 
                                                                          0.0.0.0/0
                                                                          
+
                                                                          IP address or IP address group of the Kafka client
                                                                          
                                                                           		
 
                                                                          Accessing a Kafka instance over a public network (in ciphertext)
                                                                          
                                                                           		
 
                                                                          9093
                                                                          
 
                                                                          0.0.0.0/0
                                                                          
+
                                                                          IP address or IP address group of the Kafka client
                                                                          
                                                                           		
 
                                                                          • Accessing a Kafka instance over a private network within a VPC (in ciphertext)
                                                                          • Accessing a Kafka instance using a peering connection across VPCs (in ciphertext)
                                                                          
                                                                           		
 
                                                                          9193
                                                                          
 
                                                                          ::/0
                                                                          
+
                                                                          IP address or IP address group of the Kafka client
                                                                          
                                                                           		
 
                                                                          Accessing a Kafka instance using IPv6 addresses (with SSL) (private or public network)
                                                                          
                                                                           		
 
                                                                          198.19.128.0/17
                                                                          
 
                                                                          Accessing a Kafka instance using a VPC endpoint across VPCs (in cipher- or plaintext)
                                                                          
+
                                                                          Accessing a Kafka instance using a VPC endpoint across VPCs (in ciphertext or plaintext)
                                                                          
                                                                           		
 
                                                                          
 
                                                                          Inbound
                                                                          
@@ -162,9 +162,9 @@
                                                                           		
 
                                                                          9011
                                                                          
 
                                                                          0.0.0.0/0
                                                                          
+
                                                                          IP address or IP address group of the Kafka client
                                                                          
 
                                                                          Accessing a Kafka instance using DNAT (in cipher- or plaintext)
                                                                          
+
                                                                          Accessing a Kafka instance using DNAT (in ciphertext or plaintext)
                                                                          
                                                                           		
 
                                                                          
 
 
                                                                          You need to configure a VPC and subnet for the Kafka instance as required. You can use the current account's existing VPC and subnet, or create new ones.
                                                                          
 
                                                                          Note when creating a VPC and a subnet:
                                                                          
-
                                                                          • The VPC must be created in the same region as the Kafka instance.
                                                                          • The Kafka instance supports IPv6 after it is enabled for the subnet. The Kafka instance with IPv6 enabled can be accessed on a client using IPv6 addresses.
                                                                          
+
                                                                          • The VPC must be created in the same region as the Kafka instance.
                                                                          • The Kafka instance supports IPv6 after it is enabled for the subnet. The instance with IPv6 enabled can be accessed on a client using IPv6 addresses.
                                                                          
                                                                           		
 
                                                                          For details on how to create a VPC and a subnet, see Creating a VPC. If you need to create and use a new subnet in an existing VPC, see Creating a Subnet for the VPC.
                                                                          
 
                                                                          Security group
                                                                          
                                                                           		
 
                                                                          Different Kafka instances can use the same or different security groups.
                                                                          
+
                                                                          The security group must be in the same region as the Kafka instance.
                                                                          
 
                                                                          Before accessing a Kafka instance, configure security groups based on the access mode. For details, see Table 2.
                                                                          
                                                                           		
 
                                                                          For details on how to create a security group, see Creating a Security Group. For details on how to add rules to a security group, see Adding a Security Group Rule.
                                                                          
@@ -50,27 +51,29 @@
 
                                                                          
 
                                                                          
 
                                                                          
-
                                                                          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.
                                                                            
+
                                                                            Notes and Constraints
                                                                            • SASL_SSL cannot be manually configured for instances with IPv6 enabled.
                                                                            • Ciphertext access is unavailable for single-node instances.
                                                                            
+
                                                                            
+
                                                                            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, three, or more AZs as required. The AZs cannot be changed once the instance is created.
                                                                              
 
                                                                            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. 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.
                                                                              
 
                                                                            11. 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. 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.
                                                                                  
-
                                                                                3. For Brokers, specify the broker quantity.
                                                                                4. 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.
                                                                                  
+
                                                                                  • 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. Broker Flavor: Select a broker flavor that best fit your needs.
                                                                                      Maximum number of partitions per broker × 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.
                                                                                      
+
                                                                                    3. For Brokers, specify the broker quantity.
                                                                                    4. 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 type can be high I/O or ultra-high I/O. For more information, see Disk Types and Performance.
                                                                                      
+
                                                                                      The disk type can be high I/O, ultra-high I/O, General Purpose SSD, or Extreme SSD. For more information, see Disk Types and Performance.
                                                                                      
 
                                                                                    5. 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.
                                                                                      
-
                                                                                    6. 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.
                                                                                      
+
                                                                                    7. Capacity Threshold Policy: Policy used when the disk usage reaches the threshold. The capacity threshold is 95%.
                                                                                      • Automatically delete: Messages can be produced and consumed, 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 produced, but existing messages can still be consumed. This policy is suitable for scenarios where no data loss can be tolerated.
                                                                                      
 
                                                                                    
 
                                                                                    Figure 1 Cluster instance specifications
                                                                                    
-
                                                                                  • 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. Broker Flavor: Select a broker flavor that best fit your needs.
                                                                                    3. Brokers: The instance can have only one broker.
                                                                                    4. 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.
                                                                                      
+
                                                                                    5. 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. Broker Flavor: Select a broker flavor that best fit your needs.
                                                                                      3. Brokers: The instance can have only one broker.
                                                                                      4. 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 type can be high I/O or ultra-high I/O. For more information, see Disk Types and Performance.
                                                                                        
+
                                                                                        The disk type can be high I/O, ultra-high I/O, General Purpose SSD, or Extreme SSD. For more information, see Disk Types and Performance.
                                                                                        
 
                                                                                      5. 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.
                                                                                        
-
                                                                                      6. 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.
                                                                                        
+
                                                                                      7. Capacity Threshold Policy: Policy used when the disk usage reaches the threshold. The capacity threshold is 95%.
                                                                                        • Automatically delete: Messages can be produced and consumed, 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 produced, but existing messages can still be consumed. This policy is suitable for scenarios where no data loss can be tolerated.
                                                                                        
 
                                                                                      
 
                                                                                      Figure 2 Single-node instance specifications
                                                                                      
 
                                                                                  
@@ -83,54 +86,54 @@
 
                                                                                  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.
                                                                                  
 
                                                                              
 
                                                                            12. Configure the instance access mode.
                                                                              
-
                                                                              Table 2 Instance access modes
                                                                              Public or Private Network
                                                                              
+
                                                                              
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@@ -141,55 +144,54 @@
 
                                                                              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.
                                                                              
-
                                                                              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.
                                                                              
+
                                                                              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
                                                                              
+
                                                                              
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@@ -199,7 +201,7 @@
 
                                                                               
                                                                              Private Network Access or Public Network Access is not displayed for instances with IPv6 enabled.
                                                                              
 
                                                                            13. Configure Kafka SASL_SSL.
                                                                              This parameter indicates whether to enable SASL authentication when a client connects to the instance. If you enable Kafka SASL_SSL, data will be encrypted for transmission to enhance security.
                                                                              
-
                                                                              This setting is enabled by default. It cannot be changed after the instance is created. If you want to use a different setting, you must create a new instance.
                                                                              
+
                                                                              This setting is enabled by default. It cannot be changed after the instance is created. If you want to use a different setting, you must create an instance.
                                                                              
 
                                                                              After Kafka SASL_SSL is enabled, you can determine whether to enable SASL/PLAIN. If SASL/PLAIN is disabled, the SCRAM-SHA-512 mechanism is used to transmit data. 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 the instance is created.
                                                                              
 
                                                                              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.
                                                                              
@@ -214,65 +216,81 @@
 
                                                                              Enabling Smart Connect creates two brokers.
                                                                              
 
                                                                               
                                                                              Single-node instances do not have this parameter.
                                                                              
 
                                                                              
-
                                                                            14. 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.
                                                                              
+
                                                                            15. Configure Automatic Topic Creation.
                                                                              This setting is disabled by default. You can configure 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.
                                                                              
+
                                                                              For cluster instances, 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. These parameters cannot be modified for single-node instances.
                                                                              
 
-
                                                                              16. 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.
                                                                              
                                                                               		
 
                                                                              Cross-VPC Access Protocol
                                                                              
+
                                                                              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.
                                                                              
+
                                                                              • 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
                                                                              
+
                                                                              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.
                                                                              
+
                                                                              • 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.
                                                                              • 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.
                                                                              
+
                                                                              • 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.
                                                                              
 
                                                                              The username cannot be changed once ciphertext access is enabled.
                                                                              
                                                                               		
 
                                                                              
 
                                                                              Table 4 Topic parameters
                                                                              Parameter
                                                                              
+
                                                                              
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
@@ -282,7 +300,7 @@
 
                                                                              • If you have predefined tags, select a predefined pair of tag key and value. You can click View predefined tags to go to the Tag Management Service (TMS) console and view or create tags.
                                                                              • You can also create new tags by specifying Tag key and Tag value.
                                                                              Up to 20 tags can be added to each Kafka instance. For details about the requirements on tags, see Configuring Kafka Instance Tags.
                                                                            16. Enter a Description of the instance for 0–1024 characters.
                                                                              17. 
-
                                                                            17. Click Create.
                                                                            18. Confirm the instance information, and click Submit.
                                                                            19. Return to the instance list and check whether the Kafka instance has been created.
                                                                              It takes 3 to 15 minutes to create an instance. During this period, the instance status is Creating.
                                                                              
+
                                                                            20. Click Create.
                                                                            21. Confirm the instance information, and click Submit.
                                                                            22. Return to the Kafka instance list and check whether the Kafka instance has been created.
                                                                              It takes 3 to 15 minutes to create an instance. During this period, the instance status is Creating.
                                                                              
 
                                                                              • If the instance is created successfully, its status changes to Running.
                                                                              • If the instance is in the Failed state, delete it by referring to Deleting Kafka Instances and try creating another one. If the instance creation fails again, contact customer service.
                                                                                 
                                                                                Instances that fail to be created do not occupy other resources.
                                                                                
 
                                                                                
 
                                                                              
diff --git a/docs/dms/umn/kafka-ug-180604014.html b/docs/dms/umn/kafka-ug-180604014.html
index 324697961..553b7e76b 100644
--- a/docs/dms/umn/kafka-ug-180604014.html
+++ b/docs/dms/umn/kafka-ug-180604014.html
@@ -2,13 +2,11 @@
 
 
                                                                              Viewing and Modifying Basic Information of a Kafka Instance
                                                                              
 
                                                                              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 Smart Connect and private network access.
                                                                              
-
                                                                              
+
                                                                              Notes and Constraints
                                                                              Single-node instances do not support reconfiguration of Smart Connect and 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. You can filter Kafka 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.
                                                                                
+
                                                                                Viewing Kafka Instance Details
                                                                                1. Log in to the console.
                                                                                2. Click  in the upper left corner to select the region where your 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. Table 1 describes the various possible statuses of a Kafka instance.
                                                                                  
 
                                                                              23. Table 4 Topic parameters
                                                                              Parameter
                                                                              
 
                                                                              Default Value
                                                                              
+
                                                                              Default Value (Single-node)
                                                                              
 
                                                                              Modified Value
                                                                              
+
                                                                              Default Value (Cluster)
                                                                              
+
                                                                              Modified To (Cluster)
                                                                              
                                                                               		
 
                                                                              
 
                                                                              Partitions
                                                                              
+
                                                                              Partitions
                                                                              
 
                                                                              3
                                                                              
+
                                                                              1
                                                                              
 
                                                                              5
                                                                              
+
                                                                              3
                                                                              
+
                                                                              5
                                                                              
                                                                               		
 
                                                                              Replicas
                                                                              
+
                                                                              Replicas
                                                                              
 
                                                                              3
                                                                              
+
                                                                              1
                                                                              
 
                                                                              3
                                                                              
+
                                                                              3
                                                                              
+
                                                                              3
                                                                              
                                                                               		
 
                                                                              Aging Time (h)
                                                                              
+
                                                                              Aging Time (h)
                                                                              
 
                                                                              72
                                                                              
+
                                                                              72
                                                                              
 
                                                                              72
                                                                              
+
                                                                              72
                                                                              
+
                                                                              72
                                                                              
                                                                               		
 
                                                                              Synchronous Replication
                                                                              
+
                                                                              Synchronous Replication
                                                                              
 
                                                                              Disabled
                                                                              
+
                                                                              Disabled
                                                                              
 
                                                                              Disabled
                                                                              
+
                                                                              Disabled
                                                                              
+
                                                                              Disabled
                                                                              
                                                                               		
 
                                                                              Synchronous Flushing
                                                                              
+
                                                                              Synchronous Flushing
                                                                              
 
                                                                              Disabled
                                                                              
+
                                                                              Disabled
                                                                              
 
                                                                              Disabled
                                                                              
+
                                                                              Disabled
                                                                              
+
                                                                              Disabled
                                                                              
                                                                               		
 
                                                                              Message Timestamp
                                                                              
+
                                                                              Message Timestamp
                                                                              
 
                                                                              CreateTime
                                                                              
+
                                                                              CreateTime
                                                                              
 
                                                                              CreateTime
                                                                              
+
                                                                              CreateTime
                                                                              
+
                                                                              CreateTime
                                                                              
                                                                               		
 
                                                                              Max. Message Size (bytes)
                                                                              
+
                                                                              Max. Message Size (bytes)
                                                                              
 
                                                                              10,485,760
                                                                              
+
                                                                              10,485,760
                                                                              
 
                                                                              10,485,760
                                                                              
+
                                                                              10,485,760
                                                                              
+
                                                                              10,485,760
                                                                              
                                                                               		
 
                                                                              
                                                                               
 
 
                                                                              Table 1 Kafka instance status description
                                                                              Status
                                                                              
                                                                               		
 
                                                                              Description
                                                                              
@@ -173,82 +171,81 @@
 
 
                                                                              
 
-
                                                                              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 3 Modifiable Kafka parameters
                                                                                Parameter
                                                                                
+
                                                                                Modifying Basic Information of a Kafka Instance
                                                                                1. Log in to the console.
                                                                                2. Click  in the upper left corner to select the region where your instance is located.
                                                                                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                4. Click the desired instance to go to the instance details page.
                                                                                5. Modify the following parameters if needed:
                                                                                  
+
                                                                                  
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/dms/umn/kafka-ug-180604015.html b/docs/dms/umn/kafka-ug-180604015.html
index 241965e04..2e7862d6d 100644
--- a/docs/dms/umn/kafka-ug-180604015.html
+++ b/docs/dms/umn/kafka-ug-180604015.html
@@ -2,13 +2,11 @@
 
 
                                                                                  Restarting a Kafka Instance
                                                                                  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.
                                                                                  
+
                                                                                  Notes and Constraints
                                                                                  • When a Kafka instance is being restarted, message consumption and production requests of clients will be rejected.
                                                                                  • To maintain service connections during instance restart, configure the retry mechanism on the client.
                                                                                  
 
                                                                                  
-
                                                                                  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.
                                                                                    
+
                                                                                    Prerequisite
                                                                                    The status of the Kafka instance you want to restart is either Running or Faulty.
                                                                                    
+
                                                                                    
+
                                                                                    Procedure
                                                                                    1. Log in to the console.
                                                                                    2. Click  in the upper left corner to select the region where your 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 Kafka instance to be restarted, click Restart.
                                                                                      • Click the desired Kafka instance to go to the instance details page. 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.
                                                                                      
 
                                                                                       
                                                                                      Restarting a Kafka instance only restarts the instance process and does not restart the VM where the instance is located.
                                                                                      
 
                                                                                      
diff --git a/docs/dms/umn/kafka-ug-180604016.html b/docs/dms/umn/kafka-ug-180604016.html
index 696f750c3..04b411562 100644
--- a/docs/dms/umn/kafka-ug-180604016.html
+++ b/docs/dms/umn/kafka-ug-180604016.html
@@ -2,16 +2,13 @@
 
 
                                                                                      Deleting Kafka Instances
                                                                                      
 
                                                                                      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.
                                                                                      
-
                                                                                      
+
                                                                                      Notes and Constraints
                                                                                      Deleting a Kafka instance will clear the instance data without any backup. Exercise caution.
                                                                                      
+
                                                                                      
 
                                                                                      Prerequisites
                                                                                      The status of the Kafka instance you want to delete is Running or Faulty.
                                                                                      
 
                                                                                      
-
                                                                                      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.
                                                                                        
-
                                                                                        
+
                                                                                        Procedure
                                                                                        1. Log in to the console.
                                                                                        2. Click  in the upper left corner to select the region where your 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 go to the instance details page. In the upper right corner, choose More > Delete.
                                                                                          
 
                                                                                        5. In the Delete Instance dialog box, enter DELETE and click OK to delete the Kafka instance.
                                                                                          It takes 1 to 60 seconds to delete a Kafka instance.
                                                                                          
+
                                                                                          The Kafka instances are deleted when they are no longer displayed in the instance list.
                                                                                          
 
                                                                                        
 
                                                                                        
 
                                                                                      
diff --git a/docs/dms/umn/kafka-ug-180604018.html b/docs/dms/umn/kafka-ug-180604018.html
index da63a2103..f5a7a84f3 100644
--- a/docs/dms/umn/kafka-ug-180604018.html
+++ b/docs/dms/umn/kafka-ug-180604018.html
@@ -2,64 +2,81 @@
 
 
                                                                                      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 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.
                                                                                      
+
                                                                                      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.
                                                                                      
+
                                                                                      The following parameters of cluster instances can be changed on the Parameters page: log.retention.hours (retention period), default.replication.factor (replica quantity), or num.partitions (partition quantity). 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
                                                                                  
                                                                                   		
 
                                                                                  
 
                                                                                  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.
                                                                                  
                                                                                   		
 
                                                                                  Enterprise Project
                                                                                  
+
                                                                                  Description
                                                                                  
 
                                                                                  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.
                                                                                  
-
                                                                                  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.
                                                                                  
                                                                                   		
 
                                                                                  Security Group
                                                                                  
+
                                                                                  Enterprise Project
                                                                                  
 
                                                                                  Click , select a new security group 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.
                                                                                  
+
                                                                                  Security Group
                                                                                  
+
                                                                                  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.
                                                                                  
                                                                                   		
 
                                                                                  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.
                                                                                  
                                                                                   		
 
                                                                                  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.
                                                                                  
                                                                                   		
 
                                                                                  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.
                                                                                  
+
                                                                                  When the policies are triggered, messages may be deleted or cannot be produced.
                                                                                  
                                                                                   		
 
                                                                                  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.
                                                                                  
                                                                                   		
 
                                                                                  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.
                                                                                  
                                                                                   		
 
                                                                                  Table 1 Topic parameters
                                                                                  Parameter
                                                                                  
+
                                                                                  
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
@@ -67,74 +84,69 @@
 
                                                                                  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.
                                                                                  
+
                                                                                  Notes and Constraints
                                                                                  • The partition quantity of topics of a single-node or cluster Kafka instance is limited. When the partition quantity limit is reached, you can no longer create topics. The quantity varies with instance specifications. For details, see Cluster Kafka Instances and Single-node Kafka Instances.
                                                                                  • For an instance with ciphertext access enabled, if allow.everyone.if.no.acl.found is set to false, topics can be created on the client only for the initial user (set when ciphertext access is enabled for the first time).
                                                                                  • If a topic name starts with a special character, for example, an underscore (_) or a number sign (#), monitoring data cannot be displayed.
                                                                                  • Due to the limitation of the Kafka kernel, topics whose names contain only period or underscore difference cannot be created. For example, assume that the Topic_1 topic is created, creating a topic named Topic.1 will fail and throw the Topic 'topic.1' collides with existing topics: topic_1 exception.
                                                                                  
 
                                                                                  
-
                                                                                  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.
                                                                                    
-
                                                                                    
-
                                                                                  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.
                                                                                  6. Enter a topic name, specify other parameters, and click OK.
                                                                                    Figure 1 Creating a topic
                                                                                    
+
                                                                                    Creating a Topic on the Console
                                                                                    1. Log in to the console.
                                                                                    2. Click  in the upper left corner to select the region where your 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.
                                                                                    6. Enter a topic name, specify other parameters, and click OK.
                                                                                      Figure 1 Creating a topic (cluster instance)
                                                                                      
 
-
                                                                                  Table 1 Topic parameters
                                                                                  Parameter
                                                                                  
 
                                                                                  Default Value
                                                                                  
+
                                                                                  Default Value (Single-node)
                                                                                  
 
                                                                                  Modified Value
                                                                                  
+
                                                                                  Default Value (Cluster)
                                                                                  
+
                                                                                  Modified To (Cluster)
                                                                                  
                                                                                   		
 
                                                                                  
 
                                                                                  Partitions
                                                                                  
+
                                                                                  Partitions
                                                                                  
 
                                                                                  3
                                                                                  
+
                                                                                  1
                                                                                  
 
                                                                                  5
                                                                                  
+
                                                                                  3
                                                                                  
+
                                                                                  5
                                                                                  
                                                                                   		
 
                                                                                  Replicas
                                                                                  
+
                                                                                  Replicas
                                                                                  
 
                                                                                  3
                                                                                  
+
                                                                                  1
                                                                                  
 
                                                                                  3
                                                                                  
+
                                                                                  3
                                                                                  
+
                                                                                  3
                                                                                  
                                                                                   		
 
                                                                                  Aging Time (h)
                                                                                  
+
                                                                                  Aging Time (h)
                                                                                  
 
                                                                                  72
                                                                                  
+
                                                                                  72
                                                                                  
 
                                                                                  72
                                                                                  
+
                                                                                  72
                                                                                  
+
                                                                                  72
                                                                                  
                                                                                   		
 
                                                                                  Synchronous Replication
                                                                                  
+
                                                                                  Synchronous Replication
                                                                                  
 
                                                                                  Disabled
                                                                                  
+
                                                                                  Disabled
                                                                                  
 
                                                                                  Disabled
                                                                                  
+
                                                                                  Disabled
                                                                                  
+
                                                                                  Disabled
                                                                                  
                                                                                   		
 
                                                                                  Synchronous Flushing
                                                                                  
+
                                                                                  Synchronous Flushing
                                                                                  
 
                                                                                  Disabled
                                                                                  
+
                                                                                  Disabled
                                                                                  
 
                                                                                  Disabled
                                                                                  
+
                                                                                  Disabled
                                                                                  
+
                                                                                  Disabled
                                                                                  
                                                                                   		
 
                                                                                  Message Timestamp
                                                                                  
+
                                                                                  Message Timestamp
                                                                                  
 
                                                                                  CreateTime
                                                                                  
+
                                                                                  CreateTime
                                                                                  
 
                                                                                  CreateTime
                                                                                  
+
                                                                                  CreateTime
                                                                                  
+
                                                                                  CreateTime
                                                                                  
                                                                                   		
 
                                                                                  Max. Message Size (bytes)
                                                                                  
+
                                                                                  Max. Message Size (bytes)
                                                                                  
 
                                                                                  10,485,760
                                                                                  
+
                                                                                  10,485,760
                                                                                  
 
                                                                                  10,485,760
                                                                                  
+
                                                                                  10,485,760
                                                                                  
+
                                                                                  10,485,760
                                                                                  
                                                                                   		
 
                                                                                  
                                                                                   
 
 
                                                                                  Table 2 Topic parameters
                                                                                  Parameter
                                                                                  
+
                                                                                  
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@@ -142,51 +154,84 @@
 
                                                                                  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
                                                                                  • __dms_dial_test
                                                                                  
 
                                                                                  Once the topic is created, you cannot modify its name.
                                                                                  
-
                                                                                   NOTE: 
                                                                                  Due to the limitation of the Kafka kernel, topics whose names contain only period or underscore difference cannot be created. For example, assume that the Topic_1 topic is created, creating a topic named Topic.1 will fail and throw the Topic 'topic.1' collides with existing topics: topic_1 exception.
                                                                                  
-
                                                                                  
+
                                                                                  Due to the limitation of the Kafka kernel, topics whose names contain only period or underscore difference cannot be created. For example, assume that the Topic_1 topic is created, creating a topic named Topic.1 will fail and throw the Topic 'topic.1' collides with existing topics: topic_1 exception.
                                                                                  
                                                                                   		
 
                                                                                  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
                                                                                  
+
                                                                                  Value range: 1–200
                                                                                  
                                                                                   		
 
                                                                                  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
                                                                                  
 
                                                                                  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.
                                                                                  
+
                                                                                  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 (bytes)
                                                                                  
 
                                                                                  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
                                                                                  
 
                                                                                  
 
                                                                                  
 
                                                                                  
+
                                                                                  After a topic is created, view the new topic on the topic list page.
                                                                                  
 
                                                                                  
 
-
                                                                                  Creating a Topic on the 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}
                                                                                    
-
                                                                                    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. To ensure performance, a partition number within 200 is recommended for each topic.
                                                                                    • number-of-replicas: number of replicas in a topic.
                                                                                    
+
                                                                                    Creating a Topic on the Client
                                                                                    If your client is v2.2 or later, you can use kafka-topics.sh to create topics and manage topic parameters.
                                                                                    
+
                                                                                    • 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}
                                                                                      
+
+
                                                                                      
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                      Table 3 Topic creation parameters
                                                                                      Parameter
                                                                                      
+
                                                                                      Description
                                                                                      
+
                                                                                      topic-name
                                                                                      
+
                                                                                      topic name, which can be customized.
                                                                                      
+
                                                                                      connection-address
                                                                                      
+
                                                                                      Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                                                                      
+
                                                                                      number-of-partitions
                                                                                      
+
                                                                                      Number of partitions in the topic.
                                                                                      
+
                                                                                      To ensure performance, 200 or less partitions are recommended for each topic.
                                                                                      
+
                                                                                      number-of-replicas
                                                                                      
+
                                                                                      Number of replicas of 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]#
                                                                                      
-
                                                                                    • 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 and go to 2 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 and go to 2 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. For a Kafka instance with ciphertext access enabled, do as follows:
                                                                                        1. (Optional) If the username and password, and the SSL certificate has been configured, skip this step and go to 2. Otherwise, do as follows:
                                                                                          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} 
                                                                                          
+
+
                                                                                          
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                          Table 4 Topic creation parameters
                                                                                          Parameter
                                                                                          
+
                                                                                          Description
                                                                                          
+
                                                                                          topic-name
                                                                                          
+
                                                                                          topic name, which can be customized.
                                                                                          
+
                                                                                          connection-address
                                                                                          
+
                                                                                          Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                                                                          
+
                                                                                          number-of-partitions
                                                                                          
+
                                                                                          Number of partitions in the topic.
                                                                                          
+
                                                                                          To ensure performance, 200 or less partitions are recommended for each topic.
                                                                                          
+
                                                                                          number-of-replicas
                                                                                          
+
                                                                                          Number of replicas of a topic.
                                                                                          
+
                                                                                          ssl-user-config.properties
                                                                                          
+
                                                                                          Configuration file name. This file contains username, password, and SSL certificate information.
                                                                                          
+
                                                                                          
 
                                                                                          
-
                                                                                        3. 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. To ensure performance, a partition number within 200 is recommended for each 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.
diff --git a/docs/dms/umn/kafka-ug-180604019.html b/docs/dms/umn/kafka-ug-180604019.html
index 7d62dfff6..7310c39af 100644
--- a/docs/dms/umn/kafka-ug-180604019.html
+++ b/docs/dms/umn/kafka-ug-180604019.html
@@ -1,59 +1,68 @@
 
 
 
                                                                                          Deleting a Kafka Topic
                                                                                          
-
                                                                                          Delete a topic using either of the following methods:
                                                                                          
+
                                                                                          This document describes how to delete a topic.
                                                                                          
 
-
                                                                                          Prerequisites
                                                                                          • A Kafka instance has been created, and a topic has been created in this instance.
                                                                                          • The instance is in the Running state.
                                                                                          
+
                                                                                          Notes and Constraints
                                                                                          • Deleting a topic clears the topic data permanently.
                                                                                          • For an instance with ciphertext access enabled, if allow.everyone.if.no.acl.found is set to false, the topic can be deleted on the client only by the initial user (set in first ciphertext access enablement).
                                                                                          
 
                                                                                          
-
                                                                                          Constraint
                                                                                          If your Kafka instances are connected using Logstash, stop Logstash before deleting topics. Otherwise, services may crash.
                                                                                          
+
                                                                                          Prerequisite
                                                                                          The instance is in the Running state.
                                                                                          
 
                                                                                          
-
                                                                                          Deleting a Kafka 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.
                                                                                          6. Delete topics using either of the following methods:
                                                                                            • Select one or more topics and click Delete Topic in the upper left corner.
                                                                                            • In the row containing the topic you want to delete, choose More > Delete.
                                                                                            
-
                                                                                          7. In the Delete Topic dialog box that is displayed, click OK to delete the topic.
                                                                                          
+
                                                                                          Deleting a Kafka Topic (Console)
                                                                                          1. Log in to the console.
                                                                                          2. Click  in the upper left corner to select the region where your instance is located.
                                                                                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                          4. Click the desired instance to go to the instance details page.
                                                                                          5. In the navigation pane, choose Topics.
                                                                                          6. Delete topics using either of the following methods:
                                                                                            • Select one or more topics and click Delete Topic in the upper left corner.
                                                                                            • In the row containing the topic you want to delete, choose More > Delete.
                                                                                            
+
                                                                                          7. In the Delete Topic dialog box, click OK.
                                                                                            The topic is deleted if it is not displayed in the topic list.
                                                                                            
+
                                                                                          
 
                                                                                          
 
                                                                                          Deleting a Kafka Topic on the Client
                                                                                          If your Kafka client version is later than 2.2, you can use kafka-topics.sh to delete topics.
                                                                                          
-
                                                                                           
                                                                                          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}
                                                                                            
-
                                                                                            Parameter description:
                                                                                            
-
                                                                                            • connection-address: can be obtained from the Connection area on the Basic Information page on the Kafka console.
                                                                                            • topic-name: topic name.
                                                                                            
+
                                                                                            • 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}
                                                                                              
+
+
                                                                                              
+
+
+
+
+
+
+
+
+
+
+
                                                                                              Table 1 Topic deletion parameters
                                                                                              Parameter
                                                                                              
+
                                                                                              Description
                                                                                              
+
                                                                                              connection-address
                                                                                              
+
                                                                                              Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                                                                              
+
                                                                                              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]#
                                                                                              
-
                                                                                            • 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 and go to 2 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 and go to 2 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. For a Kafka instance with ciphertext access enabled, do as follows:
                                                                                                1. (Optional) If the SSL certificate has been configured, skip this step and go to 2. Otherwise, do as follows:
                                                                                                  Create the ssl-user-config.properties file in the /config directory of the Kafka client and add the SSL certificate configurations 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}
                                                                                                  
+
+
                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                  Table 2 Topic deletion parameters
                                                                                                  Parameter
                                                                                                  
+
                                                                                                  Description
                                                                                                  
+
                                                                                                  connection-address
                                                                                                  
+
                                                                                                  Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                                                                                  
+
                                                                                                  topic-name
                                                                                                  
+
                                                                                                  Topic name.
                                                                                                  
+
                                                                                                  ssl-user-config.properties
                                                                                                  
+
                                                                                                  Configuration file name. This file contains username, password, and SSL certificate information.
                                                                                                  
+
                                                                                                  
 
                                                                                                  
-
                                                                                                3. 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 c64863965..7ca60b8b4 100644
--- a/docs/dms/umn/kafka-ug-180604020.html
+++ b/docs/dms/umn/kafka-ug-180604020.html
@@ -2,46 +2,104 @@
 
 
                                                                                                  Connecting to Kafka Using the Client (Plaintext Access)
                                                                                                  
 
                                                                                                  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 a connection, 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
                                                                                                      
+
                                                                                                      Notes and Constraints
                                                                                                      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 is available. 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.
                                                                                                      • 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 
+
                                                                                                      • If automatic topic creation is not enabled for the Kafka instance, create a topic before connecting to the instance.
                                                                                                      • Compatible Kafka CLI 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.
                                                                                                        
 
                                                                                                      
 
                                                                                                      
 
                                                                                                      Accessing the Instance Using CLI
                                                                                                      The following uses Linux as an example.
                                                                                                      
 
                                                                                                      1. Decompress the Kafka CLI package.
                                                                                                        Access the directory where the CLI package is stored and run the following command to decompress the package:
                                                                                                        
-
                                                                                                        tar -zxf [kafka_tar]
                                                                                                        
-
                                                                                                        In the preceding command, [kafka_tar] indicates the name of the CLI package.
                                                                                                        
+
                                                                                                        tar -zxf {kafka_tar}
                                                                                                        
+
                                                                                                        In the preceding command, {kafka_tar} indicates the name of the CLI package.
                                                                                                        
 
                                                                                                        For example:
                                                                                                        
 
                                                                                                        tar -zxf kafka_2.12-2.7.2.tgz
                                                                                                        
 
                                                                                                      2. Access the /bin directory of the Kafka CLI.
                                                                                                        In Windows, you need to access the /bin/windows directory.
                                                                                                        
-
                                                                                                      3. 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.
                                                                                                        • {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.
                                                                                                        
+
                                                                                                        cd {kafka_tar}/bin
                                                                                                        
+
                                                                                                      4. Run the following command to produce messages:
                                                                                                        ./kafka-console-producer.sh --broker-list ${connection-address} --topic ${topic-name}
                                                                                                        
+
+
                                                                                                        
+
+
+
+
+
+
+
+
+
+
+
                                                                                                        Table 1 Message production parameters
                                                                                                        Parameter
                                                                                                        
+
                                                                                                        Description
                                                                                                        
+
                                                                                                        Connection Address
                                                                                                        
+
                                                                                                        Connection address of the Kafka instance.
                                                                                                        
+
                                                                                                        Obtained in Prerequisites.
                                                                                                        
+
                                                                                                        Topic Name
                                                                                                        
+
                                                                                                        The name of the topic created for the Kafka instance.
                                                                                                        
+
                                                                                                        If automatic topic creation is 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
 >DMS
 >Kafka!
 >^C[root@ecs-kafka bin]# 
                                                                                                        
-
                                                                                                        To stop creating messages, press Ctrl+C to exit.
                                                                                                        
-
                                                                                                      5. 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.
                                                                                                        • {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:
                                                                                                        
+
                                                                                                        To stop producing messages, press Ctrl+C to exit.
                                                                                                        
+
                                                                                                      6. Run the following command to consume messages:
                                                                                                        ./kafka-console-consumer.sh --bootstrap-server {connection-address} --topic {topic-name} --group {consumer-group-name} --from-beginning
                                                                                                        
+
+
                                                                                                        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                        Table 2 Message consumption parameters
                                                                                                        Parameter
                                                                                                        
+
                                                                                                        Description
                                                                                                        
+
                                                                                                        Connection Address
                                                                                                        
+
                                                                                                        Connection address of the Kafka instance.
                                                                                                        
+
                                                                                                        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 starts with a special character, for example, an underscore (_) or a number sign (#), monitoring data cannot be displayed.
                                                                                                        
+
                                                                                                         WARNING: 
                                                                                                        Ensure that the consumer group name in the command line is the same as that specified in the configuration file (consumer.properties), if any. Otherwise, message consumption may fail.
                                                                                                        
+
                                                                                                        To view and change the consumer group name in the configuration file, see 4.a.
                                                                                                        
+
                                                                                                        
+
                                                                                                        
+
                                                                                                        
+
                                                                                                        To view and change the consumer group name in the configuration file:
                                                                                                        
+
                                                                                                        1. Access the /config directory of the Kafka CLI.
                                                                                                          cd ../config
                                                                                                          
+
                                                                                                        2. Edit the consumer.properties file.
                                                                                                          vim consumer.properties
                                                                                                          
+
                                                                                                        3. Press i to view and change the consumer group name.
                                                                                                          group.id indicates the consumer group name. You can change the name as required.
                                                                                                          
+
                                                                                                          # consumer group id
+group.id=test-consumer-group
                                                                                                          
+
                                                                                                        4. Press Esc. Enter the following line and press Enter. Save the consumer.properties file and exit.
                                                                                                          :wq
                                                                                                          
+
                                                                                                        
+
                                                                                                        Sample message consumption:
                                                                                                        
 
                                                                                                        [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!
 DMS
 Hello
 ^CProcessed a total of 3 messages
 [root@ecs-kafka bin]# 
                                                                                                        
-
                                                                                                        To stop retrieving messages, press Ctrl+C to exit.
                                                                                                        
+
                                                                                                        To stop consuming messages, press Ctrl+C to exit.
                                                                                                        
 
                                                                                                      
 
                                                                                                      
 
                                                                                                    
diff --git a/docs/dms/umn/kafka-ug-180801001.html b/docs/dms/umn/kafka-ug-180801001.html
index fce51b1ff..d66c066c3 100644
--- a/docs/dms/umn/kafka-ug-180801001.html
+++ b/docs/dms/umn/kafka-ug-180801001.html
@@ -2,62 +2,265 @@
 
 
                                                                                                    Connecting to Kafka Using the Client (Ciphertext Access)
                                                                                                    
 
                                                                                                    This section describes how to access a Kafka instance in ciphertext on an open-source Kafka client. The client connects to the Kafka instance with SASL authentication. If the security protocol SASL_SSL is used, the client communicates with the Kafka instance in encryption, improving security.
                                                                                                    
-
                                                                                                    For security purposes, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is supported.
                                                                                                    
-
                                                                                                    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
                                                                                                        
+
                                                                                                        Notes and Constraints
                                                                                                        • For security purposes, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is supported.
                                                                                                        • 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 is available. 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.
                                                                                                          
+
                                                                                                        • The SASL mechanism in use is known.
                                                                                                          In the Connection area on the Kafka instance details page, view SASL Mechanism. 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, and earlier ones use the old certificate. Later instances are incompatible with the old certificate, and earlier ones are incompatible with the new certificate.
                                                                                                          
+
                                                                                                        • 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.
                                                                                                        • 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 
+
                                                                                                        • Compatible Kafka CLI 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.
                                                                                                          
 
                                                                                                        
 
                                                                                                        
 
                                                                                                        Accessing the Instance Using CLI
                                                                                                        The following uses Linux as an example.
                                                                                                        
-
                                                                                                        1. Map hosts to IP addresses in the /etc/hosts file on the host where the client is located, so that the client can quickly parse the instance brokers.
                                                                                                          Set IP addresses to the instance connection addresses obtained in Prerequisites. Set hosts to the names of instance hosts. Specify a unique name for each host.
                                                                                                          
-
                                                                                                          For example:
                                                                                                          
+
                                                                                                          1. Map hosts to IP addresses in the /etc/hosts file on the host where the client is located, so that the client can quickly parse the instance brokers.
                                                                                                            1. Run the following command to edit the /etc/hosts file:
                                                                                                              vim /etc/hosts
                                                                                                              
+
                                                                                                            2. Press i and add the mapping between the host and IP address to the /etc/hosts file.
                                                                                                              ip 1 host name 1
+ip 2 host name 2
+ip 3 host name 3
                                                                                                              
+
+
                                                                                                              
+
+
+
+
+
+
+
+
+
+
+
                                                                                                              Table 1 Parameters in the /etc/hosts file
                                                                                                              Parameter
                                                                                                              
+
                                                                                                              Description
                                                                                                              
+
                                                                                                              ip
                                                                                                              
+
                                                                                                              Connection address of the Kafka instance, which is obtained from Prerequisites.
                                                                                                              
+
                                                                                                              host name
                                                                                                              
+
                                                                                                              Name of each instance host.
                                                                                                              
+
                                                                                                              Host names are user-defined and must be unique.
                                                                                                              
+
                                                                                                              
+
                                                                                                              
+
                                                                                                              For example:
                                                                                                              
 
                                                                                                              10.154.48.120 server01
 10.154.48.121 server02
 10.154.48.122 server03
                                                                                                              
+
                                                                                                            3. Press Esc. Enter the following line and press Enter. Save the /etc/hosts file and exit.
                                                                                                              :wq
                                                                                                              
+
                                                                                                            
 
                                                                                                          2. Decompress the Kafka CLI package.
                                                                                                            Access the directory where the CLI package is stored and run the following command to decompress the package:
                                                                                                            
-
                                                                                                            tar -zxf [kafka_tar]
                                                                                                            
-
                                                                                                            In the preceding command, [kafka_tar] indicates the name of the CLI package.
                                                                                                            
+
                                                                                                            tar -zxf {kafka_tar}
                                                                                                            
+
                                                                                                            In the preceding command, {kafka_tar} indicates the name of the CLI package.
                                                                                                            
 
                                                                                                            For example:
                                                                                                            
 
                                                                                                            tar -zxf kafka_2.12-2.7.2.tgz
                                                                                                            
-
                                                                                                          3. 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 configuration files of the Kafka CLI.
                                                                                                              Configuration files: producer.properties and consumer.properties
                                                                                                              
+
                                                                                                              Modify the producer.properties file.
                                                                                                              
+
                                                                                                              1. Go to the /config directory of the Kafka CLI.
                                                                                                                cd {kafka_tar}/config
                                                                                                                
+
                                                                                                              2. Edit the producer.properties file.
                                                                                                                vim producer.properties
                                                                                                                
+
                                                                                                              3. Press i and add the following content to the producer.properties file:
                                                                                                                1. Kafka instances support two authentication mechanisms. Add the one obtained in SASL authentication mechanism to the configuration file. If both SCRAM-SHA-512 and PLAIN are enabled, use either of them in connection configurations.
                                                                                                                  • PLAIN:
                                                                                                                    sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
 username="**********" \
 password="**********";        
-sasl.mechanism=PLAIN
                                                                                                                    
-
                                                                                                                    Parameter description:
                                                                                                                    
-
                                                                                                                    username and password: username and password you set when enabling ciphertext access for the first time or when creating a user.
                                                                                                                    
-
                                                                                                                  • If SCRAM-SHA-512 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.scram.ScramLoginModule required \
+sasl.mechanism=PLAIN
                                                                                                                    
+
+
                                                                                                                    
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                    Table 2 SASL authentication mechanism parameters
                                                                                                                    Parameter
                                                                                                                    
+
                                                                                                                    Description
                                                                                                                    
+
                                                                                                                    username
                                                                                                                    
+
                                                                                                                    Set in instance creation or user creation.
                                                                                                                    
+
                                                                                                                    password
                                                                                                                    
+
                                                                                                                    Set in instance creation or user creation.
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                  • SCRAM-SHA-512:
                                                                                                                    sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
 username="**********" \
 password="**********";        
-sasl.mechanism=SCRAM-SHA-512
                                                                                                                    
-
                                                                                                                    Parameter description:
                                                                                                                    
-
                                                                                                                    username and password: username and password you set when enabling ciphertext access for the first time or when creating a user.
                                                                                                                    
+sasl.mechanism=SCRAM-SHA-512
                                                                                          
+
+
                                                                                          
+
+
+
+
+
+
+
+
+
+
+
                                                                                          Table 3 SASL authentication mechanism parameters
                                                                                          Parameter
                                                                                          
+
                                                                                          Description
                                                                                          
+
                                                                                          username
                                                                                          
+
                                                                                          Set in instance creation or user creation.
                                                                                          
+
                                                                                          password
                                                                                          
+
                                                                                          Set in instance creation or user creation.
                                                                                          
+
                                                                                          
+
                                                                                          
 
                                                                                    
-
                                                                                  • Modify the Kafka CLI configuration file based on the security protocol.
                                                                                    • SASL_SSL: 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_SSL
-ssl.truststore.location={ssl_truststore_path}
+
                                                                                    • Kafka instances support two security protocols. Add the one obtained in the security protocol to the configuration file.
                                                                                      • SASL_SSL:
                                                                                        security.protocol=SASL_SSL
+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.
                                                                                        
-
                                                                                      • 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
                                                                                        
+
+
                                                                                        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                        Table 4 SASL_SSL parameters
                                                                                        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
                                                                                        
+
                                                                                        Password of the Kafka client certificate.
                                                                                        
+
                                                                                        dms@kafka by default 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:
                                                                                        security.protocol=SASL_PLAINTEXT
                                                                                        
 
                                                                                      
+
                                                                                      • 
+
                                                                                    • Press Esc. Enter the following line and press Enter. Save the producer.properties file and exit.
                                                                                      :wq
                                                                                      
+
                                                                                      • 
+
                                                                                      Modify the consumer.properties file.
                                                                                      
+
                                                                                      1. Edit the consumer.properties file.
                                                                                        vim consumer.properties
                                                                                        
+
                                                                                      2. Press i and add the following content to the consumer.properties file:
                                                                                        1. Kafka instances support two authentication mechanisms. Add the one obtained in SASL authentication mechanism to the configuration file. If both SCRAM-SHA-512 and PLAIN are enabled, use either of them in connection configurations.
                                                                                          • PLAIN:
                                                                                            sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=PLAIN
                                                                                            
+
+
                                                                                            
+
+
+
+
+
+
+
+
+
+
+
                                                                                            Table 5 SASL authentication mechanism parameters
                                                                                            Parameter
                                                                                            
+
                                                                                            Description
                                                                                            
+
                                                                                            username
                                                                                            
+
                                                                                            Set in instance creation or user creation.
                                                                                            
+
                                                                                            password
                                                                                            
+
                                                                                            Set in instance creation or user creation.
                                                                                            
+
                                                                                            
+
                                                                                            
+
                                                                                          • SCRAM-SHA-512:
                                                                                            sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
+username="**********" \
+password="**********";        
+sasl.mechanism=SCRAM-SHA-512
                                                                                            
+
+
                                                                                            
+
+
+
+
+
+
+
+
+
+
+
                                                                                            Table 6 SASL authentication mechanism parameters
                                                                                            Parameter
                                                                                            
+
                                                                                            Description
                                                                                            
+
                                                                                            username
                                                                                            
+
                                                                                            Set in instance creation or user creation.
                                                                                            
+
                                                                                            password
                                                                                            
+
                                                                                            Set in instance creation or user creation.
                                                                                            
+
                                                                                            
+
                                                                                            
+
                                                                                          
+
                                                                                        2. Kafka instances support two security protocols. Add the one obtained in the security protocol to the configuration file.
                                                                                          • SASL_SSL:
                                                                                            security.protocol=SASL_SSL
+ssl.truststore.location={ssl_truststore_path}
+ssl.truststore.password=dms@kafka
+ssl.endpoint.identification.algorithm=
                                                                                            
+
+
                                                                                            
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                            Table 7 SASL_SSL parameters
                                                                                            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
                                                                                            
+
                                                                                            Password of the Kafka client certificate.
                                                                                            
+
                                                                                            dms@kafka by default 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:
                                                                                            security.protocol=SASL_PLAINTEXT
                                                                                            
+
                                                                                          
+
                                                                                        
+
                                                                                      3. Press Esc. Enter the following line and press Enter. Save the consumer.properties file and exit.
                                                                                        :wq
                                                                                        
+
                                                                                      
 
                                                                                    • 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.
                                                                                      • {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.
                                                                                      
+
                                                                                      cd ../bin
                                                                                      
+
                                                                                    • Run the following command to create messages:
                                                                                      ./kafka-console-producer.sh --broker-list {connection addr} --topic {topic name} --producer.config ../config/producer.properties
                                                                                      
+
+
                                                                                      
+
+
+
+
+
+
+
+
+
+
+
                                                                                      Table 8 Message production parameters
                                                                                      Parameter
                                                                                      
+
                                                                                      Description
                                                                                      
+
                                                                                      Connection Address
                                                                                      
+
                                                                                      Connection address of the Kafka instance.
                                                                                      
+
                                                                                      Obtained in Prerequisites.
                                                                                      
+
                                                                                      Topic Name
                                                                                      
+
                                                                                      The name of the topic created for the Kafka instance.
                                                                                      
+
                                                                                      If automatic topic creation is 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
@@ -65,18 +268,53 @@ ssl.endpoint.identification.algorithm=
                                                                                      
 >DMS
 >Kafka!
 >^C[root@ecs-kafka bin]# 
-
                                                                                      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.
                                                                                      • {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:
                                                                                      
+
                                                                                      To stop producing 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
                                                                                      
+
+
                                                                                      
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                      Table 9 Message consumption parameters
                                                                                      Parameter
                                                                                      
+
                                                                                      Description
                                                                                      
+
                                                                                      Connection Address
                                                                                      
+
                                                                                      Connection address of the Kafka instance.
                                                                                      
+
                                                                                      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 starts with a special character, for example, an underscore (_) or a number sign (#), monitoring data cannot be displayed.
                                                                                      
+
                                                                                       WARNING: 
                                                                                      Ensure that the consumer group name in the command line is the same as that specified in the configuration file (consumer.properties), if any. Otherwise, message consumption may fail.
                                                                                      
+
                                                                                      To view and change the consumer group name in the configuration file, see 6.a.
                                                                                      
+
                                                                                      
+
                                                                                      
+
                                                                                      
+
                                                                                      To view and change the consumer group name in the configuration file:
                                                                                      
+
                                                                                      1. Access the /config directory of the Kafka CLI.
                                                                                        cd ../config
                                                                                        
+
                                                                                      2. Edit the consumer.properties file.
                                                                                        vim consumer.properties
                                                                                        
+
                                                                                      3. Press i to view and change the consumer group name.
                                                                                        group.id indicates the consumer group name. You can change the name as required.
                                                                                        
+
                                                                                        # consumer group id
+group.id=test-consumer-group
                                                                                        
+
                                                                                      4. Press Esc. Enter the following line and press Enter. Save the consumer.properties file and exit.
                                                                                        :wq
                                                                                        
+
                                                                                      
+
                                                                                      Sample message consumption:
                                                                                      
 
                                                                                      [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
 DMS
 Kafka!
 ^CProcessed a total of 3 messages
 [root@ecs-kafka bin]# 
                                                                                      
-
                                                                                      To stop retrieving messages, press Ctrl+C to exit.
                                                                                      
+
                                                                                      To stop consuming messages, press Ctrl+C to exit.
                                                                                      
 
                                                                                      • 
 
                                                                                  
 
diff --git a/docs/dms/umn/kafka-ug-181221001.html b/docs/dms/umn/kafka-ug-181221001.html
index 630ff3477..2e446e4d0 100644
--- a/docs/dms/umn/kafka-ug-181221001.html
+++ b/docs/dms/umn/kafka-ug-181221001.html
@@ -1,6 +1,6 @@
 
 
-
                                                                                  Modifying Kafka Instance Specifications
                                                                                  
+
                                                                                  Modifying Cluster Kafka Instance Specifications
                                                                                  
 
                                                                                  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
                                                                                  
@@ -62,35 +62,34 @@
 
 
                                                                                  
 
                                                                                  
-
                                                                                   
                                                                                  This function is unavailable for single-node instances.
                                                                                  
-
                                                                                  
 
                                                                                  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.
                                                                                  
-
-
                                                                                  
-
diff --git a/docs/dms/umn/kafka_pd_0004.html b/docs/dms/umn/kafka_pd_0004.html
new file mode 100644
index 000000000..c6ef9dfc3
--- /dev/null
+++ b/docs/dms/umn/kafka_pd_0004.html
@@ -0,0 +1,148 @@
+
+
+
                                                                                  Comparing Kafka and RocketMQ
                                                                                  
+
                                                                                  
+
                                                                                  Table 2 Impact of specification modification
                                                                                  Modified Object
                                                                                  
+
                                                                                  Notes and Constraints
                                                                                  • Unavailable for single-node instances.
                                                                                  
+
                                                                                  
+
                                                                                  Impact of Specification Modification
                                                                                  
+
                                                                                  
-
-
-
-
-
-
-
@@ -101,26 +100,20 @@ 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
                                                                                  
-
                                                                                  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.
                                                                                    • 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.
                                                                                          
+
                                                                                          Procedure
                                                                                          1. Log in to the console.
                                                                                          2. Click  in the upper left corner to select the region where your 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, bandwidth, 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 (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.
                                                                                                  
+
                                                                                                • After increasing the bandwidth, add the IP address of the new broker to the client connection configuration to improve reliability.
                                                                                              
+
                                                                                            • 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.
                                                                                                  
 
                                                                                                
 
                                                                                              
 
                                                                                            
 
                                                                                            • 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.
                                                                                                  
 
                                                                                                
 
                                                                                              
-
                                                                                            • 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.
                                                                                                  
+
                                                                                                • 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.
                                                                                                  2. If public access has been enabled, configure EIPs for the new brokers.
                                                                                                  3. Click Next.
                                                                                                  4. Confirm the configurations 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 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 (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. After adding brokers, add the IP addresses of the new brokers to the client connection configuration to improve reliability.
                                                                                                  
+
                                                                                                • 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.
                                                                                                      
 
                                                                                                    
 
                                                                                                  
@@ -128,4 +121,9 @@ env.setRestartStrategy(RestartStrategies.fixedDelayRestart(3, Time.seconds(20)))
 
                                                                                              
 
                                                                                          
 
                                                                                  
+
                                                                                  
+
                                                                                  
+
                                                                                  Parent topic: Modifying Instance Specifications
                                                                                  
+
                                                                                  
+
                                                                                  
 
diff --git a/docs/dms/umn/kafka-ug-190605001.html b/docs/dms/umn/kafka-ug-190605001.html
index 9c3abb085..1db1fa661 100644
--- a/docs/dms/umn/kafka-ug-190605001.html
+++ b/docs/dms/umn/kafka-ug-190605001.html
@@ -2,11 +2,11 @@
 
 
                                                                                  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.
                                                                                  
+
                                                                                  Prerequisite
                                                                                  At least one Kafka instance has been created. The instance has at least one available message.
                                                                                  
 
                                                                                  
-
                                                                                  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. 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.
                                                                                    
+
                                                                                    Procedure
                                                                                    1. Log in to the console.
                                                                                    2. Click  in the upper left corner to select the region where your 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. Metric data is reported to Cloud Eye every minute.
                                                                                      • Click the desired instance to go to the instance details page. In the navigation pane, choose Monitoring. On the displayed page, view the monitoring data. The data is updated every minute.
                                                                                      
+
                                                                                      Click the following dimensions to view monitoring data:
                                                                                      
+
                                                                                      • Single-node instance: By Instance, By Broker, By Topic, or By Consumer Group.
                                                                                      • Cluster instance: By Instance, By Broker, By Topic, By Consumer Group, or By Smart Connect.
                                                                                      
 
                                                                                    
 
                                                                                    
 
                                                                                  
diff --git a/docs/dms/umn/kafka-ug-190904001.html b/docs/dms/umn/kafka-ug-190904001.html
index 8d87d6d0e..6139bc97f 100644
--- a/docs/dms/umn/kafka-ug-190904001.html
+++ b/docs/dms/umn/kafka-ug-190904001.html
@@ -1,36 +1,37 @@
 
 
 
                                                                                  Viewing Kafka Messages
                                                                                  
-
                                                                                  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 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 2,000 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)));
                                                                                      
 
                                                                                    
-
                                                                                  
+
                                                                                6. It takes 5 to 10 minutes to modify specifications on one broker. The more brokers, the longer time the modification takes.
                                                                                  7. 
                                                                                   		
 
                                                                                  
                                                                                   
 
 
 
                                                                                  Table 1 Message query parameters
                                                                                  Parameter
                                                                                  
+
                                                                                  When messages are lost or fail to be consumed, you can query the content and attributes of specific messages for troubleshooting.
                                                                                  
+
                                                                                  You can view the offset of different partitions, the message size, creation time, and body of messages in topics.
                                                                                  
+
                                                                                  Notes and Constraints
                                                                                  • If a topic contains a large amount of data, an internal service error may be reported when you query messages in a topic with only one replica. You can shorten the time range for query based on the data volume.
                                                                                  • To query with content, due to resource and performance restrictions, a total of 200 MB and 10,000 messages can be queried, and a maximum of 10 messages can be returned.
                                                                                  • The console displays messages smaller than 4 KB. To view messages larger than 4 KB, click Download Message.
                                                                                  
+
                                                                                  
+
                                                                                  Procedure
                                                                                  1. Log in to the console.
                                                                                  2. Click  in the upper left corner to select the region where your instance is located.
                                                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                  4. Click the desired instance to go to the instance details page.
                                                                                  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
                                                                                    
 
                                                                                    Description
                                                                                    
+
                                                                                    Description
                                                                                    
                                                                                     		
 
                                                                                    
 
                                                                                    Topic Name
                                                                                    
+
                                                                                    Topic Name
                                                                                    
 
                                                                                    Name of the topic to be queried.
                                                                                    
+
                                                                                    Name of the topic to be queried.
                                                                                    
                                                                                     		
 
                                                                                    Partition
                                                                                    
+
                                                                                    Partition
                                                                                    
 
                                                                                    Partition where the messages are located.
                                                                                    
+
                                                                                    Partition where the messages are located.
                                                                                    
 
                                                                                    If no partition is specified, messages in all partitions of the topic are displayed in the query result.
                                                                                    
                                                                                     		
 
                                                                                    Search By
                                                                                    
+
                                                                                    Search By
                                                                                    
 
                                                                                    The following methods are supported:
                                                                                    
+
                                                                                    The following methods are supported:
                                                                                    
 
                                                                                    • Creation time: Search by the time that messages are created.
                                                                                    • Offset: Search by the message position.
                                                                                    
                                                                                     		
 
                                                                                    Search For
                                                                                    
+
                                                                                    Search For
                                                                                    
 
                                                                                    This parameter is displayed only when Search By is set to Creation time.
                                                                                    
+
                                                                                    This parameter is displayed only when Search By is set to Creation time.
                                                                                    
 
                                                                                    Enter a keyword in the message body.
                                                                                    
 
                                                                                     NOTE: 
                                                                                    Due to resource and performance restrictions, query with content is limited to 10 results. Each search covers at most 10,000 records, or 200 MB. For large records (> 20 KB per message) or a long period, dump messages for offline query.
                                                                                    
 
                                                                                    
@@ -39,12 +40,42 @@
 
                                                                                    
 
                                                                                    
 
                                                                                    
-
                                                                                     
                                                                                    If a topic contains a large amount of data, an internal service error may be reported when you query messages in a topic with only one replica. You can shorten the time range for query based on the data volume.
                                                                                    
-
                                                                                    
-
                                                                                  7. Click Search to query messages.
                                                                                    Parameter description:
                                                                                    
-
                                                                                    • Topic Name: name of the topic where the message is located
                                                                                    • Partition: partition where the message is located
                                                                                    • Offset: position of the message in the partition
                                                                                    • Message Size (Byte) size of the message
                                                                                    • Created: time when the message is created. 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 year 1970 by default.
                                                                                    
-
                                                                                  8. Click View Message Body. In the displayed View Message Body dialog box, view the message content, including the topic name, partition, offset, creation time, and message body.
                                                                                     
                                                                                    The console displays messages smaller than 4 KB. To view messages larger than 4 KB, click Download Message.
                                                                                    
-
                                                                                    
+
                                                                                  9. Click Search to query messages.
                                                                                    
+
                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                    Table 2 Message parameters
                                                                                    Parameter
                                                                                    
+
                                                                                    Description
                                                                                    
+
                                                                                    Topic Name
                                                                                    
+
                                                                                    Name of the topic where the message is located.
                                                                                    
+
                                                                                    Partition
                                                                                    
+
                                                                                    Partition where the message is located.
                                                                                    
+
                                                                                    Offset
                                                                                    
+
                                                                                    Position of the message in the partition.
                                                                                    
+
                                                                                    Message Size (Byte)
                                                                                    
+
                                                                                    Size of the message.
                                                                                    
+
                                                                                    Created
                                                                                    
+
                                                                                    Time when the message is created. 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 year 1970 by default.
                                                                                    
+
                                                                                    
+
                                                                                    
+
                                                                                  10. Click View Message Body. In the displayed View Message Body dialog box, view the message content, including the topic name, partition, offset, creation time, and message body.
                                                                                    The console displays messages smaller than 4 KB. To view messages larger than 4 KB, click Download Message.
                                                                                    
 
                                                                                  11. (Optional) To restore the default settings, click Reset.
                                                                                  
 
                                                                                  
 
                                                                                  
diff --git a/docs/dms/umn/kafka-ug-200119002.html b/docs/dms/umn/kafka-ug-200119002.html
index d550ac983..9a899b0f1 100644
--- a/docs/dms/umn/kafka-ug-200119002.html
+++ b/docs/dms/umn/kafka-ug-200119002.html
@@ -67,11 +67,7 @@
 
 
                                                                                  
 
                                                                                  
-
                                                                                  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.
                                                                                      
-
                                                                                      
+
                                                                                      Procedure
                                                                                      1. Log in to the console.
                                                                                      2. Click  in the upper left corner to select the region where your instance is located.
                                                                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                      4. Click the name of the desired 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 list, specify a time range, enter a keyword in the search box, and press Enter. The tasks started within the specified time range are 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 only delete the records of tasks in the Successful, Failed, or Canceled state.
                                                                                          
 
                                                                                        
 
                                                                                        
 
                                                                                      
diff --git a/docs/dms/umn/kafka-ug-200506001.html b/docs/dms/umn/kafka-ug-200506001.html
index 32a3cf804..f5bd6e9ad 100644
--- a/docs/dms/umn/kafka-ug-200506001.html
+++ b/docs/dms/umn/kafka-ug-200506001.html
@@ -4,13 +4,13 @@
 
                                                                                      Aging time is a period that messages in a topic are retained for. Consumers must consume messages before this period ends. Otherwise, the messages will be deleted and can no longer be consumed.
                                                                                      
 
                                                                                      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.
                                                                                      
-
                                                                                      
-
                                                                                      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.
                                                                                      
+
+
                                                                                      The value of the log.retention.hours parameter takes effect only if the aging time has not been set for the topic. 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.
                                                                                      
+
                                                                                      Notes and Constraints
                                                                                      • The retention period of single-node instances can be modified only on the Topics page.
                                                                                      
+
                                                                                      
+
                                                                                      Modifying the Message Retention Period of a Topic
                                                                                      1. Log in to the console.
                                                                                      2. Click  in the upper left corner to select the region where your instance is located.
                                                                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                      4. Click the desired instance to go to the instance details page.
                                                                                      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 (1–720) and click OK.
                                                                                        View the aging time on the Topics page.
                                                                                        
+
                                                                                      
 
                                                                                      
 
                                                                                      
 
                                                                                      
diff --git a/docs/dms/umn/kafka_faq_0058.html b/docs/dms/umn/kafka_faq_0058.html
index 3b88518b6..e3c2a8763 100644
--- a/docs/dms/umn/kafka_faq_0058.html
+++ b/docs/dms/umn/kafka_faq_0058.html
@@ -1,7 +1,7 @@
 
 
 
                                                                                      How Do I Modify message.max.bytes?
                                                                                      
-
                                                                                      message.max.bytes can be modified on the Parameters page on the console. For details, see Modifying Kafka Instance Configuration Parameters.
                                                                                      
+
                                                                                      message.max.bytes can be modified on the Parameters page on the Kafka console. For details, see Modifying Kafka Instance Configuration Parameters.
                                                                                      
 
                                                                                      The maximum value of message.max.bytes is 10,485,760 bytes. If a single message is larger than this size, compress the message with algorithms or split it in the service logic.
                                                                                      
 
                                                                                      
 
                                                                                      
diff --git a/docs/dms/umn/kafka_faq_0059.html b/docs/dms/umn/kafka_faq_0059.html
index f3d0fb68f..52a08a69d 100644
--- a/docs/dms/umn/kafka_faq_0059.html
+++ b/docs/dms/umn/kafka_faq_0059.html
@@ -2,7 +2,7 @@
 
 
                                                                                      Why Does a Deleted Consumer Group Still Exist?
                                                                                      
 
                                                                                      Possible cause: Automatic consumer group creation has been enabled and your service is connected to the consumer group and consuming messages. Therefore, the consumer group is deleted but will be automatically re-created to consume messages until your service stops.
                                                                                      
-
                                                                                      Solution: Disable automatic consumer group creation. To do so, go to the Kafka console, choose Parameters in the left navigation pane, locate the row that contains auto.create.groups.enable in the Dynamic Parameters area, click Edit, set the Current Value to false, and click Save. Then, delete the consumer group. auto.create.groups.enable is not displayed for some instances. For details, see the console. In this case, modify your service code to stop connecting to the consumer group. Then, delete the consumer group. To change the auto.create.groups.enable parameter setting, see Modifying Kafka Instance Configuration Parameters.
                                                                                      
+
                                                                                      Solution: Disable automatic consumer group creation. To do so, go to the Kafka console, choose Parameters in the left navigation pane, locate the row containing auto.create.groups.enable in the Dynamic Parameters area, click Edit, set the Current Value to false, and click Save. Then, delete the consumer group. auto.create.groups.enable is not displayed for some instances. For details, see the console. In this case, modify your service code to stop connecting to the consumer group. Then, delete the consumer group. To change the auto.create.groups.enable parameter setting, see Modifying Kafka Instance Configuration Parameters.
                                                                                      
 
                                                                                      
 
                                                                                      
 
                                                                                      
diff --git a/docs/dms/umn/kafka_faq_0061.html b/docs/dms/umn/kafka_faq_0061.html
index 7503f78ad..4709d9d39 100644
--- a/docs/dms/umn/kafka_faq_0061.html
+++ b/docs/dms/umn/kafka_faq_0061.html
@@ -22,7 +22,7 @@
 
                                                                                  High compiling complexity because Go compilers need extra resources to configure the imported C++ libraries
                                                                                  
                                                                                   		
 
                                                                                  kafka-go
                                                                                  
+
                                                                                  Kafka-go
                                                                                  
                                                                                   		
 
                                                                                  • A simple and lite Kafka client easy for learning and usage
                                                                                  • Reduced application size and complexity with limited library and fewer dependencies
                                                                                  
 
                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                  Table 1 Functions
                                                                                  Feature
                                                                                  
+
                                                                                  RocketMQ
                                                                                  
+
                                                                                  Kafka
                                                                                  
+
                                                                                  Priority queue
                                                                                  
+
                                                                                  Not supported
                                                                                  
+
                                                                                  Not supported
                                                                                  
+
                                                                                  Delayed queue
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Not supported
                                                                                  
+
                                                                                  Dead letter queue
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Not supported
                                                                                  
+
                                                                                  Message retry
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Not supported
                                                                                  
+
                                                                                  Retrieval mode
                                                                                  
+
                                                                                  Pull-based and push-based
                                                                                  
+
                                                                                  Pull-based
                                                                                  
+
                                                                                  Message broadcasting
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Message tracking
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Supports offset and timestamp tracking.
                                                                                  
+
                                                                                  Message accumulation
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Supports
                                                                                  
+
                                                                                  Persistence
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Message tracing
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Not supported
                                                                                  
+
                                                                                  Message filtering
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Multi-tenancy
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Multi-protocol
                                                                                  
+
                                                                                  Compatible with RocketMQ.
                                                                                  
+
                                                                                  Only supports Apache Kafka.
                                                                                  
+
                                                                                  Multi-language
                                                                                  
+
                                                                                  Supports clients in multiple programming languages.
                                                                                  
+
                                                                                  Kafka is written in Scala and Java and supports clients in multiple programming languages.
                                                                                  
+
                                                                                  Throttling
                                                                                  
+
                                                                                  Pending
                                                                                  
+
                                                                                  Not supported
                                                                                  
+
                                                                                  Ordered message delivery
                                                                                  
+
                                                                                  Queue-level order
                                                                                  
+
                                                                                  Partition-level order
                                                                                  
+
                                                                                  Security
                                                                                  
+
                                                                                  SSL authentication
                                                                                  
+
                                                                                  SSL and SASL authentication and read/write permissions control
                                                                                  
+
                                                                                  Transactional messages
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  Supported
                                                                                  
+
                                                                                  
+
                                                                                  
+
                                                                                  
+
                                                                                  
+
                                                                                  
+
                                                                                  Parent topic: Service Overview
                                                                                  
+
                                                                                  
+
                                                                                  
+
diff --git a/docs/dms/umn/kafka_trouble_0007.html b/docs/dms/umn/kafka_trouble_0007.html
new file mode 100644
index 000000000..f06557321
--- /dev/null
+++ b/docs/dms/umn/kafka_trouble_0007.html
@@ -0,0 +1,16 @@
+
+
+
                                                                                  Flink 1.15 Consumption Progress Submission Failure
                                                                                  
+
                                                                                  Symptom
                                                                                  To consume Kafka messages in Flink 1.15, the consumption progress fails to be submitted, and the error messages "COORDINATOR_NOT_AVAILABLE" are thrown.
                                                                                  
+
                                                                                  
+
                                                                                  Root Cause
                                                                                  Bug on the Kafka client used by Flink 1.15: When the consumption progress fails to be submitted for once, the client sets the coordinator to unavailable and it cannot be automatically restored.
                                                                                  
+
                                                                                  
+
                                                                                  Solution
                                                                                  • Restart the Flink job.
                                                                                  • Upgrade Flink to 1.16 or later.
                                                                                  
+
                                                                                  
+
                                                                                  
+
                                                                                  
+
                                                                                  
+
                                                                                  Parent topic: Troubleshooting
                                                                                  
+
                                                                                  
+
                                                                                  
+
diff --git a/docs/dms/umn/kafka_ug_0017.html b/docs/dms/umn/kafka_ug_0017.html
index 75d57fac9..a7d17f276 100644
--- a/docs/dms/umn/kafka_ug_0017.html
+++ b/docs/dms/umn/kafka_ug_0017.html
@@ -5,21 +5,18 @@
 
                                                                                  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.
                                                                                  
-
                                                                                  
-
                                                                                  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.
                                                                                  
+
                                                                                  Notes and Constraints
                                                                                  • 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.
                                                                                    
+
                                                                                  • Unavailable for single-node instances.
                                                                                  
 
                                                                                  
 
                                                                                  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.
                                                                                    
+
                                                                                    Procedure
                                                                                    1. Log in to the console.
                                                                                    2. Click  in the upper left corner to select the region where your 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 go to the instance details page. Choose More > Enable Smart Connect in the upper right corner.
                                                                                      • Click the desired Kafka instance to go to the instance details page. Click  next to Smart Connect.
                                                                                      • Click the desired Kafka instance to go to the instance details page. 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. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                    7. 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.
                                                                                      
-
                                                                                    8. 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.
                                                                                      
-
                                                                                      
-
                                                                                    9. On the displayed Enabling Smart Connect for Kafka Instance page, ensure that Smart Connect is enabled and click Submit.
                                                                                    
+
                                                                                  3. On the displayed Enabling Smart Connect for Kafka Instance page, ensure that Smart Connect is enabled and click Submit.
                                                                                    Smart Connect has been successfully enabled if the task is in the Successful state on the Background Tasks tab page of the Background Tasks page.
                                                                                    
+
                                                                                  
 
                                                                                  
-
                                                                                  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.
                                                                                  
+
                                                                                  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
index 8589a21a0..e91981e01 100644
--- a/docs/dms/umn/kafka_ug_0018.html
+++ b/docs/dms/umn/kafka_ug_0018.html
@@ -2,31 +2,25 @@
 
 
                                                                                  Managing Smart Connect Tasks
                                                                                  
 
                                                                                  View, delete, start, pause, or restart a Smart Connect task.
                                                                                  
-
                                                                                   
                                                                                  This function is unavailable for single-node instances.
                                                                                  
-
                                                                                  
-
                                                                                  Prerequisites
                                                                                  A Smart Connect task has been created.
                                                                                  
+
                                                                                  Notes and Constraints
                                                                                  Unavailable for single-node instances. 
                                                                                  
 
                                                                                  
-
                                                                                  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.
                                                                                    
+
                                                                                    Prerequisite
                                                                                    A Smart Connect task has been created.
                                                                                    
+
                                                                                    
+
                                                                                    Viewing Smart Connect Tasks
                                                                                    1. Log in to the console.
                                                                                    2. Click  in the upper left corner to select the region where your instance is located.
                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                    4. Click the desired instance to go to the instance details page.
                                                                                    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.
                                                                                    
+
                                                                                    Deleting a Smart Connect Task
                                                                                    1. Log in to the console.
                                                                                    2. Click  in the upper left corner to select the region where your instance is located.
                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                    4. Click the desired instance to go to the instance details page.
                                                                                    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.
                                                                                      The task is deleted when it is no longer displayed in the Smart Connect task list.
                                                                                      
+
                                                                                    
 
                                                                                    
 
                                                                                    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 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.
                                                                                      
+
                                                                                      1. Log in to the console.
                                                                                      2. Click  in the upper left corner to select the region where your instance is located.
                                                                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                      4. Click the desired instance to go to the instance details page.
                                                                                      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.
                                                                                        
+
                                                                                        The task is started or paused when it is in the Running or Paused state on the Smart Connect tasks page.
                                                                                        
 
                                                                                      
 
                                                                                    
-
                                                                                    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.
                                                                                      Once the task is restarted, a success message is displayed in the upper left area of the page.
                                                                                      
+
                                                                                      Restarting a Smart Connect Task
                                                                                      1. Log in to the console.
                                                                                      2. Click  in the upper left corner to select the region where your instance is located.
                                                                                      3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                      4. Click the desired instance to go to the instance details page.
                                                                                      5. In the navigation pane, choose Smart Connect.
                                                                                      6. In the row containing the desired Smart Connect task, click Restart.
                                                                                        Precautions:
                                                                                        
+
                                                                                        • 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.
                                                                                        Once the task is restarted, a success message is displayed in the upper area of the page.
                                                                                        
 
                                                                                      
 
                                                                                      
 
                                                                                    
diff --git a/docs/dms/umn/kafka_ug_0021.html b/docs/dms/umn/kafka_ug_0021.html
index 22ac46274..b16bf2e9d 100644
--- a/docs/dms/umn/kafka_ug_0021.html
+++ b/docs/dms/umn/kafka_ug_0021.html
@@ -2,51 +2,39 @@
 
 
                                                                                    Querying the Kafka 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:
                                                                                      
-
                                                                                      • DEAD: The consumer group has no member or metadata.
                                                                                      • EMPTY: The consumer group has metadata but has no member.
                                                                                      • PREPARING_REBALANCE: The consumer group is to be rebalanced.
                                                                                      • COMPLETING_REBALANCE: All members have joined the consumer group.
                                                                                      • STABLE: Members in the consumer group can consume messages normally.
                                                                                      
-
                                                                                    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 (Console)
                                                                                    1. Log in to the console.
                                                                                    2. Click  in the upper left corner to select the region where your instance is located.
                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                    4. Click the desired instance to go to the instance details page.
                                                                                    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:
                                                                                      
+
                                                                                      • DEAD: The consumer group has no member or metadata.
                                                                                      • EMPTY: The consumer group has metadata but has no member.
                                                                                      • PREPARING_REBALANCE: The consumer group is to be rebalanced.
                                                                                      • COMPLETING_REBALANCE: All members have joined the consumer group.
                                                                                      • STABLE: Members in the consumer group can consume messages normally.
                                                                                      
+
                                                                                    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
                                                                                      
+
                                                                                      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
                                                                                        
 
                                                                                        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]#
                                                                                        
-
                                                                                      • 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 and go to 2 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 and go to 2 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. For a Kafka instance with ciphertext access enabled, do as follows:
                                                                                          1. (Optional) If the username and password, and the SSL certificate has been configured, skip this step and go to 2. Otherwise, do as follows:
                                                                                            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} 
                                                                                            
+
+
                                                                                            
+
+
+
+
+
+
+
+
+
+
+
                                                                                            Table 1 Consumer group list query parameters
                                                                                            Parameter
                                                                                            
+
                                                                                            Description
                                                                                            
+
                                                                                            connection-address
                                                                                            
+
                                                                                            Connection address of a Kafka instance. To obtain the address, choose Basic Information > Connection.
                                                                                            
+
                                                                                            ssl-user-config.properties
                                                                                            
+
                                                                                            Configuration file name. This file contains username, password, and SSL certificate information.
                                                                                            
+
                                                                                            
 
                                                                                            
-
                                                                                          3. 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
diff --git a/docs/dms/umn/kafka_ug_0023.html b/docs/dms/umn/kafka_ug_0023.html
index 7be624ae7..670accf41 100644
--- a/docs/dms/umn/kafka_ug_0023.html
+++ b/docs/dms/umn/kafka_ug_0023.html
@@ -5,36 +5,34 @@
 
                                                                                            Partition reassignment is required in the following scenarios:
                                                                                            
 
                                                                                            • 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 replica quantity of a topic can be changed during partition reassignment.
                                                                                            
 
                                                                                            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.
                                                                                            
+
                                                                                            Notes and Constraints
                                                                                            • Unavailable for single-node instances.
                                                                                            • 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.
                                                                                            
 
                                                                                            
-
                                                                                            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.
                                                                                            
+
                                                                                            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.
                                                                                            • 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 longer for a topic with a large data volume. To check the volume, see the Message Size metric on the monitoring page by referring to Viewing Kafka Metrics. 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.
                                                                                            
 
                                                                                            
-
                                                                                            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 Topics.
                                                                                            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.
                                                                                              
+
                                                                                              Prerequisite
                                                                                              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 the region where your instance is located.
                                                                                              3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                              4. Click the desired instance to go to the instance details page.
                                                                                              5. In the navigation pane, choose Topics.
                                                                                              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. Set automatic reassignment parameters.
                                                                                                
-
                                                                                                Table 1 Automatic balancing parameters
                                                                                                Parameter
                                                                                                
+
                                                                                                
-
-
-
@@ -65,7 +63,7 @@
 
@@ -76,10 +74,8 @@
 
                                                                                                
-
                                                                                                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 Topics.
                                                                                                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. 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.
                                                                                                  
+
                                                                                                  Manual Reassignment
                                                                                                  1. Log in to the console.
                                                                                                  2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                  4. Click the desired instance to go to the instance details page.
                                                                                                  5. In the navigation pane, choose Topics.
                                                                                                  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. 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 of 300 MB/s is used), you are not advised to limit the bandwidth. Otherwise, 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
                                                                                                    
 
                                                                                                  8. (Optional) Click Calculate. Time Required indicates how long manual balancing will take.
                                                                                                    The one-click calculation function does not affect the performance of Kafka instances.
                                                                                                    
 
                                                                                                  9. Click OK.
                                                                                                    The following table lists how to check whether reassignment is complete (scheduled and non-scheduled tasks):
                                                                                                    
@@ -98,7 +94,7 @@
 
                                                                                                
@@ -110,7 +106,7 @@
 
                                                                                                Re-scheduling Partition Reassignment
                                                                                                1. On the Scheduled tasks tab page on the Background Tasks page, click the drop-down box in the upper left corner, select a time period, enter the desired topic name in the search box, and press Enter.
                                                                                                  Figure 5 Querying reassignment schedules
                                                                                                  
-
                                                                                                2. In the row that contains the desired task, click Modify.
                                                                                                3. In the Change Schedule dialog box, change the schedule or cancel the scheduled task.
                                                                                                  • To change the schedule, select a time and click OK.
                                                                                                  • To cancel the task, select Cancel (as shown in Figure 6) and click OK.
                                                                                                    Figure 6 Canceling a scheduled reassignment task
                                                                                                    
+
                                                                                                  • In the row that contains the desired task, click Modify.
                                                                                                  • In the Change Schedule dialog box, change the schedule or cancel the scheduled task.
                                                                                                    • To change the schedule, select a time and click OK.
                                                                                                    • To cancel the task, select Cancel (as shown in Figure 6) and click OK.
                                                                                                      Figure 6 Canceling a reassignment schedule
                                                                                                      
 
                                                                                                    
 
                                                                                                
 
                                                                                                
@@ -378,9 +374,8 @@
 
                                                                                                Figure 9 Reassignment scenario 3
                                                                                                As shown in Figure 9, one replica needs to fetch data from Broker 0 for partition reassignment, and the other replica needs to fetch data from Broker 0 for message production. Since the throttle does not distinguish between message production and partition reassignment, the traffic caused by both is limited and counted.
                                                                                                
-
                                                                                                • Bandwidth required by Broker 0 to complete partition reassignment within 200s = (100 MB + 700 KB/s x 200s)/200s + 700 KB/s= 1.9 MB/s
                                                                                                • Bandwidth required by Broker 2 to complete partition reassignment within 200s = 100 MB/200s = 0.5 MB/s
                                                                                                
+
                                                                                                • Bandwidth required by Broker 0 to complete partition reassignment within 200s = (100 MB + 700 KB/s × 200s)/200s + 700 KB/s= 1.9 MB/s
                                                                                                • Bandwidth required by Broker 2 to complete partition reassignment within 200s = 100 MB/200s = 0.5 MB/s
                                                                                                In conclusion, to complete the partition reassignment task within 200s, set the throttle to a value greater than or equal to 1.9 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.
                                                                                                
-
                                                                                                
 
                                                                                                
diff --git a/docs/dms/umn/kafka_ug_0024.html b/docs/dms/umn/kafka_ug_0024.html
index b04e59410..2f46063e1 100644
--- a/docs/dms/umn/kafka_ug_0024.html
+++ b/docs/dms/umn/kafka_ug_0024.html
@@ -2,9 +2,8 @@
 
 
                                                                                                Viewing Sample Code of Kafka Production and Consumption
                                                                                                
 
                                                                                                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.
                                                                                                  
+
                                                                                                  Procedure
                                                                                                  1. Log in to the console.
                                                                                                  2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                  4. Click the desired instance to go to the instance details page.
                                                                                                  5. In the navigation pane, choose Topics.
                                                                                                  6. Click View Sample Code. The Sample Code dialog box is displayed.
                                                                                                    The sample code is available in Java, Go, and Python, and PlainText, SASL_SSL, and SASL_PLAINTEXT access modes.
                                                                                                    
+
                                                                                                    • PlainText: Accessing the Kafka instance in plaintext.
                                                                                                    • SASL_SSL: Accessing the Kafka instance in ciphertext with SASL authentication. SASL authentication uses PLAIN or SCRAM-SHA-512.
                                                                                                    • SASL_PLAINTEXT: Accessing the Kafka instance in plaintext with SASL authentication. SASL authentication uses PLAIN or SCRAM-SHA-512.
                                                                                                    
 
                                                                                                  
 
                                                                                                  
 
                                                                                                
diff --git a/docs/dms/umn/kafka_ug_0027.html b/docs/dms/umn/kafka_ug_0027.html
index 53ff39c67..2f5ee92dd 100644
--- a/docs/dms/umn/kafka_ug_0027.html
+++ b/docs/dms/umn/kafka_ug_0027.html
@@ -4,9 +4,7 @@
 
                                                                                                Export the topic list on the console. Batch export is supported.
                                                                                                
 
                                                                                                Prerequisites
                                                                                                A topic has been created.
                                                                                                
 
                                                                                                
-
                                                                                                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.
                                                                                                  
+
                                                                                                  Procedure
                                                                                                  1. Log in to the console.
                                                                                                  2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                  4. Click the desired instance to go to the instance details page.
                                                                                                  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
index ff49d32a0..6fbef1543 100644
--- a/docs/dms/umn/kafka_ug_0041.html
+++ b/docs/dms/umn/kafka_ug_0041.html
@@ -3,16 +3,13 @@
 
                                                                                                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.
                                                                                                
-
                                                                                                
-
                                                                                                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.
                                                                                                
+
                                                                                                Notes and Constraints
                                                                                                • 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.
                                                                                                • Unavailable for single-node instances.
                                                                                                
 
                                                                                                
 
                                                                                                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.
                                                                                                
+
                                                                                                Procedure
                                                                                                1. Log in to the console.
                                                                                                2. Click  in the upper left corner to select the region where your 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 go to the instance details page. Choose More > Disable Smart Connect in the upper right corner.
                                                                                                  
+
                                                                                                5. Click  to disable Smart Connect. Then click Next.
                                                                                                6. Ensure that Smart Connect is disabled and click Submit.
                                                                                                  Smart Connect has been successfully disabled if the task is in the Successful state on the Background Tasks tab page of the Background Tasks page.
                                                                                                  
+
                                                                                                
 
                                                                                                
 
                                                                                                
 
                                                                                                
diff --git a/docs/dms/umn/kafka_ug_0043.html b/docs/dms/umn/kafka_ug_0043.html
index 95f3c0745..b6920e8a8 100644
--- a/docs/dms/umn/kafka_ug_0043.html
+++ b/docs/dms/umn/kafka_ug_0043.html
@@ -1,75 +1,89 @@
 
 
 
                                                                                                Configuring Automatic Topic Creation
                                                                                                
-
                                                                                                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.
                                                                                                
+
                                                                                                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.
                                                                                                
+
                                                                                                The following parameters of cluster instances can be changed on the Parameters page: log.retention.hours (retention period), default.replication.factor (replica quantity), or num.partitions (partition quantity). 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 1 Parameters of automatic reassignment
                                                                                                Parameter
                                                                                                
                                                                                                 		
 
                                                                                                Description
                                                                                                
                                                                                                 		
 
                                                                                                
 
                                                                                                Brokers
                                                                                                
+
                                                                                                Broker Name
                                                                                                
                                                                                                 		
 
                                                                                                Select the brokers to assign the topic's partition replicas to.
                                                                                                
                                                                                                 		
 
                                                                                                Topics
                                                                                                
+
                                                                                                Replicas
                                                                                                
                                                                                                 		
 
                                                                                                Enter the number of replicas to be automatically reassigned. The number of replicas must be less than or equal to the number of brokers.
                                                                                                
                                                                                                 		
 
                                                                                                
 
                                                                                                Max. Bandwidth
                                                                                                
 
                                                                                                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.
                                                                                                
+
                                                                                                Specify throttle. The default value is -1, indicating that there is no throttle.
                                                                                                
+
                                                                                                If the instance has low workload (for example, only 30 of 300 MB/s is used), you are not advised to limit the bandwidth. Otherwise, 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.
                                                                                                
                                                                                                 		
 
                                                                                                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.
                                                                                                  
-
                                                                                                2. Click Background tasks tab page. When the task status is Successful, reassignment has completed.
                                                                                                
+
                                                                                              8. Click Background tasks. When the task status is Successful, reassignment has completed.
                                                                                                9. 
                                                                                                 		
 
                                                                                                
                                                                                                 
 
 
                                                                                                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.
                                                                                                  
-
                                                                                                2. Click Background tasks tab page. When the task status is Successful, reassignment has completed.
                                                                                                
+
                                                                                              9. Click Background tasks. When the task status is Successful, reassignment has completed.
                                                                                                10. 
                                                                                                 		
 
                                                                                                
                                                                                                 
 
 
 
 
 
 
 
                                                                                                Table 1 Topic parameters
                                                                                                Parameter
                                                                                                
+
                                                                                                
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
                                                                                                Table 1 Topic parameters
                                                                                                Parameter
                                                                                                
 
                                                                                                Default Value
                                                                                                
+
                                                                                                Default Value (Single-node)
                                                                                                
 
                                                                                                Modified Value
                                                                                                
+
                                                                                                Default Value (Cluster)
                                                                                                
+
                                                                                                Modified To (Cluster)
                                                                                                
                                                                                                 		
 
                                                                                                
 
                                                                                                Partitions
                                                                                                
+
                                                                                                Partitions
                                                                                                
 
                                                                                                3
                                                                                                
+
                                                                                                1
                                                                                                
 
                                                                                                5
                                                                                                
+
                                                                                                3
                                                                                                
+
                                                                                                5
                                                                                                
                                                                                                 		
 
                                                                                                Replicas
                                                                                                
+
                                                                                                Replicas
                                                                                                
 
                                                                                                3
                                                                                                
+
                                                                                                1
                                                                                                
 
                                                                                                3
                                                                                                
+
                                                                                                3
                                                                                                
+
                                                                                                3
                                                                                                
                                                                                                 		
 
                                                                                                Aging Time (h)
                                                                                                
+
                                                                                                Aging Time (h)
                                                                                                
 
                                                                                                72
                                                                                                
+
                                                                                                72
                                                                                                
 
                                                                                                72
                                                                                                
+
                                                                                                72
                                                                                                
+
                                                                                                72
                                                                                                
                                                                                                 		
 
                                                                                                Synchronous Replication
                                                                                                
+
                                                                                                Synchronous Replication
                                                                                                
 
                                                                                                Disabled
                                                                                                
+
                                                                                                Disabled
                                                                                                
 
                                                                                                Disabled
                                                                                                
+
                                                                                                Disabled
                                                                                                
+
                                                                                                Disabled
                                                                                                
                                                                                                 		
 
                                                                                                Synchronous Flushing
                                                                                                
+
                                                                                                Synchronous Flushing
                                                                                                
 
                                                                                                Disabled
                                                                                                
+
                                                                                                Disabled
                                                                                                
 
                                                                                                Disabled
                                                                                                
+
                                                                                                Disabled
                                                                                                
+
                                                                                                Disabled
                                                                                                
                                                                                                 		
 
                                                                                                Message Timestamp
                                                                                                
+
                                                                                                Message Timestamp
                                                                                                
 
                                                                                                CreateTime
                                                                                                
+
                                                                                                CreateTime
                                                                                                
 
                                                                                                CreateTime
                                                                                                
+
                                                                                                CreateTime
                                                                                                
+
                                                                                                CreateTime
                                                                                                
                                                                                                 		
 
                                                                                                Max. Message Size (bytes)
                                                                                                
+
                                                                                                Max. Message Size (bytes)
                                                                                                
 
                                                                                                10,485,760
                                                                                                
+
                                                                                                10,485,760
                                                                                                
 
                                                                                                10,485,760
                                                                                                
+
                                                                                                10,485,760
                                                                                                
+
                                                                                                10,485,760
                                                                                                
                                                                                                 		
 
                                                                                                
                                                                                                 
 
                                                                                                
 
                                                                                                
-
                                                                                                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.
                                                                                                  
-
                                                                                                  
-
                                                                                                6. Click OK.
                                                                                                  You can view the execution status of the task on the Background Tasks page.
                                                                                                  
-
                                                                                                
+
                                                                                                Notes and Constraints
                                                                                                Enabling or disabling automatic topic creation may restart the instance.
                                                                                                
+
                                                                                                
+
                                                                                                Procedure
                                                                                                1. Log in to the console.
                                                                                                2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                4. Click the name of the desired Kafka instance to go to the Basic Information page.
                                                                                                5. In the Instance Information area, click  or  next to Automatic Topic Creation. The Confirm dialog box is displayed.
                                                                                                6. Click OK. The Background Tasks page is displayed. Automatic topic creation has been configured when the task is in the Successful state.
                                                                                                
 
                                                                                                
 
                                                                                                
 
                                                                                                
diff --git a/docs/dms/umn/kafka_ug_0044.html b/docs/dms/umn/kafka_ug_0044.html
index 15684d25f..8c1c0a203 100644
--- a/docs/dms/umn/kafka_ug_0044.html
+++ b/docs/dms/umn/kafka_ug_0044.html
@@ -3,13 +3,11 @@
 
                                                                                                Configuring Plaintext or Ciphertext Access to Kafka Instances
                                                                                                
 
                                                                                                You can access a Kafka instance in plaintext or ciphertext. This section describes how to change the access mode on the console.
                                                                                                
 
                                                                                                • Plaintext access: Clients connect to the Kafka instance without SASL authentication.
                                                                                                • Ciphertext access: Clients connect to the Kafka instance with SASL authentication.
                                                                                                
-
                                                                                                 
                                                                                                • When you change the access mode for the first time, some instances will restart. You can see the actual situation on the console. The restart takes about 75–80s. The instance will not be restarted when the access mode is changed again.
                                                                                                • For a single-node instance, you can only enable or disable plaintext for public network access.
                                                                                                • The access mode cannot be changed for instances with IPv6 enabled.
                                                                                                
-
                                                                                                
+
                                                                                                Notes and Constraints
                                                                                                • When you change the access mode for the first time, some instances will restart. You can see the actual situation on the console. The restart takes about 75–80s. The instance will not be restarted when the access mode is changed again.
                                                                                                • For a single-node instance, you can only enable or disable plaintext for public network access.
                                                                                                • The access mode cannot be changed for instances with IPv6 enabled.
                                                                                                
+
                                                                                                
 
                                                                                                Prerequisites
                                                                                                You can change the access mode of a Kafka instance only when the instance is in the Running state.
                                                                                                
 
                                                                                                
-
                                                                                                Enabling Plaintext 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. An instance can be accessed in plaintext over the private network and public network. For details about how to enable plaintext access, see Table 1.
                                                                                                  
+
                                                                                                  Enabling Plaintext Access
                                                                                                  1. Log in to the console.
                                                                                                  2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                  3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                  4. Click the name of a Kafka instance to go to the Basic Information page.
                                                                                                  5. An instance can be accessed in plaintext over the private network and public network. For details about how to enable plaintext access, see Table 1.
                                                                                                    
 
                                                                                                    
-
-
@@ -31,25 +29,46 @@
 
                                                                                                    
-
                                                                                                    Enabling Ciphertext 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. An instance can be accessed in ciphertext over the private network and public network. For details about how to enable ciphertext access, see Table 2.
                                                                                                      
-
                                                                                                    Table 1 Enabling plaintext access
                                                                                                    Access Method
                                                                                                    
                                                                                                     		
 
                                                                                                    Enabling Plaintext Access
                                                                                                    
@@ -18,12 +16,12 @@
 
                                                                                                    
 
                                                                                                    Private network plaintext access
                                                                                                    
 
                                                                                                    1. Click  next to Plaintext Access in the Private Network Access area. A confirmation dialog box is displayed.
                                                                                                    2. Click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, plaintext access is successfully enabled.
                                                                                                    
+
                                                                                                    1. Click  next to Plaintext Access in the Private Network Access area. A confirmation dialog box is displayed.
                                                                                                    2. Click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, plaintext access is successfully enabled.
                                                                                                    
                                                                                                     		
 
                                                                                                    
 
                                                                                                    Public network plaintext access
                                                                                                    
 
                                                                                                    1. Check that Public Access is enabled. If it is not enabled, enable it. For details, see Configuring Kafka Public Access.
                                                                                                    2. Click  next to Plaintext Access in the Public Network Access area. A confirmation dialog box is displayed.
                                                                                                    3. Click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, plaintext access is successfully enabled.
                                                                                                    
+
                                                                                                    1. Check that Public Access is enabled. If it is not enabled, enable it. For details, see Configuring Kafka Public Access.
                                                                                                    2. Click  next to Plaintext Access in the Public Network Access area. A confirmation dialog box is displayed.
                                                                                                    3. Click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, plaintext access is successfully enabled.
                                                                                                    
                                                                                                     		
 
                                                                                                    
                                                                                                     
 
 
                                                                                                    Table 2 Enabling ciphertext access
                                                                                                    Access Method
                                                                                                    
+
                                                                                                    Disabling Plaintext Access
                                                                                                    1. Log in to the console.
                                                                                                    2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Click the name of a Kafka instance to go to the Basic Information page.
                                                                                                    5. An instance can be accessed in plaintext over the private network and public network. For details about how to disable plaintext access, see Table 2.
                                                                                                      
+
                                                                                                      
-
-
-
+
+
+
+
+
+
                                                                                                      Table 2 Disabling plaintext access
                                                                                                      Access Method
                                                                                                      
 
                                                                                                      Enabling Ciphertext Access
                                                                                                      
+
                                                                                                      Disabling Plaintext Access
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Private network ciphertext access
                                                                                                      
+
                                                                                                      Private network plaintext access
                                                                                                      
 
                                                                                                      1. Click  next to Ciphertext Access in the Private Network Access area. The Private Network Ciphertext Access dialog box is displayed.
                                                                                                      2. Set the Kafka security protocol, SASL/PLAIN mechanism, username, and password, and click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, ciphertext access is successfully enabled.
                                                                                                         NOTE: 
                                                                                                        • When enabling ciphertext access for the first time (including through private network and public network), you need to set the Kafka security protocol, SASL/PLAIN mechanism, username, and password. Next time when you enable ciphertext access, you only need to set the Kafka security protocol.
                                                                                                        • To disable private network ciphertext access, contact customer service.
                                                                                                        
+
                                                                                                      Once enabled, private network access cannot be disabled. Enable plaintext or ciphertext access, or both. If ciphertext access is disabled, plaintext access cannot be disabled.
                                                                                                      
+
                                                                                                      1. Click  next to Plaintext Access in the Private Network Access area.
                                                                                                      2. Click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, plaintext access is successfully disabled.
                                                                                                      
+
                                                                                                      Public network plaintext access
                                                                                                      
+
                                                                                                      1. Click  next to Plaintext Access in the Public Network Access area.
                                                                                                      2. Click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, plaintext access is successfully disabled.
                                                                                                      
+
                                                                                                      
+
                                                                                                      
+
                                                                                                    
+
                                                                                                    
+
                                                                                                    Enabling Ciphertext Access
                                                                                                    1. Log in to the console.
                                                                                                    2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                    3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                    4. Click the name of a Kafka instance to go to the Basic Information page.
                                                                                                    5. An instance can be accessed in ciphertext over the private network and public network. For details about how to enable ciphertext access, see Table 3.
                                                                                                      
+
                                                                                                      
+
+
+
+
+
-
-
@@ -59,91 +78,63 @@
 
                                                                                                      The Kafka security protocol, SASL/PLAIN mechanism, username, and password are described as follows.
                                                                                                      
 
-
                                                                                                      Table 3 Enabling ciphertext access
                                                                                                      Access Method
                                                                                                      
+
                                                                                                      Enabling Ciphertext Access
                                                                                                      
+
                                                                                                      Private network ciphertext access
                                                                                                      
+
                                                                                                      1. Click  next to Ciphertext Access in the Private Network Access area. The Private Network Ciphertext Access dialog box is displayed.
                                                                                                      2. Set the Kafka security protocol, SASL/PLAIN mechanism, username, and password, and click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, ciphertext access is successfully enabled.
                                                                                                         NOTE: 
                                                                                                        • When enabling ciphertext access for the first time (including through private network and public network), you need to set the Kafka security protocol, SASL/PLAIN mechanism, username, and password. Next time when you enable ciphertext access, you only need to set the Kafka security protocol.
                                                                                                        • To disable private network ciphertext access, contact customer service.
                                                                                                        
 
                                                                                                        
 
                                                                                                      
                                                                                                       		
 
                                                                                                      Public network ciphertext access
                                                                                                      
+
                                                                                                      Public network ciphertext access
                                                                                                      
 
                                                                                                      1. Check that Public Access is enabled. If it is not enabled, enable it. For details, see Configuring Kafka Public Access.
                                                                                                      2. Click  next to Ciphertext Access in the Public Network Access area. The Public Network Ciphertext Access dialog box is displayed.
                                                                                                      3. Set the Kafka security protocol, SASL/PLAIN mechanism, username, and password, and click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, ciphertext access is successfully enabled.
                                                                                                         NOTE: 
                                                                                                        When enabling ciphertext access for the first time (including through private network and public network), you need to set the Kafka security protocol, SASL/PLAIN mechanism, username, and password. Next time when you enable ciphertext access, you only need to set the Kafka security protocol.
                                                                                                        
+
                                                                                                      1. Check that Public Access is enabled. If it is not enabled, enable it. For details, see Configuring Kafka Public Access.
                                                                                                      2. Click  next to Ciphertext Access in the Public Network Access area. The Public Network Ciphertext Access dialog box is displayed.
                                                                                                      3. Set the Kafka security protocol, SASL/PLAIN mechanism, username, and password, and click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, ciphertext access is successfully enabled.
                                                                                                         NOTE: 
                                                                                                        When enabling ciphertext access for the first time (including through private network and public network), you need to set the Kafka security protocol, SASL/PLAIN mechanism, username, and password. Next time when you enable ciphertext access, you only need to set the Kafka security protocol.
                                                                                                        
 
                                                                                                        
 
                                                                                                      
                                                                                                       		
 
                                                                                                      Table 3 Ciphertext access parameters
                                                                                                      Parameter
                                                                                                      
+
                                                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                      Table 4 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.
                                                                                                      
                                                                                                       		
 
                                                                                                      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 authentication is recommended for plaintext transmission.
                                                                                                      
                                                                                                       		
 
                                                                                                      Cross-VPC Access Protocol
                                                                                                      
+
                                                                                                      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.
                                                                                                      
+
                                                                                                      • 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
                                                                                                      
+
                                                                                                      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.
                                                                                                      
+
                                                                                                      • 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.
                                                                                                      
 
                                                                                                      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.
                                                                                                      
                                                                                                       		
 
                                                                                                      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.
                                                                                                      • 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 forward or backward.
                                                                                                      
+
                                                                                                      • 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 forward or backward.
                                                                                                      
 
                                                                                                      The username cannot be changed once ciphertext access is enabled.
                                                                                                      
                                                                                                       		
 
                                                                                                      
                                                                                                       
 
                                                                                                      
 
                                                                                                      
-
                                                                                                       
                                                                                                      The Kafka security protocol, SASL/PLAIN mechanism, username, and password are required when the client accesses a Kafka instance with ciphertext access enabled. For details, see Connecting to Kafka Using the Client (Ciphertext Access).
                                                                                                      
-
                                                                                                      
+
                                                                                                      The Kafka security protocol, SASL/PLAIN mechanism, username, and password are required when the client accesses a Kafka instance with ciphertext access enabled. For details, see Connecting to Kafka Using the Client (Ciphertext Access).
                                                                                                      
 
                                                                                                      
 
-
                                                                                                      Disabling Plaintext 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. An instance can be accessed in plaintext over the private network and public network. For details about how to disable plaintext access, see Table 4.
                                                                                                        
-
                                                                                                        
-
-
-
-
-
-
-
-
-
-
-
                                                                                                        Table 4 Disabling plaintext access
                                                                                                        Access Method
                                                                                                        
-
                                                                                                        Disabling Plaintext Access
                                                                                                        
-
                                                                                                        Private network plaintext access
                                                                                                        
-
                                                                                                        Once enabled, private network access cannot be disabled. Enable plaintext or ciphertext access, or both. If ciphertext access is disabled, plaintext access cannot be disabled.
                                                                                                        
-
                                                                                                        1. Click  next to Plaintext Access in the Private Network Access area.
                                                                                                        2. Click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, plaintext access is successfully disabled.
                                                                                                        
-
                                                                                                        Public network plaintext access
                                                                                                        
-
                                                                                                        1. Click  next to Plaintext Access in the Public Network Access area.
                                                                                                        2. Click OK. The Background Tasks page is displayed. If the status of the task turns to Successful, plaintext access is successfully disabled.
                                                                                                        
-
                                                                                                        
-
                                                                                                        
-
                                                                                                      
-
                                                                                                      
-
                                                                                                      Disabling Ciphertext 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. An instance can be accessed in ciphertext over the private network and public network. For details about how to disable ciphertext access, see Table 5.
                                                                                                        
+
                                                                                                        Disabling Ciphertext Access
                                                                                                        1. Log in to the console.
                                                                                                        2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                        4. Click the name of a Kafka instance to go to the Basic Information page.
                                                                                                        5. An instance can be accessed in ciphertext over the private network and public network. For details about how to disable ciphertext access, see Table 5.
                                                                                                          
 
                                                                                                          Table 5 Disabling ciphertext access
                                                                                                          Access Method
                                                                                                          
                                                                                                           		
 
                                                                                                          Disabling Plaintext Access
                                                                                                          
@@ -163,8 +154,7 @@
 
 
                                                                                                          
 
                                                                                                          
-
                                                                                                           
                                                                                                          After you disable ciphertext access, the created users will not be deleted. You do not need to create users again when you enable ciphertext access next time.
                                                                                                          
-
                                                                                                          
+
                                                                                                          After you disable ciphertext access, the created users will not be deleted. You do not need to create users again when you enable ciphertext access next time.
                                                                                                          
 
                                                                                                        
 
                                                                                                        
 
                                                                                                      
diff --git a/docs/dms/umn/kafka_ug_0045.html b/docs/dms/umn/kafka_ug_0045.html
index 4841e1661..345ec496b 100644
--- a/docs/dms/umn/kafka_ug_0045.html
+++ b/docs/dms/umn/kafka_ug_0045.html
@@ -2,18 +2,144 @@
 
 
                                                                                                      Viewing Kafka Topic Details
                                                                                                      
 
                                                                                                      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.
                                                                                                        
+
                                                                                                        Notes and Constraints
                                                                                                        • If an instance contains more than 10,000 consumer groups, the subscribed topics cannot be queried.
                                                                                                        • The producer information is displayed only when a producer is producing messages into topics.
                                                                                                        
+
                                                                                                        
+
                                                                                                        Procedure
                                                                                                        1. Log in to the console.
                                                                                                        2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                        3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                        4. Click the desired instance to go to the instance details page.
                                                                                                        5. In the navigation pane, choose Topics.
                                                                                                        6. Click a topic to view its details.
                                                                                                          On the topic details page, the basic information, partitions, producers, and subscriptions are displayed.
                                                                                                          
+
+
                                                                                                          
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                          Table 1 Basic topic information
                                                                                                          Parameter
                                                                                                          
+
                                                                                                          Description
                                                                                                          
+
                                                                                                          Topic Name
                                                                                                          
+
                                                                                                          Name of this topic.
                                                                                                          
+
                                                                                                          Brokers
                                                                                                          
+
                                                                                                          This topic has been associated with brokers.
                                                                                                          
+
                                                                                                          Partitions
                                                                                                          
+
                                                                                                          Number of partitions of this topic.
                                                                                                          
+
                                                                                                          Created
                                                                                                          
+
                                                                                                           CAUTION: 
                                                                                                          The topic creation time is not displayed on the topic details page in any of the following cases:
                                                                                                          
+
                                                                                                          • The topics were created much earlier. See the console.
                                                                                                          • The topics were created automatically, or by commands or code on the client.
                                                                                                          
 
                                                                                                          
-
                                                                                                        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.
                                                                                                            
+
                                                                                                            Time when this topic is created.
                                                                                                            
+
                                                                                                          11. 
+
                                                                                                          
+
                                                                                                          Figure 1 Partitions
                                                                                                          
+
+
                                                                                                          
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                          Table 2 Partition information of a topic
                                                                                                          Parameter
                                                                                                          
+
                                                                                                          Description
                                                                                                          
+
                                                                                                          Partition
                                                                                                          
+
                                                                                                          Partition No. of this topic.
                                                                                                          
+
                                                                                                          Minimum Offset
                                                                                                          
+
                                                                                                          Minimum offset of this partition.
                                                                                                          
+
                                                                                                          Maximum Offset
                                                                                                          
+
                                                                                                          Maximum offset of this partition.
                                                                                                          
+
                                                                                                          Messages
                                                                                                          
+
                                                                                                          Number of messages in this partition.
                                                                                                          
+
                                                                                                          Updated
                                                                                                          
+
                                                                                                          Time when the last message in this partition is updated.
                                                                                                          
+
                                                                                                          
+
                                                                                                          
+
                                                                                                           
                                                                                                          For topics created much earlier, Producer tab page is not displayed on the topic details page. See the console.
                                                                                                          
 
                                                                                                          
-
                                                                                                        11. 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.
                                                                                                          
+
+
                                                                                                          
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                          Table 3 Producer information of a topic
                                                                                                          Parameter
                                                                                                          
+
                                                                                                          Description
                                                                                                          
+
                                                                                                          Broker Address
                                                                                                          
+
                                                                                                          Broker address of the Kafka instance connected to the producer.
                                                                                                          
+
                                                                                                          Producer Address
                                                                                                          
+
                                                                                                          Address of the producer client.
                                                                                                          
+
                                                                                                          Producer Connected
                                                                                                          
+
                                                                                                          Time when the producer is connected to the Kafka instance.
                                                                                                          
+
                                                                                                          
+
                                                                                                          
+
                                                                                                           
                                                                                                          If an instance contains more than 10,000 consumer groups, the subscribed topics cannot be queried.
                                                                                                          
 
                                                                                                          
-
                                                                                                        12. Partitions: partition No., minimum offset, maximum offset, number of messages, and message update time
                                                                                                          Figure 1 Partitions
                                                                                                          
-
                                                                                                        13. 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.
                                                                                                          
-
                                                                                                          
-
                                                                                                          14. 
+
+
                                                                                                          
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                          Table 4 Subscriptions of a topic
                                                                                                          Parameter
                                                                                                          
+
                                                                                                          Description
                                                                                                          
+
                                                                                                          Consumer Group Name
                                                                                                          
+
                                                                                                          Name of the consumer group that subscribes to this topic.
                                                                                                          
+
                                                                                                          Clicking a consumer group name can go to the consumer group details page and view the consumer list and consumption progress.
                                                                                                          
+
                                                                                                          Status
                                                                                                          
+
                                                                                                          Current status of a consumer group.
                                                                                                          
+
                                                                                                          • DEAD: The consumer group has no member or metadata.
                                                                                                          • EMPTY: The consumer group has metadata but has no member.
                                                                                                          • PREPARING_REBALANCE: The consumer group is to be rebalanced.
                                                                                                          • COMPLETING_REBALANCE: All members have joined the consumer group.
                                                                                                          • STABLE: Members in the consumer group can consume messages normally.
                                                                                                          
+
                                                                                                          Coordinator(ID)
                                                                                                          
+
                                                                                                          Broker where the Coordinator component is.
                                                                                                          
+
                                                                                                          Accumulated Messages
                                                                                                          
+
                                                                                                          Number of remaining messages that can be consumed in a consumer group.
                                                                                                          
+
                                                                                                          Details
                                                                                                          
+
                                                                                                          Clicking Details to go to the consumer group details.
                                                                                                          
+
                                                                                                          
+
                                                                                                          
 
                                                                                                        
 
                                                                                                        
 
                                                                                                        
diff --git a/docs/dms/umn/kafka_ug_0046.html b/docs/dms/umn/kafka_ug_0046.html
index 88fa04b92..d12ec04ed 100644
--- a/docs/dms/umn/kafka_ug_0046.html
+++ b/docs/dms/umn/kafka_ug_0046.html
@@ -2,17 +2,13 @@
 
 
                                                                                                        Deleting Kafka Messages
                                                                                                        
 
                                                                                                        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.
                                                                                                        
-
                                                                                                        
+
                                                                                                        Notes and Constraints
                                                                                                        Deleting messages takes effect permanently.
                                                                                                        
 
                                                                                                        
-
                                                                                                        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
                                                                                                          
+
                                                                                                          Prerequisite
                                                                                                          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.
                                                                                                          
+
                                                                                                          
+
                                                                                                          Procedure
                                                                                                          1. Log in to the console.
                                                                                                          2. Click  in the upper left corner to select the region where your instance is located.
                                                                                                          3. Click Service List and choose Application > Distributed Message Service. The Kafka instance list is displayed.
                                                                                                          4. Click the desired instance to go to the instance details page.
                                                                                                          5. In the navigation pane, choose Topics.
                                                                                                          6. In the row that contains the topic whose messages you want to delete, choose More > Delete Messages. The Delete Messages dialog box is displayed.
                                                                                                          7. Set the parameters for deleting messages, as shown in Table 1.
                                                                                                            Figure 1 Deleting messages
                                                                                                            
 
 
                                                                                                            
@@ -28,7 +24,7 @@
 
@@ -37,6 +33,8 @@
 
                                                                                                            To delete messages from multiple partitions, click Add Partition and specify the partition and offset for the messages to be deleted. 10 partitions can be deleted at most at a time.
                                                                                                          8. Click OK. The Deletion Result dialog box is displayed. Click OK to delete the messages.
                                                                                                            Figure 2 Deletion result
                                                                                                            
+
                                                                                                          9. Verify whether the message is deleted.
                                                                                                            To query with offset on the Message Query page, enter the following parameters. If no message is found, it is deleted successfully.
                                                                                                            • Partition: Enter the partition No. from 7.
                                                                                                            • Offset: Enter a random offset if the offset from 7 is -1. Otherwise, enter an integer smaller than the offset.
                                                                                                            
+
                                                                                                            
 
                                                                                                            10. Table 1 Parameters for deleting a message
                                                                                                            Parameter
                                                                                                            
 
                                                                                                            Offset
                                                                                                            
                                                                                                             		
 
                                                                                                            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.
                                                                                                            
+
                                                                                                             WARNING: 
                                                                                                            • 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.