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
Doesn't seem to retry Timeout::Error #72
Comments
I guess same question on |
I'm also experiencing this issue. When my job get s a timeout exception it is not retried and put in the failed queue. |
+1 |
anyone figured this out? I tried standarderror, i tried being explicit with AWS::S3::Errors::RequestTimeout.... no luck. |
+1 still seeing this.... |
Can anyone (other then @barmstrong) provide some more details:
Bonus points if you provide a pull request with a test case! (even without a fix) |
Ruby 2.0.0 class SyncChannel |
@Proletarian I vaguely recall dealing w/ this exact issue at a previous company. But I can't remember the fix for the life of me. Let me reach out to them tomorrow and see if anyone can locate what we did to fix it. |
I'm using
extend Resque::Plugins::ExponentialBackoff
with the default retry schedule and it works great normally, but it seems likeTimeout::Error
is not being retried. In other words, I'm quite sure the service was up during one of the 6 attempts over the 6 hour time window. And when I manually retry the job from the failed job queue, it works right away.I remember there was some issues back in the day with ruby where certain exceptions would subclass
Error
instead ofException
or something along those lines. But it seems like that is not a problem here:Can you think of any reason Timeout::Error wouldn't be getting retried? Thanks!
The text was updated successfully, but these errors were encountered: