YarnAllocator miss clean targetNumExecutorsPerResourceProfileId after YarnSchedulerBackend call stop

We meet a case that user call sc.stop() after run all custom code, but stuck in some place. 

Cause below situation

1. User call sc.stop()
2. sc.stop() stuck in some process, but SchedulerBackend.stop was called
3. Since tarn ApplicationMaster didn't finish， still call YarnAllocator.allocateResources()
4. Since driver endpoint stop new allocated executor failed to register
5. untll trigger Max number of executor failures

Caused by 

Before call CoarseGrainedSchedulerBackend.stop() will call YarnSchedulerBackend.requestTotalExecutor() to clean request info

From the log we make sure that CoarseGrainedSchedulerBackend.stop()  was called

When YarnAllocator handle then empty resource request,  since resourceTotalExecutorsWithPreferedLocalities is empty, miss clean targetNumExecutorsPerResourceProfileId.