Can't undersand curator dry-run logs

Elastic Stack Elasticsearch
1

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?)

  "_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
  },
2

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.

3

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.

4

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

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

And curator filters

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?

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

Reading thru Curator "allocated" filtertype does not seem to work

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

1 Like
6

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