[CI] HeapAttackIT testLookupExplosionManyMatches failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic #6237 / single-processor-node-tests
• elasticsearch-periodic-platform-support #6219 / amazonlinux-2023_platform-support-aws
• elasticsearch-periodic-platform-support #6212 / oraclelinux-9_platform-support-unix
• elasticsearch-periodic-platform-support #6107 / windows-2022_checkpart1_platform-support-windows

Reproduction Line:

./gradlew ":test:external-modules:test-esql-heap-attack:javaRestTest" --tests "org.elasticsearch.xpack.esql.heap_attack.HeapAttackIT.testLookupExplosionManyMatches" -Dtests.seed=318CEC8A8DAB5000 -Dtests.configure_test_clusters_with_one_processor=true -Dtests.locale=nds-NL -Dtests.timezone=Antarctica/Casey -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Expected a map containing
  status: expected <429> but was <400>
   error: a map containing
      type: expected "circuit_breaking_exception" but was "resource_already_exists_exception"
    reason: "index [sensor_lookup/VpS0dnT_RvySWWLP14cIqQ] already exists" unexpected but ok
index_uuid: "VpS0dnT_RvySWWLP14cIqQ" unexpected but ok
     index: "sensor_lookup" unexpected but ok
root_cause: <[{reason=index [sensor_lookup/VpS0dnT_RvySWWLP14cIqQ] already exists, index_uuid=VpS0dnT_RvySWWLP14cIqQ, index=sensor_lookup, type=resource_already_exists_exception}]> unexpected but ok

Issue Reasons:

• [main] 4 failures in test testLookupExplosionManyMatches (0.7% fail rate in 603 executions)
• [main] 3 failures in pipeline elasticsearch-periodic-platform-support (25.0% fail rate in 12 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)

[alex-spies]

@nik9000 looks like we create a test index multiple times. Is it okay if I assign this to you?

[nik9000]

Got it!