[SPARK-20286] dynamicAllocation.executorIdleTimeout is ignored after unpersist

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.1
• Fix Version/s: 3.0.0
• Component/s: Spark Core
• Assignee: Marcelo Masiero Vanzin
• Reporter: Miguel Pérez
• Created: 10/Apr/17 22:16
• Updated: 14/Jul/19 22:42
• Resolved: 05/Jun/19 13:10

Description

With dynamic allocation enabled, it seems that executors with cached data which are unpersisted are still being killed using the dynamicAllocation.cachedExecutorIdleTimeout configuration, instead of dynamicAllocation.executorIdleTimeout. Assuming the default configuration (dynamicAllocation.cachedExecutorIdleTimeout = Infinity), an executor with unpersisted data won't be released until the job ends.

How to reproduce

• Set different values for dynamicAllocation.executorIdleTimeout and dynamicAllocation.cachedExecutorIdleTimeout
• Load a file into a RDD and persist it
• Execute an action on the RDD (like a count) so some executors are activated.
• When the action has finished, unpersist the RDD
• The application UI removes correctly the persisted data from the Storage tab, but if you look in the Executors tab, you will find that the executors remain active until (dynamicAllocation.cachedExecutorIdleTimeout is reached.

Issue Links

• is duplicated by: SPARK-24786 Executors not being released after all cached data is unpersisted
• links to: [Github] Pull Request #22015 (dhruve)
• links to: GitHub Pull Request #22015
• links to: GitHub Pull Request #24704