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
[ISSUE #5091] [Store-A] Speed up Broker initialization by concurrently loading ConsumeQueue #5093
Conversation
…g Broker initialization
Codecov Report
@@ Coverage Diff @@
## develop #5093 +/- ##
=============================================
+ Coverage 43.16% 43.32% +0.16%
- Complexity 7759 7802 +43
=============================================
Files 995 996 +1
Lines 69170 69289 +119
Branches 9154 9165 +11
=============================================
+ Hits 29855 30018 +163
+ Misses 35562 35508 -54
- Partials 3753 3763 +10
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
long recoverCqStart = System.currentTimeMillis(); | ||
long maxPhyOffsetOfConsumeQueue = this.recoverConsumeQueue(); | ||
long recoverCqEnd = System.currentTimeMillis(); | ||
private boolean recover(final boolean lastExitOK, final boolean recoverConcurrently) { |
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.
How about keeping the original function signature? We can also get the brokerConfig in the recover function.
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.
ok, I will fix it
…g ConsumeQueue during Broker initialization
8dab33c
to
1ec50df
Compare
No description provided.