Discrepancy between shim cache and core app/task list after scheduler restart

When scheduler restarts, occasionally it gets into a situation where the application is still in Running state despite the application getting terminated in the cluster. This is confirmed with the attached state dump.

The scheduler core logs indicate all nodes are being evaluated for non-existing application (also attached). The CPU is being used up doing this unneeded evaluation.