Periodic OnlyOffice cache eviction (no manual rm needed) #13
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_office#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Symptom
OnlyOffice's
/var/lib/onlyoffice/documentserver/App_Data/cache/files/data/grows without bound. Every distinct doc_key leaves anEditor.bin+origin.<ext>. Across weeks of dev + multiple users, this eats disk silently. Manualrm -rfis the only current cure (and it's documented as a poisoned-cache fix, not a maintenance task).Cause
No automatic eviction policy. OnlyOffice itself doesn't manage cache lifetime — the host system is expected to.
Proposed fix
Periodic prune, either in
hero_office_server(background task, runs hourly) or as a hero_proc job spawned byservice_onlyoffice.nu. Policy:App_Data/cache/files/data/<key>/(context, filename)from the doc_key map; if the source file's mtime is older than N days (default 7), delete the cache entry.Acceptance
cache_statsRPC method.