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

Question: how do I prevent LOG.old.XXXX to grow out of control #55

Closed
AndreSteenbergen opened this issue Mar 15, 2019 · 1 comment
Closed

Comments

@AndreSteenbergen
Copy link

I use RocksDb.OpenReadOnly(options, config.GetString("akka.rocksdb.path"), false); Every 10 seconds or so. This way I keep a few recent readers present at all time. Problem is I end up with quite a lot of log.OLD files.

How do I keep my directory somewhat clean?

@warrenfalk
Copy link
Owner

That's a question about rocksdb internal behavior that I don't know enough about to answer. The question probably should be posed to the rocksdb team, but they may expect you to translate to the C++ equivalent. You might try looking at this: facebook/rocksdb#2166 which suggests that there is a delete_obsolete_files_period_micros option. You might try DbOptions.SetDeleteObsoleteFilesPeriodMicros(), but I can't speak much to its behavior other than the summary included which is:

        /// <summary>
        /// The periodicity when obsolete files get deleted. The default
        /// value is 6 hours. The files that get out of scope by compaction
        /// process will still get automatically delete on every compaction,
        /// regardless of this setting
        /// </summary>

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

2 participants