From 9e2fe42af8c64a3777b6c5d1aa09b9675ea1abda Mon Sep 17 00:00:00 2001 From: Anastasiia Terenteva Date: Wed, 18 Mar 2026 18:16:23 +0000 Subject: [PATCH] Remove redundant closeOperation for abandoned executions Ordering with executions.remove doesn't matter for abandoned operations, since a concurrent operation retry will find the thombtone and fail anyway. --- .../spark/sql/connect/service/SparkConnectExecutionManager.scala | 1 - 1 file changed, 1 deletion(-) diff --git a/sql/connect/server/src/main/scala/org/apache/spark/sql/connect/service/SparkConnectExecutionManager.scala b/sql/connect/server/src/main/scala/org/apache/spark/sql/connect/service/SparkConnectExecutionManager.scala index 2a936b526d96a..091dfb671667d 100644 --- a/sql/connect/server/src/main/scala/org/apache/spark/sql/connect/service/SparkConnectExecutionManager.scala +++ b/sql/connect/server/src/main/scala/org/apache/spark/sql/connect/service/SparkConnectExecutionManager.scala @@ -159,7 +159,6 @@ private[connect] class SparkConnectExecutionManager() extends Logging { // getting an INVALID_HANDLE.OPERATION_ABANDONED error on a retry. if (abandoned) { abandonedTombstones.put(key, executeHolder.getExecuteInfo) - executeHolder.sessionHolder.closeOperation(executeHolder) } // Remove the execution from the map *after* putting it in abandonedTombstones.