Huanli-Meng commented on a change in pull request #11667:
URL: https://github.com/apache/pulsar/pull/11667#discussion_r689174704
##########
File path: site2/docs/concepts-messaging.md
##########
@@ -65,11 +67,11 @@ You can have different types of access modes on topics for
producers.
> **Note**
>
-> Once an application creates a producer with the `Exclusive` or
`WaitForExclusive` access mode successfully, the instance of the application is
guaranteed to be the **only one writer** on the topic. Other producers trying
to produce on this topic get errors immediately or have to wait until they get
the `Exclusive` access.
+> Once an application creates a producer with `Exclusive` or
`WaitForExclusive` access mode successfully, the instance of this application
is guaranteed to be the **only writer** on 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 `Exclusive` access.
Review comment:
```suggestion
> Once an application creates a producer with `Exclusive` or
`WaitForExclusive` access mode successfully, the instance of this application
is guaranteed to be the **only writer** on the topic. Any other producers
trying to produce messages to this topic will either get errors immediately or
have to wait until they get the `Exclusive` access.
```
##########
File path: site2/docs/concepts-messaging.md
##########
@@ -180,18 +182,18 @@ If you want to acknowledge messages negatively, you can
use the following API.
consumer.negativeAcknowledge(msg);
```
-> **Note**
-> If batching is enabled, other messages and the negatively acknowledged
messages in the same batch are redelivered to the consumer.
+> **Note**
+> If batching is enabled, all messages in one batch are redelivered to the
consumer.
### Acknowledgement timeout
-If 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 tracks the unacknowledged
messages within the entire `acktimeout` time range, and sends a `redeliver
unacknowledged messages` request to the broker automatically when the
acknowledgement timeout is specified.
+If a message is not consumed successfully, and you want the broker to
redeliver this message automatically, then you can adopt the unacknowledged
message automatic redelivery mechanism. With this redelivery approach enabled,
the client tracks the unacknowledged messages within the entire `acktimeout`
time range, and sends a `redeliver unacknowledged messages` request to the
broker automatically when the acknowledgement timeout is specified.
Review comment:
```suggestion
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 `acktimeout` time
range, and sends a `redeliver unacknowledged messages` request to the broker
automatically when the acknowledgement timeout is specified.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
