This release fixes a bug that could, in certain cases, cause data to be lost from a connection. Due to the way beanstalk reservations work no data is permanently lost and the main effect of this would be a delay in task execution.
Thanks for pointing out the problem @mialex!
This is a maintenance release.
One issue that was fixed in this release was the risk of an infinite loop in
Now after a timeout, configurable via
ini-set('default_socket_timeout', $timeout), the
getLine() function will throw an exception to bring it in line with
If your worker has to potentially wait a long time for jobs you might start to see exceptions that you did not see before. Even though this behavior is a change it allows you to actually detect errors instead of just waiting forever.
If your worker is currently managed by a supervisor (ie, it restarts after it dies), set your socket timeout to a value like
3600. This means that if the worker doesn't get jobs for 12 hours, it will be restarted 12 times, but in return, if the connection is dead the worker will restart after at most 1 hour and resume working.
If a crash of your worker results in manually having to restart it you should really change the configuration.
One option that partially resolves this is properly catching errors in
reserve(), socket errors are in that sense nothing new, the changes in this version just make them more consistent in certain cases.
Please login to add feedback.
|submitted||4 months ago|
|in testing||4 months ago|
|in stable||4 months ago|