-
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
Does the library support broker recover back #27
Comments
Hi, this sounds weird. Could you try to enable debugging in rdkafka while reproducing this issue? |
HI, but, when I don't test, I found a log is very strange
my test step:
|
Could you try to enable debugging in librdkafka? If you are using rdkafka_example or rdkafka_performance all you need to do is provide the "-d all" command-line switch. After broker restart it might take up to topic.metadata.refresh.interval.ms (default 10s) before the partitions are available to rdkafka. |
I have enabled the debuging as you mentioned.
after I start the server again the log is following
but after do this serveral time, there is no debug message come from librdkakfa
|
Are there no kafka debug messages between [2013-11-27 17:45:39.890] and [2013-11-27 17:49:39.479] ? |
this morning when I stop the kafka and start again, there will be no more log form librdkafka. following is the whole log message
|
continue
and when I start the kafka again, the connection is established.
|
I dont see any problems in the last log output you added here. What happens after the brokers come up again? Thanks |
HI, |
Okay, thanks for clarifying. Would it be possible for you to attach gdb to this process when librdkafka seems to be dead:
and then issue the following command in gdb:
And paste the output in this issue. |
Hi, |
Oh, and I cant seem to see the pictures that you upload to this issue. The links are broken. |
I already send you an email. |
|
|
|
Jerry, can you update to the latest version on master branch and see if you can reproduce? |
HI, |
Thanks for your help in sorting out this issue! |
Hi,
In my case, when the kafka cluster is shutdown, and the producer use the librdkafka still try to send the log to kafka, it will failed.
but When I start the Kafka cluster, the producer also can't send the log to kafka, and I found the socket in producer is "CLOSE_WAIT" status
Does the librdlibary has the feature to support checking broker alive? Thanks~!
The text was updated successfully, but these errors were encountered: