Azure-docs: How to limit the rocks DB log file size?

Created on 29 Jan 2020  Â·  5Comments  Â·  Source: MicrosoftDocs/azure-docs

Hi,
From the rocks DB options file, I can see that the max_log_file_size is set to zero and the LOG file inside the Database folder goes on increasing. Will this exhaust the device disk storage? I can see that the log file count is limited to 1. How can I set a limit to the log file size from the cloud.


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri2 cxp iot-edgsvc product-question triaged

Most helpful comment

@JesvinJoseph Thanks for bringing this to our attention. Unfortunately we missed this setting and it's hardcoded right now in the storage module. It looks like the log will indeed grow indefinitely. We should fix this in the next version.

All 5 comments

@JesvinJoseph Thank you for your interest in Azure. In looking into this configuration, it appears that there is some potential to limit this growth. Please see: Why Rocks DB logging of edgeHub is written filesystem?
I am investigating this further to identity current capabilities. Can you share the Rocks DB options file? Thank you!

@Mike-Ubezzi-MSFT Thank you for the quick response. I have attached the options file created inside the Database folder of edge blob storage.
OPTIONS-000059.txt

The issue that you mentioned is also accurate to me. But I need to persist the messages from edgeHub. But when I started to persist, Rocks DB is creating multiple logs inside the edgeHub folder each with 64MB size. This is going to exhaust my disk space. I have created a similar issue of edgeHub here

@JesvinJoseph Thanks for bringing this to our attention. Unfortunately we missed this setting and it's hardcoded right now in the storage module. It looks like the log will indeed grow indefinitely. We should fix this in the next version.

@JesvinJoseph If there are no additional questions, we will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

@JesvinJoseph If there are no additional questions, we will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

@mbialecka @Mike-Ubezzi-MSFT Is there any workaround for this?

Was this page helpful?
0 / 5 - 0 ratings