# Issue with kibana/es after update to 9.1.0

**URL:** <https://discuss.elastic.co/t/issue-with-kibana-es-after-update-to-9-1-0/381265>\
**Category:** Elasticsearch\
**Created:** [August 22, 2025, 4:11pm UTC](https://discuss.elastic.co/t/issue-with-kibana-es-after-update-to-9-1-0/381265 "2025-08-22T16:11:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kim.ae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kim.ae/32/144726_2.png) [@kim.ae](https://discuss.elastic.co/u/kim.ae)\
**Post date:** [August 22, 2025, 4:11pm UTC](https://discuss.elastic.co/t/issue-with-kibana-es-after-update-to-9-1-0/381265/1 "2025-08-22T16:11:56Z")

</div>

Hello Community and Elastic team,  
We are using the ECK community version Installed in a AKS with k8s version 1.32.6.  
We just updated the installation to 9.1.0 from 8.15.x. No we are unable to create index templates, it throws the error:

```auto
{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Determinizing automaton with 723 states and 779 transitions would require more than 10000 effort.",
  "attributes": {
    "error": {
      "root_cause": [
        {
          "type": "too_complex_to_determinize_exception",
          "reason": "Determinizing automaton with 723 states and 779 transitions would require more than 10000 effort."
        }
      ],
      "type": "too_complex_to_determinize_exception",
      "reason": "Determinizing automaton with 723 states and 779 transitions would require more than 10000 effort."
    }
  }
}

```

This happens independently from index pattern.

ECK Setup:  
number of nodes: 13  
3 master nodes, 6 hot nodes and 4 cold nodes.  
There is no additional options enabled for elasticsearch resource.

example of a index\_template creation request that fail with above exception:

```auto
PUT _index_template/my-index-template-name
{
  "template": {
    "settings": {
      "index": {
        "mode": "standard"
      }
    }
  },
  "index_patterns": [
    "some-index"
  ],
  "data_stream": {}
}

```

If any more information is needed please let me know.  
Thanks in advance,

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 22, 2025, 4:31pm UTC](https://discuss.elastic.co/t/issue-with-kibana-es-after-update-to-9-1-0/381265/2 "2025-08-22T16:31:58Z")

</div>

Did you follow a [supported upgrade path](https://www.elastic.co/docs/deploy-manage/upgrade#upgrade-paths-8.x) when you performed the upgrade?

---

<div class="post-metadata">

**Author:** ![kim.ae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kim.ae/32/144726_2.png) [@kim.ae](https://discuss.elastic.co/u/kim.ae)\
**Post date:** [August 22, 2025, 4:35pm UTC](https://discuss.elastic.co/t/issue-with-kibana-es-after-update-to-9-1-0/381265/3 "2025-08-22T16:35:49Z")

</div>

Yes, the operator does not accept anything different from that. I first updated to 8.19.x and only after that I was able to update to 9.1.0.

---

<div class="post-metadata">

**Author:** ![kim.ae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kim.ae/32/144726_2.png) [@kim.ae](https://discuss.elastic.co/u/kim.ae)\
**Post date:** [August 26, 2025, 2:56pm UTC](https://discuss.elastic.co/t/issue-with-kibana-es-after-update-to-9-1-0/381265/4 "2025-08-26T14:56:36Z")

</div>

One more information that might be useful.  
I have checked logs and this is happening [here](https://github.com/elastic/elasticsearch/blob/v9.1.0/server/src/main/java/org/elasticsearch/cluster/metadata/MetadataIndexTemplateService.java#L1003), whenever it is checking for conflicts between index\_templates.  
I already tried to update the setting `xpack.security.automata.max_determinized_states`, but this do not have any effect at all.

---

<div class="post-metadata">

**Author:** ![kim.ae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kim.ae/32/144726_2.png) [@kim.ae](https://discuss.elastic.co/u/kim.ae)\
**Post date:** [August 27, 2025, 3:48pm UTC](https://discuss.elastic.co/t/issue-with-kibana-es-after-update-to-9-1-0/381265/5 "2025-08-27T15:48:48Z")

</div>

> [@kim.ae](#):
>
> `too_complex_to_determinize_exception`

For those who have the same issue, my team found out what was the issue.  
Please take a look on this issue report: [`too_complex_to_determinize_exception` is thrown in a few cases due to the patterns in index template · Issue #127972 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/127972)  
The way to fix this, if you jumped from version 8.x to 9.x is to delete the index\_template that you think is the culprit (probably the one with a lot of index patterns with more than one wildcard), and recreated it with a more simple patterns (avoiding the double+ wildcard 😃 )