This is an automated email from the ASF dual-hosted git repository.
penghui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 666af1a [Doc]Update document to indicating effect of negative acking
message for order sube type like exclusive, failover and key_shared. (#9681)
666af1a is described below
commit 666af1a95ba42cc5fdf7bdee578da4c1bfe2a795
Author: Marvin Cai <[email protected]>
AuthorDate: Thu Feb 25 05:55:25 2021 -0800
[Doc]Update document to indicating effect of negative acking message for
order sube type like exclusive, failover and key_shared. (#9681)
* Update document to indicating effect of negative acking message for order
sub type like exclusive, failover and key_shared.
---
site2/docs/concepts-messaging.md | 2 ++
site2/docs/reference-terminology.md | 3 ++-
site2/website/versioned_docs/version-2.5.0/concepts-messaging.md | 2 ++
site2/website/versioned_docs/version-2.5.1/concepts-messaging.md | 2 ++
site2/website/versioned_docs/version-2.5.2/concepts-messaging.md | 2 ++
site2/website/versioned_docs/version-2.6.0/concepts-messaging.md | 2 ++
site2/website/versioned_docs/version-2.6.0/reference-terminology.md | 3 ++-
site2/website/versioned_docs/version-2.6.1/concepts-messaging.md | 2 ++
site2/website/versioned_docs/version-2.6.1/reference-terminology.md | 3 ++-
site2/website/versioned_docs/version-2.6.2/concepts-messaging.md | 2 ++
site2/website/versioned_docs/version-2.6.2/reference-terminology.md | 3 ++-
site2/website/versioned_docs/version-2.6.3/concepts-messaging.md | 2 ++
site2/website/versioned_docs/version-2.6.3/reference-terminology.md | 3 ++-
site2/website/versioned_docs/version-2.7.0/concepts-messaging.md | 2 ++
site2/website/versioned_docs/version-2.7.0/reference-terminology.md | 3 ++-
site2/website/versioned_docs/version-2.7.1/concepts-messaging.md | 2 ++
site2/website/versioned_docs/version-2.7.1/reference-terminology.md | 3 ++-
17 files changed, 34 insertions(+), 7 deletions(-)
diff --git a/site2/docs/concepts-messaging.md b/site2/docs/concepts-messaging.md
index ae266c5..b9b7125 100644
--- a/site2/docs/concepts-messaging.md
+++ b/site2/docs/concepts-messaging.md
@@ -128,6 +128,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
> **Note**
> If batching is enabled, other messages and the negatively acknowledged
> messages in the same batch are redelivered to the consumer.
diff --git a/site2/docs/reference-terminology.md
b/site2/docs/reference-terminology.md
index c6d40aa..25ebcee 100644
--- a/site2/docs/reference-terminology.md
+++ b/site2/docs/reference-terminology.md
@@ -80,7 +80,8 @@ if no acknowledgement, then the message will be retained
until it's processed.
When an application fails to process a particular message, it can sends a
"negative ack" to Pulsar
to signal that the message should be replayed at a later timer. (By default,
failed messages are
-replayed after a 1 minute delay)
+replayed after a 1 minute delay). Be aware that negative acknowledgment on
ordered subscription types,
+such as Exclusive, Failover and Key_Shared, can cause failed messages to
arrive consumers out of the original order.
#### Unacknowledged
diff --git a/site2/website/versioned_docs/version-2.5.0/concepts-messaging.md
b/site2/website/versioned_docs/version-2.5.0/concepts-messaging.md
index 3066286..3a79bb7 100644
--- a/site2/website/versioned_docs/version-2.5.0/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.5.0/concepts-messaging.md
@@ -90,6 +90,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
### Acknowledgement timeout
When a message is not consumed successfully, and you want to trigger the
broker to redeliver the message automatically, you can adopt the unacknowledged
message automatic re-delivery mechanism. Client will track the unacknowledged
messages within the entire `acktimeout` time range, and send a `redeliver
unacknowledged messages` request to the broker automatically when the
acknowledgement timeout is specified.
diff --git a/site2/website/versioned_docs/version-2.5.1/concepts-messaging.md
b/site2/website/versioned_docs/version-2.5.1/concepts-messaging.md
index 74889a2..50cf41e 100644
--- a/site2/website/versioned_docs/version-2.5.1/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.5.1/concepts-messaging.md
@@ -99,6 +99,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
> Note
> If batching is enabled, other messages in the same batch may be redelivered
> to the consumer as well as the negatively acknowledged messages.
diff --git a/site2/website/versioned_docs/version-2.5.2/concepts-messaging.md
b/site2/website/versioned_docs/version-2.5.2/concepts-messaging.md
index d5d5833..fba1b92 100644
--- a/site2/website/versioned_docs/version-2.5.2/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.5.2/concepts-messaging.md
@@ -99,6 +99,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
> Note
> If batching is enabled, other messages in the same batch may be redelivered
> to the consumer as well as the negatively acknowledged messages.
diff --git a/site2/website/versioned_docs/version-2.6.0/concepts-messaging.md
b/site2/website/versioned_docs/version-2.6.0/concepts-messaging.md
index b9d19e7..862dc9a 100644
--- a/site2/website/versioned_docs/version-2.6.0/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.0/concepts-messaging.md
@@ -105,6 +105,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
> **Note**
> If batching is enabled, other messages in the same batch may be redelivered
> to the consumer as well as the negatively acknowledged messages.
diff --git
a/site2/website/versioned_docs/version-2.6.0/reference-terminology.md
b/site2/website/versioned_docs/version-2.6.0/reference-terminology.md
index 790b375..1d0e4b1 100644
--- a/site2/website/versioned_docs/version-2.6.0/reference-terminology.md
+++ b/site2/website/versioned_docs/version-2.6.0/reference-terminology.md
@@ -81,7 +81,8 @@ if no acknowledgement, then the message will be retained
until it's processed.
When an application fails to process a particular message, it can sends a
"negative ack" to Pulsar
to signal that the message should be replayed at a later timer. (By default,
failed messages are
-replayed after a 1 minute delay)
+replayed after a 1 minute delay). Be aware that negative acknowledgment on
ordered subscription types,
+such as Exclusive, Failover and Key_Shared, can cause failed messages to
arrive consumers out of the original order.
#### Unacknowledged
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 dab92f4..635e51d 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
@@ -129,6 +129,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
> **Note**
> If batching is enabled, other messages and the negatively acknowledged
> messages in the same batch are redelivered to the consumer.
diff --git
a/site2/website/versioned_docs/version-2.6.1/reference-terminology.md
b/site2/website/versioned_docs/version-2.6.1/reference-terminology.md
index d752a0c..4bf0a7b 100644
--- a/site2/website/versioned_docs/version-2.6.1/reference-terminology.md
+++ b/site2/website/versioned_docs/version-2.6.1/reference-terminology.md
@@ -81,7 +81,8 @@ if no acknowledgement, then the message will be retained
until it's processed.
When an application fails to process a particular message, it can sends a
"negative ack" to Pulsar
to signal that the message should be replayed at a later timer. (By default,
failed messages are
-replayed after a 1 minute delay)
+replayed after a 1 minute delay). Be aware that negative acknowledgment on
ordered subscription types,
+such as Exclusive, Failover and Key_Shared, can cause failed messages to
arrive consumers out of the original order.
#### Unacknowledged
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 74d46ed..90b0774 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
@@ -129,6 +129,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
> **Note**
> If batching is enabled, other messages and the negatively acknowledged
> messages in the same batch are redelivered to the consumer.
diff --git
a/site2/website/versioned_docs/version-2.6.2/reference-terminology.md
b/site2/website/versioned_docs/version-2.6.2/reference-terminology.md
index ee72e16..d760773 100644
--- a/site2/website/versioned_docs/version-2.6.2/reference-terminology.md
+++ b/site2/website/versioned_docs/version-2.6.2/reference-terminology.md
@@ -81,7 +81,8 @@ if no acknowledgement, then the message will be retained
until it's processed.
When an application fails to process a particular message, it can sends a
"negative ack" to Pulsar
to signal that the message should be replayed at a later timer. (By default,
failed messages are
-replayed after a 1 minute delay)
+replayed after a 1 minute delay). Be aware that negative acknowledgment on
ordered subscription types,
+such as Exclusive, Failover and Key_Shared, can cause failed messages to
arrive consumers out of the original order.
#### Unacknowledged
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 39526d4..9d44449 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
@@ -129,6 +129,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
> **Note**
> If batching is enabled, other messages and the negatively acknowledged
> messages in the same batch are redelivered to the consumer.
diff --git
a/site2/website/versioned_docs/version-2.6.3/reference-terminology.md
b/site2/website/versioned_docs/version-2.6.3/reference-terminology.md
index 52e7d45..4ad8cfa 100644
--- a/site2/website/versioned_docs/version-2.6.3/reference-terminology.md
+++ b/site2/website/versioned_docs/version-2.6.3/reference-terminology.md
@@ -81,7 +81,8 @@ if no acknowledgement, then the message will be retained
until it's processed.
When an application fails to process a particular message, it can sends a
"negative ack" to Pulsar
to signal that the message should be replayed at a later timer. (By default,
failed messages are
-replayed after a 1 minute delay)
+replayed after a 1 minute delay). Be aware that negative acknowledgment on
ordered subscription types,
+such as Exclusive, Failover and Key_Shared, can cause failed messages to
arrive consumers out of the original order.
#### Unacknowledged
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 19cb95c..cec4149 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
@@ -129,6 +129,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
> **Note**
> If batching is enabled, other messages and the negatively acknowledged
> messages in the same batch are redelivered to the consumer.
diff --git
a/site2/website/versioned_docs/version-2.7.0/reference-terminology.md
b/site2/website/versioned_docs/version-2.7.0/reference-terminology.md
index ad1d368..1694fa8 100644
--- a/site2/website/versioned_docs/version-2.7.0/reference-terminology.md
+++ b/site2/website/versioned_docs/version-2.7.0/reference-terminology.md
@@ -81,7 +81,8 @@ if no acknowledgement, then the message will be retained
until it's processed.
When an application fails to process a particular message, it can sends a
"negative ack" to Pulsar
to signal that the message should be replayed at a later timer. (By default,
failed messages are
-replayed after a 1 minute delay)
+replayed after a 1 minute delay). Be aware that negative acknowledgment on
ordered subscription types,
+such as Exclusive, Failover and Key_Shared, can cause failed messages to
arrive consumers out of the original order.
#### Unacknowledged
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 1812214..2a0519d 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
@@ -129,6 +129,8 @@ In the exclusive and failover subscription modes, consumers
only negatively ackn
In the shared and Key_Shared subscription modes, you can negatively
acknowledge messages individually.
+Be aware that negative acknowledgment on ordered subscription types, such as
Exclusive, Failover and Key_Shared, can cause failed messages to arrive
consumers out of the original order.
+
> **Note**
> If batching is enabled, other messages and the negatively acknowledged
> messages in the same batch are redelivered to the consumer.
diff --git
a/site2/website/versioned_docs/version-2.7.1/reference-terminology.md
b/site2/website/versioned_docs/version-2.7.1/reference-terminology.md
index 411d4a3..e89d9d0 100644
--- a/site2/website/versioned_docs/version-2.7.1/reference-terminology.md
+++ b/site2/website/versioned_docs/version-2.7.1/reference-terminology.md
@@ -81,7 +81,8 @@ if no acknowledgement, then the message will be retained
until it's processed.
When an application fails to process a particular message, it can sends a
"negative ack" to Pulsar
to signal that the message should be replayed at a later timer. (By default,
failed messages are
-replayed after a 1 minute delay)
+replayed after a 1 minute delay). Be aware that negative acknowledgment on
ordered subscription types,
+such as Exclusive, Failover and Key_Shared, can cause failed messages to
arrive consumers out of the original order.
#### Unacknowledged
