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

Checkpoint file path in Helm Chart values defaults to /app instead of /data which mounts the PVC. #104

Open
digitalthumbs opened this issue Dec 9, 2024 · 0 comments

Comments

@digitalthumbs
Copy link

Describe the bug
If deploying the replicator using the helm chart requires the deployment of a persistent volume and claim, would it not make more sense to have the default path of the checkpoint file to write to a file within the volume?

This ensures that between helm upgrades and deployments, the replicator will continue from previous state.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy the replicator helm chart to a K8S cluster
  2. Make a configuration change to your deployment.
  3. Re-deploy/upgrade the chart
  4. Restart the replicator.

Expected behavior
The replicator would resume from the checkpoint it left at prior to restarting.

Actual behavior
The replicator restarts replication from the begging, no checkpoint file is found.

EventStore details

  • EventStore server version: 23.10.3

  • Operating system: Kubernetes / Amazon Linux

  • EventStore client version (if applicable):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant