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

Warn/Crash if close() or destroy() is called with outstanding references #1437

Open
edenhill opened this issue Oct 3, 2017 · 4 comments
Open

Comments

@edenhill
Copy link
Contributor

edenhill commented Oct 3, 2017

To help users track down hang-on-termination bugs we could keep track of messages and other objects currently in the application's care that should have been returned to librdkafka prior to calling the destructor.

@nkirsch
Copy link

nkirsch commented Nov 2, 2017

@edenhill we're seeing some intermittent hangs on shutdown and in a different bug report you stated "recent versions has additional debug code to help troubleshoot termination hangs". Can you point me towards that debugging code?

Thanks!

@edenhill
Copy link
Contributor Author

edenhill commented Nov 2, 2017

This commit adds some information why a broker thread is not terminating:
b8bb295

Enable debug with debug=broker.

It would be great if you could provide a reliable reproduction of this hang.

@nkirsch
Copy link

nkirsch commented Nov 2, 2017

Thanks! We see this intermittently at scale, so we don't yet have a consistent way to reproduce. We're also not yet at that commit, but we'll see what we can do when we get there.

@edenhill
Copy link
Contributor Author

edenhill commented Nov 2, 2017

Thank you. librdkafka 0.11.1 was just released and is the release you want to upgrade to when the time comes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants