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.

Sign up for GitHub

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

Jump to bottom

client: re-connect if connection closed by broker #102

Closed
xitep opened this issue Jul 2, 2016 · 1 comment · Fixed by #117
Closed

client: re-connect if connection closed by broker #102

xitep opened this issue Jul 2, 2016 · 1 comment · Fixed by #117
Labels
0.4.x bug

Comments

@xitep
Copy link
Collaborator

xitep commented Jul 2, 2016

As of Kafka 0.9, brokers will actively shutdown client connections which are idle for more than a broker configured timeout (the broker configuration parameter is connections.max.idle.ms; defaults to 10 minutes). kafka-rust should re-establish its broken connections to brokers.

Using example/console-producer.rs to send a message, leaving it untouched for more than 10 minutes, and then sending another message should not result in an error (currently UnexpectedEOF.)
@xitep xitep added the bug label Jul 2, 2016
@xitep xitep added the 0.5.x label Aug 2, 2016
This was referenced Aug 2, 2016
Closed
Merged
@xitep xitep added 0.4.x and removed 0.5.x labels Aug 2, 2016
@xitep xitep closed this as completed in #117 Aug 4, 2016
@xitep
Copy link
Collaborator Author

xitep commented Aug 4, 2016

Pushed to crates.io.

@xitep xitep mentioned this issue Aug 17, 2016
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0.4.x bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Idle connections kafka-rust/kafka-rust
1 participant
@xitep