Closed Bug 1475610 Opened 7 years ago Closed 7 years ago

Unhandled error in async rendering when rendering is already in progress

Categories

(developer.mozilla.org Graveyard :: General, enhancement, P3)

All
Other
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jwhitlock, Unassigned)

Details

(Keywords: in-triage, Whiteboard: [specification][type:bug][points=1])

What did you do? ================ Several times a week, the render_document async task fails, because the Document already has a render in progress. What happened? ============== The Document.render task raises a DocumentRenderingInProgress exception. The task attempts to email this to admins, which fails to render as an email. What should have happened? ========================== The async task should not attempt to render a document that is already in progress, or should handle this exception. The task should also not attempt to email admins, but instead should log exceptions to Sentry (bug 1428086). Is there anything else we should know? ======================================
Keywords: in-triage
Priority: -- → P3
Whiteboard: [specification][type:bug] → [specification][type:bug][points=1]
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/2ea0f9c002d2e4684dc3dee889ff5bd47c4ef9dc bug 1475610: Handle DocumentRenderingInProgress Do not attempt to email admins when a DocumentRenderingInProgress exception is raised by the render function. Also, pass the string version of the exception to mail_admins. https://github.com/mozilla/kuma/commit/e45937d93bc2939fe82b4e7914b27b5cb1536cfa Merge pull request #5003 from jwhitlock/rendering-task-1475610 bug 1475610: Handle DocumentRenderingInProgress
This code is live in production, and the errors have been silenced. The new issues are bug 1500766 (MySQL server has gone away) and bug 1500769 (DNS lookup failure for database).
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.