[
https://issues.apache.org/jira/browse/SPARK-49479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xi Chen updated SPARK-49479:
----------------------------
Description:
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. In SPARK-46895 we replaced the timer with non-daemon
single thread scheduled executor, but the issue still exists.
We should use daemon single thread scheduled executor instead.
was:
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. In SPARK-46895 we replaced the timer with non-daemon
single thread scheduled executor, but the issue still exists.
We should usedaemon single thread scheduled executor instead.
> 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. In SPARK-46895 we replaced the timer with
> non-daemon single thread scheduled executor, but the issue still exists.
> We should use daemon single thread scheduled executor instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
