Thank you, Yukon!
I still have some question about transactional messaging
1. Does the transactional messaging need to be "exactly only once" delivered?
2. Where to store the transaction state? Since the state must be persistent
and also updated.
About the second question, I've considered about some methods
1. Inside of the message. But it is said that this would generate lots of
dirty pages on the OS.
2. In a database, especially an SQL database. Since class
JDBCTransactionStore already exists. But I want to know whether the DB will be
the bottleneck of performance or scalability.
3. Like Kafka, use an internal topic called Transaction log. It will record
all the operation about transaction states. And store the latest states in the
memory. If a partition crashed, It will read the log to recover. But the
recovery would be slow.
4. Similar to 3, store and the transaction state in the Transaction log. But
if there's a lot of transaction message, (I guess)this would be like 1 to
generate many dirty pages.
发件人: yukon <yu...@apache.org>
发送时间: 2018年3月5日 12:28:47
主题: Re: 答复: [GSOC|ROCKETMQ-123]Support Distributed Transactional Messaging
The links you mentioned just are interfaces, we should implement these APIs.
On Tue, Feb 27, 2018 at 12:07 PM, 李 德鑫 <dexi...@outlook.com> wrote:
> My previous email didn't clarify the question clearly, so I'll try to make
> it in detail.
> In this jira's(https://issues.apache.org/jira/browse/ROCKETMQ-123)
> Implement a TransactionProducer and LocalTransactionChecker, guarantee
> message delivery and local transaction operations are atomic.
> The following is the simple transactional messaging flow:
> 1. TransactionProducer sends a half message to the broker. A half message
> means it's not confirmed and can't be delivered to the consumer.
> 2. TransactionProducer executes the specific local transaction.
> 3. Commit or Rollback the half message according to the status of the
> local transaction. A half message will be deleted if it's rollbacked and
> delivered to the consumer if it's committed.
> The 1st step I found in https://github.com/apache/
> The 2nd step I found in https://github.com/apache/
> The 3rd step I found in https://github.com/apache/
> rocketmq/client/impl/producer/DefaultMQProducerImpl.java#L1026 for client
> and https://github.com/apache/rocketmq/blob/master/broker/
> EndTransactionProcessor.java#L49 for broker
> And my question is what is the part to be implemented for this issue? Is
> there anything I missed?
> 发件人: 李 德鑫 <dexi...@outlook.com>
> 发送时间: 2018年2月23日 9:35:17
> 收件人: firstname.lastname@example.org
> 主题: [GSOC|ROCKETMQ-123]Support Distributed Transactional Messaging
> I am working on this issue
> (https://issues.apache.org/jira/browse/ROCKETMQ-123) as my GSOC project
> [ROCKETMQ-123] Support Distributed Transactional Messaging ...<
> In most businesses, transactional messaging is frequently used to make a
> series of operations as an atomic transaction. At present, RocketMQ doesn't
> support ...
> However, there already have
> rocketmq - Mirror of Apache RocketMQ
> and TransactionCheckListener
> So, what is the part I should implement for this issue?
> Dexin Li