Help Center/ MapReduce Service/ Component Operation Guide (LTS)/ Using Spark/Spark2x/ Common Issues About Spark/ Spark Core/ Why Do Executors Fail to Be Removed After the NodeManager Is Stopped?
Updated on 2025-08-22 GMT+08:00

Why Do Executors Fail to Be Removed After the NodeManager Is Stopped?

Question

If the NodeManager is stopped with the executor dynamic allocation enabled, the executors on the node containing the stopped NodeManager fail to be removed from the driver UI when the idle time expires.

Answer

When the ResourceManager detects that the NodeManager has stopped, the Spark driver has already marked the executors for termination due to idle timeout. However, since the NodeManager is no longer running, the executors cannot be properly terminated.

Consequently, the driver is unable to detect the LOST event for the executors. As a result, they remain in the driver's executor list and continue to appear on the driver UI.

This behavior is expected when the YARN NodeManager is stopped. Once the NodeManager starts again, the executors will be removed.