Data, Data Engineer, Open Source, Spark, Kubernetes.
node is overly busy (e.g., some other container is using too much CPU or the NodeManager is doing too much to respond). The failure is indicative of a busy cluster or nodes that are having issues for some other reason. Check the affected node, cordon it, fix it, and put it back in the cluster.