-
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
Crash on rd_kafka_topic_metadata_update #155
Comments
|
Did you set |
no set rd_kafka_conf_set_partitioner_cb() |
after add rd_kafka_conf_set_partitioner_cb(),gain failedinfo :Local: Broker handle destroyed |
Can you elaborate on what happened after setting the callback? |
after setting the callback,also get core as above,and gain "Local: Broker handle destroyed" in the server log. |
The |
Can you show me your code for setting up the topic configuration and creating the topic, etc? |
int initKafka() {
} |
|
the code about init kafka conf ,deal message,write2kafka |
Thanks, I cant see anything that is obviously wrong. |
yes,i create a new topic,and use it,the server is run ok. |
run the program in valgrind, has little memory leak |
Can you paste or email me the output from valgrind? |
When it crashes, that is |
==26482== LEAK SUMMARY: |
I need more output from valgrind, that is just the summary, I need the detailed output where it leaks. I'd also want you to trigger the crash when running valgrind and provide me that output aswell. |
the core can not reappear, but it create topic failed,and the errno=22(Invalid argument). |
==737== Memcheck, a memory error detector |
i clear some extraneous code. ==4786== Memcheck, a memory error detector |
Are you reusing the topic_conf for multiple topics? |
thanks edenhill , now i set the topic conf as null. |
if you want to reuse the topic_conf object you need to duplicate it, so change your topic_new call to:
|
RD_KAFKA_RESP_ERR__MSG_TIMED_OUT is means the respose about send message timeout or the message in produce buffer timeout? |
That means the message timed out in the local queue, this is usually caused by the broker not being available, or limited bandwidth to the broker. |
Can we close this issue? |
User c api,when start server,get the core info.
kafka version is 0.8.0
librdkafka is branch master
and the issues was find before,as the issues #132
#132
The text was updated successfully, but these errors were encountered: