Go client Put() blocks forever if called on disconnected connection -- intended behavior?

29 views

Skip to first unread message

Will Hawkins

unread,

Jul 29, 2016, 1:22:01 AM7/29/16

to beanstalk-talk

Hello everyone!

First of all, I sincerely appreciate all the work that everyone in the "community" does to provide us users with a simple, scalable and robust tool like beanstalk.

I just have a quick question about the Put method of the Go beanstalk client:

Scenario:

I have a beanstalk connection that is connected to a q. I do several Put()s and everything is great. Then the beanstalk server goes away. The next "several" (I've experimented and determined the value is 2) Put()s will fail and return a non-nil error value.

However, after that, if I call Put() again on that same connection, the function call blocks forever.

Obviously the proper way to handle this is to respond to the failure earlier (i.e., either the first or second time that the Put() returns an error). However, I am just wondering if this blocking is the intended behavior and its source. It seems like it is related to the underlying textproto object that drives the io with the server, but I was hoping someone could possibly speak authoritatively about this.

I hope that this is a reasonable venue to ask such a question. If not, please tell me to go somewhere else (or just "away"!).

Again, thank you to everyone involved with beanstalk and the related ecosystem!

Will

Keith Rarick

unread,

Jul 29, 2016, 1:59:33 AM7/29/16

to beansta...@googlegroups.com

On Thu, Jul 28, 2016 at 10:21 PM Will Hawkins <hawk...@gmail.com> wrote:

if I call Put() again on that same connection, the function call blocks forever.