Major Description
According to sershe HS2 interactive at startup-time tries to eagerly allocated what ever needed to execute queries. But currently this process is kind of broken.
AS of now HS2I starts and tries to allocate the resources but in cases there is not enough Yarn resources in the desired queue, HS2I will keep trying in the background forever and will not bubble this up as an issue. trying forever to allocate without signaling error defeats the idea of eagerly allocate in my opinion. I think HS2I has to fail the start if after XX minutes can not eagerly allocate the minimum space needed to run the max concurrent query.
CC hagleitn/t3rmin4t0r