The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Bug #10442

Delayed job failures are not cleared when clearing jobs with 'rake jobs:clear'. Using "Mark all as read" hangs with large number of failures.

Added by Steven Seed over 4 years ago. Updated about 4 years ago.

Status:AcceptedStart date:11/01/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Keywords: Affected URL:
Branch: Affected Dashboard version:

Description

I have a ton of delayed job failures in my dashboard under background tasks. They are mostly failed imports of report yaml files that were deleted (using the ‘rake jobs:clear’ command. There are over 40000 of them so I can’t use the “Mark all as read” button because it causes dashboard to hang forever (or longer than I’m willing to wait). I originally used the ‘rake jobs:clear’ command to clear out all pending delayed jobs that had built up over time. That’s when they appeared in the “delayed_jobs_failures” list ie. “Background Task Failures”. My problem is the log of failed jobs is so large that I can’t clear them properly.

delayed_job_failures.png - screen capture of failed tasks window (50.5 KB) Steven Seed, 11/01/2011 04:36 pm

History

#1 Updated by Nigel Kersten over 4 years ago

  • Status changed from Unreviewed to Accepted
  • Target version set to 173

From the list discussion:

Luke Bigum:

FYI this is a lot faster to delete everything from a MySQL table:

TRUNCATE TABLE delayed_job_failures;

This should be a relatively simple rake task to put in place.

#2 Updated by Anonymous about 4 years ago

  • Target version deleted (173)

Also available in: Atom PDF