You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/02/11 02:47:19 UTC
[pulsar-site] branch main updated (33046a1 -> 84ea62b)
This is an automated email from the ASF dual-hosted git repository.
urfree pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git.
from 33046a1 update
new 822fc08 update
new f512951 update
new 84ea62b update
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
site2/tools/sync-docs.sh | 2 ++
site2/website/package.json | 3 ++-
site2/website/scripts/crowdin-cli.jar | Bin 0 -> 11676600 bytes
.../version-2.5.0/administration-pulsar-manager.md | 2 +-
.../version-2.6.0/administration-pulsar-manager.md | 2 +-
.../version-2.6.1/administration-pulsar-manager.md | 2 +-
.../version-2.6.1/concepts-messaging.md | 2 +-
.../version-2.6.2/administration-pulsar-manager.md | 2 +-
.../version-2.6.2/concepts-messaging.md | 2 +-
.../version-2.6.3/administration-pulsar-manager.md | 2 +-
.../version-2.6.3/concepts-messaging.md | 2 +-
.../version-2.6.4/administration-pulsar-manager.md | 2 +-
.../version-2.6.4/concepts-messaging.md | 2 +-
.../version-2.6.4/tiered-storage-azure.md | 1 -
.../version-2.7.0/administration-pulsar-manager.md | 2 +-
.../version-2.7.0/concepts-messaging.md | 2 +-
.../version-2.7.0/tiered-storage-azure.md | 1 -
.../version-2.7.1/administration-pulsar-manager.md | 2 +-
.../version-2.7.1/concepts-messaging.md | 2 +-
.../version-2.7.1/tiered-storage-azure.md | 1 -
.../version-2.7.2/administration-pulsar-manager.md | 2 +-
.../version-2.7.2/concepts-messaging.md | 2 +-
.../version-2.7.2/tiered-storage-azure.md | 1 -
.../version-2.7.3/administration-pulsar-manager.md | 2 +-
.../version-2.7.3/concepts-messaging.md | 2 +-
.../version-2.7.3/tiered-storage-azure.md | 1 -
.../version-2.7.4/administration-pulsar-manager.md | 2 +-
.../version-2.7.4/concepts-messaging.md | 2 +-
.../version-2.7.4/tiered-storage-azure.md | 1 -
.../version-2.8.0/administration-pulsar-manager.md | 2 +-
.../version-2.8.0/concepts-messaging.md | 2 +-
.../version-2.8.0/tiered-storage-azure.md | 1 -
.../version-2.8.1/administration-pulsar-manager.md | 2 +-
.../version-2.8.1/concepts-messaging.md | 2 +-
.../version-2.8.1/tiered-storage-azure.md | 1 -
.../version-2.8.2/administration-pulsar-manager.md | 2 +-
.../version-2.8.2/concepts-messaging.md | 2 +-
.../version-2.8.2/tiered-storage-azure.md | 1 -
.../version-2.9.0/administration-pulsar-manager.md | 2 +-
.../version-2.9.0/concepts-messaging.md | 2 +-
.../version-2.9.0/tiered-storage-azure.md | 1 -
.../version-2.9.1/administration-pulsar-manager.md | 2 +-
.../version-2.9.1/concepts-messaging.md | 2 +-
.../version-2.9.1/tiered-storage-azure.md | 1 -
44 files changed, 34 insertions(+), 42 deletions(-)
create mode 100755 site2/tools/sync-docs.sh
create mode 100644 site2/website/scripts/crowdin-cli.jar
[pulsar-site] 01/03: update
Posted by ur...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
commit 822fc08f3aa498a606d1f71f9f7f13d31e20469d
Author: LiLi <ur...@apache.org>
AuthorDate: Fri Feb 11 10:36:52 2022 +0800
update
Signed-off-by: LiLi <ur...@apache.org>
---
site2/website/package.json | 3 ++-
site2/website/scripts/crowdin-cli.jar | Bin 0 -> 11676600 bytes
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/site2/website/package.json b/site2/website/package.json
index d22e8a5..27104bb 100644
--- a/site2/website/package.json
+++ b/site2/website/package.json
@@ -9,7 +9,8 @@
"rename-version": "docusaurus-rename-version",
"test": "jest --detectOpenHandles",
"crowdin-upload": "crowdin --config ../crowdin.yaml upload sources --auto-update -b master",
- "crowdin-download": "crowdin --config ../crowdin.yaml download -b master"
+ "crowdin-download": "crowdin --config ../crowdin.yaml download -b master",
+ "crowdin-test": "java -jar ./scripts/crowdin-cli.jar --config ../crowdin.yaml download -b master"
},
"devDependencies": {
"axios": "^0.18.0",
diff --git a/site2/website/scripts/crowdin-cli.jar b/site2/website/scripts/crowdin-cli.jar
new file mode 100644
index 0000000..dd3a47f
Binary files /dev/null and b/site2/website/scripts/crowdin-cli.jar differ
[pulsar-site] 02/03: update
Posted by ur...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
commit f51295176e5cc0e0b772bf0bf5984e3742d56759
Author: LiLi <ur...@apache.org>
AuthorDate: Fri Feb 11 10:42:23 2022 +0800
update
Signed-off-by: LiLi <ur...@apache.org>
---
.../versioned_docs/version-2.5.0/administration-pulsar-manager.md | 2 +-
.../versioned_docs/version-2.6.0/administration-pulsar-manager.md | 2 +-
.../versioned_docs/version-2.6.1/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.6.1/concepts-messaging.md | 2 +-
.../versioned_docs/version-2.6.2/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.6.2/concepts-messaging.md | 2 +-
.../versioned_docs/version-2.6.3/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.6.3/concepts-messaging.md | 2 +-
.../versioned_docs/version-2.6.4/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.6.4/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.6.4/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.7.0/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.7.0/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.7.0/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.7.1/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.7.1/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.7.1/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.7.2/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.7.2/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.7.2/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.7.3/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.7.3/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.7.3/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.7.4/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.7.4/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.7.4/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.8.0/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.8.0/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.8.0/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.8.1/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.8.1/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.8.1/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.8.2/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.8.2/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.8.2/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.9.0/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.9.0/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.9.0/tiered-storage-azure.md | 1 -
.../versioned_docs/version-2.9.1/administration-pulsar-manager.md | 2 +-
site2/website/versioned_docs/version-2.9.1/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.9.1/tiered-storage-azure.md | 1 -
41 files changed, 30 insertions(+), 41 deletions(-)
diff --git a/site2/website/versioned_docs/version-2.5.0/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.5.0/administration-pulsar-manager.md
index 4497ef7..339b641 100644
--- a/site2/website/versioned_docs/version-2.5.0/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.5.0/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.6.0/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.6.0/administration-pulsar-manager.md
index 90399d8..f2e410b 100644
--- a/site2/website/versioned_docs/version-2.6.0/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.6.0/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.6.1/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.6.1/administration-pulsar-manager.md
index 2cc16a8..b83642f 100644
--- a/site2/website/versioned_docs/version-2.6.1/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.6.1/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.6.1/concepts-messaging.md b/site2/website/versioned_docs/version-2.6.1/concepts-messaging.md
index 74bb323..90fa982 100644
--- a/site2/website/versioned_docs/version-2.6.1/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.1/concepts-messaging.md
@@ -66,7 +66,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChuckedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.6.2/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.6.2/administration-pulsar-manager.md
index 5bc3741..1e7ac5d 100644
--- a/site2/website/versioned_docs/version-2.6.2/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.6.2/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.6.2/concepts-messaging.md b/site2/website/versioned_docs/version-2.6.2/concepts-messaging.md
index c733115..ab39a85 100644
--- a/site2/website/versioned_docs/version-2.6.2/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.2/concepts-messaging.md
@@ -66,7 +66,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChuckedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.6.3/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.6.3/administration-pulsar-manager.md
index a3246de..6fa77e0 100644
--- a/site2/website/versioned_docs/version-2.6.3/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.6.3/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.6.3/concepts-messaging.md b/site2/website/versioned_docs/version-2.6.3/concepts-messaging.md
index 20404c9..4cc7213 100644
--- a/site2/website/versioned_docs/version-2.6.3/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.3/concepts-messaging.md
@@ -66,7 +66,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChuckedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.6.4/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.6.4/administration-pulsar-manager.md
index 50ea7db..ddcc34f 100644
--- a/site2/website/versioned_docs/version-2.6.4/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.6.4/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.6.4/concepts-messaging.md b/site2/website/versioned_docs/version-2.6.4/concepts-messaging.md
index 91c8874..8b26fc2 100644
--- a/site2/website/versioned_docs/version-2.6.4/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.4/concepts-messaging.md
@@ -66,7 +66,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChuckedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.6.4/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.6.4/tiered-storage-azure.md
index 9398661..51c1abe 100644
--- a/site2/website/versioned_docs/version-2.6.4/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.6.4/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.7.0/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.7.0/administration-pulsar-manager.md
index f93373c..0ab35b1 100644
--- a/site2/website/versioned_docs/version-2.7.0/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.7.0/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.7.0/concepts-messaging.md b/site2/website/versioned_docs/version-2.7.0/concepts-messaging.md
index 8780b20..5beb097 100644
--- a/site2/website/versioned_docs/version-2.7.0/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.7.0/concepts-messaging.md
@@ -66,7 +66,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChuckedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.7.0/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.7.0/tiered-storage-azure.md
index bd822b7..508d9d9 100644
--- a/site2/website/versioned_docs/version-2.7.0/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.7.0/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.7.1/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.7.1/administration-pulsar-manager.md
index f557242..3692803 100644
--- a/site2/website/versioned_docs/version-2.7.1/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.7.1/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.7.1/concepts-messaging.md b/site2/website/versioned_docs/version-2.7.1/concepts-messaging.md
index eb27562..d2260e5 100644
--- a/site2/website/versioned_docs/version-2.7.1/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.7.1/concepts-messaging.md
@@ -66,7 +66,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChuckedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.7.1/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.7.1/tiered-storage-azure.md
index 0dbc89e..cba7636 100644
--- a/site2/website/versioned_docs/version-2.7.1/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.7.1/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.7.2/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.7.2/administration-pulsar-manager.md
index 5836636..c14a1c4 100644
--- a/site2/website/versioned_docs/version-2.7.2/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.7.2/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.7.2/concepts-messaging.md b/site2/website/versioned_docs/version-2.7.2/concepts-messaging.md
index b8b6327..cc0b6f5 100644
--- a/site2/website/versioned_docs/version-2.7.2/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.7.2/concepts-messaging.md
@@ -66,7 +66,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChuckedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.7.2/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.7.2/tiered-storage-azure.md
index f08bfc2..eee8e0b 100644
--- a/site2/website/versioned_docs/version-2.7.2/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.7.2/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.7.3/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.7.3/administration-pulsar-manager.md
index ac55fe6..799f3f4 100644
--- a/site2/website/versioned_docs/version-2.7.3/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.7.3/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.7.3/concepts-messaging.md b/site2/website/versioned_docs/version-2.7.3/concepts-messaging.md
index b1f9700..2c2aa46 100644
--- a/site2/website/versioned_docs/version-2.7.3/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.7.3/concepts-messaging.md
@@ -66,7 +66,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChuckedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.7.3/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.7.3/tiered-storage-azure.md
index 3562de8..944fb34 100644
--- a/site2/website/versioned_docs/version-2.7.3/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.7.3/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.7.4/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.7.4/administration-pulsar-manager.md
index 2a7e7bb..145e85a 100644
--- a/site2/website/versioned_docs/version-2.7.4/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.7.4/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.7.4/concepts-messaging.md b/site2/website/versioned_docs/version-2.7.4/concepts-messaging.md
index 2abfa30..ffcc427 100644
--- a/site2/website/versioned_docs/version-2.7.4/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.7.4/concepts-messaging.md
@@ -66,7 +66,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChuckedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.7.4/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.7.4/tiered-storage-azure.md
index 7608f38..1549e42 100644
--- a/site2/website/versioned_docs/version-2.7.4/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.7.4/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.8.0/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.8.0/administration-pulsar-manager.md
index 2fdd7f8..e861f64 100644
--- a/site2/website/versioned_docs/version-2.8.0/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.8.0/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.8.0/concepts-messaging.md b/site2/website/versioned_docs/version-2.8.0/concepts-messaging.md
index a879c44..e39891c 100644
--- a/site2/website/versioned_docs/version-2.8.0/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.8.0/concepts-messaging.md
@@ -100,7 +100,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChunkedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.8.0/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.8.0/tiered-storage-azure.md
index 72a5969..654b94c 100644
--- a/site2/website/versioned_docs/version-2.8.0/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.8.0/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.8.1/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.8.1/administration-pulsar-manager.md
index aed97df..6c8aed1 100644
--- a/site2/website/versioned_docs/version-2.8.1/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.8.1/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.8.1/concepts-messaging.md b/site2/website/versioned_docs/version-2.8.1/concepts-messaging.md
index ebcda4c..bb4e40b 100644
--- a/site2/website/versioned_docs/version-2.8.1/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.8.1/concepts-messaging.md
@@ -100,7 +100,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChunkedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.8.1/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.8.1/tiered-storage-azure.md
index 8efe825..e89e08d 100644
--- a/site2/website/versioned_docs/version-2.8.1/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.8.1/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.8.2/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.8.2/administration-pulsar-manager.md
index e0caefe..49f6ada 100644
--- a/site2/website/versioned_docs/version-2.8.2/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.8.2/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.8.2/concepts-messaging.md b/site2/website/versioned_docs/version-2.8.2/concepts-messaging.md
index 47e1c5e..197f954 100644
--- a/site2/website/versioned_docs/version-2.8.2/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.8.2/concepts-messaging.md
@@ -100,7 +100,7 @@ When you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription types.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChunkedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.8.2/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.8.2/tiered-storage-azure.md
index efaea21..1612b19 100644
--- a/site2/website/versioned_docs/version-2.8.2/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.8.2/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.9.0/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.9.0/administration-pulsar-manager.md
index a7d20f4..a43080b 100644
--- a/site2/website/versioned_docs/version-2.9.0/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.9.0/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.9.0/concepts-messaging.md b/site2/website/versioned_docs/version-2.9.0/concepts-messaging.md
index 6aefb9b..7d2dba2 100644
--- a/site2/website/versioned_docs/version-2.9.0/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.9.0/concepts-messaging.md
@@ -102,7 +102,7 @@ Before you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription modes.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChunkedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.9.0/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.9.0/tiered-storage-azure.md
index 5abb34a..93a16ac 100644
--- a/site2/website/versioned_docs/version-2.9.0/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.9.0/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
diff --git a/site2/website/versioned_docs/version-2.9.1/administration-pulsar-manager.md b/site2/website/versioned_docs/version-2.9.1/administration-pulsar-manager.md
index c524583..b792897 100644
--- a/site2/website/versioned_docs/version-2.9.1/administration-pulsar-manager.md
+++ b/site2/website/versioned_docs/version-2.9.1/administration-pulsar-manager.md
@@ -90,7 +90,7 @@ If you want to enable JWT authentication, use one of the following methods.
* Method 1: use command-line tool
```
-wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/apache-pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
+wget https://dist.apache.org/repos/dist/release/pulsar/pulsar-manager/pulsar-manager-0.2.0/apache-pulsar-manager-0.2.0-bin.tar.gz
tar -zxvf apache-pulsar-manager-0.2.0-bin.tar.gz
cd pulsar-manager
tar -zxvf pulsar-manager.tar
diff --git a/site2/website/versioned_docs/version-2.9.1/concepts-messaging.md b/site2/website/versioned_docs/version-2.9.1/concepts-messaging.md
index d641d62..b22ff53 100644
--- a/site2/website/versioned_docs/version-2.9.1/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.9.1/concepts-messaging.md
@@ -102,7 +102,7 @@ Before you enable chunking, read the following instructions.
- Chunking is only supported for persisted topics.
- Chunking is only supported for the exclusive and failover subscription modes.
-When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
+When chunking is enabled (`chunkingEnabled=true`), if the message size is greater than the allowed maximum publish-payload size, the producer splits the original message into chunked messages and publishes them with chunked metadata to the broker separately and in order. At the broker side, the chunked messages are stored in the managed-ledger in the same way as that of ordinary messages. The only difference is that the consumer needs to buffer the chunked messages and combines them into [...]
The consumer consumes the chunked messages and buffers them until the consumer receives all the chunks of a message. And then the consumer stitches chunked messages together and places them into the receiver-queue. Clients consume messages from the receiver-queue. Once the consumer consumes the entire large message and acknowledges it, the consumer internally sends acknowledgement of all the chunk messages associated to that large message. You can set the `maxPendingChunkedMessage` param [...]
diff --git a/site2/website/versioned_docs/version-2.9.1/tiered-storage-azure.md b/site2/website/versioned_docs/version-2.9.1/tiered-storage-azure.md
index ed41910..5d9f149 100644
--- a/site2/website/versioned_docs/version-2.9.1/tiered-storage-azure.md
+++ b/site2/website/versioned_docs/version-2.9.1/tiered-storage-azure.md
@@ -204,7 +204,6 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
Offload was a success
```
-
If there is an error in offloading, the error is propagated to the `pulsar-admin topics offload-status` command.
```bash
[pulsar-site] 03/03: update
Posted by ur...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
commit 84ea62b14a8b923c000f0e2497ada407891d35f6
Author: LiLi <ur...@apache.org>
AuthorDate: Fri Feb 11 10:46:55 2022 +0800
update
Signed-off-by: LiLi <ur...@apache.org>
---
site2/tools/sync-docs.sh | 2 ++
1 file changed, 2 insertions(+)
diff --git a/site2/tools/sync-docs.sh b/site2/tools/sync-docs.sh
new file mode 100755
index 0000000..b154721
--- /dev/null
+++ b/site2/tools/sync-docs.sh
@@ -0,0 +1,2 @@
+cp -r ../pulsar/site2/website/versioned_docs/* ./site2/website/versioned_docs
+cp -r ../pulsar/site2/website/versioned_sidebars/* ./site2/website/versioned_sidebars
\ No newline at end of file