iamqq23ue commented on pull request #3382:
URL: https://github.com/apache/rocketmq/pull/3382#issuecomment-975019098
I agree with what you said "No storage system can guarantee 100% persistent
availability"
Therefore, it is necessary to ensure that the client can handle the
exception in the first time when the storage fails.
If the tenant who sets ASYNC_FLUSH shares the broker with the tenant who
sets SYNC_FLUSH, it can only be required in accordance with the stricter
SYNC_FLUSH.
------------------ 原始邮件 ------------------
发件人:
"apache/rocketmq"
***@***.***>;
发送时间: 2021年11月22日(星期一) 上午10:29
***@***.***>;
***@***.******@***.***>;
主题: Re: [apache/rocketmq] FIX ISSUE#2706 the problem of returning
SEND_OK after flush failed,The original pull request was #2707. (#3382)
I think anyone who sets SYNC_FLUSH expects that SEND_OK will only be
returned when all data is written to the disk.
Of course, but the error handling strategy varies. No storage system can
guarantee 100% persistent availability.
And, RocketMQ can be used for multi tenants, users with ASYNC_FLUSH
requirement can share a broker with SYNC_FLUSH enabled.
—
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
