[
https://issues.apache.org/jira/browse/SPARK-25183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao resolved SPARK-25183.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.4.0
Issue resolved by pull request 22186
[https://github.com/apache/spark/pull/22186]
> Spark HiveServer2 registers shutdown hook with JVM, not ShutdownHookManager;
> race conditions can arise
> ------------------------------------------------------------------------------------------------------
>
> Key: SPARK-25183
> URL: https://issues.apache.org/jira/browse/SPARK-25183
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.2.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 2.4.0
>
>
> Spark's HiveServer2 registers a shutdown hook with the JVM
> {{Runtime.addShutdownHook()}} which can happen in parallel with the
> ShutdownHookManager sequence of spark & Hadoop, which operate the shutdowns
> in an ordered sequence.
> This has some risks
> * FS shutdown before rename of logs completes, SPARK-6933
> * Delays of rename on object stores may block FS close operation, which, on
> clusters with timeouts hooks (HADOOP-12950) of FileSystem.closeAll() can
> force a kill of that shutdown hook and other problems.
> General outcome: logs aren't present.
> Proposed fix:
> * register hook with {{org.apache.spark.util.ShutdownHookManager}}
> * HADOOP-15679 to make shutdown wait time configurable, so O(data) renames
> don't trigger timeouts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
