Skip to content

[aspire] Managed Garnet starts with no persistence flag #2636

Closed

Description

@rickylabs

Summary

The managed Garnet resource is launched with the Lua flags only. No append-only file, checkpoint or recovery option is set, so queued jobs, saga messages and timers are lost when the container restarts, even when a data directory is mounted.

Evidence (main at b0eb079, same on v0.0.9)

  • packages/cli/src/kernel/templates/aspire/helpers/register/generate-register-infrastructure.ts:34: GARNET_LEASE_ARGS = ['--lua', '--lua-transaction-mode'].
  • Lines 486-540 of the same file pass those arguments and an optional /data bind mount. No --aof, --checkpointdir or --recover argument is generated.

Expected behavior

When a data path is configured, managed Garnet starts with persistence on and recovers its data at start. Without a data path the cache stays ephemeral, and the docs say so.

Acceptance

  • With a data path, the generated launch enables the append-only file, stores AOF and checkpoints under the mounted directory, and recovers on start.
  • A runtime test enqueues a job, restarts the Garnet container and sees the job delivered.
  • Without a data path the launch is unchanged.
  • The docs state the durability of each mode.

Acceptance verified by #2643 (comment). Full PR runtime/evaluation gates remain tracked in the PR.

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

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions