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

Improve documentation on snapshot restore using URL (read-only) repository #16280

Closed
ppf2 opened this issue Jan 27, 2016 · 8 comments · Fixed by #56920
Closed

Improve documentation on snapshot restore using URL (read-only) repository #16280

ppf2 opened this issue Jan 27, 2016 · 8 comments · Fixed by #56920
Assignees
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >docs General docs changes Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. Team:Docs Meta label for docs team

Comments

@ppf2
Copy link
Member

ppf2 commented Jan 27, 2016

A few documentation improvement suggestions based on user experience in the field:

  • Will be nice to add a cross reference to setting up read only url repository from the restore section of the guide.
  • Providing an example (eg. for file protocol) will be nice.
PUT /_snapshot/my_restore_repo
{
  "type": "url",
  "settings": {
    "url": "file:///nfs/path"
  }
}
  • When setting up a read-only repository, only setting up repositories.url.allowed_urls is sufficient. The statements below suggests that path.repo is also required.

"URL Repository supports the following protocols: "http", "https", "ftp", "file" and "jar". URL repositories with http:, https:, and ftp: URLs has to be whitelisted by specifying allowed URLs in the repositories.url.allowed_urls setting. "
"URL repositories with file: URLs can only point to locations registered in the path.repo setting similar to shared file system repository."

@ppf2 ppf2 added >docs General docs changes :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs labels Jan 27, 2016
@clintongormley clintongormley added the help wanted adoptme label Jan 28, 2016
@frederikbosch
Copy link
Contributor

I dont get the purpose of this method at all. Could someone dxplain it?

@clintongormley
Copy link
Contributor

@frederikbosch you can make snapshots available to the public (or privately to others) via a read-only URL repository.

@frederikbosch
Copy link
Contributor

@clintongormley Alright, but how is that achieved? Is the data pushed to some other location?

@frederikbosch
Copy link
Contributor

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.

@clintongormley
Copy link
Contributor

@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

@frederikbosch
Copy link
Contributor

@clintongormley Thanks for your answers! That is really helpful.

@BaranOrnarli
Copy link

@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.

@debadair
Copy link
Contributor

[docs issue triage]

@rjernst rjernst added Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. Team:Docs Meta label for docs team labels May 4, 2020
@jrodewig jrodewig self-assigned this May 15, 2020
@elastic elastic deleted a comment from wchrisdean May 18, 2020
@elastic elastic deleted a comment from wchrisdean May 18, 2020
@elastic elastic deleted a comment from wchrisdean May 18, 2020
jrodewig added a commit that referenced this issue May 27, 2020
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
jrodewig added a commit that referenced this issue May 27, 2020
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
jrodewig added a commit that referenced this issue May 27, 2020
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
jrodewig added a commit that referenced this issue May 27, 2020
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >docs General docs changes Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. Team:Docs Meta label for docs team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants