Reap finished job rows on the maintenance tick #180

Open
opened 2026-08-12 03:05:27 +00:00 by rosa · 0 comments
Owner

Nothing removes Done/Killed rows from the job store, so it grows for the life of a deployment (Steady State). This predates the apalis v1 upgrade but the separate jobs database (#177) makes it visible. apalis v1 exposes a vacuum operation on backends; wire it into the existing daily database-maintenance tick and decide retention — immediate reaping vs keeping recent failures for inspection.

Nothing removes Done/Killed rows from the job store, so it grows for the life of a deployment (Steady State). This predates the apalis v1 upgrade but the separate jobs database (#177) makes it visible. apalis v1 exposes a vacuum operation on backends; wire it into the existing daily database-maintenance tick and decide retention — immediate reaping vs keeping recent failures for inspection.
rosa added this to the v0.2 milestone 2026-08-12 03:23:30 +00:00
rosa modified the milestone from v0.2 to Apalis 1.0 2026-08-12 03:44:16 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rosa/vernier#180
No description provided.