Skip to content
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

Event callback was not called when connections are resumed #875

Closed
9 tasks
nobody93 opened this issue Oct 31, 2016 · 2 comments
Closed
9 tasks

Event callback was not called when connections are resumed #875

nobody93 opened this issue Oct 31, 2016 · 2 comments

Comments

@nobody93
Copy link

Description

Hi,

I have an eventCallback class inherited from RdKafka::EventCb, it got event callback when the connection was down or server was down, but it did not get event when the connection was resumed. I don't want to run this->producer->produce until I can make sure that the connection is ok. Is it the normal behaviour of the RdKafka::EventCb or did I miss something here?

Thank you.

How to reproduce

Checklist

Please provide the following information:

  • librdkafka version (release number or git tag):
  • Apache Kafka version:
  • librdkafka client configuration:
  • Operating system:
  • Using the legacy Consumer
  • Using the high-level KafkaConsumer
  • Provide logs (with debug=.. as necessary) from librdkafka
  • Provide broker log excerpts
  • Critical issue
@edenhill
Copy link
Contributor

edenhill commented Nov 2, 2016

To quote https://github.com/edenhill/librdkafka/blob/master/INTRODUCTION.md#message-reliability

This [broker failure] is handled automatically by librdkafka and the application does not need to take any action at any of the above events. The message will be resent up to "message.send.max.retries" times before reporting a failure back to the application.

@edenhill
Copy link
Contributor

edenhill commented Nov 3, 2016

There is currently no non-debug log or event to indicate that the connection is back up.

Duplicate of #137

@edenhill edenhill closed this as completed Nov 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants