.ds-logstash shards remain

Elastic Stack Elasticsearch
1

I have an issue in that I have 2200 of these .ds-logstash-DATE indices that are not being cleaned out as part of the ILM policy. They are from a data stream.
Below is the linked ILM policy

PUT _ilm/policy/logstash-lifecycle-policy
{
  "policy": {
    "phases": {
      "hot": {
        "min_age": "0ms",
        "actions": {
          "rollover": {
            "max_primary_shard_size": "25gb",
            "max_age": "1d"
          },
          "set_priority": {
            "priority": 100
          }
        }
      },
      "delete": {
        "min_age": "14d",
        "actions": {
          "delete": {
            "delete_searchable_snapshot": true
          }
        }
      }
    }
  }
}
The data stream is also part of the same ILM policy.

Any ideas what these are and why they remain? They are causing my shard count to reach it's maximum which is then causing errors.

Tx
2

Can you share an explain on one of them?

3

Please see below:

{
  ".ds-logstash-2022.09.30-2022.10.10-000013" : {
    "aliases" : { },
    "mappings" : {
      "_data_stream_timestamp" : {
        "enabled" : true
      },
      "properties" : {
        "@timestamp" : {
          "type" : "date"
        }
      }
    },
    "settings" : {
      "index" : {
        "lifecycle" : {
          "name" : "logstash-lifecycle-policy",
          "rollover_alias" : "logstash",
          "indexing_complete" : "true"
        },
        "routing" : {
          "allocation" : {
            "include" : {
              "_tier_preference" : "data_hot"
            }
          }
        },
        "hidden" : "true",
        "number_of_shards" : "3",
        "provided_name" : ".ds-logstash-2022.09.30-2022.10.10-000013",
        "creation_date" : "1665431888858",
        "priority" : "100",
        "number_of_replicas" : "1",
        "uuid" : "xxxxxxxxx",
        "version" : {
          "created" : "7170299"
        }
      }
    },
    "data_stream" : "logstash-2022.09.30"
  }
}
4

Hi just checking if anyone has a possible solution here?

5

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