[
https://issues.apache.org/jira/browse/TUBEMQ-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135498#comment-17135498
]
Jeff Zhou commented on TUBEMQ-126:
----------------------------------
I see recently the PR of TUBEMQ-126 has been ceased, is there any modification
on the design?
Through TUBEMQ-123, it seems FileStorage is the next downstream layer before
actual flush, so is there architectural change on the plan of TUBEMQ-110?
> Increase the unflushed data bytes control
> -----------------------------------------
>
> Key: TUBEMQ-126
> URL: https://issues.apache.org/jira/browse/TUBEMQ-126
> Project: Apache TubeMQ
> Issue Type: Sub-task
> Reporter: Guocheng Zhang
> Assignee: Jeff Zhou
> Priority: Major
> Labels: pull-request-available
> Attachments: screenshot-1.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, there are unflushThreshold indicating the number of unwashed disks
> and unflushInterval indicating the maximum interval of unwashed disks.
> Through analysis, data flushing check should increase the unflushed data
> bytes control:
> !screenshot-1.png!
> The unflushed indicators are setted to threshold to monitor and make the
> possibility of data loss of within the controllable range, but the time
> interval and the number of messages are not enough, for example, the same
> 1000 messages, in the case of a 100-byte message and a 512K-byte message, we
> not only need to check the number of entries, but also need to check the
> accumulated total data size of the unwashed disk
> For this problem, the new version plans to adjust to increase the
> unflushDataSize indicator.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
