Open andig opened 7 months ago
We generally don't recommend autostopping machines with LiteFS. Is this the tutorial you were following?
I was following this and then on to https://github.com/superfly/litefs-example/tree/main/fly-io-config. Noticed the problem when one of the small machines went away due to being idle.
We generally don't recommend autostopping machines with LiteFS.
I was assuming that the LiteFS Proxy (or the Fly Loadbalancer?) uses the Consul information to direct the request to a running instance. Maybe that's just not how it works.
Migrated from https://github.com/superfly/litefs-example/issues/10
I'm new to
litefs
and following the example tutorial. The demo application comes up on fly but is unstable. It will serve a few requests and then go into sporadicIt seems as if this is cause by the application auto-scaling the second, cloned machine away:
I assume this is due to the proxy trying to connect to the downscaling machine. As such, the second machine would decrease availability, at least when auto-scaling.
Is this the expected behaviour of the proxy?