[CI] MultiClusterSpecIT class failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-intake #30783 / 9.2.1_bwc-snapshots
• elasticsearch-intake #30782 / 9.2.1_bwc-snapshots
• elasticsearch-pull-request #102047 / 9.3.0_part_3_bwc-snapshots
• elasticsearch-intake #30778 / 9.1.7_bwc-snapshots
• elasticsearch-intake #30779 / 9.1.7_bwc-snapshots
• elasticsearch-intake #30777 / 9.3.0_bwc-snapshots
• elasticsearch-pull-request #102038 / 8.19.7_part_3_bwc-snapshots
• elasticsearch-intake #30776 / 8.19.7_bwc-snapshots
• elasticsearch-intake #30776 / 9.1.7_bwc-snapshots
• elasticsearch-intake #30776 / 9.3.0_bwc-snapshots

Reproduction Line:

./gradlew ":x-pack:plugin:esql:qa:server:multi-clusters:v9.2.1#oldToNew" -Dtests.class="org.elasticsearch.xpack.esql.ccq.MultiClusterSpecIT" -Dtests.method="test {csv-spec:k8s-timeseries-present-over-time.Present_over_time_of_keyword}" -Dtests.seed=BDD106349E9389E0 -Dtests.bwc=true -Dtests.locale=fo-FO -Dtests.timezone=Arctic/Longyearbyen -Druntime.java=25

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Previous test setup failed: 60.000 milliseconds timeout on connection http-outgoing-12 [ACTIVE]

Issue Reasons:

• [main] 33 failures in class org.elasticsearch.xpack.esql.ccq.MultiClusterSpecIT (3.3% fail rate in 1000 executions)
• [main] 4 failures in step 9.2.1_bwc-snapshots (20.0% fail rate in 20 executions)
• [main] 2 failures in step 9.2.1_part_3_bwc-snapshots (3.0% fail rate in 67 executions)
• [main] 3 failures in step 9.1.7_part_3_bwc-snapshots (4.6% fail rate in 65 executions)
• [main] 5 failures in step 9.3.0_part_3_bwc-snapshots (7.6% fail rate in 66 executions)
• [main] 4 failures in step 8.19.7_part_3_bwc-snapshots (6.2% fail rate in 65 executions)
• [main] 2 failures in step 8.19.7_bwc-snapshots (11.1% fail rate in 18 executions)
• [main] 5 failures in step 9.1.7_bwc-snapshots (27.8% fail rate in 18 executions)
• [main] 3 failures in step 9.3.0_bwc-snapshots (16.7% fail rate in 18 executions)
• [main] 10 failures in pipeline elasticsearch-intake (47.6% fail rate in 21 executions)
• [main] 10 failures in pipeline elasticsearch-pull-request (14.7% fail rate in 68 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]

I found this in the logs for the first failing test, spatial.CentroidFromAirportsAfterIntersectsCompoundPredicateNotIndexedNorDocValues}:

[2025-10-29T08:19:49,045][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [remote_cluster-0] fatal error in thread [elasticsearch[remote_cluster-0][esql_worker][T#4]], exiting java.lang.AssertionError: BYTES_REF NOT IN (NULL, LONG)	
	at org.elasticsearch.compute.lucene.ValuesSourceReaderOperator.process(ValuesSourceReaderOperator.java:164)	
	at org.elasticsearch.compute.operator.AbstractPageMappingOperator.getOutput(AbstractPageMappingOperator.java:76)	
	at org.elasticsearch.compute.operator.Driver.runSingleLoopIteration(Driver.java:247)	
	at org.elasticsearch.compute.operator.Driver.run(Driver.java:178)	
	at org.elasticsearch.compute.operator.Driver$1.doRun(Driver.java:364)	
	at org.elasticsearch.server@8.15.5/org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)	
	at org.elasticsearch.server@8.15.5/org.elasticsearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:33)	
	at org.elasticsearch.server@8.15.5/org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:984)	
	at org.elasticsearch.server@8.15.5/org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)	
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)	
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)	
	at java.base/java.lang.Thread.run(Thread.java:1570)

@craigtaverner , this like #116945 again. I think you were trying to get more failing build scans by unmuting in #137116, right? In any case, I think it's best if you took a look.