librelist archives

« back to archive

Retry jobs still in fail queue

Retry jobs still in fail queue

From:
Santosh c
Date:
2011-11-30 @ 14:27
Hi,
When we retry a job and it succeeds why is it still under Failed jobs? Is
there a way to make it go away from the Failed jobs list? Do we need to use
any plugins for that?

thanks.

Re: Retry jobs still in fail queue

From:
Santosh c
Date:
2011-12-02 @ 02:49
Any clue anyone? This will make our life easy, so appreciate any insights
into this. Thanks!

On Wed, Nov 30, 2011 at 7:57 PM, Santosh c <santoshc197@gmail.com> wrote:

> Hi,
> When we retry a job and it succeeds why is it still under Failed jobs? Is
> there a way to make it go away from the Failed jobs list? Do we need to use
> any plugins for that?
>
> thanks.
>

Re: [resque] Re: Retry jobs still in fail queue

From:
Josiah Kiehl
Date:
2011-12-02 @ 02:52
I don't think it makes sense to remove it. Retry copies the job and
requeues it. The failure still happened so it's still in the failure log.
If you want to get rid of it, just hit remove.  You can tell it didn't fail
again because it doesn't add a new entry to the failed queue.

Josiah

On Thu, Dec 1, 2011 at 6:49 PM, Santosh c <santoshc197@gmail.com> wrote:

> Any clue anyone? This will make our life easy, so appreciate any insights
> into this. Thanks!
>
>
> On Wed, Nov 30, 2011 at 7:57 PM, Santosh c <santoshc197@gmail.com> wrote:
>
>> Hi,
>> When we retry a job and it succeeds why is it still under Failed jobs? Is
>> there a way to make it go away from the Failed jobs list? Do we need to use
>> any plugins for that?
>>
>> thanks.
>>
>
>

Re: [resque] Re: Retry jobs still in fail queue

From:
Santosh c
Date:
2011-12-02 @ 04:52
Hi Josiah, the scenario is like this:

we have daily 100,000 jobs of 8 different types. we are still in the
'learning' phase where because of the variation in the job data their
processing fails as we dont handle every scenario yet. So let's say some
5000 jobs of a given type fail, we look at one of them and debug/fix it
using the retry option. However this fixes say only 2000 of these failed
jobs. It is in this situation that we want to "Retry all failed jobs" so
that we can start looking at the other 3000 that will fail again. Currently
this is very tough.

We moved from beanstalkd to resque and are loving the feature of seeing the
failed jobs along with the failure stacktrace in the web UI. However if
there's a way to flush out the succeeded ones from the failed ones after
retry, that will be even more useful. Thank you.

santosh

On Fri, Dec 2, 2011 at 8:22 AM, Josiah Kiehl <bluepojo@gmail.com> wrote:

> I don't think it makes sense to remove it. Retry copies the job and
> requeues it. The failure still happened so it's still in the failure log.
> If you want to get rid of it, just hit remove.  You can tell it didn't fail
> again because it doesn't add a new entry to the failed queue.
>
> Josiah
>
>
> On Thu, Dec 1, 2011 at 6:49 PM, Santosh c <santoshc197@gmail.com> wrote:
>
>> Any clue anyone? This will make our life easy, so appreciate any insights
>> into this. Thanks!
>>
>>
>> On Wed, Nov 30, 2011 at 7:57 PM, Santosh c <santoshc197@gmail.com> wrote:
>>
>>> Hi,
>>> When we retry a job and it succeeds why is it still under Failed jobs?
>>> Is there a way to make it go away from the Failed jobs list? Do we need to
>>> use any plugins for that?
>>>
>>> thanks.
>>>
>>
>>
>

Re: [resque] Re: Retry jobs still in fail queue

From:
Tatsuya Ono
Date:
2011-12-02 @ 10:30
Maybe my plugin can help?
https://github.com/ono/resque-cleaner

It lets you to remove(clear) jobs just after retried (Select Action -
'Retry and Clear').

Tatsuya

On 2 December 2011 04:52, Santosh c <santoshc197@gmail.com> wrote:

> Hi Josiah, the scenario is like this:
>
> we have daily 100,000 jobs of 8 different types. we are still in the
> 'learning' phase where because of the variation in the job data their
> processing fails as we dont handle every scenario yet. So let's say some
> 5000 jobs of a given type fail, we look at one of them and debug/fix it
> using the retry option. However this fixes say only 2000 of these failed
> jobs. It is in this situation that we want to "Retry all failed jobs" so
> that we can start looking at the other 3000 that will fail again. Currently
> this is very tough.
>
> We moved from beanstalkd to resque and are loving the feature of seeing
> the failed jobs along with the failure stacktrace in the web UI. However if
> there's a way to flush out the succeeded ones from the failed ones after
> retry, that will be even more useful. Thank you.
>
> santosh
>
>
> On Fri, Dec 2, 2011 at 8:22 AM, Josiah Kiehl <bluepojo@gmail.com> wrote:
>
>> I don't think it makes sense to remove it. Retry copies the job and
>> requeues it. The failure still happened so it's still in the failure log.
>> If you want to get rid of it, just hit remove.  You can tell it didn't fail
>> again because it doesn't add a new entry to the failed queue.
>>
>> Josiah
>>
>>
>> On Thu, Dec 1, 2011 at 6:49 PM, Santosh c <santoshc197@gmail.com> wrote:
>>
>>> Any clue anyone? This will make our life easy, so appreciate any
>>> insights into this. Thanks!
>>>
>>>
>>> On Wed, Nov 30, 2011 at 7:57 PM, Santosh c <santoshc197@gmail.com>wrote:
>>>
>>>> Hi,
>>>> When we retry a job and it succeeds why is it still under Failed jobs?
>>>> Is there a way to make it go away from the Failed jobs list? Do we need to
>>>> use any plugins for that?
>>>>
>>>> thanks.
>>>>
>>>
>>>
>>
>

Re: [resque] Re: Retry jobs still in fail queue

From:
Santosh c
Date:
2011-12-03 @ 02:09
Thank you! will try it out.

On Fri, Dec 2, 2011 at 4:00 PM, Tatsuya Ono <ononoma@gmail.com> wrote:

> Maybe my plugin can help?
> https://github.com/ono/resque-cleaner
>
> It lets you to remove(clear) jobs just after retried (Select Action -
> 'Retry and Clear').
>
> Tatsuya
>
> On 2 December 2011 04:52, Santosh c <santoshc197@gmail.com> wrote:
>
>> Hi Josiah, the scenario is like this:
>>
>> we have daily 100,000 jobs of 8 different types. we are still in the
>> 'learning' phase where because of the variation in the job data their
>> processing fails as we dont handle every scenario yet. So let's say some
>> 5000 jobs of a given type fail, we look at one of them and debug/fix it
>> using the retry option. However this fixes say only 2000 of these failed
>> jobs. It is in this situation that we want to "Retry all failed jobs" so
>> that we can start looking at the other 3000 that will fail again. Currently
>> this is very tough.
>>
>> We moved from beanstalkd to resque and are loving the feature of seeing
>> the failed jobs along with the failure stacktrace in the web UI. However if
>> there's a way to flush out the succeeded ones from the failed ones after
>> retry, that will be even more useful. Thank you.
>>
>> santosh
>>
>>
>> On Fri, Dec 2, 2011 at 8:22 AM, Josiah Kiehl <bluepojo@gmail.com> wrote:
>>
>>> I don't think it makes sense to remove it. Retry copies the job and
>>> requeues it. The failure still happened so it's still in the failure log.
>>> If you want to get rid of it, just hit remove.  You can tell it didn't fail
>>> again because it doesn't add a new entry to the failed queue.
>>>
>>> Josiah
>>>
>>>
>>> On Thu, Dec 1, 2011 at 6:49 PM, Santosh c <santoshc197@gmail.com> wrote:
>>>
>>>> Any clue anyone? This will make our life easy, so appreciate any
>>>> insights into this. Thanks!
>>>>
>>>>
>>>> On Wed, Nov 30, 2011 at 7:57 PM, Santosh c <santoshc197@gmail.com>wrote:
>>>>
>>>>> Hi,
>>>>> When we retry a job and it succeeds why is it still under Failed jobs?
>>>>> Is there a way to make it go away from the Failed jobs list? Do we need to
>>>>> use any plugins for that?
>>>>>
>>>>> thanks.
>>>>>
>>>>
>>>>
>>>
>>
>