# Hot/Warm Index Allocation Failing due to Other Shard Allocation

**URL:** <https://discuss.elastic.co/t/hot-warm-index-allocation-failing-due-to-other-shard-allocation/116721>\
**Category:** Elasticsearch\
**Created:** [January 23, 2018, 5:17pm UTC](https://discuss.elastic.co/t/hot-warm-index-allocation-failing-due-to-other-shard-allocation/116721 "2018-01-23T17:17:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)\
**Post date:** [January 23, 2018, 5:17pm UTC](https://discuss.elastic.co/t/hot-warm-index-allocation-failing-due-to-other-shard-allocation/116721/1 "2018-01-23T17:17:08Z")

</div>

I have a [hot/warm architecture](https://www.elastic.co/blog/hot-warm-architecture-in-elasticsearch-5-x) in ES 5.6.2. This architecture is in place for certain high IO indices; primarily Nginx indices. After two days, I use Curator to update the index requirements from:

```auto
            "require": {
              "box_type": "hot"
            }

```

to:

```auto
            "require": {
              "box_type": "warm"
            }

```

to force the indices to be allocated away from my precious SSDs and onto spinning disks. This has worked fantastically up until recently when I lost a node and the whole cluster rebalanced. Now I have other indexes taking allocation priority over my Nginx indexes. This causes the SSDs to fill up and ingestion comes to a grinding halt.

Does anyone know how to prioritize the allocation of these indices? More importantly, I'm looking to prioritize the allocation of hot =\> warm Nginx indices, which are also indices created within the last few days. I'm looking at the [shard balancing settings](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/shards-allocation.html#_shard_balancing_heuristics), but unsure if I can do anything except make all Nginx indices the highest priority (Nginx indices on HDDs; `"box_type": "warm"` should be lower priority than Nginx indices on SSDs; `"box_type": "hot"`).

When I run curator: `curator --config curator.yml allocate-nginx-3day.yml`, I get the following trace:

```auto
2018-01-23 10:17:56,407 DEBUG curator.utils health_check:1492 KWARGS= "{'relocating_shards': 0}"
2018-01-23 10:17:56,418 DEBUG curator.utils health_check:1506 NO MATCH: Value for key "0", health check data: 2
2018-01-23 10:17:56,418 DEBUG curator.utils wait_for_it:1726 Response: False
2018-01-23 10:17:56,418 DEBUG curator.utils wait_for_it:1746 Action "allocation" not yet complete, 1015 total seconds elapsed. Waiting 3 seconds before checking again.
2018-01-23 10:17:59,419 DEBUG curator.utils wait_for_it:1723 Elapsed time: 1018 seconds

```

My curator config:

```auto
---
client:
  hosts:
    - 127.0.0.1
  port: 9200
  url_prefix:
  use_ssl: False
  certificate:
  client_cert:
  client_key:
  ssl_no_validate: False
  http_auth:
  timeout: 30
  master_only: False

logging:
  loglevel: DEBUG
  logfile:
  logformat: default
  blacklist: ['elasticsearch', 'urllib3']

```

Allocation script:

```auto
actions:
  1:
    action: allocation
    description: "Apply shard allocation filtering rules to the specified indices"
    options:
      key: box_type
      value: warm
      allocation_type: require
      wait_for_completion: true
      timeout_override:
      continue_if_exception: false
      disable_action: false
    filters:
    - filtertype: pattern
      kind: prefix
      value: nginx-
    - filtertype: age
      source: name
      direction: older
      timestring: '%Y.%m.%d'
      unit: days
      unit_count: 2

```

Cluster settings:

```auto
{
  "persistent": {
    "cluster": {
      "routing": {
        "allocation": {
          "allow_rebalance": "always",
          "cluster_concurrent_rebalance": "2",
          "node_concurrent_recoveries": "2",
          "disk": {
            "watermark": {
              "low": "95%",
              "high": "98%"
            }
          }
        }
      }
    }
  },
  "transient": {}
}

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 20, 2018, 5:17pm UTC](https://discuss.elastic.co/t/hot-warm-index-allocation-failing-due-to-other-shard-allocation/116721/2 "2018-02-20T17:17:16Z")

</div>

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