[
https://issues.apache.org/jira/browse/TUBEMQ-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109770#comment-17109770
]
Guocheng Zhang commented on TUBEMQ-126:
---------------------------------------
Later, I thought about it: in fact, the memory flush disk and the disk flush
disk can be combined to one, based on the modified TUBEMQ-123, the memory
flushes the disk according to the block. At this time, it has been indicated
that the data needs to be refreshed to the file. Correspondingly, the file
layer flush Disk control can be cut out
Anyway, I will practice this idea in the next implementation to see if it is
feasible
> 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
> Priority: Major
> Attachments: screenshot-1.png
>
>
> 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)
