rocketmq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vongosl...@apache.org
Subject [rocketmq] branch develop updated: [ISSUE #1866] Fix typo in document
Date Wed, 01 Apr 2020 07:19:23 GMT
This is an automated email from the ASF dual-hosted git repository.

vongosling pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/rocketmq.git


The following commit(s) were added to refs/heads/develop by this push:
     new 18a879b  [ISSUE #1866] Fix typo in document
18a879b is described below

commit 18a879b58cb546172e72b42c2b15913081013fff
Author: superleo-cn <superleo.peking@gmail.com>
AuthorDate: Wed Apr 1 15:19:15 2020 +0800

    [ISSUE #1866] Fix typo in document
---
 docs/en/Example_Transaction.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/en/Example_Transaction.md b/docs/en/Example_Transaction.md
index 2f74368..a35b040 100644
--- a/docs/en/Example_Transaction.md
+++ b/docs/en/Example_Transaction.md
@@ -88,8 +88,8 @@ public class TransactionListenerImpl implements TransactionListener {
 
 ## 3 Usage Constraint  
 1. Messages of the transactional have no schedule and batch support.
-2. In order to avoid a single message being checked too many times and lead to half queue
message accumulation,  we limited the number of checks for a single message to 15 times by
default, but users can change this limit by change the ```transactionCheckMax``` parameter
in the configuration of the broker,  if one message has been checked over ```transactionCheckMax```
times,  broker will discard this message and print an error log at the same time by default.
Users can change this behav [...]
-3. A transactional message will be checked after a certain period of time that determined
by parameter ```transactionTimeout``` in the configuration of the broker. And users also can
change this limit by set user property “CHECK_IMMUNITY_TIME_IN_SECONDS” when sending transactional
message, this parameter takes precedence over the “transactionTimeout” parameter. 
+2. In order to avoid a single message being checked too many times and lead to half queue
message accumulation,  we limited the number of checks for a single message to 15 times by
default, but users can change this limit by change the ```transactionCheckMax``` parameter
in the configuration of the broker,  if one message has been checked over ```transactionCheckMax```
times,  broker will discard this message and print an error log at the same time by default.
Users can change this behav [...]
+3. A transactional message will be checked after a certain period of time that determined
by parameter g```transactionTimeout``` in the configuration of the broker. And users also
can change this limit by set user property ```CHECK_IMMUNITY_TIME_IN_SECONDS``` when sending
transactional message, this parameter takes precedence over the ```transactionTimeout``` parameter.

 4. A transactional message maybe checked or consumed more than once. 
 5. Committed message reput to the user’s target topic may fail. Currently, it depends on
the log record. High availability is ensured by the high availability mechanism of RocketMQ
itself. If you want to ensure that the transactional message isn’t lost and the transaction
integrity is guaranteed, it is recommended to use synchronous double write. mechanism. 
 6. Producer IDs of transactional messages cannot be shared with producer IDs of other types
of messages. Unlike other types of message, transactional messages allow backward queries.
MQ Server query clients by their Producer IDs.


Mime
View raw message