-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Improve documentation on snapshot restore using URL (read-only) repository #16280
Comments
I dont get the purpose of this method at all. Could someone dxplain it? |
@frederikbosch you can make snapshots available to the public (or privately to others) via a read-only URL repository. |
@clintongormley Alright, but how is that achieved? Is the data pushed to some other location? |
My case is that I want to push the backup directly (without hitting the local fs) to another location (over HTTPS over FTPS/SFTP). And I thought that this backup type might be useful. For me S3, HDFS and Azure are not an option. |
@frederikbosch no, it's read only. it's for making read only copies available to others, not for making the snapshots yourself. we don't have an http only writable repository |
@clintongormley Thanks for your answers! That is really helpful. |
@clintongormley is there no way to transfer a local zipped folder (generated via _snapshot "fs") to ES Master node, then distribute it across the ES cluster without "shared drives"? I was looking for a way to simply point to a "local filesystem repo" and have the Master ES node distribute it into the cluster or _snapshot-restore it by reading the local filesystem (read-only). The "Type: 'fs'" ES-repo requires a COPY of the folder in EACH datanode/masternode which is really difficult with one folder/zip that is gigantic. |
[docs issue triage] |
Makes following changes to better clarify docs for read-only URL snapshot repositories: * Adds an example snippet for registering a URL repository * Rewrites the protocols paragraph * Adds a note to explicitly point out that only URLs using the `ftp`, `http`, `http`, and `jar` protocols do not need the `path.repo` setting. Fixes #16280
Makes following changes to better clarify docs for read-only URL snapshot repositories: * Adds an example snippet for registering a URL repository * Rewrites the protocols paragraph * Adds a note to explicitly point out that only URLs using the `ftp`, `http`, `http`, and `jar` protocols do not need the `path.repo` setting. Fixes #16280
Makes following changes to better clarify docs for read-only URL snapshot repositories: * Adds an example snippet for registering a URL repository * Rewrites the protocols paragraph * Adds a note to explicitly point out that only URLs using the `ftp`, `http`, `http`, and `jar` protocols do not need the `path.repo` setting. Fixes #16280
Makes following changes to better clarify docs for read-only URL snapshot repositories: * Adds an example snippet for registering a URL repository * Rewrites the protocols paragraph * Adds a note to explicitly point out that only URLs using the `ftp`, `http`, `http`, and `jar` protocols do not need the `path.repo` setting. Fixes #16280
A few documentation improvement suggestions based on user experience in the field:
The text was updated successfully, but these errors were encountered: