[YARN-9100] Add tests for GpuResourceAllocator and do minor code cleanup

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.0, 3.2.1, 3.1.3
• Hadoop Flags: Reviewed
• Assignee: Peter Bacsko
• Reporter: Szilard Nemeth
• Created: 09/Dec/18 22:15
• Updated: 16/Aug/19 13:35
• Resolved: 16/Aug/19 13:35

Description

Add tests for GpuResourceAllocator and do minor code cleanup

• Improved log and exception messages
• Added some new debug logs
• Some methods are named like *Copy, these are returning copies of internal data structures. The word "copy" is just a noise in their name, so they have been renamed. Additionally, the copied data structures modified to be immutable.
• The waiting loop in method assignGpus were decoupled into a new class, RetryCommand.

Some more words about the new class RetryCommand:
There are some similar waiting loops in the code in: AMRMClient, AMRMClientAsync and even in GenericTestUtils (see waitFor method). RetryCommand could be a future replacement of these duplicated code, as it gives a solution to this waiting loop problem in a generic way.
The only downside of the usage of RetryCommand in GpuResourceAllocator (startGpuAssignmentLoop) is the ugly exception handling part, but that's solely because how Java deals with checked exceptions vs. lambdas. If there's a cleaner way to solve the exception handling, I'm open for any suggestions.