Periodically purge disposals

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
backend

Research direction

Start by tracing how disposal information is stored during an active workflow session and how nodes are revisited. Define a concrete retention policy for old or repeated disposals, then verify that long-running sessions no longer accumulate them without bound while retaining the required latest information.

Written by the indexing model from the issue text.

Description

For very long-running tasks it's possible that disposal information may pile up arbitrarily high without being helpful. This could especially be a problem if a workflow is used as the main loop of an application.

We should provide a way for disposals to be periodically purged even while a workflow session is still active, especially for disposals that are very old or whose nodes have been revisited.

Perhaps we could choose to only retain the latest disposal of a node per session, or put a cap on how many disposals are stored per node per session.

Dominant language
Rust
Stars
75
Forks
18
Avg merge
12d 12h
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-rmf/crossflow

All issues in open-rmf/crossflow

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.