From what I understand, ECE automates creating snapshots by creating a found-snapshots repository which stores the snapshots of all the clusters in a folder described by their cluster id.
And so for Cluster A, its settings would look like
GET <cluster A endpoint>/_snapshot/found_snapshots
{
"type": "s3",
"settings": {
"bucket": "<s3_bucket_name>",
"client": "mys3client",
"secret_key": "<s3_secret_key>",
"base_path": "snapshots/<Cluster A ID>",
"access_key": "<s3_access_key>",
}
}
Is there any way we can update the base_path for cluster A to store snapshots in a folder with a different name instead of its id?
Issuing a PUT command with an updated base path seems to work until the snapshots are fired at its 30 minute interval which causes the base_path to revert back to the cluster id.
Is there a better way to change the base path of a cluster's snapshot location permanently so it is not referred by its cluster id?
That said it's not ideal because a) requires messing about with only-semi-documented advanced cluster data (I believe the 2.x v1 API has better model support but, the UI support is still JSON editing), b) requires pasting access keys in the cluster data etc
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.