Rollover creates index with default shards instead of 1st index shard configuration

OpenSearch
, ,
1

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

Describe the issue:
I have an index associated with a rollover policy that has 1 shard and 1 replica. After policy is executed, a new index -000002 is generated, but with 5 shards and 1 replica

Configuration:

{
    "policy": {
        "policy_id": "email-sender-ms_policy",
        "description": "A policy for email sender rollover and delete",
        "last_updated_time": 1668540938405,
        "schema_version": 14,
        "error_notification": null,
        "default_state": "rollover",
        "states": [
            {
                "name": "rollover",
                "actions": [
                    {
                        "retry": {
                            "count": 3,
                            "backoff": "exponential",
                            "delay": "1m"
                        },
                        "rollover": {
                            "min_size": "100mb"
                        }
                    }
                ],
                "transitions": [
                    {
                        "state_name": "delete",
                        "conditions": {
                            "min_index_age": "7d"
                        }
                    }
                ]
            },
            {
                "name": "delete",
                "actions": [
                    {
                        "retry": {
                            "count": 3,
                            "backoff": "exponential",
                            "delay": "1m"
                        },
                        "delete": {}
                    }
                ],
                "transitions": []
            }
        ],
        "ism_template": [
            {
                "index_patterns": [
                    "email-sender-ms*"
                ],
                "priority": 100,
                "last_updated_time": 1668540938405
            }
        ]
    }
}

Relevant Logs or Screenshots:

image
image1586×276 32.2 KB

2

Yes I am experiencing the same behavior in AWS Opensearch 2.3.

Is there any solution that the rolled over index takes the number of primary shards is taken from the first index instead of the global default?

3

Did you find a solution to this? I’d also like to be able to set settings of the new rolled over index to the same as the original index