You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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?
Code of Conduct
The text was updated successfully, but these errors were encountered: