# When the number of shards reaches 1000, ISM stops rollover indices. Even after I delete some shards, it still does not automatically resume rollover

**URL:** <https://forum.opensearch.org/t/when-the-number-of-shards-reaches-1000-ism-stops-rollover-indices-even-after-i-delete-some-shards-it-still-does-not-automatically-resume-rollover/24881>\
**Category:** OpenSearch\
**Tags:** discuss\
**Created:** [June 26, 2025, 9:08am UTC](https://forum.opensearch.org/t/when-the-number-of-shards-reaches-1000-ism-stops-rollover-indices-even-after-i-delete-some-shards-it-still-does-not-automatically-resume-rollover/24881 "2025-06-26T09:08:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![llllxxxxx](https://avatars.discourse-cdn.com/v4/letter/l/34f0e0/32.png) [@llllxxxxx](https://forum.opensearch.org/u/llllxxxxx)\
**Post date:** [June 26, 2025, 9:08am UTC](https://forum.opensearch.org/t/when-the-number-of-shards-reaches-1000-ism-stops-rollover-indices-even-after-i-delete-some-shards-it-still-does-not-automatically-resume-rollover/24881/1 "2025-06-26T09:08:33Z")

</div>

**Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser):  
2.9.1

**Describe the issue** :

ism explain shows:

```auto
   ".ds-XXXXX-XXXX-000395" : {
      "action" : {
         "consumed_retries" : 3,
         "failed" : true,
         "index" : 0,
         "name" : "rollover",
      },
      "enabled" : false,
      "index" : ".ds-XXXXX-XXXX-000395",
      "info" : {
         "cause" : "Validation Failed: 1: this action would add [4] total shards, but this cluster currently has [998]/[1000] maximum shards open;",
         "message" : "Failed to rollover index [index=.ds-XXXXX-XXXX-000395]"
      },

```

I want the rollover to happen automatically after some shards are deleted. How can I achieve this?  
Currently, even after deleting some shards, the rollover does not resume because the ‘enable’ setting is set to false.

**Configuration** :

```auto
    "states": [
      {
        "name": "normal_state",
        "actions": [
          {
            "retry": {
              "count": 3,
              "backoff": "exponential",
              "delay": "1m"
            },
            "rollover": {
              "min_index_age": "12h"
            }
          }
        ],
        "transitions": [
          {
            "state_name":"delete_state",
            "conditions": {
              "min_index_age": "7d"
            }
          }
        ]
      },

```

**Relevant Logs or Screenshots** :

---

<div class="post-metadata">

**Author:** ![Anthony](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/anthony/32/9939_2.png) [@Anthony](https://forum.opensearch.org/u/Anthony)\
**Post date:** [June 26, 2025, 9:44am UTC](https://forum.opensearch.org/t/when-the-number-of-shards-reaches-1000-ism-stops-rollover-indices-even-after-i-delete-some-shards-it-still-does-not-automatically-resume-rollover/24881/2 "2025-06-26T09:44:35Z")

</div>

I don’t think there is a way to achieve this, you would just need to make sure that it never reaches the limit, by either reducing the number of shards or [increasing the limit](https://docs.opensearch.org/docs/latest/api-reference/cluster-api/cluster-settings/#update-cluster-setting):

```auto
PUT _cluster/settings
{
   "persistent":{
      "cluster.max_shards_per_node": 1500
   }
}

```