# Can't undersand curator dry-run logs

**URL:** <https://discuss.elastic.co/t/cant-undersand-curator-dry-run-logs/164909>\
**Category:** Elasticsearch\
**Created:** [January 19, 2019, 8:01pm UTC](https://discuss.elastic.co/t/cant-undersand-curator-dry-run-logs/164909 "2019-01-19T20:01:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![memelet](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@memelet](https://discuss.elastic.co/u/memelet)\
**Post date:** [January 19, 2019, 8:01pm UTC](https://discuss.elastic.co/t/cant-undersand-curator-dry-run-logs/164909/1 "2019-01-19T20:01:58Z")

</div>

I am running a force\_merge in dry-run and getting logs like below. I can't seem to tell if curator would have run the action or not. (I know what _I_ think it should do. But what does _curator_ think it should do?)

```auto
  "_source": {
    "elasticsearch_cluster": "ingest",
    "host": "p-ingest-elasticsearch-master-1",
    "host_role": "elasticsearch-master",
    "component": "curator.utils",
    "message": "DRY-RUN: allocation: connect-v3-sicom-sicom-mtconnectdataitems-2019.01.08-000001 with arguments: {'body': {'index.routing.allocation.include.node_class': 'warm'}}",
    "@version": "1",
    "@timestamp": "2019-01-19T19:51:42.472Z",
    "env": "production",
    "type": "curator",
    "level": "INFO",
    "name": "curator",
    "path": "/log/curator.log",
    "function": "show_dry_run",
    "linenum": 927
  },

```

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [January 19, 2019, 8:23pm UTC](https://discuss.elastic.co/t/cant-undersand-curator-dry-run-logs/164909/2 "2019-01-19T20:23:53Z")

</div>

> [@memelet](#):
>
> ```auto
> "DRY-RUN: allocation: connect-v3-sicom-sicom-mtconnectdataitems-2019.01.08-000001 with arguments: {'body': {'index.routing.allocation.include.node_class': 'warm'}}"
> 
> ```

Not sure where force-merge enters in, but this is saying that Curator _would_ have applied index shard allocation routing settings to `include` tag/key `node_class` with value `warm` to index `connect-v3-sicom-sicom-mtconnectdataitems-2019.01.08-000001`.

---

<div class="post-metadata">

**Author:** ![memelet](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@memelet](https://discuss.elastic.co/u/memelet)\
**Post date:** [January 20, 2019, 12:15am UTC](https://discuss.elastic.co/t/cant-undersand-curator-dry-run-logs/164909/3 "2019-01-20T00:15:18Z")

</div>

Ah, sorry. I had two actions, mixed up the log I pasted.

So when there exists a log like this it means it would have applied the action? No log and the action would not have been applied?

I was confused I guess because of how the rollover API works -- it shows each consideration with the results of the conditions. It would be really nice if curator could do something similar.

---

<div class="post-metadata">

**Author:** ![memelet](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@memelet](https://discuss.elastic.co/u/memelet)\
**Post date:** [January 23, 2019, 8:29pm UTC](https://discuss.elastic.co/t/cant-undersand-curator-dry-run-logs/164909/4 "2019-01-23T20:29:12Z")

</div>

I think I still don't understand. Consider index connect-v3-x-x-mtconnectdataitems-201812/\_settings

```auto
    "settings" : {
      "index" : {
        "routing" : {
          "allocation" : {
            "include" : {
              "node_class" : "warm"
            }
          }
        },

```

And curator filters

```auto
actions:
  1:
    action: replicas
    description: Reduce replicas before moving to warm
    options:
      count: 1
      ignore_empty_list: true
      wait_for_completion: true
    filters:
      - filtertype: allocated
        key: node_class
        value: hot
        allocation_type: include
      - filtertype: pattern
        kind: prefix
        value: connect-
      - filtertype: age
        source: field_stats
        direction: older
        unit: days
        unit_count: 30
        field: timestamp
        stats_result: min_value

```

The 'allocated' filter specifies 'hot', where index is 'cold'.

Yet the curators say it will fire on that index for this action?

```auto
DRY-RUN: replicas: connect-v3-x-x-mtconnectdataitems-201812 with arguments: {'count': 1}

```

---

<div class="post-metadata">

**Author:** ![memelet](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@memelet](https://discuss.elastic.co/u/memelet)\
**Post date:** [January 23, 2019, 8:46pm UTC](https://discuss.elastic.co/t/cant-undersand-curator-dry-run-logs/164909/5 "2019-01-23T20:46:26Z")

</div>

Reading thru [Curator "allocated" filtertype does not seem to work](https://discuss.elastic.co/t/curator-allocated-filtertype-does-not-seem-to-work/118899/8)

I didn't get that exclude default is per filter type. I see now.

---

<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, 2019, 8:46pm UTC](https://discuss.elastic.co/t/cant-undersand-curator-dry-run-logs/164909/6 "2019-02-20T20:46:28Z")

</div>

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