-
Notifications
You must be signed in to change notification settings - Fork 332
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(remote_wal): implement topic allocation #2970
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #2970 +/- ##
===========================================
- Coverage 85.90% 85.80% -0.10%
===========================================
Files 780 780
Lines 125900 126088 +188
===========================================
+ Hits 108157 108195 +38
- Misses 17743 17893 +150 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
# Number of partitions per topic. | ||
# num_partitions = 1 | ||
# Expected number of replicas of each partition. | ||
# replication_factor = 3 | ||
# Above which a topic creation operation will be cancelled. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use more concise words.
Nit(Non-blocking):
# Above which a topic creation operation will be cancelled. | |
# The timeout of topic creation |
if let Err(e) = self.wal_options_allocator.start().await { | ||
error!(e; "Failed to start wal options allocator"); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit(Non-blocking):
We should ensure the start will only be executed once in the life cycle. We can improve this in the future.
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
WalOptionsAllocator
so wal options could be allocated while the metasrv is handling a create table request.TODO
Checklist
Refer to a related PR or issue link (optional)
Tracing issue for Kafka remote wal: #2722