[
https://issues.apache.org/jira/browse/TUBEMQ-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149045#comment-17149045
]
ASF subversion and git services commented on TUBEMQ-126:
--------------------------------------------------------
Commit a68f9bea8bd4ca3cb1af73d66ecb17e7c237d958 in incubator-tubemq's branch
refs/heads/master from gosonzhang
[ https://gitbox.apache.org/repos/asf?p=incubator-tubemq.git;h=a68f9be ]
[TUBEMQ-126] Increase the unflushed data bytes control (addendum)(#175)
Co-authored-by: gosonzhang <[email protected]>
> 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, suspended
> Attachments: screenshot-1.png
>
> Time Spent: 2h 40m
> 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)
