-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Make kafka version configurable #5046
Make kafka version configurable #5046
Conversation
@@ -150,7 +150,7 @@ kafka: | |||
protocols: | |||
- TLSv1.2 | |||
protocol: "{{ kafka_protocol_for_setup }}" | |||
version: 2.12-2.3.1 | |||
version: "{{ kafka_version | default('2.13-2.7.0') }}" |
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.
Need to see if it does not introduce any regression.
Just for those who visit this PR, that issue makes committing offests take more than 5 seconds, accordingly it would dramatically increase the wait time of certain activations. |
Codecov Report
@@ Coverage Diff @@
## master #5046 +/- ##
==========================================
- Coverage 82.52% 75.17% -7.35%
==========================================
Files 206 211 +5
Lines 10006 10454 +448
Branches 445 471 +26
==========================================
- Hits 8257 7859 -398
- Misses 1749 2595 +846
Continue to review full report at Codecov.
|
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
862df50
to
5cde872
Compare
Have any comment? I benchmarked against the EnvEnv: 3 PM nodes(128G memory; 40 core cpu;) Benchmark testI run producer and consumer side's script at the same time in kafka0 container.
I configured
We can saw the the tps is very high as well, when fetch I also tested below scenes During benchmarking, i observed the cpu/memory doesn't consume too much for all kafka nodes FYI, on our production env, the consumer.commit offset timeout(>=5.seconds) issue didn't reappeared after we used the latest kafka version. |
What I mentioned was the benchmarking of OpenWhisk with this version of Kafka. |
Thanks @ningyougang and @style95! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5046 +/- ##
===========================================
- Coverage 82.52% 71.79% -10.73%
===========================================
Files 206 219 +13
Lines 10006 11256 +1250
Branches 445 503 +58
===========================================
- Hits 8257 8081 -176
- Misses 1749 3175 +1426 ☔ View full report in Codecov by Sentry. |
2.7.0
kafka latest version:
2.7.0
fixed a bug: https://issues.apache.org/jira/browse/KAFKA-8334It happened in our env, after deploy latest kafka version in PM, the problem gone.
Description
Related issue and scope
My changes affect the following components
Types of changes
Checklist: