We have a situation that only occurs on our production environment, and we
can't reproduce an our test/uat systems.
What appears to happen is that we put a job on a queue, and the client
reserves the job ten times (which is the maximum number of times we allow)
at which point we bury the job.
Our client code is basically (some detail omitted) as follows.
sub consume {
my $self = shift;
my $job;
RESERVE: {
my $bs = $self->beanstalk;
$bs->watch('my_queue');
$job = $bs->reserve;
my $stats = $job->stats;
if ($stats->reserves > 10) {
carp "Job failed max reserves. Burying.";
$job->bury;
redo RESERVE;
}
};
return $job;
}
The fact that the job is being buried (we get the error in the log) means
that at least the client is calling 'consume'.
We don't get any other debug messages in the log file (even a log message
called immediately after calling consume).
We don't think we are getting any client timeout errors (that is checked in
the consume method but not shown in the above code) and in any case the job
is failing very quickly. We are taking the default timeout (120 seconds)
(we will provide a timeout in the next release) and the max_reserves error
is occurring within seconds.
So, the hypothesis is that the client is crashing (even though we don't get
any error messages in the log file).
I note from a separate question in this mailing list that a possible cause
is 'the client connection to the server closes'. Is there anything I would
expect to see in a log file that I could check for this happening?
Kind Regards
Ian
--
You received this message because you are subscribed to the Google Groups
"beanstalk-talk" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/beanstalk-talk/-/XWJpE5arDlIJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/beanstalk-talk?hl=en.
