Topic starter
08/07/2026 6:57 pm
TL;DR: Routine cleanup of large action_logs tables can turn into long-running, lock-heavy maintenance that makes instances slow or unusable, according to Passbolt. The operational lesson is that log retention, purge granularity, and maintenance windows must be treated as production controls, not housekeeping.
Editorial analysis by NHI Mgmt Group, based on content published by PassBolt: “Automating Passbolt Maintenance, Part 2: Prepare the first run on large databases”.
Key questions
Q: What breaks when a large action log purge runs without a maintenance window?
A: The purge can hold locks long enough to make the instance slow or unusable, and users may experience delayed logins, stalled queries, or a frozen administration workflow.
Q: When should teams prioritize log retention changes over disk reclamation?
A: Prioritise row deletion first when the immediate problem is performance or table bloat, and treat disk reclamation as a separate step only when storage pressure remains after the purge.
Q: How do you know a purge strategy is too aggressive for the environment?
A: If dry-run estimates suggest a very large deletion, or if the table has grown across years without maintenance, the strategy is too aggressive for one pass.
Practitioner guidance
- Plan purge work in explicit maintenance windows Assume downtime if you are deleting a large volume of logs, and communicate the window before the first purge run begins.
- Run purges in staged retention passes Start with the oldest retention threshold that matches the system age, then step down in smaller passes instead of deleting everything older than one date.
- Separate disk reclamation from row deletion Use OPTIMIZE TABLE only when you truly need filesystem space back, because it can lock the table and require additional free capacity during the rebuild.
Bottom line: Large action log tables can turn maintenance into a service-availability event rather than a routine admin task.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
08/07/2026 7:20 pm
Large audit-log cleanup is a production control, not a housekeeping task. The article shows that once an action log reaches the million-row range, maintenance behaviour changes from routine admin work into a service-availability decision. That shifts the governance question from whether logs should be retained to how retention can be reduced without breaking the system. Practitioners should treat log cleanup as an availability-sensitive control surface.
A question worth separating out:
Q: What should administrators do before rebuilding a large action_logs table?
A: Confirm that the maintenance window is reliable, because a rebuild can lock the table and temporarily require significant extra disk space. If the window is not dependable, defer the rebuild and focus on reducing the log volume safely first.
👉 Read our full editorial: Passbolt maintenance at scale: why large action log purges stall