[
https://issues.apache.org/jira/browse/ROCKETMQ-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15784514#comment-15784514
]
ASF GitHub Bot commented on ROCKETMQ-23:
----------------------------------------
Github user shroman commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/20
@zhouxinyu I made changes according to your comments, and added more tests.
In {{CommitLog.FlushRealTimeService#run()}}, we will try to flush as long
as the data is available or {{MAX_FLUSH_COMMIT_NUM}} is not reached, logging
when flushing fails. It is almost same as before (checking the return value of
{{flush()}}) but checking if looks neat to me. What do you think?
> MappedFileQueue#flush should return true when flushing is successful
> --------------------------------------------------------------------
>
> Key: ROCKETMQ-23
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-23
> Project: Apache RocketMQ
> Issue Type: Bug
> Components: rocketmq-store
> Affects Versions: 4.0.0-incubating
> Reporter: Roman Shtykh
> Assignee: Roman Shtykh
>
> In the current implementation, MappedFileQueue#flush returns {{false}} when
> flushing is successful.
> This is not intuitive and error prone.
> For instance, in {{CommitLog#run line:915-918}}
> {code}
> for (int i = 0; i < RETRY_TIMES_OVER && !result; i++) {
> result = CommitLog.this.mappedFileQueue.flush(0);
> // ...
> }
> {code}
> I believe retries has to be done when flushing is not successful. But with
> the code above, it can try to flush only once on CommitLog termination and
> not continue retrying.
> The same is for {{DefaultMessageStore#doFlush line:1551}}
> Or is this not retry on failure, but the number of times flushing has to be
> done? Then, {{RETRY_TIMES_OVER}} should be renamed to something like
> {{FLUSH_NUM}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
