-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
log spamming on [ble/block_based/block_based_table_reader.cc:852] Tail prefetch size 524288 is calculated based on TailPrefetchStats #12664
Comments
I am seeing the same in our envs since updating to 9.0.0. It was introduced here #11406
I was thinking of opening PR to suggest changing log level to |
You'll want to make sure your files are compacted by a new enough version before we delete the complicated original behavior as a fallback (TailPrefetchStats). Any version that spews the warning is new enough. |
@ajkr thanks! I triggered a manual compaction via Java API: public void compactRange() throws RocksDBException {
compactRange(null);
} but I still see a lot logs like that (RocksDB 8.11.4). Any idea why? |
Because I think
|
Expected behavior
To not receive these logs (or to know what to do, like documentation).
Actual behavior
Many logs per second
Steps to reproduce the behavior
I'm not able to reproduce it locally (windows 11) but this appears often in our Linux servers. It is happening since the upgrade to rocksdbjni 8.x.
This is the OPTIONS file:
The text was updated successfully, but these errors were encountered: