Description
When nm recovery is enabled, after NM restart, some containers always stay in SCHEDULED because of no sufficient resources.
The root cause is that utilizationTracker.addContainerResources has been called twice when restart.
When nm recovery is enabled, after NM restart, some containers always stay in SCHEDULED because of no sufficient resources.
The root cause is that utilizationTracker.addContainerResources has been called twice when restart.