You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2021/12/14 06:59:52 UTC
[GitHub] [rocketmq] iamqq23ue commented on issue #3617: Why does case SLAVE_NOT_AVALIABLE roll back when sending transaction messages
iamqq23ue commented on issue #3617:
URL: https://github.com/apache/rocketmq/issues/3617#issuecomment-993217120
I think that when the client receives a SLAVE_NOT_AVAILABLE, the client must resend the message, and it may still be sent to the abnormal broker.
Therefore I think that the message should not be returned when SLAVE_NOT_AVAILABLE.
------------------ 原始邮件 ------------------
发件人: "apache/rocketmq" ***@***.***>;
发送时间: 2021年12月14日(星期二) 下午2:42
***@***.***>;
***@***.******@***.***>;
主题: Re: [apache/rocketmq] Why does case SLAVE_NOT_AVALIABLE roll back when sending transaction messages (Issue #3617)
IMO, for the client, SLAVE_NOT_AVAILABLE is returned when sending a transaction message. At this time, the message has been successfully written to the master, and the client can resend it after ROLLBACK_MESSAGE.
For Broker, after receiving the commit message sent by the client, if SLAVE_NOT_AVAILABLE occurs, the commit message has been written to the master at this time, so it will automatically synchronize after the slave is restored, otherwise it will not make any sense to resend the commit after the return fails. .
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org