-
Notifications
You must be signed in to change notification settings - Fork 328
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
feat: recover file cache index asynchronously #5087
feat: recover file cache index asynchronously #5087
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5087 +/- ##
==========================================
- Coverage 84.04% 83.80% -0.24%
==========================================
Files 1157 1157
Lines 216477 216506 +29
==========================================
- Hits 181944 181449 -495
- Misses 34533 35057 +524 |
a33b7b5
to
8c339f4
Compare
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Recovering the cache index synchronously for a large number of files (potentially in the hundreds of thousands) can be highly time-consuming (e.g., ~10 seconds). This PR addresses the issue by making the cache index recovery process asynchronous, significantly reducing the startup time of the datanode.
Checklist