My index write api request blocked by status 403 after adding index lifecycle policy

Elastic Stack Elasticsearch
1

This is what happened today.

  1. I'm using index without life cycle management. The index name is "vehicle-iot-coordinate", it's size is about 280GB and it grow with rate of 1GB/day.
  2. I'm adding lifecycle management. (disable rollover, only has hot, frozen, delete phase. Move data to frozen after 14 days,.)
  3. As soon as I adding ILM, my hot instance's disk allocation is spiked to 100%, so I doubled my instance size.
  4. After the deployment is successful, my server raise error.
{
  "error": {
    "root_cause": [
      {
        "type": "cluster_block_exception",
        "reason": "index [partial-vehicle-iot-coordinate] blocked by: [FORBIDDEN/8/index write (api)];"
      }
    ],
    "type": "cluster_block_exception",
    "reason": "index [partial-vehicle-iot-coordinate] blocked by: [FORBIDDEN/8/index write (api)];"
  },
  "status": 403
}

I already did the api with this.

{
  "index.blocks.read_only_allow_delete": null,
  "index.blocks.write": null
}

But it raise this error.

{
    "error": {
        "root_cause": [
            {
                "type": "illegal_argument_exception",
                "reason": "illegal value can't update [index.blocks.write] from [true] to [false]"
            }
        ],
        "type": "illegal_argument_exception",
        "reason": "illegal value can't update [index.blocks.write] from [true] to [false]",
        "caused_by": {
            "type": "illegal_argument_exception",
            "reason": "Cannot remove write block from searchable snapshot index"
        }
    },
    "status": 400
}

Please help.

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.