I feel like the Snapshot documentation is not clear on if it is possible to register a repository locally on a member of a cluster (master) without this being accessible from the other members (non-masters).
A snapshot is a backup taken from a running Elasticsearch cluster. You can take snapshots of individual indices or of the entire cluster. Snapshots can be stored in either local or remote repositories. Remote repositories can reside on S3, HDFS, Azure, Google Cloud Storage, and other platforms supported by a repository plugin.
You can take snapshots of individual indices or of the entire cluster. Snapshots can be stored in either local or remote repositories.
The above could be interpreted as you can take snapshot of a cluster locally on a node, without that repository needed be be accessible from the other members of the cluster.
Then concretely about fs repository types, it talks about Shared file system repositories as if it was a different thing to a local file system.
I sais for a shared files system the same location must be mounted on all members of the cluster but It does not specify clearly that a shared file system is required in an cluster as opposed to a local filesystem.
I find the language a bit vague and misleading.
The only way I knew how to interpret the documentations was by digging in to external tutorials, examples and ticket.
Could you please try and make this section of the Documentation a bit more concise.
Could registering a repository locally on a filesystem that is not shared across the cluster work?
Is there anyway to register a repository locally in the master mode without that repository being accessible from the other cluster members?
Kind regards and thanks.