Index is not Rollover

I have 8 node cluster 3 master 3 hot node and 2 warm node.I have an index called log-wlb-system
in hot node it will rotate every index after 1 day or when its size reach to 1gb and in warm node the retention is 2 days and delete it after 2 days

{
  "policy": {
    "phases": {
      "hot": {
        "min_age": "0ms",
        "actions": {
          "rollover": {
            "max_size": "50gb",
            "max_age": "1d"
          },
          "set_priority": {
            "priority": 100
          }
        }
      },
      "warm": {
        "min_age": "2d",
        "actions": {
          "set_priority": {
            "priority": 50
          }
        }
      },
      "delete": {
        "min_age": "2d",
        "actions": {
          "delete": {
            "delete_searchable_snapshot": true
          }
        }
      }
    }
  }
}

log-wlb-system details

health status index                            uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   log-wlb-system-2021.05.19-000001 gG2SxdF-R9a6eakoTGTGpA   1   1        479            2      1.4mb        750.8kb
green  open   log-wlb-system-2021.05.20-000002 vrxZsqhdRfC9GIE0x3utww   1   1        449            0      1.2mb        649.8kb
green  open   log-wlb-system-2021.05.21-000003 9pwBNOcCTG-o9e-8gJgioA   1   1          4            0      187kb         93.5kb

shards information

index                            shard prirep state   docs   store ip            node
log-wlb-system-2021.05.19-000001 0     p      STARTED  479 750.8kb xx.xx.xx.xx eh1
log-wlb-system-2021.05.19-000001 0     r      STARTED  479 750.8kb xx.xx.xx.xx  eh2
log-wlb-system-2021.05.20-000002 0     r      STARTED  449 649.8kb xx.xx.xx.xx  eh1
log-wlb-system-2021.05.20-000002 0     p      STARTED  449 649.8kb xx.xx.xx.xx  eh2
log-wlb-system-2021.05.21-000003 0     p      STARTED    4  93.5kb xx.xx.xx.xx  eh3
log-wlb-system-2021.05.21-000003 0     r      STARTED    4  93.5kb xx.xx.xx.xx  eh2

elasticsearch.yml file for warm node

# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
#       Before you set out to tweak and tune the configuration, make sure you
#       understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: hot-warm
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: ew1
node.roles: ["data_warm"]
#
# Add custom attributes to the node:
#
#node.attr.rack_id: rack_4
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: ew1
#
# Set a custom port for HTTP:
#
#http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
discovery.seed_hosts: ["em1", "em2","em3","eh1","eh2","eh3","eh4","ew2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
cluster.initial_master_nodes: ["em1", "em2","em3"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
xpack.security.enabled: true
#xpack.security.audit.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: full
xpack.security.transport.ssl.client_authentication: required
xpack.security.transport.ssl.key: certs/ew1/ew1.key
xpack.security.transport.ssl.certificate: certs/ew1/ew1.crt
xpack.security.transport.ssl.certificate_authorities: certs/ca/ca.crt

xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.key:  certs/ew1/ew1.key
xpack.security.http.ssl.certificate: certs/ew1/ew1.crt
xpack.security.http.ssl.certificate_authorities: certs/ca/ca.crt

xpack.monitoring.exporters.my_local:
  type: local
  use_ingest: false

the index is not rollovering

Thanks for using Elasticsearch and ILM.

the index is not rollovering

Can you please be more specific about which index is not rolling over and provide the output of that index's _ilm/explain API? I see you have log-wlb-system-2021.05.19-000001, log-wlb-system-2021.05.20-000002 and log-wlb-system-2021.05.21-000003 so rollover seems to work.

Do you mean, by any chance, that the index is not moving to the warm node? If that's the case, is the age condition since rollover met? ie. has it been 2 days since the index rolled over? This information is available in the _ilm/explain output under the age field.

1 Like

Sorry for late reply i was testing ilm policy in other index also..now i have found that index is rollovering but it does not come to warm state it just delete after 2 days

{
  "indices" : {
    "log-wlb-system-2021.05.26-000003" : {
      "index" : "log-wlb-system-2021.05.26-000003",
      "managed" : true,
      "policy" : "winlogbeat_system_policy",
      "lifecycle_date_millis" : 1622091069456,
      "age" : "2.7h",
      "phase" : "hot",
      "phase_time_millis" : 1622004609807,
      "action" : "complete",
      "action_time_millis" : 1622091070878,
      "step" : "complete",
      "step_time_millis" : 1622091070878,
      "phase_execution" : {
        "policy" : "winlogbeat_system_policy",
        "phase_definition" : {
          "min_age" : "0ms",
          "actions" : {
            "rollover" : {
              "max_size" : "50gb",
              "max_age" : "1d"
            },
            "set_priority" : {
              "priority" : 100
            }
          }
        },
        "version" : 1,
        "modified_date_in_millis" : 1620639240215
      }
    },
    "log-wlb-system-2021.05.25-000002" : {
      "index" : "log-wlb-system-2021.05.25-000002",
      "managed" : true,
      "policy" : "winlogbeat_system_policy",
      "lifecycle_date_millis" : 1622004608849,
      "age" : "1.11d",
      "phase" : "hot",
      "phase_time_millis" : 1621918149692,
      "action" : "complete",
      "action_time_millis" : 1622004610379,
      "step" : "complete",
      "step_time_millis" : 1622004610379,
      "phase_execution" : {
        "policy" : "winlogbeat_system_policy",
        "phase_definition" : {
          "min_age" : "0ms",
          "actions" : {
            "rollover" : {
              "max_size" : "50gb",
              "max_age" : "1d"
            },
            "set_priority" : {
              "priority" : 100
            }
          }
        },
        "version" : 1,
        "modified_date_in_millis" : 1620639240215
      }
    },
    "log-wlb-system-2021.05.27-000004" : {
      "index" : "log-wlb-system-2021.05.27-000004",
      "managed" : true,
      "policy" : "winlogbeat_system_policy",
      "lifecycle_date_millis" : 1622091069606,
      "age" : "2.7h",
      "phase" : "hot",
      "phase_time_millis" : 1622091070395,
      "action" : "rollover",
      "action_time_millis" : 1622091071151,
      "step" : "check-rollover-ready",
      "step_time_millis" : 1622091071151,
      "phase_execution" : {
        "policy" : "winlogbeat_system_policy",
        "phase_definition" : {
          "min_age" : "0ms",
          "actions" : {
            "rollover" : {
              "max_size" : "50gb",
              "max_age" : "1d"
            },
            "set_priority" : {
              "priority" : 100
            }
          }
        },
        "version" : 1,
        "modified_date_in_millis" : 1620639240215
      }
    }
  }
}

elasticsearch log file

[2021-05-27T10:20:08,858][INFO ][o.e.x.i.IndexLifecycleTransition] [em3] moving index [log-wlb-system-2021.05.24-000001] from [{"phase":"hot","action":"complete","name":"complete"}] to [{"phase":"warm","action":"set_priority","name":"set_priority"}] in policy [winlogbeat_system_policy]
[2021-05-27T10:20:09,115][INFO ][o.e.x.i.IndexLifecycleTransition] [em3] moving index [log-wlb-system-2021.05.24-000001] from [{"phase":"warm","action":"set_priority","name":"set_priority"}] to [{"phase":"warm","action":"migrate","name":"branch-check-skip-action"}] in policy [winlogbeat_system_policy]
[2021-05-27T10:20:09,285][INFO ][o.e.x.i.IndexLifecycleTransition] [em3] moving index [log-wlb-system-2021.05.24-000001] from [{"phase":"warm","action":"migrate","name":"branch-check-skip-action"}] to [{"phase":"warm","action":"migrate","name":"migrate"}] in policy [winlogbeat_system_policy]
[2021-05-27T10:20:09,673][INFO ][o.e.x.i.IndexLifecycleTransition] [em3] moving index [log-wlb-system-2021.05.24-000001] from [{"phase":"warm","action":"migrate","name":"migrate"}] to [{"phase":"warm","action":"migrate","name":"check-migration"}] in policy [winlogbeat_system_policy]
[2021-05-27T10:20:09,909][INFO ][o.e.x.i.IndexLifecycleTransition] [em3] moving index [log-wlb-system-2021.05.24-000001] from [{"phase":"warm","action":"migrate","name":"check-migration"}] to [{"phase":"warm","action":"complete","name":"complete"}] in policy [winlogbeat_system_policy]
[2021-05-27T10:20:10,262][INFO ][o.e.x.i.IndexLifecycleTransition] [em3] moving index [log-wlb-system-2021.05.24-000001] from [{"phase":"warm","action":"complete","name":"complete"}] to [{"phase":"delete","action":"delete","name":"wait-for-shard-history-leases"}] in policy [winlogbeat_system_policy]
[2021-05-27T10:21:08,898][INFO ][o.e.x.i.IndexLifecycleTransition] [em3] moving index [log-wlb-system-2021.05.24-000001] from [{"phase":"delete","action":"delete","name":"wait-for-shard-history-leases"}] to [{"phase":"delete","action":"delete","name":"cleanup-snapshot"}] in policy [winlogbeat_system_policy]
[2021-05-27T10:21:09,427][INFO ][o.e.x.i.IndexLifecycleTransition] [em3] moving index [log-wlb-system-2021.05.24-000001] from [{"phase":"delete","action":"delete","name":"cleanup-snapshot"}] to [{"phase":"delete","action":"delete","name":"delete"}] in policy [winlogbeat_system_policy]
[2021-05-27T10:21:09,452][INFO ][o.e.c.m.MetadataDeleteIndexService] [em3] [log-wlb-system-2021.05.24-000001/nNmx37YDSLSj0g4hn27s9Q] deleting index

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