Skip to content

More optimal way to cleanup/delete blob from external storage, with tradeoff #146

Description

@longquanzheng

Currently the blobs are only deleted after the whole workflow's history are deleted (all runs -- including runs from continueAsNew, reset and IDReusePolicy).

This is the safest way, mainly because Temporal/Dex support "Reset/TimeTravel" API to go back to any previous point of the history.

But this could potentially lead to some extra storage cost that user may want to optimize.

E.g. if user can accept that they won't reset to any point before X days ago, then we can delete the blobs more aggresively -- we could find the closed runs that closed more than X days ago, if any of the blobs are no longer be used in next run, then they can be safely deleted.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions