You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by pe...@apache.org on 2021/11/11 13:35:11 UTC
[pulsar] branch asf-site updated: Updated site at revision 5dbb7d2
This is an automated email from the ASF dual-hosted git repository.
penghui pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/asf-site by this push:
new dc51dae Updated site at revision 5dbb7d2
dc51dae is described below
commit dc51dae7ab020976ea36097639c1da662cab256c
Author: Pulsar Site Updater <de...@pulsar.incubator.apache.org>
AuthorDate: Thu Nov 11 13:33:38 2021 +0000
Updated site at revision 5dbb7d2
---
content/api/admin/2.10.0-SNAPSHOT/index-all.html | 2 +
.../pulsar/client/admin/internal/BaseResource.html | 22 +-
.../pulsar/client/admin/internal/BookiesImpl.html | 2 +-
.../client/admin/internal/BrokerStatsImpl.html | 2 +-
.../pulsar/client/admin/internal/BrokersImpl.html | 2 +-
.../pulsar/client/admin/internal/ClustersImpl.html | 2 +-
.../client/admin/internal/ComponentResource.html | 2 +-
.../client/admin/internal/FunctionsImpl.html | 2 +-
.../pulsar/client/admin/internal/LookupImpl.html | 2 +-
.../client/admin/internal/NamespacesImpl.html | 2 +-
.../admin/internal/NonPersistentTopicsImpl.html | 2 +-
.../pulsar/client/admin/internal/PackagesImpl.html | 2 +-
.../client/admin/internal/ProxyStatsImpl.html | 2 +-
.../client/admin/internal/ResourceGroupsImpl.html | 2 +-
.../client/admin/internal/ResourceQuotasImpl.html | 2 +-
.../pulsar/client/admin/internal/SchemasImpl.html | 2 +-
.../pulsar/client/admin/internal/SinksImpl.html | 2 +-
.../pulsar/client/admin/internal/SourcesImpl.html | 2 +-
.../pulsar/client/admin/internal/TenantsImpl.html | 2 +-
.../client/admin/internal/TopicPoliciesImpl.html | 2 +-
.../pulsar/client/admin/internal/TopicsImpl.html | 2 +-
.../client/admin/internal/TransactionsImpl.html | 2 +-
.../pulsar/client/admin/internal/WorkerImpl.html | 2 +-
.../pulsar-broker/2.10.0-SNAPSHOT/index-all.html | 14 +-
.../apache/pulsar/broker/class-use/BundleData.html | 28 +
.../broker/loadbalance/ModularLoadManager.html | 42 +-
.../loadbalance/impl/ModularLoadManagerImpl.html | 64 +-
.../common/naming/NamespaceBundleFactory.html | 49 +-
.../common/naming/class-use/NamespaceBundle.html | 10 +-
content/api/python/2.10.0-SNAPSHOT/index.html | 6 +-
content/api/python/index.html | 6 +-
.../zh-CN/2.1.0-incubating/concepts-messaging.html | 6 +-
.../2.1.0-incubating/concepts-messaging/index.html | 6 +-
.../deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
.../zh-CN/2.1.1-incubating/concepts-messaging.html | 6 +-
.../2.1.1-incubating/concepts-messaging/index.html | 6 +-
.../deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
content/docs/zh-CN/2.2.0/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.2.0/concepts-messaging/index.html | 6 +-
.../2.2.0/deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
content/docs/zh-CN/2.2.1/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.2.1/concepts-messaging/index.html | 6 +-
.../2.2.1/deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
content/docs/zh-CN/2.3.0/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.3.0/concepts-messaging/index.html | 2 +-
.../2.3.0/deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
content/docs/zh-CN/2.3.0/reference-cli-tools.html | 14 +-
.../zh-CN/2.3.0/reference-cli-tools/index.html | 14 +-
content/docs/zh-CN/2.3.1/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.3.1/concepts-messaging/index.html | 2 +-
.../2.3.1/deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
content/docs/zh-CN/2.3.1/reference-cli-tools.html | 28 +-
.../zh-CN/2.3.1/reference-cli-tools/index.html | 28 +-
content/docs/zh-CN/2.3.2/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.3.2/concepts-messaging/index.html | 2 +-
.../2.3.2/deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
content/docs/zh-CN/2.3.2/reference-cli-tools.html | 30 +-
.../zh-CN/2.3.2/reference-cli-tools/index.html | 30 +-
content/docs/zh-CN/2.4.0/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.4.0/concepts-messaging/index.html | 2 +-
.../2.4.0/deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
content/docs/zh-CN/2.4.0/reference-cli-tools.html | 38 +-
.../zh-CN/2.4.0/reference-cli-tools/index.html | 38 +-
content/docs/zh-CN/2.4.1/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.4.1/concepts-messaging/index.html | 2 +-
.../2.4.1/deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
content/docs/zh-CN/2.4.1/reference-cli-tools.html | 38 +-
.../zh-CN/2.4.1/reference-cli-tools/index.html | 38 +-
content/docs/zh-CN/2.4.2/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.4.2/concepts-messaging/index.html | 2 +-
.../2.4.2/deploy-bare-metal-multi-cluster.html | 2 +-
.../deploy-bare-metal-multi-cluster/index.html | 2 +-
content/docs/zh-CN/2.4.2/reference-cli-tools.html | 38 +-
.../zh-CN/2.4.2/reference-cli-tools/index.html | 38 +-
content/docs/zh-CN/2.5.0/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.5.0/concepts-messaging/index.html | 2 +-
.../2.5.0/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.5.0/helm-install.html | 2 +-
content/docs/zh-CN/2.5.0/helm-install/index.html | 2 +-
content/docs/zh-CN/2.5.0/helm-prepare.html | 8 +-
content/docs/zh-CN/2.5.0/helm-prepare/index.html | 8 +-
content/docs/zh-CN/2.5.0/reference-cli-tools.html | 48 +-
.../zh-CN/2.5.0/reference-cli-tools/index.html | 48 +-
content/docs/zh-CN/2.5.1/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.5.1/concepts-messaging/index.html | 2 +-
.../2.5.1/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.5.1/helm-install.html | 2 +-
content/docs/zh-CN/2.5.1/helm-install/index.html | 2 +-
content/docs/zh-CN/2.5.1/helm-prepare.html | 8 +-
content/docs/zh-CN/2.5.1/helm-prepare/index.html | 8 +-
content/docs/zh-CN/2.5.1/reference-cli-tools.html | 48 +-
.../zh-CN/2.5.1/reference-cli-tools/index.html | 48 +-
content/docs/zh-CN/2.5.2/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.5.2/concepts-messaging/index.html | 2 +-
.../2.5.2/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.5.2/helm-install.html | 2 +-
content/docs/zh-CN/2.5.2/helm-install/index.html | 2 +-
content/docs/zh-CN/2.5.2/helm-prepare.html | 8 +-
content/docs/zh-CN/2.5.2/helm-prepare/index.html | 8 +-
content/docs/zh-CN/2.5.2/reference-cli-tools.html | 48 +-
.../zh-CN/2.5.2/reference-cli-tools/index.html | 48 +-
content/docs/zh-CN/2.6.0/concepts-messaging.html | 2 +-
.../docs/zh-CN/2.6.0/concepts-messaging/index.html | 2 +-
.../2.6.0/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.6.0/helm-install.html | 2 +-
content/docs/zh-CN/2.6.0/helm-install/index.html | 2 +-
content/docs/zh-CN/2.6.0/helm-prepare.html | 10 +-
content/docs/zh-CN/2.6.0/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.6.0/reference-cli-tools.html | 60 +-
.../zh-CN/2.6.0/reference-cli-tools/index.html | 60 +-
.../zh-CN/2.6.0/sql-deployment-configurations.html | 2 +-
.../2.6.0/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/2.6.1/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.6.1/concepts-messaging/index.html | 6 +-
.../2.6.1/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.6.1/helm-install.html | 2 +-
content/docs/zh-CN/2.6.1/helm-install/index.html | 2 +-
content/docs/zh-CN/2.6.1/helm-prepare.html | 10 +-
content/docs/zh-CN/2.6.1/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.6.1/reference-cli-tools.html | 60 +-
.../zh-CN/2.6.1/reference-cli-tools/index.html | 60 +-
.../zh-CN/2.6.1/sql-deployment-configurations.html | 2 +-
.../2.6.1/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/2.6.2/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.6.2/concepts-messaging/index.html | 6 +-
.../2.6.2/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.6.2/helm-install.html | 2 +-
content/docs/zh-CN/2.6.2/helm-install/index.html | 2 +-
content/docs/zh-CN/2.6.2/helm-prepare.html | 10 +-
content/docs/zh-CN/2.6.2/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.6.2/reference-cli-tools.html | 66 +-
.../zh-CN/2.6.2/reference-cli-tools/index.html | 66 +-
.../zh-CN/2.6.2/sql-deployment-configurations.html | 2 +-
.../2.6.2/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/2.6.3/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.6.3/concepts-messaging/index.html | 6 +-
.../2.6.3/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.6.3/helm-install.html | 2 +-
content/docs/zh-CN/2.6.3/helm-install/index.html | 2 +-
content/docs/zh-CN/2.6.3/helm-prepare.html | 10 +-
content/docs/zh-CN/2.6.3/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.6.3/reference-cli-tools.html | 66 +-
.../zh-CN/2.6.3/reference-cli-tools/index.html | 66 +-
.../zh-CN/2.6.3/sql-deployment-configurations.html | 2 +-
.../2.6.3/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/2.6.4/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.6.4/concepts-messaging/index.html | 6 +-
.../2.6.4/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.6.4/helm-install.html | 2 +-
content/docs/zh-CN/2.6.4/helm-install/index.html | 2 +-
content/docs/zh-CN/2.6.4/helm-prepare.html | 10 +-
content/docs/zh-CN/2.6.4/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.6.4/reference-cli-tools.html | 66 +-
.../zh-CN/2.6.4/reference-cli-tools/index.html | 66 +-
.../zh-CN/2.6.4/sql-deployment-configurations.html | 2 +-
.../2.6.4/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/2.7.0/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.7.0/concepts-messaging/index.html | 6 +-
.../2.7.0/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.7.0/helm-install.html | 2 +-
content/docs/zh-CN/2.7.0/helm-install/index.html | 2 +-
content/docs/zh-CN/2.7.0/helm-prepare.html | 10 +-
content/docs/zh-CN/2.7.0/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.7.0/reference-cli-tools.html | 66 +-
.../zh-CN/2.7.0/reference-cli-tools/index.html | 66 +-
.../zh-CN/2.7.0/sql-deployment-configurations.html | 2 +-
.../2.7.0/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/2.7.1/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.7.1/concepts-messaging/index.html | 6 +-
.../2.7.1/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.7.1/helm-install.html | 2 +-
content/docs/zh-CN/2.7.1/helm-install/index.html | 2 +-
content/docs/zh-CN/2.7.1/helm-prepare.html | 10 +-
content/docs/zh-CN/2.7.1/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.7.1/reference-cli-tools.html | 72 +-
.../zh-CN/2.7.1/reference-cli-tools/index.html | 72 +-
.../zh-CN/2.7.1/sql-deployment-configurations.html | 2 +-
.../2.7.1/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/2.7.2/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.7.2/concepts-messaging/index.html | 6 +-
.../2.7.2/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.7.2/helm-install.html | 2 +-
content/docs/zh-CN/2.7.2/helm-install/index.html | 2 +-
content/docs/zh-CN/2.7.2/helm-prepare.html | 10 +-
content/docs/zh-CN/2.7.2/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.7.2/reference-cli-tools.html | 72 +-
.../zh-CN/2.7.2/reference-cli-tools/index.html | 72 +-
.../zh-CN/2.7.2/sql-deployment-configurations.html | 2 +-
.../2.7.2/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/2.7.3/concepts-messaging.html | 6 +-
.../docs/zh-CN/2.7.3/concepts-messaging/index.html | 6 +-
.../2.7.3/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.7.3/helm-install.html | 2 +-
content/docs/zh-CN/2.7.3/helm-install/index.html | 2 +-
content/docs/zh-CN/2.7.3/helm-prepare.html | 10 +-
content/docs/zh-CN/2.7.3/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.7.3/reference-cli-tools.html | 72 +-
.../zh-CN/2.7.3/reference-cli-tools/index.html | 72 +-
.../zh-CN/2.7.3/sql-deployment-configurations.html | 2 +-
.../2.7.3/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/2.8.0/concepts-messaging.html | 8 +-
.../docs/zh-CN/2.8.0/concepts-messaging/index.html | 8 +-
.../2.8.0/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/2.8.0/helm-install.html | 2 +-
content/docs/zh-CN/2.8.0/helm-install/index.html | 2 +-
content/docs/zh-CN/2.8.0/helm-prepare.html | 10 +-
content/docs/zh-CN/2.8.0/helm-prepare/index.html | 10 +-
content/docs/zh-CN/2.8.0/reference-cli-tools.html | 92 +--
.../zh-CN/2.8.0/reference-cli-tools/index.html | 92 +--
.../zh-CN/2.8.0/sql-deployment-configurations.html | 2 +-
.../2.8.0/sql-deployment-configurations/index.html | 2 +-
content/docs/zh-CN/concepts-messaging.html | 8 +-
content/docs/zh-CN/concepts-messaging/index.html | 8 +-
.../zh-CN/deploy-bare-metal-multi-cluster.html | 4 +-
.../deploy-bare-metal-multi-cluster/index.html | 4 +-
content/docs/zh-CN/helm-install.html | 2 +-
content/docs/zh-CN/helm-install/index.html | 2 +-
content/docs/zh-CN/helm-prepare.html | 10 +-
content/docs/zh-CN/helm-prepare/index.html | 10 +-
content/docs/zh-CN/next/concepts-messaging.html | 126 +--
.../docs/zh-CN/next/concepts-messaging/index.html | 126 +--
.../next/deploy-bare-metal-multi-cluster.html | 54 +-
.../deploy-bare-metal-multi-cluster/index.html | 54 +-
content/docs/zh-CN/next/helm-install.html | 2 +-
content/docs/zh-CN/next/helm-install/index.html | 2 +-
content/docs/zh-CN/next/helm-prepare.html | 4 +-
content/docs/zh-CN/next/helm-prepare/index.html | 4 +-
content/docs/zh-CN/next/reference-cli-tools.html | 144 ++--
.../docs/zh-CN/next/reference-cli-tools/index.html | 144 ++--
.../zh-CN/next/sql-deployment-configurations.html | 86 +-
.../next/sql-deployment-configurations/index.html | 86 +-
content/docs/zh-CN/reference-cli-tools.html | 92 +--
content/docs/zh-CN/reference-cli-tools/index.html | 92 +--
.../docs/zh-CN/sql-deployment-configurations.html | 2 +-
.../zh-CN/sql-deployment-configurations/index.html | 2 +-
content/swagger/2.10.0-SNAPSHOT/swagger.json | 902 ++++++++++----------
.../swagger/2.10.0-SNAPSHOT/swaggerfunctions.json | 510 ++++++------
.../swagger/2.10.0-SNAPSHOT/swaggerpackages.json | 404 ++++-----
content/swagger/2.10.0-SNAPSHOT/swaggersink.json | 404 ++++-----
content/swagger/2.10.0-SNAPSHOT/swaggersource.json | 404 ++++-----
content/swagger/2.10.0-SNAPSHOT/v2/swagger.json | 910 ++++++++++-----------
.../2.10.0-SNAPSHOT/v3/swaggerfunctions.json | 510 ++++++------
.../2.10.0-SNAPSHOT/v3/swaggerpackages.json | 404 ++++-----
.../swagger/2.10.0-SNAPSHOT/v3/swaggersink.json | 404 ++++-----
.../swagger/2.10.0-SNAPSHOT/v3/swaggersource.json | 404 ++++-----
content/swagger/master/swagger.json | 902 ++++++++++----------
content/swagger/master/swaggerfunctions.json | 510 ++++++------
content/swagger/master/swaggerpackages.json | 404 ++++-----
content/swagger/master/swaggersink.json | 404 ++++-----
content/swagger/master/swaggersource.json | 404 ++++-----
content/swagger/master/v2/swagger.json | 910 ++++++++++-----------
content/swagger/master/v3/swaggerfunctions.json | 510 ++++++------
content/swagger/master/v3/swaggerpackages.json | 404 ++++-----
content/swagger/master/v3/swaggersink.json | 404 ++++-----
content/swagger/master/v3/swaggersource.json | 404 ++++-----
.../tools/pulsar-admin/2.10.0-SNAPSHOT/index.html | 7 +-
278 files changed, 7371 insertions(+), 7229 deletions(-)
diff --git a/content/api/admin/2.10.0-SNAPSHOT/index-all.html b/content/api/admin/2.10.0-SNAPSHOT/index-all.html
index 247c9cf..def0804 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/index-all.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/index-all.html
@@ -2449,6 +2449,8 @@
<dd> </dd>
<dt><span class="memberNameLink"><a href="org/apache/pulsar/client/admin/internal/SourcesImpl.html#stopSourceAsync-java.lang.String-java.lang.String-java.lang.String-">stopSourceAsync(String, String, String)</a></span> - Method in class org.apache.pulsar.client.admin.internal.<a href="org/apache/pulsar/client/admin/internal/SourcesImpl.html" title="class in org.apache.pulsar.client.admin.internal">SourcesImpl</a></dt>
<dd> </dd>
+<dt><span class="memberNameLink"><a href="org/apache/pulsar/client/admin/internal/BaseResource.html#sync-java.util.function.Supplier-">sync(Supplier<CompletableFuture<T>>)</a></span> - Method in class org.apache.pulsar.client.admin.internal.<a href="org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></dt>
+<dd> </dd>
</dl>
<a name="I:T">
<!-- -->
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BaseResource.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BaseResource.html
index ab51038..4ee0de7 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BaseResource.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BaseResource.html
@@ -18,7 +18,7 @@
catch(err) {
}
//-->
-var methods = {"i0":10,"i1":10,"i2":10,"i3":10,"i4":10,"i5":10,"i6":10,"i7":9,"i8":10,"i9":10};
+var methods = {"i0":10,"i1":10,"i2":10,"i3":10,"i4":10,"i5":10,"i6":10,"i7":9,"i8":10,"i9":10,"i10":10};
var tabs = {65535:["t0","All Methods"],1:["t1","Static Methods"],2:["t2","Instance Methods"],8:["t4","Concrete Methods"]};
var altColor = "altColor";
var rowColor = "rowColor";
@@ -221,6 +221,10 @@ extends <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Object.html
<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><javax.ws.rs.client.Invocation.Builder></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#requestAsync-javax.ws.rs.client.WebTarget-">requestAsync</a></span>(javax.ws.rs.client.WebTarget target)</code> </td>
</tr>
+<tr id="i10" class="altColor">
+<td class="colFirst"><code>protected <T> T</code></td>
+<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#sync-java.util.function.Supplier-">sync</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/util/function/Supplier.html?is-external=true" title="class or interface in java.util.function">Supplier</a><<a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or inter [...]
+</tr>
</table>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
@@ -380,12 +384,26 @@ extends <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Object.html
<a name="getReasonFromServer-javax.ws.rs.WebApplicationException-">
<!-- -->
</a>
-<ul class="blockListLast">
+<ul class="blockList">
<li class="blockList">
<h4>getReasonFromServer</h4>
<pre>public static <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> getReasonFromServer(javax.ws.rs.WebApplicationException e)</pre>
</li>
</ul>
+<a name="sync-java.util.function.Supplier-">
+<!-- -->
+</a>
+<ul class="blockListLast">
+<li class="blockList">
+<h4>sync</h4>
+<pre>protected <T> T sync(<a href="https://docs.oracle.com/javase/8/docs/api/java/util/function/Supplier.html?is-external=true" title="class or interface in java.util.function">Supplier</a><<a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><T>> executor)
+ throws org.apache.pulsar.client.admin.PulsarAdminException</pre>
+<dl>
+<dt><span class="throwsLabel">Throws:</span></dt>
+<dd><code>org.apache.pulsar.client.admin.PulsarAdminException</code></dd>
+</dl>
+</li>
+</ul>
</li>
</ul>
</li>
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BookiesImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BookiesImpl.html
index 024d528..5963726 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BookiesImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BookiesImpl.html
@@ -223,7 +223,7 @@ implements org.apache.pulsar.client.admin.Bookies</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BrokerStatsImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BrokerStatsImpl.html
index 47123b3..2b8d431 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BrokerStatsImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BrokerStatsImpl.html
@@ -232,7 +232,7 @@ implements org.apache.pulsar.client.admin.BrokerStats</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BrokersImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BrokersImpl.html
index 228c2b9..ead56331 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BrokersImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/BrokersImpl.html
@@ -287,7 +287,7 @@ implements org.apache.pulsar.client.admin.Brokers</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ClustersImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ClustersImpl.html
index 5e5a451..1c1dbff 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ClustersImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ClustersImpl.html
@@ -363,7 +363,7 @@ implements org.apache.pulsar.client.admin.Clusters</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ComponentResource.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ComponentResource.html
index 6f20d94..16183ad 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ComponentResource.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ComponentResource.html
@@ -185,7 +185,7 @@ extends <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseR
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/FunctionsImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/FunctionsImpl.html
index 268f487..46a3bf3 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/FunctionsImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/FunctionsImpl.html
@@ -532,7 +532,7 @@ implements org.apache.pulsar.client.admin.Functions</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/LookupImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/LookupImpl.html
index cb12310..73988f9 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/LookupImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/LookupImpl.html
@@ -205,7 +205,7 @@ implements org.apache.pulsar.client.admin.Lookup</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/NamespacesImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/NamespacesImpl.html
index fe18f6a..ca2cbfe 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/NamespacesImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/NamespacesImpl.html
@@ -1469,7 +1469,7 @@ implements org.apache.pulsar.client.admin.Namespaces</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/NonPersistentTopicsImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/NonPersistentTopicsImpl.html
index 027dca3..5f98868 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/NonPersistentTopicsImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/NonPersistentTopicsImpl.html
@@ -239,7 +239,7 @@ implements org.apache.pulsar.client.admin.NonPersistentTopics</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/PackagesImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/PackagesImpl.html
index 7cab0f4..92aeea6 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/PackagesImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/PackagesImpl.html
@@ -259,7 +259,7 @@ implements org.apache.pulsar.client.admin.Packages</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ProxyStatsImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ProxyStatsImpl.html
index 385938a..7af656d 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ProxyStatsImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ProxyStatsImpl.html
@@ -188,7 +188,7 @@ implements org.apache.pulsar.client.admin.ProxyStats</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ResourceGroupsImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ResourceGroupsImpl.html
index a2867a7..e9dee56 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ResourceGroupsImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ResourceGroupsImpl.html
@@ -223,7 +223,7 @@ implements org.apache.pulsar.client.admin.ResourceGroups</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ResourceQuotasImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ResourceQuotasImpl.html
index a3cb590..2e33003 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ResourceQuotasImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/ResourceQuotasImpl.html
@@ -227,7 +227,7 @@ implements org.apache.pulsar.client.admin.ResourceQuotas</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SchemasImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SchemasImpl.html
index a8ee80f..66e75a4 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SchemasImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SchemasImpl.html
@@ -281,7 +281,7 @@ implements org.apache.pulsar.client.admin.Schemas</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SinksImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SinksImpl.html
index 63fd01b..326e8f0 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SinksImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SinksImpl.html
@@ -410,7 +410,7 @@ implements org.apache.pulsar.client.admin.Sinks, org.apache.pulsar.client.admin.
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SourcesImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SourcesImpl.html
index 354a25b..e2e886d 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SourcesImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/SourcesImpl.html
@@ -410,7 +410,7 @@ implements org.apache.pulsar.client.admin.Sources, org.apache.pulsar.client.admi
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TenantsImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TenantsImpl.html
index 03ab93f..a4ea08e 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TenantsImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TenantsImpl.html
@@ -259,7 +259,7 @@ implements org.apache.pulsar.client.admin.Tenants, org.apache.pulsar.client.admi
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TopicPoliciesImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TopicPoliciesImpl.html
index bf5d928..0fa2f9a 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TopicPoliciesImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TopicPoliciesImpl.html
@@ -921,7 +921,7 @@ implements org.apache.pulsar.client.admin.TopicPolicies</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TopicsImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TopicsImpl.html
index 98f2b37..9ad184e 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TopicsImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TopicsImpl.html
@@ -1473,7 +1473,7 @@ implements org.apache.pulsar.client.admin.Topics</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TransactionsImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TransactionsImpl.html
index 1bf973a..26ad35a 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TransactionsImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/TransactionsImpl.html
@@ -287,7 +287,7 @@ implements org.apache.pulsar.client.admin.Transactions</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/WorkerImpl.html b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/WorkerImpl.html
index 9172202..4bf5615 100644
--- a/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/WorkerImpl.html
+++ b/content/api/admin/2.10.0-SNAPSHOT/org/apache/pulsar/client/admin/internal/WorkerImpl.html
@@ -219,7 +219,7 @@ implements org.apache.pulsar.client.admin.Worker</pre>
<!-- -->
</a>
<h3>Methods inherited from class org.apache.pulsar.client.admin.internal.<a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html" title="class in org.apache.pulsar.client.admin.internal">BaseResource</a></h3>
-<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
+<code><a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncDeleteRequest-javax.ws.rs.client.WebTarget-javax.ws.rs.client.InvocationCallback-">asyncDeleteRequest</a>, <a href="../../../../../../org/apache/pulsar/client/admin/internal/BaseResource.html#asyncGetRequest-javax.ws.rs.client.WebTarget- [...]
</ul>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
diff --git a/content/api/pulsar-broker/2.10.0-SNAPSHOT/index-all.html b/content/api/pulsar-broker/2.10.0-SNAPSHOT/index-all.html
index 7c1d7d2..ea89817 100644
--- a/content/api/pulsar-broker/2.10.0-SNAPSHOT/index-all.html
+++ b/content/api/pulsar-broker/2.10.0-SNAPSHOT/index-all.html
@@ -3359,6 +3359,14 @@
<dd> </dd>
<dt><span class="memberNameLink"><a href="org/apache/pulsar/broker/loadbalance/LoadData.html#getBundleData--">getBundleData()</a></span> - Method in class org.apache.pulsar.broker.loadbalance.<a href="org/apache/pulsar/broker/loadbalance/LoadData.html" title="class in org.apache.pulsar.broker.loadbalance">LoadData</a></dt>
<dd> </dd>
+<dt><span class="memberNameLink"><a href="org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#getBundleDataOrDefault-java.lang.String-">getBundleDataOrDefault(String)</a></span> - Method in class org.apache.pulsar.broker.loadbalance.impl.<a href="org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html" title="class in org.apache.pulsar.broker.loadbalance.impl">ModularLoadManagerImpl</a></dt>
+<dd> </dd>
+<dt><span class="memberNameLink"><a href="org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#getBundleDataOrDefault-java.lang.String-">getBundleDataOrDefault(String)</a></span> - Method in interface org.apache.pulsar.broker.loadbalance.<a href="org/apache/pulsar/broker/loadbalance/ModularLoadManager.html" title="interface in org.apache.pulsar.broker.loadbalance">ModularLoadManager</a></dt>
+<dd>
+<div class="block">Fetch bundle's load report data.</div>
+</dd>
+<dt><span class="memberNameLink"><a href="org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#getBundleDataPath-java.lang.String-">getBundleDataPath(String)</a></span> - Static method in class org.apache.pulsar.broker.loadbalance.impl.<a href="org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html" title="class in org.apache.pulsar.broker.loadbalance.impl">ModularLoadManagerImpl</a></dt>
+<dd> </dd>
<dt><span class="memberNameLink"><a href="org/apache/pulsar/broker/namespace/NamespaceService.html#getBundleIfPresent-org.apache.pulsar.common.naming.TopicName-">getBundleIfPresent(TopicName)</a></span> - Method in class org.apache.pulsar.broker.namespace.<a href="org/apache/pulsar/broker/namespace/NamespaceService.html" title="class in org.apache.pulsar.broker.namespace">NamespaceService</a></dt>
<dd> </dd>
<dt><span class="memberNameLink"><a href="org/apache/pulsar/common/naming/NamespaceBundle.html#getBundleRange--">getBundleRange()</a></span> - Method in class org.apache.pulsar.common.naming.<a href="org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a></dt>
@@ -3387,9 +3395,11 @@
<dd> </dd>
<dt><span class="memberNameLink"><a href="org/apache/pulsar/broker/service/PulsarStats.html#getBundleStats--">getBundleStats()</a></span> - Method in class org.apache.pulsar.broker.service.<a href="org/apache/pulsar/broker/service/PulsarStats.html" title="class in org.apache.pulsar.broker.service">PulsarStats</a></dt>
<dd> </dd>
-<dt><span class="memberNameLink"><a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundlesWithHighestTopics-org.apache.pulsar.common.naming.NamespaceName-">getBundlesWithHighestTopics(NamespaceName)</a></span> - Method in class org.apache.pulsar.common.naming.<a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html" title="class in org.apache.pulsar.common.naming">NamespaceBundleFactory</a></dt>
+<dt><span class="memberNameLink"><a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundleWithHighestThroughput-org.apache.pulsar.common.naming.NamespaceName-">getBundleWithHighestThroughput(NamespaceName)</a></span> - Method in class org.apache.pulsar.common.naming.<a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html" title="class in org.apache.pulsar.common.naming">NamespaceBundleFactory</a></dt>
+<dd> </dd>
+<dt><span class="memberNameLink"><a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundleWithHighestTopics-org.apache.pulsar.common.naming.NamespaceName-">getBundleWithHighestTopics(NamespaceName)</a></span> - Method in class org.apache.pulsar.common.naming.<a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html" title="class in org.apache.pulsar.common.naming">NamespaceBundleFactory</a></dt>
<dd> </dd>
-<dt><span class="memberNameLink"><a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundlesWithHighestTopicsAsync-org.apache.pulsar.common.naming.NamespaceName-">getBundlesWithHighestTopicsAsync(NamespaceName)</a></span> - Method in class org.apache.pulsar.common.naming.<a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html" title="class in org.apache.pulsar.common.naming">NamespaceBundleFactory</a></dt>
+<dt><span class="memberNameLink"><a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundleWithHighestTopicsAsync-org.apache.pulsar.common.naming.NamespaceName-">getBundleWithHighestTopicsAsync(NamespaceName)</a></span> - Method in class org.apache.pulsar.common.naming.<a href="org/apache/pulsar/common/naming/NamespaceBundleFactory.html" title="class in org.apache.pulsar.common.naming">NamespaceBundleFactory</a></dt>
<dd> </dd>
<dt><span class="memberNameLink"><a href="org/apache/pulsar/broker/service/AbstractTopic.html#getBytesInCounter--">getBytesInCounter()</a></span> - Method in class org.apache.pulsar.broker.service.<a href="org/apache/pulsar/broker/service/AbstractTopic.html" title="class in org.apache.pulsar.broker.service">AbstractTopic</a></dt>
<dd> </dd>
diff --git a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/class-use/BundleData.html b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/class-use/BundleData.html
index 5c3fbbe..50fb37c 100644
--- a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/class-use/BundleData.html
+++ b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/class-use/BundleData.html
@@ -150,6 +150,21 @@
</a>
<h3>Uses of <a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a> in <a href="../../../../../org/apache/pulsar/broker/loadbalance/package-summary.html">org.apache.pulsar.broker.loadbalance</a></h3>
<table class="useSummary" border="0" cellpadding="3" cellspacing="0" summary="Use table, listing methods, and an explanation">
+<caption><span>Methods in <a href="../../../../../org/apache/pulsar/broker/loadbalance/package-summary.html">org.apache.pulsar.broker.loadbalance</a> that return <a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a></span><span class="tabEnd"> </span></caption>
+<tr>
+<th class="colFirst" scope="col">Modifier and Type</th>
+<th class="colLast" scope="col">Method and Description</th>
+</tr>
+<tbody>
+<tr class="altColor">
+<td class="colFirst"><code><a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a></code></td>
+<td class="colLast"><span class="typeNameLabel">ModularLoadManager.</span><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#getBundleDataOrDefault-java.lang.String-">getBundleDataOrDefault</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundle)</code>
+<div class="block">Fetch bundle's load report data.</div>
+</td>
+</tr>
+</tbody>
+</table>
+<table class="useSummary" border="0" cellpadding="3" cellspacing="0" summary="Use table, listing methods, and an explanation">
<caption><span>Methods in <a href="../../../../../org/apache/pulsar/broker/loadbalance/package-summary.html">org.apache.pulsar.broker.loadbalance</a> that return types with arguments of type <a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a></span><span class="tabEnd"> </span></caption>
<tr>
<th class="colFirst" scope="col">Modifier and Type</th>
@@ -195,6 +210,19 @@
</a>
<h3>Uses of <a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a> in <a href="../../../../../org/apache/pulsar/broker/loadbalance/impl/package-summary.html">org.apache.pulsar.broker.loadbalance.impl</a></h3>
<table class="useSummary" border="0" cellpadding="3" cellspacing="0" summary="Use table, listing methods, and an explanation">
+<caption><span>Methods in <a href="../../../../../org/apache/pulsar/broker/loadbalance/impl/package-summary.html">org.apache.pulsar.broker.loadbalance.impl</a> that return <a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a></span><span class="tabEnd"> </span></caption>
+<tr>
+<th class="colFirst" scope="col">Modifier and Type</th>
+<th class="colLast" scope="col">Method and Description</th>
+</tr>
+<tbody>
+<tr class="altColor">
+<td class="colFirst"><code><a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a></code></td>
+<td class="colLast"><span class="typeNameLabel">ModularLoadManagerImpl.</span><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#getBundleDataOrDefault-java.lang.String-">getBundleDataOrDefault</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundle)</code> </td>
+</tr>
+</tbody>
+</table>
+<table class="useSummary" border="0" cellpadding="3" cellspacing="0" summary="Use table, listing methods, and an explanation">
<caption><span>Methods in <a href="../../../../../org/apache/pulsar/broker/loadbalance/impl/package-summary.html">org.apache.pulsar.broker.loadbalance.impl</a> with parameters of type <a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a></span><span class="tabEnd"> </span></caption>
<tr>
<th class="colFirst" scope="col">Modifier and Type</th>
diff --git a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/loadbalance/ModularLoadManager.html b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/loadbalance/ModularLoadManager.html
index c908332..f01219c 100644
--- a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/loadbalance/ModularLoadManager.html
+++ b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/loadbalance/ModularLoadManager.html
@@ -18,7 +18,7 @@
catch(err) {
}
//-->
-var methods = {"i0":6,"i1":6,"i2":6,"i3":6,"i4":6,"i5":6,"i6":6,"i7":6,"i8":6,"i9":6,"i10":6,"i11":6,"i12":18,"i13":6};
+var methods = {"i0":6,"i1":6,"i2":6,"i3":6,"i4":6,"i5":6,"i6":6,"i7":6,"i8":6,"i9":6,"i10":6,"i11":6,"i12":6,"i13":18,"i14":6};
var tabs = {65535:["t0","All Methods"],2:["t2","Instance Methods"],4:["t3","Abstract Methods"],16:["t5","Default Methods"]};
var altColor = "altColor";
var rowColor = "rowColor";
@@ -158,54 +158,60 @@ var activeTableTab = "activeTableTab";
</td>
</tr>
<tr id="i5" class="rowColor">
+<td class="colFirst"><code><a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a></code></td>
+<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#getBundleDataOrDefault-java.lang.String-">getBundleDataOrDefault</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundle)</code>
+<div class="block">Fetch bundle's load report data.</div>
+</td>
+</tr>
+<tr id="i6" class="altColor">
<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/List.html?is-external=true" title="class or interface in java.util">List</a><org.apache.pulsar.common.stats.Metrics></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#getLoadBalancingMetrics--">getLoadBalancingMetrics</a></span>()</code>
<div class="block">Fetch load balancing metrics.</div>
</td>
</tr>
-<tr id="i6" class="altColor">
+<tr id="i7" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#initialize-org.apache.pulsar.broker.PulsarService-">initialize</a></span>(<a href="../../../../../org/apache/pulsar/broker/PulsarService.html" title="class in org.apache.pulsar.broker">PulsarService</a> pulsar)</code>
<div class="block">Initialize this load manager using the given pulsar service.</div>
</td>
</tr>
-<tr id="i7" class="rowColor">
+<tr id="i8" class="altColor">
<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/Optional.html?is-external=true" title="class or interface in java.util">Optional</a><<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a>></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#selectBrokerForAssignment-org.apache.pulsar.common.naming.ServiceUnitId-">selectBrokerForAssignment</a></span>(org.apache.pulsar.common.naming.ServiceUnitId serviceUnit)</code>
<div class="block">As the leader broker, find a suitable broker for the assignment of the given bundle.</div>
</td>
</tr>
-<tr id="i8" class="altColor">
+<tr id="i9" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#start--">start</a></span>()</code>
<div class="block">As any broker, start the load manager.</div>
</td>
</tr>
-<tr id="i9" class="rowColor">
+<tr id="i10" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#stop--">stop</a></span>()</code>
<div class="block">As any broker, stop the load manager.</div>
</td>
</tr>
-<tr id="i10" class="altColor">
+<tr id="i11" class="rowColor">
<td class="colFirst"><code>org.apache.pulsar.policies.data.loadbalancer.LocalBrokerData</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#updateLocalBrokerData--">updateLocalBrokerData</a></span>()</code>
<div class="block">As any broker, retrieve the namespace bundle stats and system resource usage to update data local to this broker.</div>
</td>
</tr>
-<tr id="i11" class="rowColor">
+<tr id="i12" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#writeBrokerDataOnZooKeeper--">writeBrokerDataOnZooKeeper</a></span>()</code>
<div class="block">As any broker, write the local broker data to ZooKeeper.</div>
</td>
</tr>
-<tr id="i12" class="altColor">
+<tr id="i13" class="rowColor">
<td class="colFirst"><code>default void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#writeBrokerDataOnZooKeeper-boolean-">writeBrokerDataOnZooKeeper</a></span>(boolean force)</code>
<div class="block">As any broker, write the local broker data to ZooKeeper, forced or not.</div>
</td>
</tr>
-<tr id="i13" class="rowColor">
+<tr id="i14" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#writeBundleDataOnZooKeeper--">writeBundleDataOnZooKeeper</a></span>()</code>
<div class="block">As the leader broker, write bundle data aggregated from all brokers to ZooKeeper.</div>
@@ -389,7 +395,7 @@ var activeTableTab = "activeTableTab";
<a name="getLoadBalancingMetrics--">
<!-- -->
</a>
-<ul class="blockListLast">
+<ul class="blockList">
<li class="blockList">
<h4>getLoadBalancingMetrics</h4>
<pre><a href="https://docs.oracle.com/javase/8/docs/api/java/util/List.html?is-external=true" title="class or interface in java.util">List</a><org.apache.pulsar.common.stats.Metrics> getLoadBalancingMetrics()</pre>
@@ -400,6 +406,22 @@ var activeTableTab = "activeTableTab";
</dl>
</li>
</ul>
+<a name="getBundleDataOrDefault-java.lang.String-">
+<!-- -->
+</a>
+<ul class="blockListLast">
+<li class="blockList">
+<h4>getBundleDataOrDefault</h4>
+<pre><a href="../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a> getBundleDataOrDefault(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundle)</pre>
+<div class="block">Fetch bundle's load report data.</div>
+<dl>
+<dt><span class="paramLabel">Parameters:</span></dt>
+<dd><code>bundle</code> - </dd>
+<dt><span class="returnLabel">Returns:</span></dt>
+<dd>bundle data</dd>
+</dl>
+</li>
+</ul>
</li>
</ul>
</li>
diff --git a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html
index 4ab96c3..d0a71c9 100644
--- a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html
+++ b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html
@@ -18,8 +18,8 @@
catch(err) {
}
//-->
-var methods = {"i0":10,"i1":10,"i2":10,"i3":10,"i4":10,"i5":10,"i6":10,"i7":10,"i8":10,"i9":10,"i10":10,"i11":10,"i12":10,"i13":10,"i14":10,"i15":10,"i16":10};
-var tabs = {65535:["t0","All Methods"],2:["t2","Instance Methods"],8:["t4","Concrete Methods"]};
+var methods = {"i0":10,"i1":10,"i2":10,"i3":10,"i4":10,"i5":10,"i6":9,"i7":10,"i8":10,"i9":10,"i10":10,"i11":10,"i12":10,"i13":10,"i14":10,"i15":10,"i16":10,"i17":10,"i18":10};
+var tabs = {65535:["t0","All Methods"],1:["t1","Static Methods"],2:["t2","Instance Methods"],8:["t4","Concrete Methods"]};
var altColor = "altColor";
var rowColor = "rowColor";
var tableTab = "tableTab";
@@ -196,7 +196,7 @@ implements <a href="../../../../../../org/apache/pulsar/broker/loadbalance/Modul
</a>
<h3>Method Summary</h3>
<table class="memberSummary" border="0" cellpadding="3" cellspacing="0" summary="Method Summary table, listing methods, and an explanation">
-<caption><span id="t0" class="activeTableTab"><span>All Methods</span><span class="tabEnd"> </span></span><span id="t2" class="tableTab"><span><a href="javascript:show(2);">Instance Methods</a></span><span class="tabEnd"> </span></span><span id="t4" class="tableTab"><span><a href="javascript:show(8);">Concrete Methods</a></span><span class="tabEnd"> </span></span></caption>
+<caption><span id="t0" class="activeTableTab"><span>All Methods</span><span class="tabEnd"> </span></span><span id="t1" class="tableTab"><span><a href="javascript:show(1);">Static Methods</a></span><span class="tabEnd"> </span></span><span id="t2" class="tableTab"><span><a href="javascript:show(2);">Instance Methods</a></span><span class="tabEnd"> </span></span><span id="t4" class="tableTab"><span><a href="javascript:show(8);">Concrete Methods</a></span><span class="tabEnd [...]
<tr>
<th class="colFirst" scope="col">Modifier and Type</th>
<th class="colLast" scope="col">Method and Description</th>
@@ -233,68 +233,78 @@ implements <a href="../../../../../../org/apache/pulsar/broker/loadbalance/Modul
</td>
</tr>
<tr id="i5" class="rowColor">
+<td class="colFirst"><code><a href="../../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a></code></td>
+<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#getBundleDataOrDefault-java.lang.String-">getBundleDataOrDefault</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundle)</code>
+<div class="block">Fetch bundle's load report data.</div>
+</td>
+</tr>
+<tr id="i6" class="altColor">
+<td class="colFirst"><code>static <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a></code></td>
+<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#getBundleDataPath-java.lang.String-">getBundleDataPath</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundle)</code> </td>
+</tr>
+<tr id="i7" class="rowColor">
<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/List.html?is-external=true" title="class or interface in java.util">List</a><org.apache.pulsar.common.stats.Metrics></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#getLoadBalancingMetrics--">getLoadBalancingMetrics</a></span>()</code>
<div class="block">Fetch load balancing metrics.</div>
</td>
</tr>
-<tr id="i6" class="altColor">
+<tr id="i8" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#handleDataNotification-org.apache.pulsar.metadata.api.Notification-">handleDataNotification</a></span>(org.apache.pulsar.metadata.api.Notification t)</code> </td>
</tr>
-<tr id="i7" class="rowColor">
+<tr id="i9" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#initialize-org.apache.pulsar.broker.PulsarService-">initialize</a></span>(<a href="../../../../../../org/apache/pulsar/broker/PulsarService.html" title="class in org.apache.pulsar.broker">PulsarService</a> pulsar)</code>
<div class="block">Initialize this load manager using the given PulsarService.</div>
</td>
</tr>
-<tr id="i8" class="altColor">
+<tr id="i10" class="altColor">
<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/Optional.html?is-external=true" title="class or interface in java.util">Optional</a><<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a>></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#selectBrokerForAssignment-org.apache.pulsar.common.naming.ServiceUnitId-">selectBrokerForAssignment</a></span>(org.apache.pulsar.common.naming.ServiceUnitId serviceUnit)</code>
<div class="block">As the leader broker, find a suitable broker for the assignment of the given bundle.</div>
</td>
</tr>
-<tr id="i9" class="rowColor">
+<tr id="i11" class="rowColor">
<td class="colFirst"><code>boolean</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#shouldAntiAffinityNamespaceUnload-java.lang.String-java.lang.String-java.lang.String-">shouldAntiAffinityNamespaceUnload</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> namespace,
<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundle,
<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> currentBroker)</code> </td>
</tr>
-<tr id="i10" class="altColor">
+<tr id="i12" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#start--">start</a></span>()</code>
<div class="block">As any broker, start the load manager.</div>
</td>
</tr>
-<tr id="i11" class="rowColor">
+<tr id="i13" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#stop--">stop</a></span>()</code>
<div class="block">As any broker, stop the load manager.</div>
</td>
</tr>
-<tr id="i12" class="altColor">
+<tr id="i14" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#updateAll--">updateAll</a></span>()</code> </td>
</tr>
-<tr id="i13" class="rowColor">
+<tr id="i15" class="rowColor">
<td class="colFirst"><code>org.apache.pulsar.policies.data.loadbalancer.LocalBrokerData</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#updateLocalBrokerData--">updateLocalBrokerData</a></span>()</code>
<div class="block">As any broker, retrieve the namespace bundle stats and system resource usage to update data local to this broker.</div>
</td>
</tr>
-<tr id="i14" class="altColor">
+<tr id="i16" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#writeBrokerDataOnZooKeeper--">writeBrokerDataOnZooKeeper</a></span>()</code>
<div class="block">As any broker, write the local broker data to metadata store.</div>
</td>
</tr>
-<tr id="i15" class="rowColor">
+<tr id="i17" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#writeBrokerDataOnZooKeeper-boolean-">writeBrokerDataOnZooKeeper</a></span>(boolean force)</code>
<div class="block">As any broker, write the local broker data to ZooKeeper, forced or not.</div>
</td>
</tr>
-<tr id="i16" class="altColor">
+<tr id="i18" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/broker/loadbalance/impl/ModularLoadManagerImpl.html#writeBundleDataOnZooKeeper--">writeBundleDataOnZooKeeper</a></span>()</code>
<div class="block">As the leader broker, write bundle data aggregated from all brokers to metadata store.</div>
@@ -495,6 +505,32 @@ implements <a href="../../../../../../org/apache/pulsar/broker/loadbalance/Modul
</dl>
</li>
</ul>
+<a name="getBundleDataOrDefault-java.lang.String-">
+<!-- -->
+</a>
+<ul class="blockList">
+<li class="blockList">
+<h4>getBundleDataOrDefault</h4>
+<pre>public <a href="../../../../../../org/apache/pulsar/broker/BundleData.html" title="class in org.apache.pulsar.broker">BundleData</a> getBundleDataOrDefault(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundle)</pre>
+<div class="block"><span class="descfrmTypeLabel">Description copied from interface: <code><a href="../../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#getBundleDataOrDefault-java.lang.String-">ModularLoadManager</a></code></span></div>
+<div class="block">Fetch bundle's load report data.</div>
+<dl>
+<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
+<dd><code><a href="../../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html#getBundleDataOrDefault-java.lang.String-">getBundleDataOrDefault</a></code> in interface <code><a href="../../../../../../org/apache/pulsar/broker/loadbalance/ModularLoadManager.html" title="interface in org.apache.pulsar.broker.loadbalance">ModularLoadManager</a></code></dd>
+<dt><span class="returnLabel">Returns:</span></dt>
+<dd>bundle data</dd>
+</dl>
+</li>
+</ul>
+<a name="getBundleDataPath-java.lang.String-">
+<!-- -->
+</a>
+<ul class="blockList">
+<li class="blockList">
+<h4>getBundleDataPath</h4>
+<pre>public static <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> getBundleDataPath(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundle)</pre>
+</li>
+</ul>
<a name="updateAll--">
<!-- -->
</a>
diff --git a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/common/naming/NamespaceBundleFactory.html b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/common/naming/NamespaceBundleFactory.html
index 1db7336..0a1667e 100644
--- a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/common/naming/NamespaceBundleFactory.html
+++ b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/common/naming/NamespaceBundleFactory.html
@@ -18,7 +18,7 @@
catch(err) {
}
//-->
-var methods = {"i0":10,"i1":9,"i2":10,"i3":10,"i4":10,"i5":10,"i6":10,"i7":10,"i8":10,"i9":10,"i10":9,"i11":10,"i12":10,"i13":10,"i14":9,"i15":10,"i16":9,"i17":10,"i18":9};
+var methods = {"i0":10,"i1":9,"i2":10,"i3":10,"i4":10,"i5":10,"i6":10,"i7":10,"i8":10,"i9":10,"i10":10,"i11":9,"i12":10,"i13":10,"i14":10,"i15":9,"i16":10,"i17":9,"i18":10,"i19":9};
var tabs = {65535:["t0","All Methods"],1:["t1","Static Methods"],2:["t2","Instance Methods"],8:["t4","Concrete Methods"]};
var altColor = "altColor";
var rowColor = "rowColor";
@@ -185,41 +185,45 @@ extends <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Object.html
</tr>
<tr id="i8" class="altColor">
<td class="colFirst"><code><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a></code></td>
-<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundlesWithHighestTopics-org.apache.pulsar.common.naming.NamespaceName-">getBundlesWithHighestTopics</a></span>(org.apache.pulsar.common.naming.NamespaceName nsname)</code> </td>
+<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundleWithHighestThroughput-org.apache.pulsar.common.naming.NamespaceName-">getBundleWithHighestThroughput</a></span>(org.apache.pulsar.common.naming.NamespaceName nsName)</code> </td>
</tr>
<tr id="i9" class="rowColor">
-<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><<a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a>></code></td>
-<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundlesWithHighestTopicsAsync-org.apache.pulsar.common.naming.NamespaceName-">getBundlesWithHighestTopicsAsync</a></span>(org.apache.pulsar.common.naming.NamespaceName nsname)</code> </td>
+<td class="colFirst"><code><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a></code></td>
+<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundleWithHighestTopics-org.apache.pulsar.common.naming.NamespaceName-">getBundleWithHighestTopics</a></span>(org.apache.pulsar.common.naming.NamespaceName nsname)</code> </td>
</tr>
<tr id="i10" class="altColor">
+<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><<a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a>></code></td>
+<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundleWithHighestTopicsAsync-org.apache.pulsar.common.naming.NamespaceName-">getBundleWithHighestTopicsAsync</a></span>(org.apache.pulsar.common.naming.NamespaceName nsname)</code> </td>
+</tr>
+<tr id="i11" class="rowColor">
<td class="colFirst"><code>static <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getDefaultBundleRange--">getDefaultBundleRange</a></span>()</code> </td>
</tr>
-<tr id="i11" class="rowColor">
+<tr id="i12" class="altColor">
<td class="colFirst"><code><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getFullBundle-org.apache.pulsar.common.naming.NamespaceName-">getFullBundle</a></span>(org.apache.pulsar.common.naming.NamespaceName fqnn)</code> </td>
</tr>
-<tr id="i12" class="altColor">
+<tr id="i13" class="rowColor">
<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><<a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a>></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getFullBundleAsync-org.apache.pulsar.common.naming.NamespaceName-">getFullBundleAsync</a></span>(org.apache.pulsar.common.naming.NamespaceName fqnn)</code> </td>
</tr>
-<tr id="i13" class="rowColor">
+<tr id="i14" class="altColor">
<td class="colFirst"><code>long</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getLongHashCode-java.lang.String-">getLongHashCode</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> name)</code> </td>
</tr>
-<tr id="i14" class="altColor">
+<tr id="i15" class="rowColor">
<td class="colFirst"><code>static <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getNamespaceFromPoliciesPath-java.lang.String-">getNamespaceFromPoliciesPath</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> path)</code> </td>
</tr>
-<tr id="i15" class="rowColor">
+<tr id="i16" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#invalidateBundleCache-org.apache.pulsar.common.naming.NamespaceName-">invalidateBundleCache</a></span>(org.apache.pulsar.common.naming.NamespaceName namespace)</code> </td>
</tr>
-<tr id="i16" class="altColor">
+<tr id="i17" class="rowColor">
<td class="colFirst"><code>static boolean</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#isFullBundle-java.lang.String-">isFullBundle</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">String</a> bundleRange)</code> </td>
</tr>
-<tr id="i17" class="rowColor">
+<tr id="i18" class="altColor">
<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><org.apache.commons.lang3.tuple.Pair<<a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundles.html" title="class in org.apache.pulsar.common.naming">NamespaceBundles</a>,<a href="https://docs.oracle.com/javase/8/docs/api/java/util/List.html?is-external=true" [...]
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#splitBundles-org.apache.pulsar.common.naming.NamespaceBundle-int-java.lang.Long-">splitBundles</a></span>(<a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a> targetBundle,
int argNumBundles,
@@ -227,7 +231,7 @@ extends <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Object.html
<div class="block">Fetches <a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundles.html" title="class in org.apache.pulsar.common.naming"><code>NamespaceBundles</code></a> from cache for a given namespace.</div>
</td>
</tr>
-<tr id="i18" class="altColor">
+<tr id="i19" class="rowColor">
<td class="colFirst"><code>static void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#validateFullRange-java.util.SortedSet-">validateFullRange</a></span>(<a href="https://docs.oracle.com/javase/8/docs/api/java/util/SortedSet.html?is-external=true" title="class or interface in java.util">SortedSet</a><<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/String.html?is-external=true" title="class or interface in java.lang">St [...]
</tr>
@@ -289,22 +293,31 @@ extends <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Object.html
<pre>public <a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><<a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundles.html" title="class in org.apache.pulsar.common.naming">NamespaceBundles</a>> getBundlesAsync(org.apache.pulsar.common.naming.NamespaceName nsname)</pre>
</li>
</ul>
-<a name="getBundlesWithHighestTopics-org.apache.pulsar.common.naming.NamespaceName-">
+<a name="getBundleWithHighestTopics-org.apache.pulsar.common.naming.NamespaceName-">
+<!-- -->
+</a>
+<ul class="blockList">
+<li class="blockList">
+<h4>getBundleWithHighestTopics</h4>
+<pre>public <a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a> getBundleWithHighestTopics(org.apache.pulsar.common.naming.NamespaceName nsname)</pre>
+</li>
+</ul>
+<a name="getBundleWithHighestTopicsAsync-org.apache.pulsar.common.naming.NamespaceName-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
-<h4>getBundlesWithHighestTopics</h4>
-<pre>public <a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a> getBundlesWithHighestTopics(org.apache.pulsar.common.naming.NamespaceName nsname)</pre>
+<h4>getBundleWithHighestTopicsAsync</h4>
+<pre>public <a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><<a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a>> getBundleWithHighestTopicsAsync(org.apache.pulsar.common.naming.NamespaceName nsname)</pre>
</li>
</ul>
-<a name="getBundlesWithHighestTopicsAsync-org.apache.pulsar.common.naming.NamespaceName-">
+<a name="getBundleWithHighestThroughput-org.apache.pulsar.common.naming.NamespaceName-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
-<h4>getBundlesWithHighestTopicsAsync</h4>
-<pre>public <a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><<a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a>> getBundlesWithHighestTopicsAsync(org.apache.pulsar.common.naming.NamespaceName nsname)</pre>
+<h4>getBundleWithHighestThroughput</h4>
+<pre>public <a href="../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a> getBundleWithHighestThroughput(org.apache.pulsar.common.naming.NamespaceName nsName)</pre>
</li>
</ul>
<a name="getBundles-org.apache.pulsar.common.naming.NamespaceName-">
diff --git a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/common/naming/class-use/NamespaceBundle.html b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/common/naming/class-use/NamespaceBundle.html
index 348b105..7721136 100644
--- a/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/common/naming/class-use/NamespaceBundle.html
+++ b/content/api/pulsar-broker/2.10.0-SNAPSHOT/org/apache/pulsar/common/naming/class-use/NamespaceBundle.html
@@ -546,14 +546,18 @@
</tr>
<tr class="altColor">
<td class="colFirst"><code><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a></code></td>
-<td class="colLast"><span class="typeNameLabel">NamespaceBundleFactory.</span><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundlesWithHighestTopics-org.apache.pulsar.common.naming.NamespaceName-">getBundlesWithHighestTopics</a></span>(org.apache.pulsar.common.naming.NamespaceName nsname)</code> </td>
+<td class="colLast"><span class="typeNameLabel">NamespaceBundleFactory.</span><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundleWithHighestThroughput-org.apache.pulsar.common.naming.NamespaceName-">getBundleWithHighestThroughput</a></span>(org.apache.pulsar.common.naming.NamespaceName nsName)</code> </td>
</tr>
<tr class="rowColor">
<td class="colFirst"><code><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a></code></td>
-<td class="colLast"><span class="typeNameLabel">NamespaceBundles.</span><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundles.html#getFullBundle--">getFullBundle</a></span>()</code> </td>
+<td class="colLast"><span class="typeNameLabel">NamespaceBundleFactory.</span><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundleWithHighestTopics-org.apache.pulsar.common.naming.NamespaceName-">getBundleWithHighestTopics</a></span>(org.apache.pulsar.common.naming.NamespaceName nsname)</code> </td>
</tr>
<tr class="altColor">
<td class="colFirst"><code><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a></code></td>
+<td class="colLast"><span class="typeNameLabel">NamespaceBundles.</span><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundles.html#getFullBundle--">getFullBundle</a></span>()</code> </td>
+</tr>
+<tr class="rowColor">
+<td class="colFirst"><code><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a></code></td>
<td class="colLast"><span class="typeNameLabel">NamespaceBundleFactory.</span><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getFullBundle-org.apache.pulsar.common.naming.NamespaceName-">getFullBundle</a></span>(org.apache.pulsar.common.naming.NamespaceName fqnn)</code> </td>
</tr>
</tbody>
@@ -571,7 +575,7 @@
</tr>
<tr class="rowColor">
<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><<a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a>></code></td>
-<td class="colLast"><span class="typeNameLabel">NamespaceBundleFactory.</span><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundlesWithHighestTopicsAsync-org.apache.pulsar.common.naming.NamespaceName-">getBundlesWithHighestTopicsAsync</a></span>(org.apache.pulsar.common.naming.NamespaceName nsname)</code> </td>
+<td class="colLast"><span class="typeNameLabel">NamespaceBundleFactory.</span><code><span class="memberNameLink"><a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundleFactory.html#getBundleWithHighestTopicsAsync-org.apache.pulsar.common.naming.NamespaceName-">getBundleWithHighestTopicsAsync</a></span>(org.apache.pulsar.common.naming.NamespaceName nsname)</code> </td>
</tr>
<tr class="altColor">
<td class="colFirst"><code><a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html?is-external=true" title="class or interface in java.util.concurrent">CompletableFuture</a><<a href="../../../../../../org/apache/pulsar/common/naming/NamespaceBundle.html" title="class in org.apache.pulsar.common.naming">NamespaceBundle</a>></code></td>
diff --git a/content/api/python/2.10.0-SNAPSHOT/index.html b/content/api/python/2.10.0-SNAPSHOT/index.html
index 37654b5..c33bb5b 100644
--- a/content/api/python/2.10.0-SNAPSHOT/index.html
+++ b/content/api/python/2.10.0-SNAPSHOT/index.html
@@ -3764,7 +3764,7 @@ producers and consumers.</p></div>
<div class="item">
<div class="name def" id="pulsar.Client.create_producer">
- <p>def <span class="ident">create_producer</span>(</p><p>self, topic, producer_name=None, schema=<pulsar.schema.schema.BytesSchema object at 0x7f5cab27dcd0>, initial_sequence_id=None, send_timeout_millis=30000, compression_type=_pulsar.CompressionType.NONE, max_pending_messages=1000, max_pending_messages_across_partitions=50000, block_if_queue_full=False, batching_enabled=False, batching_max_messages=1000, batching_max_allowed_size_in_bytes=131072, batching_max_publish_delay_ms [...]
+ <p>def <span class="ident">create_producer</span>(</p><p>self, topic, producer_name=None, schema=<pulsar.schema.schema.BytesSchema object at 0x7fb3cf979cd0>, initial_sequence_id=None, send_timeout_millis=30000, compression_type=_pulsar.CompressionType.NONE, max_pending_messages=1000, max_pending_messages_across_partitions=50000, block_if_queue_full=False, batching_enabled=False, batching_max_messages=1000, batching_max_allowed_size_in_bytes=131072, batching_max_publish_delay_ms [...]
</div>
@@ -4018,7 +4018,7 @@ batched into single batch message:
<div class="item">
<div class="name def" id="pulsar.Client.create_reader">
- <p>def <span class="ident">create_reader</span>(</p><p>self, topic, start_message_id, schema=<pulsar.schema.schema.BytesSchema object at 0x7f5caa3741d0>, reader_listener=None, receiver_queue_size=1000, reader_name=None, subscription_role_prefix=None, is_read_compacted=False, crypto_key_reader=None)</p>
+ <p>def <span class="ident">create_reader</span>(</p><p>self, topic, start_message_id, schema=<pulsar.schema.schema.BytesSchema object at 0x7fb3cea701d0>, reader_listener=None, receiver_queue_size=1000, reader_name=None, subscription_role_prefix=None, is_read_compacted=False, crypto_key_reader=None)</p>
</div>
@@ -4235,7 +4235,7 @@ for ongoing operations to complete.</p></div>
<div class="item">
<div class="name def" id="pulsar.Client.subscribe">
- <p>def <span class="ident">subscribe</span>(</p><p>self, topic, subscription_name, consumer_type=_pulsar.ConsumerType.Exclusive, schema=<pulsar.schema.schema.BytesSchema object at 0x7f5caa374110>, message_listener=None, receiver_queue_size=1000, max_total_receiver_queue_size_across_partitions=50000, consumer_name=None, unacked_messages_timeout_ms=None, broker_consumer_stats_cache_time_ms=30000, negative_ack_redelivery_delay_ms=60000, is_read_compacted=False, properties=None, pa [...]
+ <p>def <span class="ident">subscribe</span>(</p><p>self, topic, subscription_name, consumer_type=_pulsar.ConsumerType.Exclusive, schema=<pulsar.schema.schema.BytesSchema object at 0x7fb3cea70110>, message_listener=None, receiver_queue_size=1000, max_total_receiver_queue_size_across_partitions=50000, consumer_name=None, unacked_messages_timeout_ms=None, broker_consumer_stats_cache_time_ms=30000, negative_ack_redelivery_delay_ms=60000, is_read_compacted=False, properties=None, pa [...]
</div>
diff --git a/content/api/python/index.html b/content/api/python/index.html
index 37654b5..c33bb5b 100644
--- a/content/api/python/index.html
+++ b/content/api/python/index.html
@@ -3764,7 +3764,7 @@ producers and consumers.</p></div>
<div class="item">
<div class="name def" id="pulsar.Client.create_producer">
- <p>def <span class="ident">create_producer</span>(</p><p>self, topic, producer_name=None, schema=<pulsar.schema.schema.BytesSchema object at 0x7f5cab27dcd0>, initial_sequence_id=None, send_timeout_millis=30000, compression_type=_pulsar.CompressionType.NONE, max_pending_messages=1000, max_pending_messages_across_partitions=50000, block_if_queue_full=False, batching_enabled=False, batching_max_messages=1000, batching_max_allowed_size_in_bytes=131072, batching_max_publish_delay_ms [...]
+ <p>def <span class="ident">create_producer</span>(</p><p>self, topic, producer_name=None, schema=<pulsar.schema.schema.BytesSchema object at 0x7fb3cf979cd0>, initial_sequence_id=None, send_timeout_millis=30000, compression_type=_pulsar.CompressionType.NONE, max_pending_messages=1000, max_pending_messages_across_partitions=50000, block_if_queue_full=False, batching_enabled=False, batching_max_messages=1000, batching_max_allowed_size_in_bytes=131072, batching_max_publish_delay_ms [...]
</div>
@@ -4018,7 +4018,7 @@ batched into single batch message:
<div class="item">
<div class="name def" id="pulsar.Client.create_reader">
- <p>def <span class="ident">create_reader</span>(</p><p>self, topic, start_message_id, schema=<pulsar.schema.schema.BytesSchema object at 0x7f5caa3741d0>, reader_listener=None, receiver_queue_size=1000, reader_name=None, subscription_role_prefix=None, is_read_compacted=False, crypto_key_reader=None)</p>
+ <p>def <span class="ident">create_reader</span>(</p><p>self, topic, start_message_id, schema=<pulsar.schema.schema.BytesSchema object at 0x7fb3cea701d0>, reader_listener=None, receiver_queue_size=1000, reader_name=None, subscription_role_prefix=None, is_read_compacted=False, crypto_key_reader=None)</p>
</div>
@@ -4235,7 +4235,7 @@ for ongoing operations to complete.</p></div>
<div class="item">
<div class="name def" id="pulsar.Client.subscribe">
- <p>def <span class="ident">subscribe</span>(</p><p>self, topic, subscription_name, consumer_type=_pulsar.ConsumerType.Exclusive, schema=<pulsar.schema.schema.BytesSchema object at 0x7f5caa374110>, message_listener=None, receiver_queue_size=1000, max_total_receiver_queue_size_across_partitions=50000, consumer_name=None, unacked_messages_timeout_ms=None, broker_consumer_stats_cache_time_ms=30000, negative_ack_redelivery_delay_ms=60000, is_read_compacted=False, properties=None, pa [...]
+ <p>def <span class="ident">subscribe</span>(</p><p>self, topic, subscription_name, consumer_type=_pulsar.ConsumerType.Exclusive, schema=<pulsar.schema.schema.BytesSchema object at 0x7fb3cea70110>, message_listener=None, receiver_queue_size=1000, max_total_receiver_queue_size_across_partitions=50000, consumer_name=None, unacked_messages_timeout_ms=None, broker_consumer_stats_cache_time_ms=30000, negative_ack_redelivery_delay_ms=60000, is_read_compacted=False, properties=None, pa [...]
</div>
diff --git a/content/docs/zh-CN/2.1.0-incubating/concepts-messaging.html b/content/docs/zh-CN/2.1.0-incubating/concepts-messaging.html
index 294ce03..788eb09 100644
--- a/content/docs/zh-CN/2.1.0-incubating/concepts-messaging.html
+++ b/content/docs/zh-CN/2.1.0-incubating/concepts-messaging.html
@@ -166,7 +166,7 @@ You don't need to explicitly create topics in Pulsar. 如果客户端尝试从
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -193,8 +193,8 @@ Be aware when using Shared type: * Message ordering is not guaranteed. * You can
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<p><strong>No ordering guarantees across multiple topics</strong> <br>
-When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>在多主题之间没有顺序保证</strong></p>
+<p>当生产者向一个主题发送消息时，所有的消息都被保证以相同的顺序从该主题读取。 However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.1.0-incubating/concepts-messaging/index.html b/content/docs/zh-CN/2.1.0-incubating/concepts-messaging/index.html
index 294ce03..788eb09 100644
--- a/content/docs/zh-CN/2.1.0-incubating/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.1.0-incubating/concepts-messaging/index.html
@@ -166,7 +166,7 @@ You don't need to explicitly create topics in Pulsar. 如果客户端尝试从
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -193,8 +193,8 @@ Be aware when using Shared type: * Message ordering is not guaranteed. * You can
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<p><strong>No ordering guarantees across multiple topics</strong> <br>
-When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>在多主题之间没有顺序保证</strong></p>
+<p>当生产者向一个主题发送消息时，所有的消息都被保证以相同的顺序从该主题读取。 However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.1.0-incubating/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.1.0-incubating/deploy-bare-metal-multi-cluster.html
index dd152b5..7c594cb 100644
--- a/content/docs/zh-CN/2.1.0-incubating/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.1.0-incubating/deploy-bare-metal-multi-cluster.html
@@ -123,7 +123,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.1.0-incubating/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.1.0-incubating/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.1.0-incubating/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.1.0-incubating/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.1.0-incubating/deploy-bare-metal-multi-cluster/index.html
index dd152b5..7c594cb 100644
--- a/content/docs/zh-CN/2.1.0-incubating/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.1.0-incubating/deploy-bare-metal-multi-cluster/index.html
@@ -123,7 +123,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.1.0-incubating/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.1.0-incubating/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.1.0-incubating/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.1.1-incubating/concepts-messaging.html b/content/docs/zh-CN/2.1.1-incubating/concepts-messaging.html
index c7f1430..ed4e10e 100644
--- a/content/docs/zh-CN/2.1.1-incubating/concepts-messaging.html
+++ b/content/docs/zh-CN/2.1.1-incubating/concepts-messaging.html
@@ -166,7 +166,7 @@ You don't need to explicitly create topics in Pulsar. 如果客户端尝试从
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -193,8 +193,8 @@ Be aware when using Shared type: * Message ordering is not guaranteed. * You can
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<p><strong>No ordering guarantees across multiple topics</strong> <br>
-When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>在多主题之间没有顺序保证</strong></p>
+<p>当生产者向一个主题发送消息时，所有的消息都被保证以相同的顺序从该主题读取。 However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.1.1-incubating/concepts-messaging/index.html b/content/docs/zh-CN/2.1.1-incubating/concepts-messaging/index.html
index c7f1430..ed4e10e 100644
--- a/content/docs/zh-CN/2.1.1-incubating/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.1.1-incubating/concepts-messaging/index.html
@@ -166,7 +166,7 @@ You don't need to explicitly create topics in Pulsar. 如果客户端尝试从
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -193,8 +193,8 @@ Be aware when using Shared type: * Message ordering is not guaranteed. * You can
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<p><strong>No ordering guarantees across multiple topics</strong> <br>
-When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>在多主题之间没有顺序保证</strong></p>
+<p>当生产者向一个主题发送消息时，所有的消息都被保证以相同的顺序从该主题读取。 However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.1.1-incubating/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.1.1-incubating/deploy-bare-metal-multi-cluster.html
index 33d38b4..bb5d0d5 100644
--- a/content/docs/zh-CN/2.1.1-incubating/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.1.1-incubating/deploy-bare-metal-multi-cluster.html
@@ -123,7 +123,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.1.1-incubating/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.1.1-incubating/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.1.1-incubating/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.1.1-incubating/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.1.1-incubating/deploy-bare-metal-multi-cluster/index.html
index 33d38b4..bb5d0d5 100644
--- a/content/docs/zh-CN/2.1.1-incubating/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.1.1-incubating/deploy-bare-metal-multi-cluster/index.html
@@ -123,7 +123,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.1.1-incubating/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.1.1-incubating/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.1.1-incubating/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.2.0/concepts-messaging.html b/content/docs/zh-CN/2.2.0/concepts-messaging.html
index 1f7a4fa..52e52e3 100644
--- a/content/docs/zh-CN/2.2.0/concepts-messaging.html
+++ b/content/docs/zh-CN/2.2.0/concepts-messaging.html
@@ -166,7 +166,7 @@ You don't need to explicitly create topics in Pulsar. 如果客户端尝试从
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -193,8 +193,8 @@ Be aware when using Shared type: * Message ordering is not guaranteed. * You can
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<p><strong>No ordering guarantees across multiple topics</strong> <br>
-When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>在多主题之间没有顺序保证</strong></p>
+<p>当生产者向一个主题发送消息时，所有的消息都被保证以相同的顺序从该主题读取。 However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.2.0/concepts-messaging/index.html b/content/docs/zh-CN/2.2.0/concepts-messaging/index.html
index 1f7a4fa..52e52e3 100644
--- a/content/docs/zh-CN/2.2.0/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.2.0/concepts-messaging/index.html
@@ -166,7 +166,7 @@ You don't need to explicitly create topics in Pulsar. 如果客户端尝试从
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -193,8 +193,8 @@ Be aware when using Shared type: * Message ordering is not guaranteed. * You can
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<p><strong>No ordering guarantees across multiple topics</strong> <br>
-When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>在多主题之间没有顺序保证</strong></p>
+<p>当生产者向一个主题发送消息时，所有的消息都被保证以相同的顺序从该主题读取。 However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.2.0/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.2.0/deploy-bare-metal-multi-cluster.html
index e7f74b5..d1b8d39 100644
--- a/content/docs/zh-CN/2.2.0/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.2.0/deploy-bare-metal-multi-cluster.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.2.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.2.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.2.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.2.0/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.2.0/deploy-bare-metal-multi-cluster/index.html
index e7f74b5..d1b8d39 100644
--- a/content/docs/zh-CN/2.2.0/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.2.0/deploy-bare-metal-multi-cluster/index.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.2.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.2.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.2.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.2.1/concepts-messaging.html b/content/docs/zh-CN/2.2.1/concepts-messaging.html
index 319f5a3..db7ce53 100644
--- a/content/docs/zh-CN/2.2.1/concepts-messaging.html
+++ b/content/docs/zh-CN/2.2.1/concepts-messaging.html
@@ -166,7 +166,7 @@ You don't need to explicitly create topics in Pulsar. 如果客户端尝试从
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -193,8 +193,8 @@ Be aware when using Shared type: * Message ordering is not guaranteed. * You can
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<p><strong>No ordering guarantees across multiple topics</strong> <br>
-When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>在多主题之间没有顺序保证</strong></p>
+<p>当生产者向一个主题发送消息时，所有的消息都被保证以相同的顺序从该主题读取。 However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.2.1/concepts-messaging/index.html b/content/docs/zh-CN/2.2.1/concepts-messaging/index.html
index 319f5a3..db7ce53 100644
--- a/content/docs/zh-CN/2.2.1/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.2.1/concepts-messaging/index.html
@@ -166,7 +166,7 @@ You don't need to explicitly create topics in Pulsar. 如果客户端尝试从
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -193,8 +193,8 @@ Be aware when using Shared type: * Message ordering is not guaranteed. * You can
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<p><strong>No ordering guarantees across multiple topics</strong> <br>
-When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>在多主题之间没有顺序保证</strong></p>
+<p>当生产者向一个主题发送消息时，所有的消息都被保证以相同的顺序从该主题读取。 However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.2.1/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.2.1/deploy-bare-metal-multi-cluster.html
index a1078f4..28d73b9 100644
--- a/content/docs/zh-CN/2.2.1/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.2.1/deploy-bare-metal-multi-cluster.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.2.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.2.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.2.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.2.1/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.2.1/deploy-bare-metal-multi-cluster/index.html
index a1078f4..28d73b9 100644
--- a/content/docs/zh-CN/2.2.1/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.2.1/deploy-bare-metal-multi-cluster/index.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.2.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.2.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.2.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.3.0/concepts-messaging.html b/content/docs/zh-CN/2.3.0/concepts-messaging.html
index 01ef3e6..692d14b 100644
--- a/content/docs/zh-CN/2.3.0/concepts-messaging.html
+++ b/content/docs/zh-CN/2.3.0/concepts-messaging.html
@@ -167,7 +167,7 @@
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
diff --git a/content/docs/zh-CN/2.3.0/concepts-messaging/index.html b/content/docs/zh-CN/2.3.0/concepts-messaging/index.html
index 01ef3e6..692d14b 100644
--- a/content/docs/zh-CN/2.3.0/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.3.0/concepts-messaging/index.html
@@ -167,7 +167,7 @@
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
diff --git a/content/docs/zh-CN/2.3.0/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.3.0/deploy-bare-metal-multi-cluster.html
index d8df9dc..8d3980e 100644
--- a/content/docs/zh-CN/2.3.0/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.3.0/deploy-bare-metal-multi-cluster.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.3.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.3.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.3.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.3.0/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.3.0/deploy-bare-metal-multi-cluster/index.html
index d8df9dc..8d3980e 100644
--- a/content/docs/zh-CN/2.3.0/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.3.0/deploy-bare-metal-multi-cluster/index.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.3.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.3.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.3.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.3.0/reference-cli-tools.html b/content/docs/zh-CN/2.3.0/reference-cli-tools.html
index 3ba29bb..c803650 100644
--- a/content/docs/zh-CN/2.3.0/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.3.0/reference-cli-tools.html
@@ -300,7 +300,7 @@
<tr><td><code>--auth-params</code></td><td>Authentication parameters, for example key1:val1,key2:val2</td><td></td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -399,16 +399,16 @@
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
@@ -443,7 +443,7 @@
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="monitor-brokers"></a><a href="#monitor-brokers" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 [...]
diff --git a/content/docs/zh-CN/2.3.0/reference-cli-tools/index.html b/content/docs/zh-CN/2.3.0/reference-cli-tools/index.html
index 3ba29bb..c803650 100644
--- a/content/docs/zh-CN/2.3.0/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.3.0/reference-cli-tools/index.html
@@ -300,7 +300,7 @@
<tr><td><code>--auth-params</code></td><td>Authentication parameters, for example key1:val1,key2:val2</td><td></td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -399,16 +399,16 @@
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
@@ -443,7 +443,7 @@
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="monitor-brokers"></a><a href="#monitor-brokers" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 [...]
diff --git a/content/docs/zh-CN/2.3.1/concepts-messaging.html b/content/docs/zh-CN/2.3.1/concepts-messaging.html
index 2f0aaa4..2bfeaf8 100644
--- a/content/docs/zh-CN/2.3.1/concepts-messaging.html
+++ b/content/docs/zh-CN/2.3.1/concepts-messaging.html
@@ -167,7 +167,7 @@
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
diff --git a/content/docs/zh-CN/2.3.1/concepts-messaging/index.html b/content/docs/zh-CN/2.3.1/concepts-messaging/index.html
index 2f0aaa4..2bfeaf8 100644
--- a/content/docs/zh-CN/2.3.1/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.3.1/concepts-messaging/index.html
@@ -167,7 +167,7 @@
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
diff --git a/content/docs/zh-CN/2.3.1/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.3.1/deploy-bare-metal-multi-cluster.html
index eae8615..0f89d8e 100644
--- a/content/docs/zh-CN/2.3.1/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.3.1/deploy-bare-metal-multi-cluster.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.3.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.3.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.3.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.3.1/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.3.1/deploy-bare-metal-multi-cluster/index.html
index eae8615..0f89d8e 100644
--- a/content/docs/zh-CN/2.3.1/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.3.1/deploy-bare-metal-multi-cluster/index.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.3.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.3.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.3.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.3.1/reference-cli-tools.html b/content/docs/zh-CN/2.3.1/reference-cli-tools.html
index 05d96af..3067201 100644
--- a/content/docs/zh-CN/2.3.1/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.3.1/reference-cli-tools.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td></td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,21 +426,21 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -456,13 +456,13 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
@@ -476,7 +476,7 @@
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -490,14 +490,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -516,7 +516,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.3.1/reference-cli-tools/index.html b/content/docs/zh-CN/2.3.1/reference-cli-tools/index.html
index 05d96af..3067201 100644
--- a/content/docs/zh-CN/2.3.1/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.3.1/reference-cli-tools/index.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td></td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,21 +426,21 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -456,13 +456,13 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
@@ -476,7 +476,7 @@
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -490,14 +490,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -516,7 +516,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.3.2/concepts-messaging.html b/content/docs/zh-CN/2.3.2/concepts-messaging.html
index 30f1e8d..dde42a3 100644
--- a/content/docs/zh-CN/2.3.2/concepts-messaging.html
+++ b/content/docs/zh-CN/2.3.2/concepts-messaging.html
@@ -198,7 +198,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.3.2/concepts-messaging/index.html b/content/docs/zh-CN/2.3.2/concepts-messaging/index.html
index 30f1e8d..dde42a3 100644
--- a/content/docs/zh-CN/2.3.2/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.3.2/concepts-messaging/index.html
@@ -198,7 +198,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.3.2/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.3.2/deploy-bare-metal-multi-cluster.html
index edab100..62bb1c0 100644
--- a/content/docs/zh-CN/2.3.2/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.3.2/deploy-bare-metal-multi-cluster.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.3.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.3.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.3.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.3.2/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.3.2/deploy-bare-metal-multi-cluster/index.html
index edab100..62bb1c0 100644
--- a/content/docs/zh-CN/2.3.2/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.3.2/deploy-bare-metal-multi-cluster/index.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.3.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.3.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.3.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.3.2/reference-cli-tools.html b/content/docs/zh-CN/2.3.2/reference-cli-tools.html
index 4b98e9a..4ee11ed 100644
--- a/content/docs/zh-CN/2.3.2/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.3.2/reference-cli-tools.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td></td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,21 +426,21 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -456,13 +456,13 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
@@ -476,7 +476,7 @@
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -490,14 +490,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -516,7 +516,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.3.2/reference-cli-tools/index.html b/content/docs/zh-CN/2.3.2/reference-cli-tools/index.html
index 4b98e9a..4ee11ed 100644
--- a/content/docs/zh-CN/2.3.2/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.3.2/reference-cli-tools/index.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td></td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,21 +426,21 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -456,13 +456,13 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
@@ -476,7 +476,7 @@
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -490,14 +490,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -516,7 +516,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.4.0/concepts-messaging.html b/content/docs/zh-CN/2.4.0/concepts-messaging.html
index ca5f154..9aa1242 100644
--- a/content/docs/zh-CN/2.4.0/concepts-messaging.html
+++ b/content/docs/zh-CN/2.4.0/concepts-messaging.html
@@ -198,7 +198,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.4.0/concepts-messaging/index.html b/content/docs/zh-CN/2.4.0/concepts-messaging/index.html
index ca5f154..9aa1242 100644
--- a/content/docs/zh-CN/2.4.0/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.4.0/concepts-messaging/index.html
@@ -198,7 +198,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram above, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.4.0/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.4.0/deploy-bare-metal-multi-cluster.html
index caaf0e1..e4b1dfb 100644
--- a/content/docs/zh-CN/2.4.0/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.4.0/deploy-bare-metal-multi-cluster.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.4.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.4.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.4.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.4.0/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.4.0/deploy-bare-metal-multi-cluster/index.html
index caaf0e1..e4b1dfb 100644
--- a/content/docs/zh-CN/2.4.0/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.4.0/deploy-bare-metal-multi-cluster/index.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.4.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.4.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.4.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.4.0/reference-cli-tools.html b/content/docs/zh-CN/2.4.0/reference-cli-tools.html
index 4f80045..08545a4 100644
--- a/content/docs/zh-CN/2.4.0/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.4.0/reference-cli-tools.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,22 +426,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -457,30 +457,30 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -494,14 +494,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -520,7 +520,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.4.0/reference-cli-tools/index.html b/content/docs/zh-CN/2.4.0/reference-cli-tools/index.html
index 4f80045..08545a4 100644
--- a/content/docs/zh-CN/2.4.0/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.4.0/reference-cli-tools/index.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,22 +426,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -457,30 +457,30 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -494,14 +494,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -520,7 +520,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.4.1/concepts-messaging.html b/content/docs/zh-CN/2.4.1/concepts-messaging.html
index 8484dd4..0a0514b 100644
--- a/content/docs/zh-CN/2.4.1/concepts-messaging.html
+++ b/content/docs/zh-CN/2.4.1/concepts-messaging.html
@@ -213,7 +213,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.4.1/concepts-messaging/index.html b/content/docs/zh-CN/2.4.1/concepts-messaging/index.html
index 8484dd4..0a0514b 100644
--- a/content/docs/zh-CN/2.4.1/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.4.1/concepts-messaging/index.html
@@ -213,7 +213,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.4.1/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.4.1/deploy-bare-metal-multi-cluster.html
index b479943..458ab14 100644
--- a/content/docs/zh-CN/2.4.1/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.4.1/deploy-bare-metal-multi-cluster.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.4.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.4.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.4.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.4.1/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.4.1/deploy-bare-metal-multi-cluster/index.html
index b479943..458ab14 100644
--- a/content/docs/zh-CN/2.4.1/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.4.1/deploy-bare-metal-multi-cluster/index.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.4.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.4.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.4.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.4.1/reference-cli-tools.html b/content/docs/zh-CN/2.4.1/reference-cli-tools.html
index 8d1821e..28a28f8 100644
--- a/content/docs/zh-CN/2.4.1/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.4.1/reference-cli-tools.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,22 +426,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -457,30 +457,30 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -494,14 +494,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -520,7 +520,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.4.1/reference-cli-tools/index.html b/content/docs/zh-CN/2.4.1/reference-cli-tools/index.html
index 8d1821e..28a28f8 100644
--- a/content/docs/zh-CN/2.4.1/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.4.1/reference-cli-tools/index.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,22 +426,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -457,30 +457,30 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -494,14 +494,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -520,7 +520,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.4.2/concepts-messaging.html b/content/docs/zh-CN/2.4.2/concepts-messaging.html
index 2c7d826..3d67e32 100644
--- a/content/docs/zh-CN/2.4.2/concepts-messaging.html
+++ b/content/docs/zh-CN/2.4.2/concepts-messaging.html
@@ -211,7 +211,7 @@
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.4.2/concepts-messaging/index.html b/content/docs/zh-CN/2.4.2/concepts-messaging/index.html
index 2c7d826..3d67e32 100644
--- a/content/docs/zh-CN/2.4.2/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.4.2/concepts-messaging/index.html
@@ -211,7 +211,7 @@
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.4.2/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.4.2/deploy-bare-metal-multi-cluster.html
index 70150fd..f28702a 100644
--- a/content/docs/zh-CN/2.4.2/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.4.2/deploy-bare-metal-multi-cluster.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.4.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.4.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.4.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.4.2/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.4.2/deploy-bare-metal-multi-cluster/index.html
index 70150fd..f28702a 100644
--- a/content/docs/zh-CN/2.4.2/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.4.2/deploy-bare-metal-multi-cluster/index.html
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.4.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.4.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.4.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar用到的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)">JAR</a> 包</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>这些目录将在你运行Pulsar的时候生成:</p>
diff --git a/content/docs/zh-CN/2.4.2/reference-cli-tools.html b/content/docs/zh-CN/2.4.2/reference-cli-tools.html
index df31903..7198e53 100644
--- a/content/docs/zh-CN/2.4.2/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.4.2/reference-cli-tools.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,22 +426,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -457,30 +457,30 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -494,14 +494,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -520,7 +520,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.4.2/reference-cli-tools/index.html b/content/docs/zh-CN/2.4.2/reference-cli-tools/index.html
index df31903..7198e53 100644
--- a/content/docs/zh-CN/2.4.2/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.4.2/reference-cli-tools/index.html
@@ -317,7 +317,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -426,22 +426,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber name prefix. Possible values are Exclusive, Shared, Failover.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -457,30 +457,30 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration in secs. If set to 0, it will keep publishing.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -494,14 +494,14 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
@@ -520,7 +520,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.5.0/concepts-messaging.html b/content/docs/zh-CN/2.5.0/concepts-messaging.html
index 7eedb04..864fa51 100644
--- a/content/docs/zh-CN/2.5.0/concepts-messaging.html
+++ b/content/docs/zh-CN/2.5.0/concepts-messaging.html
@@ -212,7 +212,7 @@
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.5.0/concepts-messaging/index.html b/content/docs/zh-CN/2.5.0/concepts-messaging/index.html
index 7eedb04..864fa51 100644
--- a/content/docs/zh-CN/2.5.0/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.5.0/concepts-messaging/index.html
@@ -212,7 +212,7 @@
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.5.0/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.5.0/deploy-bare-metal-multi-cluster.html
index 3e29894..9faf464 100644
--- a/content/docs/zh-CN/2.5.0/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.5.0/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.5.0/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.5.0/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.5.0/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.5.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.5.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.5.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.5.0/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.5.0/deploy-bare-metal-multi-cluster/index.html
index 3e29894..9faf464 100644
--- a/content/docs/zh-CN/2.5.0/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.5.0/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.5.0/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.5.0/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.5.0/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.5.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.5.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.5.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.5.0/helm-install.html b/content/docs/zh-CN/2.5.0/helm-install.html
index 652ce72..5de4007 100644
--- a/content/docs/zh-CN/2.5.0/helm-install.html
+++ b/content/docs/zh-CN/2.5.0/helm-install.html
@@ -92,7 +92,7 @@
</blockquote>
<p>Follow the instructions to create and connect to the Kubernetes cluster of your choice:</p>
<ul>
-<li><a href="/docs/zh-CN/2.5.0/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.5.0/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="deploy-pulsar"></a><a href="#deploy-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
<p>With the environment set up and configuration generated, you can now proceed to the <a href="/docs/zh-CN/2.5.0/helm-deploy">deployment of Pulsar</a>.</p>
diff --git a/content/docs/zh-CN/2.5.0/helm-install/index.html b/content/docs/zh-CN/2.5.0/helm-install/index.html
index 652ce72..5de4007 100644
--- a/content/docs/zh-CN/2.5.0/helm-install/index.html
+++ b/content/docs/zh-CN/2.5.0/helm-install/index.html
@@ -92,7 +92,7 @@
</blockquote>
<p>Follow the instructions to create and connect to the Kubernetes cluster of your choice:</p>
<ul>
-<li><a href="/docs/zh-CN/2.5.0/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.5.0/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="deploy-pulsar"></a><a href="#deploy-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
<p>With the environment set up and configuration generated, you can now proceed to the <a href="/docs/zh-CN/2.5.0/helm-deploy">deployment of Pulsar</a>.</p>
diff --git a/content/docs/zh-CN/2.5.0/helm-prepare.html b/content/docs/zh-CN/2.5.0/helm-prepare.html
index 427b84c..6ae2953 100644
--- a/content/docs/zh-CN/2.5.0/helm-prepare.html
+++ b/content/docs/zh-CN/2.5.0/helm-prepare.html
@@ -76,9 +76,9 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Preparing Kubernetes resources</h1></header><article><div><span><p>For a fully functional Pulsar cluster, you will need a few resources before deploying the [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>To get started easier, a script is provided to automate the cluster creation. 另外，也可以手动创建集群。</p>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
@@ -103,7 +103,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
+<tr><td>进程</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>Configuration directory to store kubernetes config</td><td>Defaults to ${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>The IP space to use within this cluster</td><td><code>default</code></td></tr>
@@ -130,7 +130,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.5.0/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.5.0/helm-prepare/index.html b/content/docs/zh-CN/2.5.0/helm-prepare/index.html
index 427b84c..6ae2953 100644
--- a/content/docs/zh-CN/2.5.0/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.5.0/helm-prepare/index.html
@@ -76,9 +76,9 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Preparing Kubernetes resources</h1></header><article><div><span><p>For a fully functional Pulsar cluster, you will need a few resources before deploying the [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>To get started easier, a script is provided to automate the cluster creation. 另外，也可以手动创建集群。</p>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
@@ -103,7 +103,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
+<tr><td>进程</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>Configuration directory to store kubernetes config</td><td>Defaults to ${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>The IP space to use within this cluster</td><td><code>default</code></td></tr>
@@ -130,7 +130,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.5.0/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.5.0/reference-cli-tools.html b/content/docs/zh-CN/2.5.0/reference-cli-tools.html
index ac28125..a76ed18 100644
--- a/content/docs/zh-CN/2.5.0/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.5.0/reference-cli-tools.html
@@ -316,7 +316,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -427,22 +427,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -458,34 +458,34 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -499,19 +499,19 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="websocket-producer"></a><a href="#websocket-producer" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -525,7 +525,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.5.0/reference-cli-tools/index.html b/content/docs/zh-CN/2.5.0/reference-cli-tools/index.html
index ac28125..a76ed18 100644
--- a/content/docs/zh-CN/2.5.0/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.5.0/reference-cli-tools/index.html
@@ -316,7 +316,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -427,22 +427,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -458,34 +458,34 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -499,19 +499,19 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="websocket-producer"></a><a href="#websocket-producer" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -525,7 +525,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.5.1/concepts-messaging.html b/content/docs/zh-CN/2.5.1/concepts-messaging.html
index 8d474e7..87846b9 100644
--- a/content/docs/zh-CN/2.5.1/concepts-messaging.html
+++ b/content/docs/zh-CN/2.5.1/concepts-messaging.html
@@ -231,7 +231,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.5.1/concepts-messaging/index.html b/content/docs/zh-CN/2.5.1/concepts-messaging/index.html
index 8d474e7..87846b9 100644
--- a/content/docs/zh-CN/2.5.1/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.5.1/concepts-messaging/index.html
@@ -231,7 +231,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.5.1/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.5.1/deploy-bare-metal-multi-cluster.html
index d097fd3..63af17b 100644
--- a/content/docs/zh-CN/2.5.1/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.5.1/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.5.1/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.5.1/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.5.1/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.5.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.5.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.5.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.5.1/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.5.1/deploy-bare-metal-multi-cluster/index.html
index d097fd3..63af17b 100644
--- a/content/docs/zh-CN/2.5.1/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.5.1/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.5.1/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.5.1/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.5.1/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.5.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.5.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.5.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.5.1/helm-install.html b/content/docs/zh-CN/2.5.1/helm-install.html
index 214f7ef..9d712bc 100644
--- a/content/docs/zh-CN/2.5.1/helm-install.html
+++ b/content/docs/zh-CN/2.5.1/helm-install.html
@@ -92,7 +92,7 @@
</blockquote>
<p>Follow the instructions to create and connect to the Kubernetes cluster of your choice:</p>
<ul>
-<li><a href="/docs/zh-CN/2.5.1/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.5.1/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="deploy-pulsar"></a><a href="#deploy-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
<p>With the environment set up and configuration generated, you can now proceed to the <a href="/docs/zh-CN/2.5.1/helm-deploy">deployment of Pulsar</a>.</p>
diff --git a/content/docs/zh-CN/2.5.1/helm-install/index.html b/content/docs/zh-CN/2.5.1/helm-install/index.html
index 214f7ef..9d712bc 100644
--- a/content/docs/zh-CN/2.5.1/helm-install/index.html
+++ b/content/docs/zh-CN/2.5.1/helm-install/index.html
@@ -92,7 +92,7 @@
</blockquote>
<p>Follow the instructions to create and connect to the Kubernetes cluster of your choice:</p>
<ul>
-<li><a href="/docs/zh-CN/2.5.1/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.5.1/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="deploy-pulsar"></a><a href="#deploy-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
<p>With the environment set up and configuration generated, you can now proceed to the <a href="/docs/zh-CN/2.5.1/helm-deploy">deployment of Pulsar</a>.</p>
diff --git a/content/docs/zh-CN/2.5.1/helm-prepare.html b/content/docs/zh-CN/2.5.1/helm-prepare.html
index 4f306c4..4574b28 100644
--- a/content/docs/zh-CN/2.5.1/helm-prepare.html
+++ b/content/docs/zh-CN/2.5.1/helm-prepare.html
@@ -76,9 +76,9 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Preparing Kubernetes resources</h1></header><article><div><span><p>For a fully functional Pulsar cluster, you will need a few resources before deploying the [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>To get started easier, a script is provided to automate the cluster creation. 另外，也可以手动创建集群。</p>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
@@ -103,7 +103,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
+<tr><td>进程</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>Configuration directory to store kubernetes config</td><td>Defaults to ${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>The IP space to use within this cluster</td><td><code>default</code></td></tr>
@@ -130,7 +130,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.5.1/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.5.1/helm-prepare/index.html b/content/docs/zh-CN/2.5.1/helm-prepare/index.html
index 4f306c4..4574b28 100644
--- a/content/docs/zh-CN/2.5.1/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.5.1/helm-prepare/index.html
@@ -76,9 +76,9 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Preparing Kubernetes resources</h1></header><article><div><span><p>For a fully functional Pulsar cluster, you will need a few resources before deploying the [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>To get started easier, a script is provided to automate the cluster creation. 另外，也可以手动创建集群。</p>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
@@ -103,7 +103,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
+<tr><td>进程</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>Configuration directory to store kubernetes config</td><td>Defaults to ${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>The IP space to use within this cluster</td><td><code>default</code></td></tr>
@@ -130,7 +130,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.5.1/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.5.1/reference-cli-tools.html b/content/docs/zh-CN/2.5.1/reference-cli-tools.html
index 886c7dc..23d75ce 100644
--- a/content/docs/zh-CN/2.5.1/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.5.1/reference-cli-tools.html
@@ -316,7 +316,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -427,22 +427,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -458,34 +458,34 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -499,19 +499,19 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="websocket-producer"></a><a href="#websocket-producer" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -525,7 +525,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.5.1/reference-cli-tools/index.html b/content/docs/zh-CN/2.5.1/reference-cli-tools/index.html
index 886c7dc..23d75ce 100644
--- a/content/docs/zh-CN/2.5.1/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.5.1/reference-cli-tools/index.html
@@ -316,7 +316,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -427,22 +427,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -458,34 +458,34 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -499,19 +499,19 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="websocket-producer"></a><a href="#websocket-producer" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -525,7 +525,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.5.2/concepts-messaging.html b/content/docs/zh-CN/2.5.2/concepts-messaging.html
index f0687d0..8a3f450 100644
--- a/content/docs/zh-CN/2.5.2/concepts-messaging.html
+++ b/content/docs/zh-CN/2.5.2/concepts-messaging.html
@@ -231,7 +231,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.5.2/concepts-messaging/index.html b/content/docs/zh-CN/2.5.2/concepts-messaging/index.html
index f0687d0..8a3f450 100644
--- a/content/docs/zh-CN/2.5.2/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.5.2/concepts-messaging/index.html
@@ -231,7 +231,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.5.2/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.5.2/deploy-bare-metal-multi-cluster.html
index fb2ffcc..559893b 100644
--- a/content/docs/zh-CN/2.5.2/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.5.2/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.5.2/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.5.2/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.5.2/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.5.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.5.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.5.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.5.2/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.5.2/deploy-bare-metal-multi-cluster/index.html
index fb2ffcc..559893b 100644
--- a/content/docs/zh-CN/2.5.2/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.5.2/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.5.2/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.5.2/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.5.2/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.5.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.5.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.5.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.5.2/helm-install.html b/content/docs/zh-CN/2.5.2/helm-install.html
index 57d3cd9..77778c4 100644
--- a/content/docs/zh-CN/2.5.2/helm-install.html
+++ b/content/docs/zh-CN/2.5.2/helm-install.html
@@ -92,7 +92,7 @@
</blockquote>
<p>Follow the instructions to create and connect to the Kubernetes cluster of your choice:</p>
<ul>
-<li><a href="/docs/zh-CN/2.5.2/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.5.2/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="deploy-pulsar"></a><a href="#deploy-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
<p>With the environment set up and configuration generated, you can now proceed to the <a href="/docs/zh-CN/2.5.2/helm-deploy">deployment of Pulsar</a>.</p>
diff --git a/content/docs/zh-CN/2.5.2/helm-install/index.html b/content/docs/zh-CN/2.5.2/helm-install/index.html
index 57d3cd9..77778c4 100644
--- a/content/docs/zh-CN/2.5.2/helm-install/index.html
+++ b/content/docs/zh-CN/2.5.2/helm-install/index.html
@@ -92,7 +92,7 @@
</blockquote>
<p>Follow the instructions to create and connect to the Kubernetes cluster of your choice:</p>
<ul>
-<li><a href="/docs/zh-CN/2.5.2/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.5.2/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="deploy-pulsar"></a><a href="#deploy-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
<p>With the environment set up and configuration generated, you can now proceed to the <a href="/docs/zh-CN/2.5.2/helm-deploy">deployment of Pulsar</a>.</p>
diff --git a/content/docs/zh-CN/2.5.2/helm-prepare.html b/content/docs/zh-CN/2.5.2/helm-prepare.html
index cabe31c..bb1b79e 100644
--- a/content/docs/zh-CN/2.5.2/helm-prepare.html
+++ b/content/docs/zh-CN/2.5.2/helm-prepare.html
@@ -76,9 +76,9 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Preparing Kubernetes resources</h1></header><article><div><span><p>For a fully functional Pulsar cluster, you will need a few resources before deploying the [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>To get started easier, a script is provided to automate the cluster creation. 另外，也可以手动创建集群。</p>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
@@ -103,7 +103,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
+<tr><td>进程</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>Configuration directory to store kubernetes config</td><td>Defaults to ${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>The IP space to use within this cluster</td><td><code>default</code></td></tr>
@@ -130,7 +130,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.5.2/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.5.2/helm-prepare/index.html b/content/docs/zh-CN/2.5.2/helm-prepare/index.html
index cabe31c..bb1b79e 100644
--- a/content/docs/zh-CN/2.5.2/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.5.2/helm-prepare/index.html
@@ -76,9 +76,9 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Preparing Kubernetes resources</h1></header><article><div><span><p>For a fully functional Pulsar cluster, you will need a few resources before deploying the [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>To get started easier, a script is provided to automate the cluster creation. 另外，也可以手动创建集群。</p>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
@@ -103,7 +103,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
+<tr><td>进程</td><td>The ID of your GCP project</td><td>No defaults, required to be set.</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>Configuration directory to store kubernetes config</td><td>Defaults to ${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>The IP space to use within this cluster</td><td><code>default</code></td></tr>
@@ -130,7 +130,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.5.2/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.5.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.5.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.5.2/reference-cli-tools.html b/content/docs/zh-CN/2.5.2/reference-cli-tools.html
index 43e21a1..2963a8e 100644
--- a/content/docs/zh-CN/2.5.2/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.5.2/reference-cli-tools.html
@@ -318,7 +318,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -429,22 +429,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -460,34 +460,34 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -501,19 +501,19 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="websocket-producer"></a><a href="#websocket-producer" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -527,7 +527,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.5.2/reference-cli-tools/index.html b/content/docs/zh-CN/2.5.2/reference-cli-tools/index.html
index 43e21a1..2963a8e 100644
--- a/content/docs/zh-CN/2.5.2/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.5.2/reference-cli-tools/index.html
@@ -318,7 +318,7 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -429,22 +429,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
</tbody>
@@ -460,34 +460,34 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -501,19 +501,19 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="websocket-producer"></a><a href="#websocket-producer" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -527,7 +527,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.0/concepts-messaging.html b/content/docs/zh-CN/2.6.0/concepts-messaging.html
index 6c8007c..a2c0b05 100644
--- a/content/docs/zh-CN/2.6.0/concepts-messaging.html
+++ b/content/docs/zh-CN/2.6.0/concepts-messaging.html
@@ -250,7 +250,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.0/concepts-messaging/index.html b/content/docs/zh-CN/2.6.0/concepts-messaging/index.html
index 6c8007c..a2c0b05 100644
--- a/content/docs/zh-CN/2.6.0/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.6.0/concepts-messaging/index.html
@@ -250,7 +250,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.0/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.6.0/deploy-bare-metal-multi-cluster.html
index 3d06615..02c0437 100644
--- a/content/docs/zh-CN/2.6.0/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.6.0/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.0/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.0/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.0/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.0/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.6.0/deploy-bare-metal-multi-cluster/index.html
index 3d06615..02c0437 100644
--- a/content/docs/zh-CN/2.6.0/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.6.0/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.0/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.0/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.0/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.0/helm-install.html b/content/docs/zh-CN/2.6.0/helm-install.html
index b914df2..bff1dbd 100644
--- a/content/docs/zh-CN/2.6.0/helm-install.html
+++ b/content/docs/zh-CN/2.6.0/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.0/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.0/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.0/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.0/helm-install/index.html b/content/docs/zh-CN/2.6.0/helm-install/index.html
index b914df2..bff1dbd 100644
--- a/content/docs/zh-CN/2.6.0/helm-install/index.html
+++ b/content/docs/zh-CN/2.6.0/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.0/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.0/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.0/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.0/helm-prepare.html b/content/docs/zh-CN/2.6.0/helm-prepare.html
index 834299a..1a7a473 100644
--- a/content/docs/zh-CN/2.6.0/helm-prepare.html
+++ b/content/docs/zh-CN/2.6.0/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.0/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.0/helm-prepare/index.html b/content/docs/zh-CN/2.6.0/helm-prepare/index.html
index 834299a..1a7a473 100644
--- a/content/docs/zh-CN/2.6.0/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.6.0/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.0/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.0/reference-cli-tools.html b/content/docs/zh-CN/2.6.0/reference-cli-tools.html
index 51e004f..a125c5b 100644
--- a/content/docs/zh-CN/2.6.0/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.6.0/reference-cli-tools.html
@@ -318,10 +318,10 @@
<tbody>
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -439,25 +439,25 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -475,35 +475,35 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -517,20 +517,20 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="websocket-producer"></a><a href="#websocket-producer" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -544,7 +544,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.0/reference-cli-tools/index.html b/content/docs/zh-CN/2.6.0/reference-cli-tools/index.html
index 51e004f..a125c5b 100644
--- a/content/docs/zh-CN/2.6.0/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.6.0/reference-cli-tools/index.html
@@ -318,10 +318,10 @@
<tbody>
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -439,25 +439,25 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -475,35 +475,35 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="read"></a><a href="#read" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -517,20 +517,20 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="websocket-producer"></a><a href="#websocket-producer" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -544,7 +544,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.0/sql-deployment-configurations.html b/content/docs/zh-CN/2.6.0/sql-deployment-configurations.html
index 881e8e4..4c55154 100644
--- a/content/docs/zh-CN/2.6.0/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.6.0/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.0/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.0/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.6.0/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.6.0/sql-deployment-configurations/index.html
index 881e8e4..4c55154 100644
--- a/content/docs/zh-CN/2.6.0/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.6.0/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.0/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.0/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.6.1/concepts-messaging.html b/content/docs/zh-CN/2.6.1/concepts-messaging.html
index 835ffd1..a73849f 100644
--- a/content/docs/zh-CN/2.6.1/concepts-messaging.html
+++ b/content/docs/zh-CN/2.6.1/concepts-messaging.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,13 +259,13 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.1/concepts-messaging/index.html b/content/docs/zh-CN/2.6.1/concepts-messaging/index.html
index 835ffd1..a73849f 100644
--- a/content/docs/zh-CN/2.6.1/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.6.1/concepts-messaging/index.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,13 +259,13 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.1/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.6.1/deploy-bare-metal-multi-cluster.html
index 2fbc96c..3f6c866 100644
--- a/content/docs/zh-CN/2.6.1/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.6.1/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.1/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.1/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.1/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.1/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.6.1/deploy-bare-metal-multi-cluster/index.html
index 2fbc96c..3f6c866 100644
--- a/content/docs/zh-CN/2.6.1/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.6.1/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.1/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.1/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.1/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.1/helm-install.html b/content/docs/zh-CN/2.6.1/helm-install.html
index c0c5c56..53b3d40 100644
--- a/content/docs/zh-CN/2.6.1/helm-install.html
+++ b/content/docs/zh-CN/2.6.1/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.1/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.1/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.1/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.1/helm-install/index.html b/content/docs/zh-CN/2.6.1/helm-install/index.html
index c0c5c56..53b3d40 100644
--- a/content/docs/zh-CN/2.6.1/helm-install/index.html
+++ b/content/docs/zh-CN/2.6.1/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.1/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.1/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.1/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.1/helm-prepare.html b/content/docs/zh-CN/2.6.1/helm-prepare.html
index c52026a..8cce471 100644
--- a/content/docs/zh-CN/2.6.1/helm-prepare.html
+++ b/content/docs/zh-CN/2.6.1/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.1/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.1/helm-prepare/index.html b/content/docs/zh-CN/2.6.1/helm-prepare/index.html
index c52026a..8cce471 100644
--- a/content/docs/zh-CN/2.6.1/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.6.1/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.1/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.1/reference-cli-tools.html b/content/docs/zh-CN/2.6.1/reference-cli-tools.html
index 189eeb5..619a6ab 100644
--- a/content/docs/zh-CN/2.6.1/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.6.1/reference-cli-tools.html
@@ -319,10 +319,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -440,26 +440,26 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -478,36 +478,36 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -522,21 +522,21 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -551,7 +551,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.1/reference-cli-tools/index.html b/content/docs/zh-CN/2.6.1/reference-cli-tools/index.html
index 189eeb5..619a6ab 100644
--- a/content/docs/zh-CN/2.6.1/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.6.1/reference-cli-tools/index.html
@@ -319,10 +319,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -440,26 +440,26 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -478,36 +478,36 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -522,21 +522,21 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -551,7 +551,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.1/sql-deployment-configurations.html b/content/docs/zh-CN/2.6.1/sql-deployment-configurations.html
index 6770c97..467e2ce 100644
--- a/content/docs/zh-CN/2.6.1/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.6.1/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>关于Presto部署的更多信息，请参阅 <a href="https://prestodb.io/docs/current/installation/deployment.html">Presto部署</a>。</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.6.1/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.6.1/sql-deployment-configurations/index.html
index 6770c97..467e2ce 100644
--- a/content/docs/zh-CN/2.6.1/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.6.1/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>关于Presto部署的更多信息，请参阅 <a href="https://prestodb.io/docs/current/installation/deployment.html">Presto部署</a>。</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.6.2/concepts-messaging.html b/content/docs/zh-CN/2.6.2/concepts-messaging.html
index 756742c..525fb9d 100644
--- a/content/docs/zh-CN/2.6.2/concepts-messaging.html
+++ b/content/docs/zh-CN/2.6.2/concepts-messaging.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,13 +259,13 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.2/concepts-messaging/index.html b/content/docs/zh-CN/2.6.2/concepts-messaging/index.html
index 756742c..525fb9d 100644
--- a/content/docs/zh-CN/2.6.2/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.6.2/concepts-messaging/index.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,13 +259,13 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.2/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.6.2/deploy-bare-metal-multi-cluster.html
index 847a5aa..2761850 100644
--- a/content/docs/zh-CN/2.6.2/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.6.2/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.2/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.2/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.2/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.2/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.6.2/deploy-bare-metal-multi-cluster/index.html
index 847a5aa..2761850 100644
--- a/content/docs/zh-CN/2.6.2/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.6.2/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.2/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.2/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.2/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.2/helm-install.html b/content/docs/zh-CN/2.6.2/helm-install.html
index 9f525818..96de668 100644
--- a/content/docs/zh-CN/2.6.2/helm-install.html
+++ b/content/docs/zh-CN/2.6.2/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.2/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.2/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.2/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.2/helm-install/index.html b/content/docs/zh-CN/2.6.2/helm-install/index.html
index 9f525818..96de668 100644
--- a/content/docs/zh-CN/2.6.2/helm-install/index.html
+++ b/content/docs/zh-CN/2.6.2/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.2/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.2/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.2/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.2/helm-prepare.html b/content/docs/zh-CN/2.6.2/helm-prepare.html
index abc16cc..2715a62 100644
--- a/content/docs/zh-CN/2.6.2/helm-prepare.html
+++ b/content/docs/zh-CN/2.6.2/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.2/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.2/helm-prepare/index.html b/content/docs/zh-CN/2.6.2/helm-prepare/index.html
index abc16cc..2715a62 100644
--- a/content/docs/zh-CN/2.6.2/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.6.2/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.2/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.2/reference-cli-tools.html b/content/docs/zh-CN/2.6.2/reference-cli-tools.html
index c91bb8e..fcc6a79 100644
--- a/content/docs/zh-CN/2.6.2/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.6.2/reference-cli-tools.html
@@ -319,10 +319,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -440,27 +440,27 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -479,38 +479,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -525,22 +525,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -555,7 +555,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.2/reference-cli-tools/index.html b/content/docs/zh-CN/2.6.2/reference-cli-tools/index.html
index c91bb8e..fcc6a79 100644
--- a/content/docs/zh-CN/2.6.2/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.6.2/reference-cli-tools/index.html
@@ -319,10 +319,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -440,27 +440,27 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -479,38 +479,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -525,22 +525,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -555,7 +555,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.2/sql-deployment-configurations.html b/content/docs/zh-CN/2.6.2/sql-deployment-configurations.html
index 3f37d27..aa6a808 100644
--- a/content/docs/zh-CN/2.6.2/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.6.2/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>关于Presto部署的更多信息，请参阅 <a href="https://prestodb.io/docs/current/installation/deployment.html">Presto部署</a>。</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.6.2/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.6.2/sql-deployment-configurations/index.html
index 3f37d27..aa6a808 100644
--- a/content/docs/zh-CN/2.6.2/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.6.2/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>关于Presto部署的更多信息，请参阅 <a href="https://prestodb.io/docs/current/installation/deployment.html">Presto部署</a>。</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.6.3/concepts-messaging.html b/content/docs/zh-CN/2.6.3/concepts-messaging.html
index af4f0ab..6bd1fef 100644
--- a/content/docs/zh-CN/2.6.3/concepts-messaging.html
+++ b/content/docs/zh-CN/2.6.3/concepts-messaging.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,13 +259,13 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.3/concepts-messaging/index.html b/content/docs/zh-CN/2.6.3/concepts-messaging/index.html
index af4f0ab..6bd1fef 100644
--- a/content/docs/zh-CN/2.6.3/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.6.3/concepts-messaging/index.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,13 +259,13 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.3/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.6.3/deploy-bare-metal-multi-cluster.html
index 7bf1992..7b60dc8 100644
--- a/content/docs/zh-CN/2.6.3/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.6.3/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.3/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.3/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.3/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.3/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.3/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.3/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.3/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.6.3/deploy-bare-metal-multi-cluster/index.html
index 7bf1992..7b60dc8 100644
--- a/content/docs/zh-CN/2.6.3/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.6.3/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.3/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.3/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.3/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.3/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.3/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.3/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.3/helm-install.html b/content/docs/zh-CN/2.6.3/helm-install.html
index 162a247..e16a3de 100644
--- a/content/docs/zh-CN/2.6.3/helm-install.html
+++ b/content/docs/zh-CN/2.6.3/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.3/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.3/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.3/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.3/helm-install/index.html b/content/docs/zh-CN/2.6.3/helm-install/index.html
index 162a247..e16a3de 100644
--- a/content/docs/zh-CN/2.6.3/helm-install/index.html
+++ b/content/docs/zh-CN/2.6.3/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.3/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.3/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.3/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.3/helm-prepare.html b/content/docs/zh-CN/2.6.3/helm-prepare.html
index 857b10a..fa8162a 100644
--- a/content/docs/zh-CN/2.6.3/helm-prepare.html
+++ b/content/docs/zh-CN/2.6.3/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.3/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.3/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.3/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.3/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.3/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.3/helm-prepare/index.html b/content/docs/zh-CN/2.6.3/helm-prepare/index.html
index 857b10a..fa8162a 100644
--- a/content/docs/zh-CN/2.6.3/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.6.3/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.3/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.3/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.3/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.3/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.3/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.3/reference-cli-tools.html b/content/docs/zh-CN/2.6.3/reference-cli-tools.html
index e39ac9d..7ec873a 100644
--- a/content/docs/zh-CN/2.6.3/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.6.3/reference-cli-tools.html
@@ -319,10 +319,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -440,27 +440,27 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -479,38 +479,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -525,22 +525,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -555,7 +555,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.3/reference-cli-tools/index.html b/content/docs/zh-CN/2.6.3/reference-cli-tools/index.html
index e39ac9d..7ec873a 100644
--- a/content/docs/zh-CN/2.6.3/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.6.3/reference-cli-tools/index.html
@@ -319,10 +319,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -440,27 +440,27 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -479,38 +479,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -525,22 +525,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -555,7 +555,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.3/sql-deployment-configurations.html b/content/docs/zh-CN/2.6.3/sql-deployment-configurations.html
index 4cd8269..c62eb4b 100644
--- a/content/docs/zh-CN/2.6.3/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.6.3/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>关于Presto部署的更多信息，请参阅 <a href="https://prestodb.io/docs/current/installation/deployment.html">Presto部署</a>。</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.3/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.3/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.6.3/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.6.3/sql-deployment-configurations/index.html
index 4cd8269..c62eb4b 100644
--- a/content/docs/zh-CN/2.6.3/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.6.3/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>关于Presto部署的更多信息，请参阅 <a href="https://prestodb.io/docs/current/installation/deployment.html">Presto部署</a>。</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.3/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.3/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.6.4/concepts-messaging.html b/content/docs/zh-CN/2.6.4/concepts-messaging.html
index dc26adc..ba223ba 100644
--- a/content/docs/zh-CN/2.6.4/concepts-messaging.html
+++ b/content/docs/zh-CN/2.6.4/concepts-messaging.html
@@ -166,7 +166,7 @@
</ul>
<blockquote>
<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p>Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -261,13 +261,13 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p>In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.4/concepts-messaging/index.html b/content/docs/zh-CN/2.6.4/concepts-messaging/index.html
index dc26adc..ba223ba 100644
--- a/content/docs/zh-CN/2.6.4/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.6.4/concepts-messaging/index.html
@@ -166,7 +166,7 @@
</ul>
<blockquote>
<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p>Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -261,13 +261,13 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p>In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.6.4/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.6.4/deploy-bare-metal-multi-cluster.html
index dda2f3c..8d464fc 100644
--- a/content/docs/zh-CN/2.6.4/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.6.4/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.4/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.4/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.4/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.4/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.4/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.4/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.4/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.6.4/deploy-bare-metal-multi-cluster/index.html
index dda2f3c..8d464fc 100644
--- a/content/docs/zh-CN/2.6.4/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.6.4/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.6.4/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.6.4/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.6.4/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.6.4/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.6.4/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.6.4/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.6.4/helm-install.html b/content/docs/zh-CN/2.6.4/helm-install.html
index 1748936..2d33bb8 100644
--- a/content/docs/zh-CN/2.6.4/helm-install.html
+++ b/content/docs/zh-CN/2.6.4/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.4/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.4/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.4/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.4/helm-install/index.html b/content/docs/zh-CN/2.6.4/helm-install/index.html
index 1748936..2d33bb8 100644
--- a/content/docs/zh-CN/2.6.4/helm-install/index.html
+++ b/content/docs/zh-CN/2.6.4/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.6.4/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.6.4/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.6.4/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.6.4/helm-prepare.html b/content/docs/zh-CN/2.6.4/helm-prepare.html
index 258d868..c3557ca 100644
--- a/content/docs/zh-CN/2.6.4/helm-prepare.html
+++ b/content/docs/zh-CN/2.6.4/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.4/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.4/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.4/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.4/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.4/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.4/helm-prepare/index.html b/content/docs/zh-CN/2.6.4/helm-prepare/index.html
index 258d868..c3557ca 100644
--- a/content/docs/zh-CN/2.6.4/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.6.4/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.6.4/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.4/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.4/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.4/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.4/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.4/reference-cli-tools.html b/content/docs/zh-CN/2.6.4/reference-cli-tools.html
index 2070d1f..3c4221d 100644
--- a/content/docs/zh-CN/2.6.4/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.6.4/reference-cli-tools.html
@@ -319,10 +319,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -440,27 +440,27 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -479,38 +479,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -525,22 +525,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -555,7 +555,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.4/reference-cli-tools/index.html b/content/docs/zh-CN/2.6.4/reference-cli-tools/index.html
index 2070d1f..3c4221d 100644
--- a/content/docs/zh-CN/2.6.4/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.6.4/reference-cli-tools/index.html
@@ -319,10 +319,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -440,27 +440,27 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -479,38 +479,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -525,22 +525,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -555,7 +555,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.6.4/sql-deployment-configurations.html b/content/docs/zh-CN/2.6.4/sql-deployment-configurations.html
index d1d567c..37d5a2d 100644
--- a/content/docs/zh-CN/2.6.4/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.6.4/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.4/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.4/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.6.4/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.6.4/sql-deployment-configurations/index.html
index d1d567c..37d5a2d 100644
--- a/content/docs/zh-CN/2.6.4/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.6.4/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.4/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.4/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.7.0/concepts-messaging.html b/content/docs/zh-CN/2.7.0/concepts-messaging.html
index b2c2ed5..f3ee958 100644
--- a/content/docs/zh-CN/2.7.0/concepts-messaging.html
+++ b/content/docs/zh-CN/2.7.0/concepts-messaging.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,7 +259,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -267,7 +267,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.7.0/concepts-messaging/index.html b/content/docs/zh-CN/2.7.0/concepts-messaging/index.html
index b2c2ed5..f3ee958 100644
--- a/content/docs/zh-CN/2.7.0/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.7.0/concepts-messaging/index.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,7 +259,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -267,7 +267,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.7.0/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.7.0/deploy-bare-metal-multi-cluster.html
index 81b62fe..47b30e7 100644
--- a/content/docs/zh-CN/2.7.0/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.7.0/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.7.0/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.7.0/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.7.0/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.7.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.7.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.7.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.7.0/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.7.0/deploy-bare-metal-multi-cluster/index.html
index 81b62fe..47b30e7 100644
--- a/content/docs/zh-CN/2.7.0/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.7.0/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.7.0/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.7.0/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.7.0/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.7.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.7.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.7.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.7.0/helm-install.html b/content/docs/zh-CN/2.7.0/helm-install.html
index 58ece05..4ea4cc2 100644
--- a/content/docs/zh-CN/2.7.0/helm-install.html
+++ b/content/docs/zh-CN/2.7.0/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.7.0/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.7.0/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.7.0/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.7.0/helm-install/index.html b/content/docs/zh-CN/2.7.0/helm-install/index.html
index 58ece05..4ea4cc2 100644
--- a/content/docs/zh-CN/2.7.0/helm-install/index.html
+++ b/content/docs/zh-CN/2.7.0/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.7.0/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.7.0/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.7.0/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.7.0/helm-prepare.html b/content/docs/zh-CN/2.7.0/helm-prepare.html
index 322e91a..ce56535 100644
--- a/content/docs/zh-CN/2.7.0/helm-prepare.html
+++ b/content/docs/zh-CN/2.7.0/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.7.0/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.7.0/helm-prepare/index.html b/content/docs/zh-CN/2.7.0/helm-prepare/index.html
index 322e91a..ce56535 100644
--- a/content/docs/zh-CN/2.7.0/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.7.0/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.7.0/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.7.0/reference-cli-tools.html b/content/docs/zh-CN/2.7.0/reference-cli-tools.html
index 0e66ba1..7e4b1dc 100644
--- a/content/docs/zh-CN/2.7.0/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.7.0/reference-cli-tools.html
@@ -324,10 +324,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -446,27 +446,27 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -485,38 +485,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -531,22 +531,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -561,7 +561,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.7.0/reference-cli-tools/index.html b/content/docs/zh-CN/2.7.0/reference-cli-tools/index.html
index 0e66ba1..7e4b1dc 100644
--- a/content/docs/zh-CN/2.7.0/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.7.0/reference-cli-tools/index.html
@@ -324,10 +324,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -446,27 +446,27 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The private key name to decrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -485,38 +485,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -531,22 +531,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -561,7 +561,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.7.0/sql-deployment-configurations.html b/content/docs/zh-CN/2.7.0/sql-deployment-configurations.html
index da7b9a5..465d05b 100644
--- a/content/docs/zh-CN/2.7.0/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.7.0/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.0/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.0/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.7.0/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.7.0/sql-deployment-configurations/index.html
index da7b9a5..465d05b 100644
--- a/content/docs/zh-CN/2.7.0/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.7.0/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.0/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.0/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.7.1/concepts-messaging.html b/content/docs/zh-CN/2.7.1/concepts-messaging.html
index f17c830..63fb8ac 100644
--- a/content/docs/zh-CN/2.7.1/concepts-messaging.html
+++ b/content/docs/zh-CN/2.7.1/concepts-messaging.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,7 +259,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -267,7 +267,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.7.1/concepts-messaging/index.html b/content/docs/zh-CN/2.7.1/concepts-messaging/index.html
index f17c830..63fb8ac 100644
--- a/content/docs/zh-CN/2.7.1/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.7.1/concepts-messaging/index.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,7 +259,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -267,7 +267,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.7.1/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.7.1/deploy-bare-metal-multi-cluster.html
index 0233c9f..23f97af 100644
--- a/content/docs/zh-CN/2.7.1/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.7.1/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.7.1/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.7.1/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.7.1/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.7.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.7.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.7.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.7.1/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.7.1/deploy-bare-metal-multi-cluster/index.html
index 0233c9f..23f97af 100644
--- a/content/docs/zh-CN/2.7.1/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.7.1/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.7.1/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.7.1/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.7.1/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.7.1/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.7.1/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.7.1/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.7.1/helm-install.html b/content/docs/zh-CN/2.7.1/helm-install.html
index 1efc1e3..e672477 100644
--- a/content/docs/zh-CN/2.7.1/helm-install.html
+++ b/content/docs/zh-CN/2.7.1/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.7.1/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.7.1/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.7.1/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.7.1/helm-install/index.html b/content/docs/zh-CN/2.7.1/helm-install/index.html
index 1efc1e3..e672477 100644
--- a/content/docs/zh-CN/2.7.1/helm-install/index.html
+++ b/content/docs/zh-CN/2.7.1/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.7.1/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.7.1/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.7.1/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.7.1/helm-prepare.html b/content/docs/zh-CN/2.7.1/helm-prepare.html
index 969f829..2808fe6 100644
--- a/content/docs/zh-CN/2.7.1/helm-prepare.html
+++ b/content/docs/zh-CN/2.7.1/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.7.1/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.7.1/helm-prepare/index.html b/content/docs/zh-CN/2.7.1/helm-prepare/index.html
index 969f829..2808fe6 100644
--- a/content/docs/zh-CN/2.7.1/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.7.1/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.7.1/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.1/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.1/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.7.1/reference-cli-tools.html b/content/docs/zh-CN/2.7.1/reference-cli-tools.html
index 94221fb..ddd54cc 100644
--- a/content/docs/zh-CN/2.7.1/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.7.1/reference-cli-tools.html
@@ -324,10 +324,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -446,29 +446,29 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
-<tr><td><code>--batch-index-ack</code></td><td>Enable or disable the batch index acknowledgment</td><td>false</td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>--batch-index-ack</code></td><td>开启或禁用批量索引确认</td><td>false</td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
-<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>Number of subscriptions (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
+<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>订阅数量 (每个主题)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>Max total size of the receiver queue across partitions</td><td>50000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>分区接收队列的最大大小</td><td>50000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -487,38 +487,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -533,22 +533,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -563,7 +563,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.7.1/reference-cli-tools/index.html b/content/docs/zh-CN/2.7.1/reference-cli-tools/index.html
index 94221fb..ddd54cc 100644
--- a/content/docs/zh-CN/2.7.1/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.7.1/reference-cli-tools/index.html
@@ -324,10 +324,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -446,29 +446,29 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
-<tr><td><code>--batch-index-ack</code></td><td>Enable or disable the batch index acknowledgment</td><td>false</td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>--batch-index-ack</code></td><td>开启或禁用批量索引确认</td><td>false</td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
-<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>Number of subscriptions (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
+<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>订阅数量 (每个主题)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>Max total size of the receiver queue across partitions</td><td>50000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>分区接收队列的最大大小</td><td>50000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -487,38 +487,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -533,22 +533,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -563,7 +563,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.7.1/sql-deployment-configurations.html b/content/docs/zh-CN/2.7.1/sql-deployment-configurations.html
index 7046e70..5dd98b7 100644
--- a/content/docs/zh-CN/2.7.1/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.7.1/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.1/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.1/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.7.1/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.7.1/sql-deployment-configurations/index.html
index 7046e70..5dd98b7 100644
--- a/content/docs/zh-CN/2.7.1/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.7.1/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.1/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.1/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.7.2/concepts-messaging.html b/content/docs/zh-CN/2.7.2/concepts-messaging.html
index d882dde..bcc9de8 100644
--- a/content/docs/zh-CN/2.7.2/concepts-messaging.html
+++ b/content/docs/zh-CN/2.7.2/concepts-messaging.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,7 +259,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -267,7 +267,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.7.2/concepts-messaging/index.html b/content/docs/zh-CN/2.7.2/concepts-messaging/index.html
index d882dde..bcc9de8 100644
--- a/content/docs/zh-CN/2.7.2/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.7.2/concepts-messaging/index.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,7 +259,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -267,7 +267,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.7.2/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.7.2/deploy-bare-metal-multi-cluster.html
index cf3ad7f..2fe5193 100644
--- a/content/docs/zh-CN/2.7.2/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.7.2/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.7.2/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.7.2/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.7.2/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -128,7 +128,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.7.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.7.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.7.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.7.2/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.7.2/deploy-bare-metal-multi-cluster/index.html
index cf3ad7f..2fe5193 100644
--- a/content/docs/zh-CN/2.7.2/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.7.2/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.7.2/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.7.2/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.7.2/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -128,7 +128,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.7.2/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.7.2/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.7.2/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.7.2/helm-install.html b/content/docs/zh-CN/2.7.2/helm-install.html
index 1989ada..29ac7b9 100644
--- a/content/docs/zh-CN/2.7.2/helm-install.html
+++ b/content/docs/zh-CN/2.7.2/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.7.2/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.7.2/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.7.2/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.7.2/helm-install/index.html b/content/docs/zh-CN/2.7.2/helm-install/index.html
index 1989ada..29ac7b9 100644
--- a/content/docs/zh-CN/2.7.2/helm-install/index.html
+++ b/content/docs/zh-CN/2.7.2/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.7.2/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.7.2/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.7.2/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.7.2/helm-prepare.html b/content/docs/zh-CN/2.7.2/helm-prepare.html
index bb80ee7..c7b1a9f 100644
--- a/content/docs/zh-CN/2.7.2/helm-prepare.html
+++ b/content/docs/zh-CN/2.7.2/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.7.2/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.7.2/helm-prepare/index.html b/content/docs/zh-CN/2.7.2/helm-prepare/index.html
index bb80ee7..c7b1a9f 100644
--- a/content/docs/zh-CN/2.7.2/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.7.2/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.7.2/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.2/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.2/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.7.2/reference-cli-tools.html b/content/docs/zh-CN/2.7.2/reference-cli-tools.html
index d7d1c80..1f5973a 100644
--- a/content/docs/zh-CN/2.7.2/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.7.2/reference-cli-tools.html
@@ -324,10 +324,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -446,29 +446,29 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
-<tr><td><code>--batch-index-ack</code></td><td>Enable or disable the batch index acknowledgment</td><td>false</td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>--batch-index-ack</code></td><td>开启或禁用批量索引确认</td><td>false</td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
-<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>Number of subscriptions (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
+<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>订阅数量 (每个主题)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>Max total size of the receiver queue across partitions</td><td>50000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>分区接收队列的最大大小</td><td>50000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -487,38 +487,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -533,22 +533,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -563,7 +563,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.7.2/reference-cli-tools/index.html b/content/docs/zh-CN/2.7.2/reference-cli-tools/index.html
index d7d1c80..1f5973a 100644
--- a/content/docs/zh-CN/2.7.2/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.7.2/reference-cli-tools/index.html
@@ -324,10 +324,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -446,29 +446,29 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
-<tr><td><code>--batch-index-ack</code></td><td>Enable or disable the batch index acknowledgment</td><td>false</td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>--batch-index-ack</code></td><td>开启或禁用批量索引确认</td><td>false</td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
-<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>Number of subscriptions (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
+<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>订阅数量 (每个主题)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>Max total size of the receiver queue across partitions</td><td>50000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>分区接收队列的最大大小</td><td>50000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -487,38 +487,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -533,22 +533,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -563,7 +563,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.7.2/sql-deployment-configurations.html b/content/docs/zh-CN/2.7.2/sql-deployment-configurations.html
index 29e41f0..0d45d8a 100644
--- a/content/docs/zh-CN/2.7.2/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.7.2/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.2/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.2/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.7.2/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.7.2/sql-deployment-configurations/index.html
index 29e41f0..0d45d8a 100644
--- a/content/docs/zh-CN/2.7.2/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.7.2/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.2/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.2/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.7.3/concepts-messaging.html b/content/docs/zh-CN/2.7.3/concepts-messaging.html
index 36b9e8a..edee543 100644
--- a/content/docs/zh-CN/2.7.3/concepts-messaging.html
+++ b/content/docs/zh-CN/2.7.3/concepts-messaging.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,7 +259,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -267,7 +267,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.7.3/concepts-messaging/index.html b/content/docs/zh-CN/2.7.3/concepts-messaging/index.html
index 36b9e8a..edee543 100644
--- a/content/docs/zh-CN/2.7.3/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.7.3/concepts-messaging/index.html
@@ -165,7 +165,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -259,7 +259,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -267,7 +267,7 @@ Currently, dead letter topic is enabled only in Shared subscription type.</p>
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.7.3/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.7.3/deploy-bare-metal-multi-cluster.html
index 4332b9f..93633a2 100644
--- a/content/docs/zh-CN/2.7.3/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.7.3/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.7.3/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.7.3/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.7.3/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.7.3/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.7.3/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.7.3/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.7.3/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.7.3/deploy-bare-metal-multi-cluster/index.html
index 4332b9f..93633a2 100644
--- a/content/docs/zh-CN/2.7.3/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.7.3/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.7.3/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.7.3/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.7.3/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -124,7 +124,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.7.3/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.7.3/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.7.3/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.7.3/helm-install.html b/content/docs/zh-CN/2.7.3/helm-install.html
index e3e5601..3132f96 100644
--- a/content/docs/zh-CN/2.7.3/helm-install.html
+++ b/content/docs/zh-CN/2.7.3/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.7.3/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.7.3/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.7.3/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.7.3/helm-install/index.html b/content/docs/zh-CN/2.7.3/helm-install/index.html
index e3e5601..3132f96 100644
--- a/content/docs/zh-CN/2.7.3/helm-install/index.html
+++ b/content/docs/zh-CN/2.7.3/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.7.3/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.7.3/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.7.3/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.7.3/helm-prepare.html b/content/docs/zh-CN/2.7.3/helm-prepare.html
index a2eeeda..56c2251 100644
--- a/content/docs/zh-CN/2.7.3/helm-prepare.html
+++ b/content/docs/zh-CN/2.7.3/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.7.3/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.3/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.3/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.3/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.3/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.7.3/helm-prepare/index.html b/content/docs/zh-CN/2.7.3/helm-prepare/index.html
index a2eeeda..56c2251 100644
--- a/content/docs/zh-CN/2.7.3/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.7.3/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.7.3/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.3/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.3/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.3/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.3/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.7.3/reference-cli-tools.html b/content/docs/zh-CN/2.7.3/reference-cli-tools.html
index 17bcd76..fc93610 100644
--- a/content/docs/zh-CN/2.7.3/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.7.3/reference-cli-tools.html
@@ -324,10 +324,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -446,29 +446,29 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
-<tr><td><code>--batch-index-ack</code></td><td>Enable or disable the batch index acknowledgment</td><td>false</td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>--batch-index-ack</code></td><td>开启或禁用批量索引确认</td><td>false</td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
-<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>Number of subscriptions (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
+<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>订阅数量 (每个主题)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>Max total size of the receiver queue across partitions</td><td>50000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>分区接收队列的最大大小</td><td>50000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -487,38 +487,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -533,22 +533,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -563,7 +563,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.7.3/reference-cli-tools/index.html b/content/docs/zh-CN/2.7.3/reference-cli-tools/index.html
index 17bcd76..fc93610 100644
--- a/content/docs/zh-CN/2.7.3/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.7.3/reference-cli-tools/index.html
@@ -324,10 +324,10 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -446,29 +446,29 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>Acknowlegments grouping delay in millis</td><td>100</td></tr>
-<tr><td><code>--batch-index-ack</code></td><td>Enable or disable the batch index acknowledgment</td><td>false</td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>--batch-index-ack</code></td><td>开启或禁用批量索引确认</td><td>false</td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
-<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>Number of subscriptions (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
+<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>订阅数量 (每个主题)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>Max total size of the receiver queue across partitions</td><td>50000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>分区接收队列的最大大小</td><td>50000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -487,38 +487,38 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -533,22 +533,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -563,7 +563,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.7.3/sql-deployment-configurations.html b/content/docs/zh-CN/2.7.3/sql-deployment-configurations.html
index 7439d29..5435f52 100644
--- a/content/docs/zh-CN/2.7.3/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.7.3/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.3/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.3/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.7.3/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.7.3/sql-deployment-configurations/index.html
index 7439d29..5435f52 100644
--- a/content/docs/zh-CN/2.7.3/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.7.3/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>For more information about deployment in Presto, refer to <a href="https://prestosql.io/docs/current/installation/deployment.html">Presto deployment</a>.</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.7.3/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.7.3/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.8.0/concepts-messaging.html b/content/docs/zh-CN/2.8.0/concepts-messaging.html
index 8a76471..4ec1fd6 100644
--- a/content/docs/zh-CN/2.8.0/concepts-messaging.html
+++ b/content/docs/zh-CN/2.8.0/concepts-messaging.html
@@ -134,7 +134,7 @@ nettyMaxFrameSizeBytes=5253120
<blockquote>
<p><strong>Note</strong></p>
<p>Once an application creates a producer with the <code>Exclusive</code> or <code>WaitForExclusive</code> access mode successfully, the instance of the application is guaranteed to be the <strong>only one writer</strong> on the topic. Other producers trying to produce on this topic get errors immediately or have to wait until they get the <code>Exclusive</code> access.</p>
-<p>For more information, see <a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68: Exclusive Producer</a>.</p>
+<p>想了解更多信息，请参阅<a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68：Exclusive Producer</a>。</p>
</blockquote>
<p>You can set producer access mode through Java Client API. For more information, see <code>ProducerAccessMode</code> in <a href="https://github.com/apache/pulsar/blob/fc5768ca3bbf92815d142fe30e6bfad70a1b4fc6/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java">ProducerBuilder.java</a>.</p>
<h3><a class="anchor" aria-hidden="true" id="compression"></a><a href="#compression" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
@@ -193,7 +193,7 @@ nettyMaxFrameSizeBytes=5253120
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -287,7 +287,7 @@ Currently, dead letter topic is enabled In the shared and Key_Shared subscriptio
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -295,7 +295,7 @@ Currently, dead letter topic is enabled In the shared and Key_Shared subscriptio
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.8.0/concepts-messaging/index.html b/content/docs/zh-CN/2.8.0/concepts-messaging/index.html
index 8a76471..4ec1fd6 100644
--- a/content/docs/zh-CN/2.8.0/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.8.0/concepts-messaging/index.html
@@ -134,7 +134,7 @@ nettyMaxFrameSizeBytes=5253120
<blockquote>
<p><strong>Note</strong></p>
<p>Once an application creates a producer with the <code>Exclusive</code> or <code>WaitForExclusive</code> access mode successfully, the instance of the application is guaranteed to be the <strong>only one writer</strong> on the topic. Other producers trying to produce on this topic get errors immediately or have to wait until they get the <code>Exclusive</code> access.</p>
-<p>For more information, see <a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68: Exclusive Producer</a>.</p>
+<p>想了解更多信息，请参阅<a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68：Exclusive Producer</a>。</p>
</blockquote>
<p>You can set producer access mode through Java Client API. For more information, see <code>ProducerAccessMode</code> in <a href="https://github.com/apache/pulsar/blob/fc5768ca3bbf92815d142fe30e6bfad70a1b4fc6/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java">ProducerBuilder.java</a>.</p>
<h3><a class="anchor" aria-hidden="true" id="compression"></a><a href="#compression" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
@@ -193,7 +193,7 @@ nettyMaxFrameSizeBytes=5253120
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -287,7 +287,7 @@ Currently, dead letter topic is enabled In the shared and Key_Shared subscriptio
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -295,7 +295,7 @@ Currently, dead letter topic is enabled In the shared and Key_Shared subscriptio
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/2.8.0/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/2.8.0/deploy-bare-metal-multi-cluster.html
index d4c4ae1..e932286 100644
--- a/content/docs/zh-CN/2.8.0/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/2.8.0/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.8.0/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.8.0/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.8.0/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -128,7 +128,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.8.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.8.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.8.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.8.0/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/2.8.0/deploy-bare-metal-multi-cluster/index.html
index d4c4ae1..e932286 100644
--- a/content/docs/zh-CN/2.8.0/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/2.8.0/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/2.8.0/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/2.8.0/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/2.8.0/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -128,7 +128,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/2.8.0/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/2.8.0/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/2.8.0/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/2.8.0/helm-install.html b/content/docs/zh-CN/2.8.0/helm-install.html
index 79ef8ca..876d389 100644
--- a/content/docs/zh-CN/2.8.0/helm-install.html
+++ b/content/docs/zh-CN/2.8.0/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.8.0/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.8.0/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.8.0/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.8.0/helm-install/index.html b/content/docs/zh-CN/2.8.0/helm-install/index.html
index 79ef8ca..876d389 100644
--- a/content/docs/zh-CN/2.8.0/helm-install/index.html
+++ b/content/docs/zh-CN/2.8.0/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/2.8.0/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/2.8.0/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/2.8.0/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/2.8.0/helm-prepare.html b/content/docs/zh-CN/2.8.0/helm-prepare.html
index c4f8915..88ccfda 100644
--- a/content/docs/zh-CN/2.8.0/helm-prepare.html
+++ b/content/docs/zh-CN/2.8.0/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.8.0/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.8.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.8.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.8.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.8.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.8.0/helm-prepare/index.html b/content/docs/zh-CN/2.8.0/helm-prepare/index.html
index c4f8915..88ccfda 100644
--- a/content/docs/zh-CN/2.8.0/helm-prepare/index.html
+++ b/content/docs/zh-CN/2.8.0/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/2.8.0/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.8.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.8.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.8.0/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.8.0/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a hr [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.8.0/reference-cli-tools.html b/content/docs/zh-CN/2.8.0/reference-cli-tools.html
index 43c396d..5633eda 100644
--- a/content/docs/zh-CN/2.8.0/reference-cli-tools.html
+++ b/content/docs/zh-CN/2.8.0/reference-cli-tools.html
@@ -324,11 +324,11 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
<tr><td><code>-v</code>, <code>--version</code></td><td>获取Pulsar客户端版本</td><td></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -379,7 +379,7 @@
<tr><td><code>--hide-content</code></td><td>不要将消息打印到控制台。</td><td>false</td></tr>
<tr><td><code>-st</code>, <code>--schema-type</code></td><td>Set the schema type. Use <code>auto_consume</code> to dump AVRO and other structured data types. Possible values: bytes, auto_consume.</td><td>bytes</td></tr>
<tr><td><code>-ekv</code>, <code>--encryption-key-value</code></td><td>The URI of public key to encrypt payload. For example, <code>file:///path/to/public.key</code> or <code>data:application/x-pem-file;base64,*****</code>.</td><td></td></tr>
-<tr><td><code>-pm</code>, <code>--pool-messages</code></td><td>Use the pooled message.</td><td>true</td></tr>
+<tr><td><code>-pm</code>, <code>--pool-messages</code></td><td>使用池化消息</td><td>true</td></tr>
</tbody>
</table>
<h2><a class="anchor" aria-hidden="true" id="pulsar-daemon"></a><a href="#pulsar-daemon" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
@@ -453,32 +453,32 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>确认分组延迟，以毫秒计</td><td>100</td></tr>
-<tr><td><code>--batch-index-ack</code></td><td>Enable or disable the batch index acknowledgment</td><td>false</td></tr>
-<tr><td><code>-bw</code>, <code>--busy-wait</code></td><td>Enable or disable Busy-Wait on the Pulsar client</td><td>false</td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>--batch-index-ack</code></td><td>开启或禁用批量索引确认</td><td>false</td></tr>
+<tr><td><code>-bw</code>, <code>--busy-wait</code></td><td>在 Pulsar 客户端启用或禁用 Busy-Wait</td><td>false</td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
-<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>Number of subscriptions (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
+<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>订阅数量 (每个主题)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topics</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-pm</code>, <code>--pool-messages</code></td><td>Use the pooled message</td><td>true</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>Max total size of the receiver queue across partitions</td><td>50000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-pm</code>, <code>--pool-messages</code></td><td>使用池化消息</td><td>true</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>分区接收队列的最大大小</td><td>50000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
-<tr><td><code>-ss</code>, <code>--subscriptions</code></td><td>A list of subscriptions to consume on (e.g. sub1,sub2)</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
+<tr><td><code>-ss</code>, <code>--subscriptions</code></td><td>要消费的订阅列表（比如 sub1,sub2）</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -499,45 +499,45 @@
<tbody>
<tr><td><code>-am</code>, <code>--access-mode</code></td><td>Producer access mode. Valid values are <code>Shared</code>, <code>Exclusive</code> and <code>WaitForExclusive</code></td><td>Shared（共享）</td></tr>
<tr><td><code>-au</code>, <code>--admin-url</code></td><td>Pulsar admin URL</td><td></td></tr>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-bw</code>, <code>--busy-wait</code></td><td>Enable or disable Busy-Wait on the Pulsar client</td><td>false</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bw</code>, <code>--busy-wait</code></td><td>在 Pulsar 客户端启用或禁用 Busy-Wait</td><td>false</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
-<tr><td><code>-fc</code>, <code>--format-class</code></td><td>Custom Formatter class name</td><td>org.apache.pulsar.testclient.DefaultMessageFormatter</td></tr>
-<tr><td><code>-fp</code>, <code>--format-payload</code></td><td>Format %i as a message index in the stream from producer and/or %t as the timestamp nanoseconds</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
+<tr><td><code>-fc</code>, <code>--format-class</code></td><td>自定义 formatter 类名</td><td>org.apache.pulsar.testclient.DefaultMessageFormatter</td></tr>
+<tr><td><code>-fp</code>, <code>--format-payload</code></td><td>格式化为来自 producer 和/或流中的消息索引作为时间戳，单位为 nanoseconds</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
<tr><td><code>-np</code>, <code>--partitions</code></td><td>Create partitioned topics with the given number of partitions. Setting this value to 0 means not trying to create a topic</td><td></td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
-<tr><td><code>-pn</code>, <code>--producer-name</code></td><td>Producer Name</td><td></td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
+<tr><td><code>-pn</code>, <code>--producer-name</code></td><td>生产者名称</td><td></td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
-<tr><td><code>--send-timeout</code></td><td>Set the sendTimeout</td><td>0</td></tr>
-<tr><td><code>--separator</code></td><td>Separator between the topic and topic number</td><td>-</td></tr>
+<tr><td><code>--send-timeout</code></td><td>设置发送超时时间</td><td>0</td></tr>
+<tr><td><code>--separator</code></td><td>Topic 和 topic 编号之间的分隔符</td><td>-</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -552,22 +552,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topics</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -582,7 +582,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.8.0/reference-cli-tools/index.html b/content/docs/zh-CN/2.8.0/reference-cli-tools/index.html
index 43c396d..5633eda 100644
--- a/content/docs/zh-CN/2.8.0/reference-cli-tools/index.html
+++ b/content/docs/zh-CN/2.8.0/reference-cli-tools/index.html
@@ -324,11 +324,11 @@
<tr><td><code>--auth-params</code></td><td>认证参数，其格式取决于认证插件类中 <code>configure</code> 方法的实现，例如 "key1:val1,key2:val2" 或 "{"key1":"val1","key2":"val2"}"</td><td>{"saslJaasClientSectionName":"PulsarClient", "serverType":"broker"}</td></tr>
<tr><td><code>--auth-plugin</code></td><td>认证插件类名称</td><td>org.apache.pulsar.client.impl.auth.AuthenticationSasl</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
-<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol to select type of routing at proxy</td><td></td></tr>
-<tr><td><code>--proxy-url</code></td><td>Proxy-server URL to which to connect</td><td></td></tr>
+<tr><td><code>--proxy-protocol</code></td><td>Proxy protocol 选择代理路由类型</td><td></td></tr>
+<tr><td><code>--proxy-url</code></td><td>要连接的 Proxy server URL</td><td></td></tr>
<tr><td><code>--url</code></td><td>Broker URL to which to connect</td><td><a href="pulsar://localhost:6650/">pulsar://localhost:6650/</a> </br> <a href="ws://localhost:8080">ws://localhost:8080</a></td></tr>
<tr><td><code>-v</code>, <code>--version</code></td><td>获取Pulsar客户端版本</td><td></td></tr>
-<tr><td><code>-h</code>, <code>--help</code></td><td>Show this help</td><td></td></tr>
+<tr><td><code>-h</code>, <code>--help</code></td><td>显示帮助</td><td></td></tr>
</tbody>
</table>
<h3><a class="anchor" aria-hidden="true" id="produce"></a><a href="#produce" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
@@ -379,7 +379,7 @@
<tr><td><code>--hide-content</code></td><td>不要将消息打印到控制台。</td><td>false</td></tr>
<tr><td><code>-st</code>, <code>--schema-type</code></td><td>Set the schema type. Use <code>auto_consume</code> to dump AVRO and other structured data types. Possible values: bytes, auto_consume.</td><td>bytes</td></tr>
<tr><td><code>-ekv</code>, <code>--encryption-key-value</code></td><td>The URI of public key to encrypt payload. For example, <code>file:///path/to/public.key</code> or <code>data:application/x-pem-file;base64,*****</code>.</td><td></td></tr>
-<tr><td><code>-pm</code>, <code>--pool-messages</code></td><td>Use the pooled message.</td><td>true</td></tr>
+<tr><td><code>-pm</code>, <code>--pool-messages</code></td><td>使用池化消息</td><td>true</td></tr>
</tbody>
</table>
<h2><a class="anchor" aria-hidden="true" id="pulsar-daemon"></a><a href="#pulsar-daemon" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
@@ -453,32 +453,32 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
-<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>Auto ack for the oldest message in consumer's receiver queue if the queue full</td><td>false</td></tr>
+<tr><td><code>-ac</code>, <code>--auto_ack_chunk_q_full</code></td><td>如果队列已满，则自动确认消费者的接收队列中最早的消息。</td><td>false</td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--acks-delay-millis</code></td><td>确认分组延迟，以毫秒计</td><td>100</td></tr>
-<tr><td><code>--batch-index-ack</code></td><td>Enable or disable the batch index acknowledgment</td><td>false</td></tr>
-<tr><td><code>-bw</code>, <code>--busy-wait</code></td><td>Enable or disable Busy-Wait on the Pulsar client</td><td>false</td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the private key to decrypt payload</td><td></td></tr>
+<tr><td><code>--batch-index-ack</code></td><td>开启或禁用批量索引确认</td><td>false</td></tr>
+<tr><td><code>-bw</code>, <code>--busy-wait</code></td><td>在 Pulsar 客户端启用或禁用 Busy-Wait</td><td>false</td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含解密有效荷载的私钥的文件</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>The expiration time for incomplete chunk messages (in milliseconds)</td><td>0</td></tr>
+<tr><td><code>-e</code>, <code>--expire_time_incomplete_chunked_messages</code></td><td>不完整区块消息的到期时间 (毫秒)</td><td>0</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>Max pending chunk messages</td><td>0</td></tr>
-<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>Number of consumers (per topic)</td><td>1</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
-<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>Number of subscriptions (per topic)</td><td>1</td></tr>
+<tr><td><code>-mc</code>, <code>--max_chunked_msg</code></td><td>最大的待处理块消息。</td><td>0</td></tr>
+<tr><td><code>-n</code>, <code>--num-consumers</code></td><td>消费者数量（每个主题）</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
+<tr><td><code>-ns</code>, <code>--num-subscriptions</code></td><td>订阅数量 (每个主题)</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topics</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-pm</code>, <code>--pool-messages</code></td><td>Use the pooled message</td><td>true</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message consumer (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>Max total size of the receiver queue across partitions</td><td>50000</td></tr>
-<tr><td><code>--replicated</code></td><td>Whether the subscription status should be replicated</td><td>false</td></tr>
+<tr><td><code>-pm</code>, <code>--pool-messages</code></td><td>使用池化消息</td><td>true</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息消费者(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
+<tr><td><code>-p</code>, <code>--receiver-queue-size-across-partitions</code></td><td>分区接收队列的最大大小</td><td>50000</td></tr>
+<tr><td><code>--replicated</code></td><td>是否应该复制订阅状态</td><td>false</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled</td><td>0</td></tr>
-<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>Subscriber name prefix</td><td>sub</td></tr>
-<tr><td><code>-ss</code>, <code>--subscriptions</code></td><td>A list of subscriptions to consume on (e.g. sub1,sub2)</td><td>sub</td></tr>
+<tr><td><code>-s</code>, <code>--subscriber-name</code></td><td>订阅者名称前缀</td><td>sub</td></tr>
+<tr><td><code>-ss</code>, <code>--subscriptions</code></td><td>要消费的订阅列表（比如 sub1,sub2）</td><td>sub</td></tr>
<tr><td><code>-st</code>, <code>--subscription-type</code></td><td>Subscriber type. Possible values are Exclusive, Shared, Failover, Key_Shared.</td><td>Exclusive</td></tr>
<tr><td><code>-sp</code>, <code>--subscription-position</code></td><td>Subscriber position. Possible values are Latest, Earliest.</td><td>Latest</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages</td><td>0</td></tr>
@@ -499,45 +499,45 @@
<tbody>
<tr><td><code>-am</code>, <code>--access-mode</code></td><td>Producer access mode. Valid values are <code>Shared</code>, <code>Exclusive</code> and <code>WaitForExclusive</code></td><td>Shared（共享）</td></tr>
<tr><td><code>-au</code>, <code>--admin-url</code></td><td>Pulsar admin URL</td><td></td></tr>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>-b</code>, <code>--batch-time-window</code></td><td>Batch messages in a window of the specified number of milliseconds</td><td>1</td></tr>
-<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>Maximum number of bytes per batch</td><td>4194304</td></tr>
-<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>Maximum number of messages per batch</td><td>1000</td></tr>
-<tr><td><code>-bw</code>, <code>--busy-wait</code></td><td>Enable or disable Busy-Wait on the Pulsar client</td><td>false</td></tr>
-<tr><td><code>-ch</code>, <code>--chunking</code></td><td>Split the message and publish in chunks if the message size is larger than allowed max size</td><td>false</td></tr>
+<tr><td><code>-bb</code>, <code>--batch-max-bytes</code></td><td>每批的最大字节</td><td>4194304</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>每批的最大消息数</td><td>1000</td></tr>
+<tr><td><code>-bw</code>, <code>--busy-wait</code></td><td>在 Pulsar 客户端启用或禁用 Busy-Wait</td><td>false</td></tr>
+<tr><td><code>-bm</code>, <code>--batch-max-messages</code></td><td>如果消息超过允许的最大大小，则将消息分割并分块发布。</td><td>false</td></tr>
<tr><td><code>-d</code>, <code>--delay</code></td><td>给消息标记延迟时间（秒）</td><td>0s</td></tr>
<tr><td><code>-z</code>, <code>--compression</code></td><td>Compress messages’ payload. Possible values are NONE, LZ4, ZLIB, ZSTD or SNAPPY.</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
-<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>The public key name to encrypt payload</td><td></td></tr>
-<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>The file which contains the public key to encrypt payload</td><td></td></tr>
-<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>Exit from the process on publish failure</td><td>false</td></tr>
-<tr><td><code>-fc</code>, <code>--format-class</code></td><td>Custom Formatter class name</td><td>org.apache.pulsar.testclient.DefaultMessageFormatter</td></tr>
-<tr><td><code>-fp</code>, <code>--format-payload</code></td><td>Format %i as a message index in the stream from producer and/or %t as the timestamp nanoseconds</td><td>false</td></tr>
+<tr><td><code>-k</code>, <code>--encryption-key-name</code></td><td>加密有效载荷的公钥名称</td><td></td></tr>
+<tr><td><code>-v</code>, <code>--encryption-key-value-file</code></td><td>包含用于加密有效载荷的公钥文件</td><td></td></tr>
+<tr><td><code>-ef</code>, <code>--exit-on-failure</code></td><td>发布失败后退出进程</td><td>false</td></tr>
+<tr><td><code>-fc</code>, <code>--format-class</code></td><td>自定义 formatter 类名</td><td>org.apache.pulsar.testclient.DefaultMessageFormatter</td></tr>
+<tr><td><code>-fp</code>, <code>--format-payload</code></td><td>格式化为来自 producer 和/或流中的消息索引作为时间戳，单位为 nanoseconds</td><td>false</td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
<tr><td><code>-o</code>, <code>--max-outstanding</code></td><td>Max number of outstanding messages</td><td>1000</td></tr>
-<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>Max number of outstanding messages across partitions</td><td>50000</td></tr>
+<tr><td><code>-p</code>, <code>--max-outstanding-across-partitions</code></td><td>跨分区场景下的最大未处理消息数</td><td>50000</td></tr>
<tr><td><code>-mk</code>, <code>--message-key-generation-mode</code></td><td>The generation mode of message key. Valid options are <code>autoIncrement</code>, <code>random</code></td><td></td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-m</code>, <code>--num-messages</code></td><td>Number of messages to publish in total. If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>-n</code>, <code>--num-producers</code></td><td>The number of producers (per topic)</td><td>1</td></tr>
-<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>Number of test threads</td><td>1</td></tr>
+<tr><td><code>-threads</code>, <code>--num-test-threads</code></td><td>测试线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topic</code></td><td>The number of topics</td><td>1</td></tr>
<tr><td><code>-np</code>, <code>--partitions</code></td><td>Create partitioned topics with the given number of partitions. Setting this value to 0 means not trying to create a topic</td><td></td></tr>
-<tr><td><code>-f</code>, <code>--payload-file</code></td><td>Use payload from an UTF-8 encoded text file and a payload will be randomly selected when publishing messages</td><td></td></tr>
-<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>The delimiter used to split lines when using payload from a file</td><td>\n</td></tr>
-<tr><td><code>-pn</code>, <code>--producer-name</code></td><td>Producer Name</td><td></td></tr>
+<tr><td><code>-f</code>, <code>--payload-file</code></td><td>使用 UTF-8 编码的文本文件的有效载荷（payload），会在发布消息时随机选择一个有效载荷</td><td></td></tr>
+<tr><td><code>-e</code>, <code>--payload-delimiter</code></td><td>当使用来自文件的有效载荷（ payload）时，设置每行之间的分隔符</td><td>\n</td></tr>
+<tr><td><code>-pn</code>, <code>--producer-name</code></td><td>生产者名称</td><td></td></tr>
<tr><td><code>-r</code>, <code>--rate</code></td><td>Publish rate msg/s across topics</td><td>100</td></tr>
-<tr><td><code>--send-timeout</code></td><td>Set the sendTimeout</td><td>0</td></tr>
-<tr><td><code>--separator</code></td><td>Separator between the topic and topic number</td><td>-</td></tr>
+<tr><td><code>--send-timeout</code></td><td>设置发送超时时间</td><td>0</td></tr>
+<tr><td><code>--separator</code></td><td>Topic 和 topic 编号之间的分隔符</td><td>-</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-s</code>, <code>--size</code></td><td>Message size (in bytes)</td><td>1024</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps publishing messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--warmup-time</code></td><td>Warm-up time in seconds</td><td>1</td></tr>
+<tr><td><code>--warmup-time</code></td><td>预热时间（秒）</td><td>1</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -552,22 +552,22 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--listener-name</code></td><td>broker 监听器名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
<tr><td><code>-c</code>, <code>--max-connections</code></td><td>Max number of TCP connections to a single broker</td><td>100</td></tr>
-<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>Set the number of threads to be used for handling connections to brokers</td><td>1</td></tr>
+<tr><td><code>-ioThreads</code>, <code>--num-io-threads</code></td><td>设置用于处理 broker 连接的线程数</td><td>1</td></tr>
<tr><td><code>-t</code>, <code>--num-topics</code></td><td>The number of topics</td><td>1</td></tr>
-<tr><td><code>-r</code>, <code>--rate</code></td><td>Simulate a slow message reader (rate in msg/s)</td><td>0</td></tr>
-<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>Size of the receiver queue</td><td>1000</td></tr>
+<tr><td><code>-r</code>, <code>--rate</code></td><td>模拟一个慢速消息 reader(速率 消息/秒)</td><td>0</td></tr>
+<tr><td><code>-q</code>, <code>--receiver-queue-size</code></td><td>接收队列的大小</td><td>1000</td></tr>
<tr><td><code>-u</code>, <code>--service-url</code></td><td>Pulsar service URL</td><td></td></tr>
<tr><td><code>-m</code>, <code>--start-message-id</code></td><td>Start message id. This can be either 'earliest', 'latest' or a specific message id by using 'lid:eid'</td><td>earliest</td></tr>
<tr><td><code>-i</code>, <code>--stats-interval-seconds</code></td><td>Statistics interval seconds. If 0, statistics will be disabled.</td><td>0</td></tr>
<tr><td><code>-time</code>, <code>--test-duration</code></td><td>Test duration (in seconds). If the value is 0 or smaller than 0, it keeps consuming messages.</td><td>0</td></tr>
<tr><td><code>--trust-cert-file</code></td><td>Path for the trusted TLS certificate file</td><td></td></tr>
-<tr><td><code>--use-tls</code></td><td>Use TLS encryption on the connection</td><td>false</td></tr>
+<tr><td><code>--use-tls</code></td><td>在连接上使用 TLS 加密</td><td>false</td></tr>
<tr><td><code>--tls-allow-insecure</code></td><td>允许不安全的 TLS 连接。</td><td></td></tr>
</tbody>
</table>
@@ -582,7 +582,7 @@
<tr><th>参数</th><th>说明</th><th>默认值</th></tr>
</thead>
<tbody>
-<tr><td><code>--auth-params</code></td><td>Authentication parameters, whose format is determined by the implementation of method <code>configure</code> in authentication plugin class. For example, <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code>.</td><td></td></tr>
+<tr><td><code>--auth-params</code></td><td>认证参数，其格式由认证插件类中<code>configure</code>方法的实现决定。 例如， <code>key1:val1,key2:val2</code> or <code>{"key1":"val1","key2":"val2"}</code></td><td></td></tr>
<tr><td><code>--auth_plugin</code></td><td>认证插件类名称</td><td></td></tr>
<tr><td><code>--conf-file</code></td><td>Configuration file</td><td></td></tr>
<tr><td><code>-h</code>, <code>--help</code></td><td>帮助信息</td><td>false</td></tr>
diff --git a/content/docs/zh-CN/2.8.0/sql-deployment-configurations.html b/content/docs/zh-CN/2.8.0/sql-deployment-configurations.html
index 6571b19..d5bff23 100644
--- a/content/docs/zh-CN/2.8.0/sql-deployment-configurations.html
+++ b/content/docs/zh-CN/2.8.0/sql-deployment-configurations.html
@@ -191,7 +191,7 @@ Options:
<p>关于 Presto 部署的更多信息，请参阅 <a href="https://trino.io/docs/current/installation/deployment.html">Presto 部署</a>。</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.8.0/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.8.0/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/2.8.0/sql-deployment-configurations/index.html b/content/docs/zh-CN/2.8.0/sql-deployment-configurations/index.html
index 6571b19..d5bff23 100644
--- a/content/docs/zh-CN/2.8.0/sql-deployment-configurations/index.html
+++ b/content/docs/zh-CN/2.8.0/sql-deployment-configurations/index.html
@@ -191,7 +191,7 @@ Options:
<p>关于 Presto 部署的更多信息，请参阅 <a href="https://trino.io/docs/current/installation/deployment.html">Presto 部署</a>。</p>
<blockquote>
<p>Note<br>
-The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. You can enable periodically write LAC on the broker by setting "bookkeeperExplicitLacIntervalInMills" in the broker.conf.</p>
+The broker does not advance LAC, so when Pulsar SQL bypass broker to query data, it can only read entries up to the LAC that all the bookies learned. 你可以通过在 broker.conf 中设置 "bookkeeperExplicitLacIntervalInMills"，在 broker 上启用定期写入LAC。</p>
</blockquote>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.8.0/sql-getting-started"><span class="arrow-prev">← </span><span>查询数据</span></a><a class="docs-next button" href="/docs/zh-CN/2.8.0/sql-rest-api"><span>REST API</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#配置-presto-pulsar-连接器">配置 Presto Pulsar 连接器</a></li><li><a href="#从现有-presto-集群查询数据">从现有 Presto 集群查询数据</ [...]
const community = document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/concepts-messaging.html b/content/docs/zh-CN/concepts-messaging.html
index dd03f55..50caa2b 100644
--- a/content/docs/zh-CN/concepts-messaging.html
+++ b/content/docs/zh-CN/concepts-messaging.html
@@ -134,7 +134,7 @@ nettyMaxFrameSizeBytes=5253120
<blockquote>
<p><strong>Note</strong></p>
<p>Once an application creates a producer with the <code>Exclusive</code> or <code>WaitForExclusive</code> access mode successfully, the instance of the application is guaranteed to be the <strong>only one writer</strong> on the topic. Other producers trying to produce on this topic get errors immediately or have to wait until they get the <code>Exclusive</code> access.</p>
-<p>For more information, see <a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68: Exclusive Producer</a>.</p>
+<p>想了解更多信息，请参阅<a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68：Exclusive Producer</a>。</p>
</blockquote>
<p>You can set producer access mode through Java Client API. For more information, see <code>ProducerAccessMode</code> in <a href="https://github.com/apache/pulsar/blob/fc5768ca3bbf92815d142fe30e6bfad70a1b4fc6/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java">ProducerBuilder.java</a>.</p>
<h3><a class="anchor" aria-hidden="true" id="compression"></a><a href="#compression" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
@@ -193,7 +193,7 @@ nettyMaxFrameSizeBytes=5253120
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -287,7 +287,7 @@ Currently, dead letter topic is enabled In the shared and Key_Shared subscriptio
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -295,7 +295,7 @@ Currently, dead letter topic is enabled In the shared and Key_Shared subscriptio
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/concepts-messaging/index.html b/content/docs/zh-CN/concepts-messaging/index.html
index dd03f55..50caa2b 100644
--- a/content/docs/zh-CN/concepts-messaging/index.html
+++ b/content/docs/zh-CN/concepts-messaging/index.html
@@ -134,7 +134,7 @@ nettyMaxFrameSizeBytes=5253120
<blockquote>
<p><strong>Note</strong></p>
<p>Once an application creates a producer with the <code>Exclusive</code> or <code>WaitForExclusive</code> access mode successfully, the instance of the application is guaranteed to be the <strong>only one writer</strong> on the topic. Other producers trying to produce on this topic get errors immediately or have to wait until they get the <code>Exclusive</code> access.</p>
-<p>For more information, see <a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68: Exclusive Producer</a>.</p>
+<p>想了解更多信息，请参阅<a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68：Exclusive Producer</a>。</p>
</blockquote>
<p>You can set producer access mode through Java Client API. For more information, see <code>ProducerAccessMode</code> in <a href="https://github.com/apache/pulsar/blob/fc5768ca3bbf92815d142fe30e6bfad70a1b4fc6/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java">ProducerBuilder.java</a>.</p>
<h3><a class="anchor" aria-hidden="true" id="compression"></a><a href="#compression" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
@@ -193,7 +193,7 @@ nettyMaxFrameSizeBytes=5253120
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because this subscription type involves multiple consumers which have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -287,7 +287,7 @@ Currently, dead letter topic is enabled In the shared and Key_Shared subscriptio
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
@@ -295,7 +295,7 @@ Currently, dead letter topic is enabled In the shared and Key_Shared subscriptio
<p>In <em>exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
diff --git a/content/docs/zh-CN/deploy-bare-metal-multi-cluster.html b/content/docs/zh-CN/deploy-bare-metal-multi-cluster.html
index 89a7411..b1cfc73 100644
--- a/content/docs/zh-CN/deploy-bare-metal-multi-cluster.html
+++ b/content/docs/zh-CN/deploy-bare-metal-multi-cluster.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -128,7 +128,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/deploy-bare-metal-multi-cluster/index.html b/content/docs/zh-CN/deploy-bare-metal-multi-cluster/index.html
index 89a7411..b1cfc73 100644
--- a/content/docs/zh-CN/deploy-bare-metal-multi-cluster/index.html
+++ b/content/docs/zh-CN/deploy-bare-metal-multi-cluster/index.html
@@ -91,7 +91,7 @@
</ul>
<p>如果你想部署单个Pulsar 集群的实例，请看<a href="/docs/zh-CN/standalone#start-the-cluster">集群和broker</a>。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="本地或者-kubernetes-运行pulsar"></a><a href="#本地或者-kubernetes-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h4><a class="anchor" aria-hidden="true" id="在本地或kubernetes容器-运行pulsar"></a><a href="#在本地或kubernetes容器-运行pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c [...]
<p>本指南向您展示了如何在非Kubernetes中部署生产环境的 Pulsar 集群。 如果你想在单台机器部署单机的 Pulsar 集群，可以参考<a href="/docs/zh-CN/standalone">本地集群部署</a>指南。 如果你想在<a href="https://kubernetes.io">Kubernetes</a>运行 Pulsar，可以参考 <a href="/docs/zh-CN/deploy-kubernetes">Kubernetes 部署 Pulsar</a> 指南，指南包含了如何在 <a href="deploy-kubernetes#pulsar-on-google-kubernetes-engine">Google Kubernetes Engine</a> 和 <a href="deploy-kubernetes#pulsar-on-amazon-web-services">Amazon Web Services</a> 的 Kubernetes 环境运行Pulsar。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="系统配置要求"></a><a href="#系统配置要求" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
@@ -128,7 +128,7 @@ $ <span class="hljs-built_in">cd</span> apache-pulsar-2.8.1
<tr><td style="text-align:left"><code>conf</code></td><td style="text-align:left">Pulsar的配置文件，包含<a href="/docs/zh-CN/reference-configuration#broker">broker配置</a>,<a href="/docs/zh-CN/reference-configuration#zookeeper">ZooKeeper 配置</a> 等等</td></tr>
<tr><td style="text-align:left"><code>examples</code></td><td style="text-align:left">一个Java JAR包，包含 <a href="/docs/zh-CN/functions-overview">Pulsar Functions</a>的例子</td></tr>
<tr><td style="text-align:left"><code>lib</code></td><td style="text-align:left">Pulsar 使用的<a href="https://en.wikipedia.org/wiki/JAR_(file_format)"> JAR </a>文件</td></tr>
-<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left"><code>.txt</code>格式的开源许可文件，适用于Pulsar 代码库的各种组件</td></tr>
+<tr><td style="text-align:left"><code>licenses</code></td><td style="text-align:left">开源许可文件是<code>.txt</code>格式，适用于Pulsar 各种组件的代码库</td></tr>
</tbody>
</table>
<p>运行 Pulsar 会立即生成以下目录。</p>
diff --git a/content/docs/zh-CN/helm-install.html b/content/docs/zh-CN/helm-install.html
index f386d4a..7edbe30 100644
--- a/content/docs/zh-CN/helm-install.html
+++ b/content/docs/zh-CN/helm-install.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/helm-install/index.html b/content/docs/zh-CN/helm-install/index.html
index f386d4a..7edbe30 100644
--- a/content/docs/zh-CN/helm-install/index.html
+++ b/content/docs/zh-CN/helm-install/index.html
@@ -93,7 +93,7 @@
</blockquote>
<p>若要创建和连接到 Kubernetes 集群，请参考下面指南：</p>
<ul>
-<li><a href="/docs/zh-CN/helm-prepare#google-kubernetes-engine">Google Kubernetes Engine</a></li>
+<li><a href="/docs/zh-CN/helm-prepare#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a></li>
</ul>
<h2><a class="anchor" aria-hidden="true" id="部署-pulsar"></a><a href="#部署-pulsar" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>如果环境设置完成并生成了配置，就可以进行下一步，开始 <a href="/docs/zh-CN/helm-deploy">部署 Pulsar</a>。</p>
diff --git a/content/docs/zh-CN/helm-prepare.html b/content/docs/zh-CN/helm-prepare.html
index 5d1fb0e..69ec5e2 100644
--- a/content/docs/zh-CN/helm-prepare.html
+++ b/content/docs/zh-CN/helm-prepare.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a href=" [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a href="#脚本创建集群" [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/helm-prepare/index.html b/content/docs/zh-CN/helm-prepare/index.html
index 5d1fb0e..69ec5e2 100644
--- a/content/docs/zh-CN/helm-prepare/index.html
+++ b/content/docs/zh-CN/helm-prepare/index.html
@@ -76,7 +76,7 @@
});
</script></nav></div><div class="container mainContainer docsContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://crowdin.com/project/apache-pulsar/zh-CN" target="_blank" rel="noreferrer noopener">Translate</a><h1 id="__docusaurus" class="postHeaderTitle">Prepare Kubernetes resources</h1></header><article><div><span><p>对于获得功能齐全的Pulsar集群，在部署Apache Pulsar Helm chart之前，你需要准备一些资源。 下文提供了部署Pulsar Helm chart之前如何准备Kub [...]
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -86,10 +86,10 @@
</ul></li>
<li><a href="#next-steps">后续步骤</a></li>
</ul>
-<h2><a class="anchor" aria-hidden="true" id="google-kubernetes-engine"></a><a href="#google-kubernetes-engine" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
+<h2><a class="anchor" aria-hidden="true" id="谷歌-kubernetes-引擎gke"></a><a href="#谷歌-kubernetes-引擎gke" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.2 [...]
<p>为了更轻松地开始，提供了一个脚本来自动创建集群。 另外，也可以手动创建集群。</p>
<ul>
-<li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a>
+<li><a href="#google-kubernetes-engine">谷歌 Kubernetes 引擎（GKE）</a>
<ul>
<li><a href="#manual-cluster-creation">手动创建集群</a></li>
<li><a href="#scripted-cluster-creation">脚本创建集群</a>
@@ -118,7 +118,7 @@
<tr><th><strong>变量</strong></th><th><strong>说明</strong></th><th><strong>默认值</strong></th></tr>
</thead>
<tbody>
-<tr><td>PROJECT</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
+<tr><td>进程</td><td>你的GCP项目ID</td><td>没有默认值。 必须指定该变量。</td></tr>
<tr><td>CLUSTER_NAME</td><td>你的GKE集群名称</td><td><code>pulsar-dev</code></td></tr>
<tr><td>CONFDIR</td><td>保存Kubernetes配置的配置目录</td><td>${HOME}/.config/streamnative</td></tr>
<tr><td>INT_NETWORK</td><td>在集群内使用的IP空间</td><td><code>default</code></td></tr>
@@ -145,7 +145,7 @@
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="后续步骤"></a><a href="#后续步骤" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>一旦你的集群启动并运行，继续<a href="/docs/zh-CN/helm-deploy">安装Apache Pulsar Helm chart</a>。</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#google-kubernetes-engine">Google Kubernetes Engine</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a href=" [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/helm-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/helm-install"><span>安装</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#谷歌-kubernetes-引擎gke">谷歌 Kubernetes 引擎（GKE）</a><ul class="toc-headings"><li><a href="#手动创建集群">手动创建集群</a></li><li><a href="#脚本创建集群" [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/next/concepts-messaging.html b/content/docs/zh-CN/next/concepts-messaging.html
index b30cc74..a5456a4 100644
--- a/content/docs/zh-CN/next/concepts-messaging.html
+++ b/content/docs/zh-CN/next/concepts-messaging.html
@@ -131,10 +131,10 @@ nettyMaxFrameSizeBytes=5253120
<p>成功成为独家生产者的生产者被视为领导者。 因此，如果你打算为自己的应用实现领导者选举方案，你可以使用这种访问模式。</p>
<blockquote>
<p><strong>Note</strong></p>
-<p>Once an application creates a producer with <code>Exclusive</code> or <code>WaitForExclusive</code> access mode successfully, the instance of this application is guaranteed to be the <strong>only writer</strong> to the topic. Any other producers trying to produce messages on this topic will either get errors immediately or have to wait until they get the <code>Exclusive</code> access.</p>
-<p>For more information, see <a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68: Exclusive Producer</a>.</p>
+<p>一旦应用程序创建了一个 <code>Exclusive</code> 或 <code>WaitForExclusive</code> 的访问模式成功， 此应用程序将为该主题的 <strong>唯一写者</strong>。 任何其他生产者试图产生关于这个 topic 的消息，要么立即得到错误，要么一直等待，直到他们得到<code>Exclusive</code>访问权。</p>
+<p>想了解更多信息，请参阅<a href="https://github.com/apache/pulsar/wiki/PIP-68:-Exclusive-Producer">PIP 68：Exclusive Producer</a>。</p>
</blockquote>
-<p>You can set producer access mode through Java Client API. For more information, see <code>ProducerAccessMode</code> in <a href="https://github.com/apache/pulsar/blob/fc5768ca3bbf92815d142fe30e6bfad70a1b4fc6/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java">ProducerBuilder.java</a> file.</p>
+<p>You can set producer access mode through Java Client API. 更多信息，请参阅<a href="https://github.com/apache/pulsar/blob/fc5768ca3bbf92815d142fe30e6bfad70a1b4fc6/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java">ProducerBuilder.java</a>文件中的<code>ProducerAccessMode</code></p>
<h3><a class="anchor" aria-hidden="true" id="compression"></a><a href="#compression" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
<p>由 producer 发布的消息在传输过程中可以被压缩。 Pulsar 目前支持以下类型的压缩：</p>
<ul>
@@ -147,13 +147,13 @@ nettyMaxFrameSizeBytes=5253120
<p>当批量处理启用时，producer 会在单个请求中积累并发送一批消息。 批量处理的量大小由最大消息数和最大发布延迟定义。 因此，积压数量是分批处理的总数，而不是信息总数。</p>
<p>在 Pulsar 中，批次被跟踪并存储为单个单元，而不是单个消息。 Consumer 将批量处理的消息拆分成单个消息。 但即使启用了批量处理，也始终将计划中的消息(通过 <code>deliverAt</code> 或者 <code>deliverAfter</code> 进行配置) 作为单个消息发送。</p>
<p>一般来说，当 consumer 确认了一个批的所有消息，该批才会被认定为确认。 这意味着当 <strong>不是所有</strong> 批处理消息都被承认时，那时出现了意外的故障， 否定的确认或确认超时可能导致这批邮件的重送。</p>
-<p>To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar introduces batch index acknowledgement since Pulsar 2.6.0. When batch index acknowledgement is enabled, the consumer filters out the batch index that has been acknowledged and sends the batch index acknowledgement request to the broker. Broker 维护批量索引的确认状态并跟踪每批索引的确认状态，以避免向 consumer 发送已确认的消息。 The batch is deleted when all indices of the messages in it are acknowledged.</p>
+<p>为了避免批量的向 consumer 重发已确认的消息，Pulsar 从 Pulsar 2.6.0 开始采用批量索引确认机制。如果启用批量索引确认机制，consumer 将筛选出已被确认的批量索引，并将批量索引确认请求发送给 broker。 Broker 维护批量索引的确认状态并跟踪每批索引的确认状态，以避免向 consumer 发送已确认的消息。 当该批信息的所有索引都被确认后，该批信息将被删除。</p>
<p>By default, batch index acknowledgement is disabled (<code>acknowledgmentAtBatchIndexLevelEnabled=false</code>). You can enable batch index acknowledgement by setting the <code>acknowledgmentAtBatchIndexLevelEnabled</code> parameter to <code>true</code> at the broker side. 启用批量索引确认将会导致更多内存开销。</p>
<h3><a class="anchor" aria-hidden="true" id="分块"></a><a href="#分块" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c [...]
-<p>当你想要启用分块(chunking) 时，请阅读以下说明。 - 不能同时启动批量处理和分块(chunking) 。 如果想要启用分块(chunking) ，您必须提前禁用批量处理。 - 只对持久主题(persisted topics) 支持分块(chunking) 。 - Chunking is only supported for Exclusive and Failover subscription types.</p>
+<p>当你想要启用分块(chunking) 时，请阅读以下说明。 - 不能同时启动批量处理和分块(chunking) 。 如果想要启用分块(chunking) ，您必须提前禁用批量处理。 - 只对持久主题(persisted topics) 支持分块(chunking) 。 - 仅独占 ( Exclusive) 和故障转移 ( Failover) 订阅模式支持分块 (chunking) 。</p>
<p>当启用分块(chunking) 时(<code>chunkingEnabled=true</code>) ，如果消息大小大于允许的最大发布有效载荷大小，则 producer 将原始消息分割成分块的消息，并将它们与块状的元数据一起单独和按顺序发布到 broker。 在 broker 中，分块的消息将和普通的消息以相同的方式存储在 Managed Ledger 上。 唯一的区别是，consumer 需要缓冲分块消息，并在收集完所有分块消息后将其合并成真正的消息。 Managed Ledger 上的分块消息可以和普通消息交织在一起。 如果 producer 未能发布消息的所有分块，则当 consumer 未能在过期时间(expire time) 内接收所有分块时，consumer 可以过期未完成的分块。 默认情况下，过期时间设置为1小时。</p>
<p>Consumer 会缓存收到的块状消息，直到收到消息的所有分块为止。 然后 consumer 将分块的消息拼接在一起，并将它们放入接收器队列中。 客户端从接收器队列中消费消息。 一旦 consumer 使用整个大消息并确认，consumer 就会在内部发送与该大消息关联的所有分块消息的确认。 You can set the <code>maxPendingChunkedMessage</code> parameter on the consumer. 当达到阈值时，consumer 通过静默确认未分块的消息或通过将其标记为未确认，要求 broker 稍后重新发送这些消息。</p>
-<p>The broker does not require any changes to support chunking for non-shared subscription. The broker only uses <code>chunkedMessageRate</code> to record chunked message rate on the topic.</p>
+<p>Broker 不需要进行任何更改以支持非共享订阅的分块。 Broker 只使用 <code>chuckedMessageRate</code> 记录主题上的分块消息速率。</p>
<h4><a class="anchor" aria-hidden="true" id="处理一个-producer-和一个订阅-consumer-的分块消息"></a><a href="#处理一个-producer-和一个订阅-consumer-的分块消息" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5 [...]
<p>如下图所示，当生产者向主题发送一批大的分块消息和普通的非分块消息时。 假设生产者发送的消息为 M1，M1 有三个分块 M1-C1，M1-C2 和 M1-C3。 这个 broker 在其管理的ledger里面保存所有的三个块消息，然后以相同的顺序分发给消费者（独占/灾备模式）。 消费者将在内存缓存所有的块消息，直到收到所有的消息块。将这些消息合并成为原始的消息M1，发送给处理进程。</p>
<p><img src="/docs/assets/chunking-01.png" alt=""></p>
@@ -178,53 +178,53 @@ nettyMaxFrameSizeBytes=5253120
<p>Client libraries provide listener implementation for consumers. For example, the <a href="/docs/zh-CN/next/client-libraries-java">Java client</a> provides a <a href="https://pulsar.incubator.apache.org/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageListener">MesssageListener</a>
interface. 在这个接口中，一旦接受到新的消息，<code>received</code>方法将被调用。</p>
<h3><a class="anchor" aria-hidden="true" id="确认"></a><a href="#确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c [...]
-<p>The consumer sends an acknowledgement request to the broker after it consumes a message successfully. Then, this consumed message will be permanently stored, and be deleted only after all the subscriptions have acknowledged it. If you want to store the messages that have been acknowledged by a consumer, you need to configure the <a href="/docs/zh-CN/next/concepts-messaging#message-retention-and-expiry">message retention policy</a>.</p>
-<p>For batch messages, you can enable batch index acknowledgement to avoid dispatching acknowledged messages to the consumer. For details about batch index acknowledgement, see <a href="#batching">batching</a>.</p>
-<p>Messages can be acknowledged in one of the following two ways:</p>
+<p>消费者在成功消费一个消息后，向 Broker 发送一个确认请求。 然后，这条被消费的消息将被永久保存，只有在所有订阅者都确认后才会被删除。 如果希望消息被消费者确认后仍然保留下来，可配置 <a href="/docs/zh-CN/next/concepts-messaging#message-retention-and-expiry">消息保留策略</a>实现。</p>
+<p>对于批处理消息，你可以启用批处理索引确认，以避免将确认的消息分派给消费者。 关于批量索引确认的细节，请参见<a href="#batching">batching</a>。</p>
+<p>消息可以通过以下两种方式之一进行确认。</p>
<ul>
-<li>Being acknowledged individually. With individual acknowledgement, the consumer acknowledges each message and sends an acknowledgement request to the broker.</li>
-<li>Being acknowledged cumulatively. With cumulative acknowledgement, the consumer <strong>only</strong> acknowledges the last message it received. All messages in the stream up to (and including) the provided message are not redelivered to that consumer.</li>
+<li>被单独确认。在单独确认的情况下，消费者确认每个消息，并向 Broker 发送确认请求。</li>
+<li>累积确认模式 在累积确认中，消费者<strong>只</strong>确认它收到的最后一条消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
-<p>If you want to acknowledge messages individually, you can use the following API.</p>
+<p>如果你想单独确认消息，你可以使用以下API。</p>
<pre><code class="hljs css language-java">consumer.acknowledge(msg);
</code></pre>
-<p>If you want to acknowledge messages cumulatively, you can use the following API.</p>
+<p>如果你想累计确认消息，你可以使用以下API。</p>
<pre><code class="hljs css language-java">consumer.acknowledgeCumulative(msg);
</code></pre>
<blockquote>
-<p><strong>Note</strong> <br>
-Cumulative acknowledgement cannot be used in <a href="#subscription-types">Shared subscription type</a>, because Shared subscription type involves multiple consumers which have access to the same subscription. In Shared subscription type, messages are acknowledged individually.</p>
+<p><strong>注意事项</strong> <br>
+累积确认不能用于<a href="#subscription-types"> Shared subscription 类型</a>，因为Shared subscription 类型涉及多个消费者，他们可以访问同一个订阅。 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>When a consumer fails to consume a message and intends to consume it again, this consumer should send a negative acknowledgement to the broker. Then, the broker will redeliver this message to the consumer.</p>
-<p>Messages are negatively acknowledged individually or cumulatively, depending on the consumption subscription type.</p>
-<p>In Exclusive and Failover subscription types, consumers only negatively acknowledge the last message they receive.</p>
-<p>In Shared and Key_Shared subscription types, consumers can negatively acknowledge messages individually.</p>
-<p>Be aware that negative acknowledgments on ordered subscription types, such as Exclusive, Failover and Key_Shared, might cause failed messages being sent to consumers out of the original order.</p>
-<p>If you want to acknowledge messages negatively, you can use the following API.</p>
-<pre><code class="hljs css language-java"><span class="hljs-comment">//With calling this api, messages are negatively acknowledged </span>
+<p>当一个消费者未能消费一个消息并打算再次消费它时，这个消费者应该向 Broker 发送一个否定的确认。 然后，Broker 将把这个消息重新传递给消费者。</p>
+<p>消息取消确认也有单条取消模式和累积取消模式 ，这依赖于消费者使用的订阅模式。</p>
+<p>在 Exclusive 模式和 Failover 订阅模式中，消费者仅仅只能对收到的最后一条消息进行取消确认。</p>
+<p>在 Shared 和 Key_Shared 的订阅类型中，消费者可以单独否定确认消息。</p>
+<p>请注意，订单订阅类型为否定， 比如Exclusive，Failover和Key_Shared之类的消息可能会导致发送失败的消息以不符合原始顺序的方式到达使用者。</p>
+<p>如果你想否定地确认信息，你可以使用以下API。</p>
+<pre><code class="hljs css language-java"><span class="hljs-comment">//调用这个api，消息会被否定地确认。</span>
consumer.negativeAcknowledge(msg);
</code></pre>
<blockquote>
-<p><strong>Note</strong> <br>
-If batching is enabled, all messages in one batch are redelivered to the consumer.</p>
+<p><strong>注意事项</strong> <br>
+如果启用了批处理，一个批处理中的所有邮件都会重新交付给消费者。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-redelivery-backoff"></a><a href="#negative-redelivery-backoff" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 1 [...]
-<p>In general, consumers are not able to process messages successfully. In this case, you can use <a href="/docs/zh-CN/next/concepts-messaging#negative-acknowledgement">negative acknowledgement</a> and redeliver the messages after processing message failures, so that the messages can be redelivered to other consumers (for the Shared subscription).</p>
-<p>But this is not flexible enough. A better way is to use the <strong>redelivery backoff mechanism</strong>. You can redeliver messages with different delays by setting the number of times the messages is retried.</p>
-<p>If you want to use <code>Negative Redelivery Backoff</code>, you can use the following API.</p>
+<p>通常，消费者无法成功处理消息。 在这种情况下，你可以使用<a href="/docs/zh-CN/next/concepts-messaging#negative-acknowledgement">negative acknowledgement</a>，并在处理消息失败后重新交付消息，这样就可以将消息重新交付给其他消费者（对于共享订阅）。</p>
+<p>但这还不够灵活。 一个更好的方法是使用** redelivery backoff 机制**。 你可以通过设置消息重试的次数，以不同的延迟来重发消息。</p>
+<p>如果你想使用<code>Negative Redelivery Backoff</code>，你可以使用以下API。</p>
<pre><code class="hljs css language-java">consumer.negativeAckRedeliveryBackoff(NegativeAckRedeliveryExponentialBackoff.builder()
.minNackTimeMs(<span class="hljs-number">1000</span>)
.maxNackTimeMs(<span class="hljs-number">60</span> * <span class="hljs-number">1000</span>)
.build())
</code></pre>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>If a message is not consumed successfully, and you want the broker to redeliver this message automatically, then you can enable automatic redelivery mechanism for unacknowledged messages. With automatic redelivery enabled, the client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
+<p>如果一个消息没有被成功消费，而你想让 Broker 自动重新交付这个消息，那么你可以为未被认可的消息启用自动重新交付机制。 在启用自动重新交付的情况下，客户端跟踪整个<code>acktimeout</code>时间范围内的未确认的消息，并在指定确认超时时向代理发送<code>重新交付未确认的消息</code>请求。</p>
<blockquote>
-<p><strong>Note</strong></p>
+<p><strong>注意事项</strong></p>
<ul>
-<li>If batching is enabled, all messages in one batch are redelivered to the consumer.</li>
-<li>The negative acknowledgement is preferable over the acknowledgement timeout, since negative acknowledgement controls the redelivery of individual messages more precisely and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</li>
+<li>如果启用了批处理，一个批次中的所有消息都会被重新交付给消费者。</li>
+<li>与 acknowledgement timeout 相比，negative acknowledgement 更可取，因为negative acknowledgement 能更精确地控制单个消息的再交付，并避免在消息处理时间超过确认超时时出现无效的再交付。</li>
</ul>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -255,14 +255,14 @@ If batching is enabled, all messages in one batch are redelivered to the consume
.subscribe();
</code></pre>
-<p>Dead letter topic depends on message redelivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
+<p>死信主题依赖消息重试 Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p><strong>Note</strong> <br>
-Currently, dead letter topic is enabled in Shared and Key_Shared subscription types.</p>
+<p><strong>注意事项</strong> <br>
+目前，死信主题在 Shared 和Key_Stared 的订阅类型中是启用的。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>很多在线的业务系统，由于业务逻辑处理出现异常，消息一般需要被重新消费。 若需要允许延时重新消费失败的消息，你可以配置生产者同时发送消息到业务主题和重试主题，并允许消费者自动重试消费。 配置了允许消费者自动重试。如果消息没有被消费成功，它将被保存到重试主题当中。并在指定延时时间后，自动重新消费重试主题里面的消费失败消息。</p>
-<p>By default, automatic retry is disabled. You can set <code>enableRetry</code> to <code>true</code> to enable automatic retry on the consumer.</p>
+<p>默认情况下，自动重试是被禁止的，你能够设置<code>enableRetry</code>为<code>true</code>去启用消费者自动重试。</p>
<p>如下例子所示，消费者会从重试主题消费消息。</p>
<pre><code class="hljs css language-java">Consumer<<span class="hljs-keyword">byte</span>[]> consumer = pulsarClient.newConsumer(Schema.BYTES)
.topic(topic)
@@ -277,11 +277,11 @@ Currently, dead letter topic is enabled in Shared and Key_Shared subscription ty
.subscriptionInitialPosition(SubscriptionInitialPosition.Earliest)
.subscribe();
</code></pre>
-<p>If you want to put messages into a retrial queue, you can use the following API.</p>
+<p>如果您想要将消息放入重试队列，您可以使用以下API。</p>
<pre><code class="hljs css language-java">consumer.reconsumeLater(msg,<span class="hljs-number">3</span>,TimeUnit.SECONDS);
</code></pre>
<h2><a class="anchor" aria-hidden="true" id="topic"></a><a href="#topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09 [...]
-<p>As in other pub-sub systems, topics in Pulsar are named channels for transmitting messages from producers to consumers. Topic names are URLs that have a well-defined structure:</p>
+<p>像其他的发布-订阅系统一样，主题是 Pulsar 在生产者和消费者当中传输消息的命名通道。主题名字是URL的形式，结构如下所示：</p>
<pre><code class="hljs css language-http">{persistent|non-persistent}://tenant/namespace/topic
</code></pre>
<table>
@@ -296,8 +296,8 @@ Currently, dead letter topic is enabled in Shared and Key_Shared subscription ty
</tbody>
</table>
<blockquote>
-<p><strong>No need to explicitly create new topics</strong> <br>
-You do not need to explicitly create topics in Pulsar. 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic [...]
+<p>**不需要明确地创建新 topic **<br>
+。 你不需要在 Pulsar 中明确地创建 topic 。 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code> [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 可以通过<a href="/docs/zh-CN/next/admin-api-namespaces#create">admin API</a>在租户下创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -305,16 +305,16 @@ You do not need to explicitly create topics in Pulsar. 如果客户端尝试从
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Four subscription types are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These types are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-types.png" alt="Subscription types"></p>
<blockquote>
-<p><strong>Pub-Sub or Queuing</strong> <br>
-In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， It is exclusive subscription type. 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 * If you want to achieve both effects simultaneously, combine exclusive subscription type with other subscription types for consumers.</p>
+<p><strong>Pub-Sub or Queuing</strong></p>
+<p>在Pulsar中，你可以灵活地使用不同的订阅模式。 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-types"></a><a href="#consumerless-subscriptions-and-their-corresponding-types" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription type is undefined. The type of a subscription is defined when a consumer connects to it, and the type can be changed by restarting all consumers with a different configuration.</p>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
-<p>In <em>Exclusive</em> type, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
+<p>在* Exclusive *当中，只允许订阅当中存在一个消费者，如果多个消费者使用同一个订阅名称去订阅同一个topic，则会报错。</p>
<p>In the diagram below, only <strong>Consumer A-0</strong> is allowed to consume messages.</p>
<blockquote>
-<p>Exclusive is the default subscription type.</p>
+<p>Exclusive模式为默认订阅模式。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-exclusive-subscriptions.png" alt="独占订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="failover灾备"></a><a href="#failover灾备" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -324,26 +324,28 @@ In Pulsar, you can use different subscriptions flexibly. 如果你想在消费
<p>In the diagram below, <strong>Consumer-B-0</strong> is the master consumer while <strong>Consumer-B-1</strong> would be the next consumer in line to receive messages if <strong>Consumer-B-0</strong> is disconnected.</p>
<p><img src="/docs/assets/pulsar-failover-subscriptions.png" alt="灾备订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="shared共享"></a><a href="#shared共享" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
-<p>In <em>shared</em> or <em>round robin</em> type, multiple consumers can attach to the same subscription. 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
+<p><em>shared</em>或者<em>round robin</em>模式中，多个消费者可以绑定到同一个订阅上。 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<p><strong>Limitations of Shared type</strong> <br>
-When using Shared type, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with Shared type.</p>
+<p><strong>Shared 类型的局限性</strong></p>
+<p>当使用 Shared 类型时，要注意以下几点。 * 不保证消息排序。 * 你不能用Shared类型来使用累积确认。</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
-<p>In <em>Key_Shared</em> type, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
+<ul>
+<li>Key_Shared *模式中，多个consumer可以绑定到同一个subscription。 Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</li>
+</ul>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
-<p>Note that when the consumers are using the Key_Shared subscription type, you need to <strong>disable batching</strong> or <strong>use key-based batching</strong> for the producers. There are two reasons why the key-based batching is necessary for Key_Shared subscription type: 1. The broker dispatches messages according to the keys of the messages, but the default batching approach might fail to pack the messages with the same key to the same batch. 2. Since it is the consumers instead [...]
-<p>The key-based batching aims at resolving the above-mentioned issues. This batching method ensures that the producers pack the messages with the same key to the same batch. The messages without a key are packed into one batch and this batch has no key. When the broker dispatches messages from this batch, it uses <code>NON_KEY</code> as the key. In addition, each consumer is associated with <strong>only one</strong> key and should receive <strong>only one message batch</strong> for the [...]
-<p>Below are examples of enabling the key-based batching under the Key_Shared subscription type, with <code>client</code> being the Pulsar client that you created.</p>
+<p>请注意，当消费者使用Key_Shared订阅类型时，你需要<strong>禁用批处理</strong>或<strong>对生产者使用基于密钥的批处理</strong>。 对于Key_Shared订阅类型，基于密钥的批处理是必要的，有两个原因。 1. Broker 根据消息的键值来分配消息，但默认的批处理方式可能无法将具有相同键值的消息打包到同一批次。 2. 由于是消费者而不是 Broker 从批次中调度消息，一个批次中第一个消息的密钥被认为是这个批次中所有消息的密钥，从而导致了上下文错误。</p>
+<p>基于密钥的批处理旨在解决上述问题。 这种批处理方法确保生产者将具有相同密钥的消息打包到同一批次。 没有密钥的信息被打包成一个批次，这个批次没有钥匙。 当 Broker 从这个批处理消息时，它使用<code>NON_KEY</code>作为密钥。 此外，每个消费者与<strong>只有一个</strong>密钥相关联，并且应该为所连接的密钥接收<strong>只有一批消息</strong>。 默认情况下，你可以通过配置生产者被允许发送的消息数量来限制批处理。</p>
+<p>下面是在Key_Shared订阅类型下启用基于密钥的批处理的例子，<code>client</code>是您创建的Pulsar客户端。</p>
<div class="tabs"><div class="nav-tabs"><div id="tab-group-2384-tab-2385" class="nav-link active" data-group="group_2384" data-tab="tab-group-2384-content-2385">Java</div><div id="tab-group-2384-tab-2386" class="nav-link" data-group="group_2384" data-tab="tab-group-2384-content-2386">C++</div><div id="tab-group-2384-tab-2387" class="nav-link" data-group="group_2384" data-tab="tab-group-2384-content-2387">Python</div></div><div class="tab-content"><div id="tab-group-2384-content-2385" cla [...]
</span></div></div><div id="tab-group-2384-content-2386" class="tab-pane" data-group="group_2384" tabindex="-1"><div><span><pre><code class="hljs">ProducerConfiguration producerConfig;<br />producerConfig.setBatchingType(ProducerConfiguration::BatchingType::KeyBasedBatching);<br />Producer producer;<br />client.createProducer("my-topic", producerConfig, producer);<br /></code></pre>
</span></div></div><div id="tab-group-2384-content-2387" class="tab-pane" data-group="group_2384" tabindex="-1"><div><span><pre><code class="hljs">producer = client.create_producer(topic='my-topic', batching_type=pulsar.BatchingType.KeyBased)<br /></code></pre>
</span></div></div></div></div>
<blockquote>
-<p><strong>Limitations of Key_Shared type</strong> <br>
-When you use Key_Shared type, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared type.</p>
+<p><strong>Key_Shared类型的局限性</strong></p>
+<p>当你使用Key_Shared类型时，要注意以下几点。 * 你需要为消息指定一个密钥或顺序密钥。 * 你不能为Key_Shared类型使用累积确认。</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="多主题订阅"></a><a href="#多主题订阅" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09 [...]
<p>当consumer订阅pulsar的主题时，它默认指定订阅了一个主题，例如：<code>persistent://public/default/my-topic</code>。 从Pulsar的1.23.0-incubating的版本开始，Pulsar消费者可以同时订阅多个topic。 你可以用以下两种方式定义topic的列表：</p>
@@ -356,8 +358,8 @@ When you use Key_Shared type, be aware that: * You need to specify a key or orde
</blockquote>
<p>当订阅多个主题的时候，Pulsar 客户端将自动调用 Pulsar API 找到符合匹配规则的主题列表，然后订阅这些主题。 如果此时有暂不存在的主题，那么一旦这些主题被创建，消费者会自动订阅这些主题。</p>
<blockquote>
-<p><strong>No ordering guarantees across multiple topics</strong> <br>
-When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>在多主题之间没有顺序保证</strong></p>
+<p>当生产者向一个主题发送消息时，所有的消息都被保证以相同的顺序从该主题读取。 However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>如下是 Java 订阅多个主题的代码示例：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -383,13 +385,13 @@ Consumer<<span class="hljs-keyword">byte</span>[]> someTopicsConsumer = pu
</code></pre>
... 23565 lines suppressed ...