Description
Currently inside AMRMProxy, LocalityMulticastAMRMProxyPolicy is not handling and splitting cancel requests from AM properly:
- For node cancel request, we should not treat it as a localized resource request. Otherwise it can lead to all weight zero issue when computing localized resource weight.
- For ANY cancel, we should broadcast to all known subclusters, not just the ones associated with localized resources.