[
https://issues.apache.org/jira/browse/SPARK-31456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjoon Hyun resolved SPARK-31456.
-----------------------------------
Fix Version/s: 3.0.0
2.4.6
Resolution: Fixed
Issue resolved by pull request 28494
[https://github.com/apache/spark/pull/28494]
> If shutdownhook is added with priority Integer.MIN_VALUE, it's supposed to be
> called the last, but it gets called before other positive priority
> shutdownhook
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-31456
> URL: https://issues.apache.org/jira/browse/SPARK-31456
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.6.3, 2.0.2, 2.1.3, 2.2.3, 2.3.4, 2.4.5
> Environment: macOS Mojave 10.14.6
> Reporter: Xiaolei Liu
> Assignee: Oleg Kuznetsov
> Priority: Major
> Fix For: 2.4.6, 3.0.0
>
>
> https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/util/ShutdownHookManager.scala
> Since shutdownHookManager use below method to do the comparison.
> override def compareTo(other: SparkShutdownHook): Int = {
> other.priority - priority
> }
> Which will cause :
> (Int)(25 - Integer.MIN_VALUE) < 0
> Then the shutdownhook with Integer.Min_VALUE would not be called the last.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
