[INLONG-126] Increase the unflushed data bytes control - ASF JIRA

Log work

Agile Board

Rank to Top

Rank to Bottom

Attach files

Attach Screenshot

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Convert to Issue

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Sub-task
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 0.5.0
Component/s: None
Labels:
- pull-request-available
- suspended

Description

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:

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.