[
https://issues.apache.org/jira/browse/SPARK-27812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852342#comment-16852342
]
Igor Calabria commented on SPARK-27812:
---------------------------------------
I believe this was introduced when `kubernetes-client` was updated in
https://issues.apache.org/jira/browse/SPARK-26742 . I can confirm that
reverting
[https://github.com/apache/spark/commit/2d4e9cf84b85a5f8278276e8d8ff59f6f4b11c4c]
fixes this issue. This is funny because it was already discussed here (2017):
[https://github.com/apache-spark-on-k8s/spark/pull/216#discussion_r112641765
|https://github.com/apache-spark-on-k8s/spark/pull/216#discussion_r112641765.]
The previous solution was setting
`.withWebsocketPingInterval({color:#6897bb}0{color})` option when instantiating
the client. This prevented the user thread from being created. Maybe something
changed with okhttp or kubernetes-client and this is no longer the case.
> kubernetes client import non-daemon thread which block jvm exit.
> ----------------------------------------------------------------
>
> Key: SPARK-27812
> URL: https://issues.apache.org/jira/browse/SPARK-27812
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
> Affects Versions: 2.4.3
> Reporter: Henry Yu
> Priority: Major
>
> I try spark-submit to k8s with cluster mode. Driver pod failed to exit with
> An Okhttp Websocket Non-Daemon Thread.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
