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

[TubeMQ] Add direct write to disk control #2620

Closed
2 tasks done
gosonzhang opened this issue Feb 21, 2022 · 0 comments · Fixed by #2763
Closed
2 tasks done

[TubeMQ] Add direct write to disk control #2620

gosonzhang opened this issue Feb 21, 2022 · 0 comments · Fixed by #2763

Comments

@gosonzhang
Copy link
Contributor

Description

At present, when Broker stores data, it first caches data through MsgMemStore and then flashes it to MsgFileStore in batches to store data persistently in files. This processing mode is very effective for disk media servers, but there are some occasions, for example, the configured topics in the system too many but insufficient memory resources, or the persistent storage medium, like SSD, is very fast, which is ok to directly write the received data to MsgFileStore for direct storage.

Based on this idea, the current Broker storage implementation is adjusted, and optional control is added to the storage path, supporting users to enable or disable the memory cache function through configuration

InLong Component

InLong TubeMQ

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant