Unable to delete snapshot

Hi!

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.

Thanks in advance,
Thomas

By the way, it's the same, when I try to view all snapshots.

[root@sally ~]# curl -XGET http://localhost:9200/_snapshot/backup/_all?pretty
{
  "error" : {
    "root_cause" : [ {
      "type" : "snapshot_exception",
      "reason" : "[backup:snapshot_2015.10.05] failed to get snapshots"
    } ],
    "type" : "snapshot_exception",
    "reason" : "[backup:snapshot_2015.10.05] Snapshot could not be read",
    "caused_by" : {
      "type" : "snapshot_exception",
      "reason" : "[backup:snapshot_2015.10.05] failed to get snapshots",
      "caused_by" : {
        "type" : "not_x_content_exception",
        "reason" : "Compressor detection can only be called on some xcontent bytes or compressed xcontent bytes"
      }
    }
  },
  "status" : 500
}

Hi,

did you receive any feedback or found a solution? I'm stuck with this problem too and found no solutioin yet (Backups fail with exception concerning "Compressor detection" after upgrade)

Thanks,
edi

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.

Sorry.