Elasticsearch is not returning this error, it's coming from something else in your system applying an unnecessary timeout. The best fix is to remove that timeout. Alternatively you can ignore the error, since the operation will continue in the background. If you like, you can retry it too.
command, i can ignore the timeout error, but as snapshot status endpoint only returns an object when there is a snapshot being taken or if it's being restored.
it's empty if the snapshot is being deleted and there is no other endpoint to track snapshot deletion operations specifically.
Just to reiterate, the real problem is a bad timeout somewhere else in your system, which you can't fix within Elasticsearch. I strongly recommend addressing that rather than trying to work around it.
This message is also not coming from Elasticsearch, and Elasticsearch 7.11 will let you try and delete the same snapshot twice. You should be able to retry the delete until it either succeeds or indicates that the snapshot was not found.
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.