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

Does FT mode w/ a SQL store still require a ReadWriteMany filesystem? #95

Closed
leefernandes opened this issue Jul 30, 2020 · 3 comments
Closed

Comments

@leefernandes
Copy link

The doc below mentions Fault Tolerant mode requiring a ReadWriteMany filesystem, my question is whether that requirement is for all storage types, or just when using a File store? Would using a SQL store still require a ReadWriteMany filesystem?

Thanks

https://docs.nats.io/nats-on-kubernetes/stan-ft-k8s-aws

"First, we need a Kubernetes cluster with a provider that offers a service with a ReadWriteMany filesystem available."

@wallyqs
Copy link
Member

wallyqs commented Jul 30, 2020

That guide is for when using FaultTolerance mode and file storage, you could use SQL storage as well with FaultTolerance.

@wallyqs wallyqs transferred this issue from nats-io/nats-streaming-server Jul 30, 2020
@leefernandes
Copy link
Author

Thanks!

@hpdobrica
Copy link

Not sure if i understood your response @wallyqs, but basically if I use SQL storage i dont need to mount a ReadWriteMany filesystem?

I did some tests and STAN seems to be working fine without it. I even mounted it just in case and i see that nothing is written on it. I might be wrong since i didn't do some super extensive testing, just ran STAN and checked the storage volume which was empty (was getting filled with cluster mode by this point though).

If what i said above is true, should the docs linked below be edited not to say
# FT mode requires a single shared ReadWriteMany PVC volume.
if the volume is only required if using file storage option?

https://github.com/nats-io/k8s/tree/master/helm/charts/stan#fault-tolerance-mode

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

3 participants