Enhancement: transfer searchable snapshot to new snapshot repository

jguay commented 1 year ago

Description

Current functionality

In the context of Elasticsearch Services cloud offering, when changing a deployment between regions or cloud providers, it is necessary to use a custom repository per documentation
When using searchable snapshot backed by found-snapshots; this is not supported and will cause red cluster on all fully/partially mounted indices because snapshot of the custom repository will only contains pointers to the repository UUID and location for searchable snapshots - found-snapshots of the source cluster is not accessible so there is no support to restore a deployment to a different Region

Error from GET _cluster/allocation will contain for cold or frozen nodes :

"explanation": "this index is backed by a searchable snapshot in a repository with UUID [<someUUID>] but no such repository is registered with this cluster; the required repository was originally named [found-snapshots]"

Requested functionality

Snapshot transfer functionality similar to clone snapshot API but where destination of the snapshot to write is a different snapshot repository

elasticsearchmachine commented 1 year ago

Pinging @elastic/es-distributed (Team:Distributed)

kingherc commented 1 year ago

I believe this also relates to https://github.com/elastic/elasticsearch/issues/89696#issuecomment-1237116957 where we discuss the possibility of updating an existing repository to a different location.

singhvirohan commented 4 months ago

@elastic/es-distributed we had a customer reach out asking for an update on this issue and whether there's been any conversations or plans to have this enhancement made available. Can you please share any inputs you may have and if there's a different ticket/channel to be following for this?

DaveCTurner commented 3 months ago

Hi @singhvirohan, there are no updates to share, nor do we currently have any plans to work on this. This is the right issue to follow.

elastic / elasticsearch