-
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: allow initializing regions in background #2930
feat: allow initializing regions in background #2930
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #2930 +/- ##
===========================================
- Coverage 85.82% 85.32% -0.50%
===========================================
Files 775 770 -5
Lines 124230 124430 +200
===========================================
- Hits 106621 106176 -445
- Misses 17609 18254 +645 |
e49d122
to
e930bb2
Compare
202a620
to
439dbb4
Compare
@waynexia The new commits changed a lot; it is better to review them again😇 |
439dbb4
to
43c3e8e
Compare
@WenyXu conflicts |
43c3e8e
to
0ea06e0
Compare
@MichaelScofield @evenyag PTAL |
6c1c7d8
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
initialize_region_in_background
, allowing users to initialize all regions in the background without blocking the startup.RegionNotReady
status code, and non-create/open requests trying to access the region under creating or opening will return theRegionNotReady
instead ofRegionNotFound.
RegionBusy
status code, ensuring only one exclusive operation(e.g., open region, close region) will be executed simultaneously.Checklist
Refer to a related PR or issue link (optional)