I just realised my automatic creating and destroying of snapshots does not work as expected. There are 2 old snapshots stuck I can not delete. All newer snapshots are created and destroyed as expected.
I created them with an older version (should be 1.7) and upgraded to 2.2
This is what I get:
[root@sally ~]# curl -XDELETE http://localhost:9200/_snapshot/backup/snapshot_2015.10.05?pretty
{
"error" : {
"root_cause" : [ {
"type" : "not_x_content_exception",
"reason" : "Compressor detection can only be called on some xcontent bytes or compressed xcontent bytes"
} ],
"type" : "not_x_content_exception",
"reason" : "Compressor detection can only be called on some xcontent bytes or compressed xcontent bytes"
},
"status" : 500
}
[root@sally ~]# rpm -q elasticsearch
elasticsearch-2.2.1-1.noarch
Since this is my personal half playground/half production cluster consisting of just one node I could destroy all snapshots or even freshly install elasticsearch but I definitely would like to know what to do when I get this in a more critical setup.
To be honest, I just deleted the whole repository and started from scratch. Since this was just my personal system it did not hurt as much as on an production system.
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.