You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
I deployed opendistro es with helm to AKS with custom image having repository azure plugin. AZ plugin installed, however when added the azure blob storage account and key in elasticsearch.yml inside the elastic container and restarted the elasticsearch, not able to create snapshot repository.
PUT _snapshot/elastic_blob
{
"type": "azure"
}
Error below
{
"error" : {
"root_cause" : [
{
"type" : "settings_exception",
"reason" : "Unable to find client with name [default]"
}
],
"type" : "repository_verification_exception",
"reason" : "[elastic_blob] path is not accessible on master node",
"caused_by" : {
"type" : "settings_exception",
"reason" : "Unable to find client with name [default]"
}
},
"status" : 500
}
The text was updated successfully, but these errors were encountered:
It looks like it's not able to see the keys you added, or you configured them wrong (it looks for keys for the default client). It would be useful to know how you added them (example) and what version of Elasticsearch you are on.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I deployed opendistro es with helm to AKS with custom image having repository azure plugin. AZ plugin installed, however when added the azure blob storage account and key in elasticsearch.yml inside the elastic container and restarted the elasticsearch, not able to create snapshot repository.
PUT _snapshot/elastic_blob
{
"type": "azure"
}
Error below
{
"error" : {
"root_cause" : [
{
"type" : "settings_exception",
"reason" : "Unable to find client with name [default]"
}
],
"type" : "repository_verification_exception",
"reason" : "[elastic_blob] path is not accessible on master node",
"caused_by" : {
"type" : "settings_exception",
"reason" : "Unable to find client with name [default]"
}
},
"status" : 500
}
The text was updated successfully, but these errors were encountered: