Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Duplicate
-
2.4.0
-
None
-
None
Description
BarrierCoordinator$ uses Timer and TimerTask. `TimerTask#cancel()` is invoked in ContextBarrierState#cancelTimerTask but `Timer#purge()` is never invoked.
Once a TimerTask is scheduled, the reference to it is not released until `Timer#purge()` is invoked even though `TimerTask#cancel()` is invoked.
Attachments
Issue Links
- is duplicated by
-
SPARK-25266 Fix memory leak in Barrier Execution Mode
- Resolved