Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[INLONG-126] Increase the unflushed data bytes control #725

Closed
dockerzhang opened this issue Jul 28, 2021 · 0 comments
Closed

[INLONG-126] Increase the unflushed data bytes control #725

dockerzhang opened this issue Jul 28, 2021 · 0 comments

Comments

@dockerzhang
Copy link
Contributor

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.

JIRA link - [INLONG-126] created by gosonzhang
@dockerzhang dockerzhang added this to the 0.5.0 milestone Jul 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant