-
Type:
Sub-task
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: amrmproxy, federation
-
Labels:None
Currently BroadcastAMRMProxyPolicy assumes that we only span the application to the sub-clusters instructed by itself via splitResourceRequests. However, with AMRMProxy HA, second attempts of the application might come up with multiple sub-clusters initially without consulting the AMRMProxyPolicy at all. This leads to exceptions in notifyOfResponse. It should simply allow the new/unknown sub-cluster heartbeat responses.