Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support retention of state across zillabase start zillabase stop #124

Open
jfallows opened this issue Oct 28, 2024 · 0 comments
Open

Support retention of state across zillabase start zillabase stop #124

jfallows opened this issue Oct 28, 2024 · 0 comments
Assignees
Labels
story Feature description from user's perspective

Comments

@jfallows
Copy link
Contributor

Describe the desired outcome from the user's perspective
As devops, I want to be able to restart zillabase without losing state.

Acceptance criteria

  • State of services should be consistent before and after zillabase restart
    • risingwave
    • karapace
    • apicurio
    • kafka

Additional context
We can use docker compose volumes, and notify the user on zillabase stop that they are being used.
We may also need an option on zillabase start to clean out any old state first.
Some services that are currently in-memory only may need to be reconfigured to support retention of state across restart.

@jfallows jfallows added the story Feature description from user's perspective label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story Feature description from user's perspective
Projects
None yet
Development

No branches or pull requests

2 participants