Snapshot with multiple indices fails on closed one


(Slavomir Kundrik) #1

Hi,

I'm trying to do a backup of indices using wildcard where some are closed and I get error (see below). I'm using version 2.0.0.

Is this expected or is it a bug?


Request:

PUT /_snapshot/logstash_backup/snapshot_2015.11.19_00
{
  "indices": "logstash*",
  "ignore_unavailable": true,
  "include_global_state": false,
  "partial": false
}

Response:

{
  "error": {
    "root_cause": [
       {
          "type": "cluster_block_exception",
          "reason": "blocked by: [FORBIDDEN/4/index closed];"
       }
    ],
    "type": "cluster_block_exception",
    "reason": "blocked by: [FORBIDDEN/4/index closed];"
  },
  "status": 403
}

(Mark Walkom) #2

The docs state;

The snapshot request also supports the ignore_unavailable option. Setting it to true will cause indices that do not exist to be ignored during snapshot creation. By default, when ignore_unavailable option is not set and an index is missing the snapshot request will fail.

But they don't really specify what they mean by indices that do not exist, and even though closed indices exist, I'd have thought that they'd fall under the ignore parameter as well. I will see if I can someone to comment on this a bit further.


(Slavomir Kundrik) #3

Judging by this API conventions doc fur multiple indices

ignore_unavailable
Controls whether to ignore if any specified indices are unavailable, this includes indices that don’t exist or closed indices. Either true or false can be specified.

I'm inclined to believe it should work on closed as well.


(system) #4