Skip to content

Add retention/cleanup policy for FileRecord #162

Description

@razam-sherwani

Dependency: READY — start now. No blockers. Genuinely low priority until #160 raises match volume, since the storage growth this bounds is proportional to scrim traffic.

Every match writes a compressed FileRecord (replays, submissions) with no cleanup path. LocalStorageService has deleteRecord/deletePhysicalFile helpers but nothing calls them on a schedule or age threshold — confirmed via search, the only two @Scheduled jobs in the codebase (StaleGameMatchRescheduler, ScheduledMatchMaker) are unrelated to file lifecycle.

Add a retention policy (age-based or count-based) and a scheduled job to enforce it, to bound storage growth as match volume increases (relevant once server-side scrimmage, #160, increases match volume significantly).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Low priorityenhancementNew feature or requestreadyNo open blockers - can be started now

    Type

    No type

    Fields

    Stage

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions