You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xi Chen (Jira)" <ji...@apache.org> on 2024/09/02 11:23:00 UTC
[jira] [Updated] (SPARK-49479) Non-daemon timer thread prevents Spark driver JVM from stopping
[ https://issues.apache.org/jira/browse/SPARK-49479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xi Chen updated SPARK-49479:
----------------------------
Summary: Non-daemon timer thread prevents Spark driver JVM from stopping (was: Non-daemon Timer prevents Spark driver JVM from stopping)
> Non-daemon timer thread prevents Spark driver JVM from stopping
> ---------------------------------------------------------------
>
> Key: SPARK-49479
> URL: https://issues.apache.org/jira/browse/SPARK-49479
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 4.0.0, 3.5.2
> Reporter: Xi Chen
> Priority: Major
>
> It is observed that when using [Spark Torch Distributor|https://spark.apache.org/docs/latest/api/python/reference/api/pyspark.ml.torch.distributor.TorchDistributor.html], Spark driver pod could hang around after calling {_}spark.stop(){_}. Although the Spark Context was shutdown, the JVM was still running.
> The reason was that there is a non-daemon Timer thread named {_}BarrierCoordinator barrier epoch increment timer{_}, which prevented the driver JVM from stopping.
> This issue is fixed in master branch by [https://github.com/apache/spark/pull/44718/files#diff-c2ca635ca0080bea12bcb5e25272a830019b3b150fc6c1cee0d268e0c12b82ceR82] which shuts down the timer thread on stop. We should backport SPARK-46895 and SPARK-46698 to branch-3.5 for fix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org