yaooqinn commented on code in PR #42199: URL: https://github.com/apache/spark/pull/42199#discussion_r1333082156
########## sql/core/src/main/scala/org/apache/spark/sql/execution/SQLExecution.scala: ########## @@ -77,6 +79,11 @@ object SQLExecution { } val rootExecutionId = sc.getLocalProperty(EXECUTION_ROOT_ID_KEY).toLong executionIdToQueryExecution.put(executionId, queryExecution) + val originalInterruptOnCancel = sc.getLocalProperty(SPARK_JOB_INTERRUPT_ON_CANCEL) + if (originalInterruptOnCancel == null) { + val interruptOnCancel = sparkSession.conf.get(SQLConf.INTERRUPT_ON_CANCEL) + sc.setInterruptOnCancel(interruptOnCancel) Review Comment: Can you also share your use case? It's likely not a sql-shell only issue. On the opposite, if the task threads are not interrupted, the scheduler could suffer from starvation of resources. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org