I noticed that when the NFS snapshot repo is unavailable during the elasticsearch service startup (e.g. is not mounted) the service refuses to start.
Is this the expected behavior?
I'd guess that issuing a warning and refusing the create a snapshot (obviously) would be better than refusing to start up at all. I mean, even if you ensure that the repo is available at startup it might become unavailable while the service is running and creating a snapshot would fail again...