tree c7a8b12c7aaf20c396ab59afc45f79cf36acbdd6
parent f2b10e069510bac3baba7f70ec8486b77ba0a05f
parent a58125bb57071996a698370e260419a2a403d0d4
author Hai Lu <halu@linkedin.com> 1606006970 -0800
committer GitHub <noreply@github.com> 1606006970 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfubi6CRBK7hj4Ov3rIwAAdHIIADS79+WrRG1VQ+CiOJg8v7v0
 EEW90WYcUlZcaHERd9Ga6v4kLpk1MDSS0HLCpkUs9mTb/76I9Tbp2TyaZrbhRBu+
 kLHAm8Dtx24HMNst0oW/LHJEOndCz5JhqkulAHSB9F2fmwV761vUjafxhRmOX9cZ
 quLZLq5CodBjwC1u0Po3flYMxRdHx+ffdFAYTilVJ3lhz3UUYojRovILlPnHlKOO
 42Iat2UJ3PXt74cHGvwGgRa+G4kCvFj2vQp/KUC6ZdxceIVx79dHj37ni7aqlkyq
 9ltGcNiLbLaq5VENd7j18MV6YDHq/5vvz39hwQxZRx20UQ0I7CPsf8SGvPpiphU=
 =uycr
 -----END PGP SIGNATURE-----
 

SAMZA-2601: avoid infinite loop when resource not allocated with host affinity disabled (#1441)

Problem: If YARN does not immediately allocate resources for a container and host affinity is disabled for the job, then the container allocator will spam the logs with messages about the request, even if the request is considered expired. This is because the allocator loops over the pending requests to check if they have been allocated, but there is no delay between loop iterations, so it might just keep checking the same pending request over and over as fast as possible. A metric is also incremented in this flow, so that metric is extremely high, which is probably not the intention.

Changes: Avoid infinite loop by breaking the loop if host affinity is disabled

Tests: new unit test

API changes: N/A

Usage instructions: N/A

Upgrade instructions: None