-
Notifications
You must be signed in to change notification settings - Fork 3.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
Kafka message from producer to consumer, the entire process takes an average of 400-600ms #2591
Closed
3 of 7 tasks
Comments
The latency is expected since you set |
ok i will try to set linger.ms = 50 or 100 and there is an another question in confluent-kafka-go consumer , i can not consumer message from broker log as:
code as follow: i do not kown the reason
|
edenhill
added a commit
that referenced
this issue
Nov 8, 2019
edenhill
added a commit
that referenced
this issue
Nov 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Read the FAQ first: https://github.com/edenhill/librdkafka/wiki/FAQ
Description
1. Producer、 consumer and kafka cluster in the same machine room。The whole process of kafka producing message to consumer is as follows:
LOG-7-RECV: [thrd:IP:9292/bootstrap]: IP:9292/1: Received ProduceResponse (v7, 53 bytes, CorrId 2, rtt 2.48ms)
so the whole process takes 498ms
2. Configuration
3. kafka-consumer code as follow:
How to reproduce
<your steps how to reproduce goes here, or remove section if not relevant>
IMPORTANT: Always try to reproduce the issue on the latest released version (see https://github.com/edenhill/librdkafka/releases), if it can't be reproduced on the latest version the issue has been fixed.
Checklist
IMPORTANT: We will close issues where the checklist has not been completed.
Please provide the following information:
<v1.1.0>
<2.12-2.3.0>
<REPLACE with e.g., message.timeout.ms=123, auto.reset.offset=earliest, ..>
<Linux ubuntu x86_64>
debug=..
as necessary) from librdkafkaThe text was updated successfully, but these errors were encountered: