You can also find HAWQ log in attachment. As expected, HAWQ tries to releaseResources, but somehow it returns success
On Fri, Nov 27, 2015 at 2:10 PM, Alexey Grishchenko <programme...@gmail.com> wrote: > Hi, guys > > I've got an issue with running HAWQ 2.0 on YARN > On starting HAWQ successfully registers YARN application and starts > allocating containers. But it never stops allocating them. Regardless the > amount of vcores and memory you give YARN to manage, HAWQ would allocate > containers until it eat all the available resources. After this, all the > queries start to hang. > > What I can see in the RM logs (full log is attached): > 2015-11-27 05:34:59,214 WARN resourcemanager.RMAuditLogger > (RMAuditLogger.java:logFailure(215)) - USER=gpadmin OPERATION=AM Released > Container TARGET=Scheduler RESULT=FAILURE DESCRIPTION=Trying to > release container not owned by app or with invalid id. > PERMISSIONS=Unauthorized access or invalid container > APPID=application_1448630699339_0002 > CONTAINERID=container_1448630699339_0002_01_000008 > > Do you know the possible reason for this? > Using HAWQ 2.0.0.0_beta build 18453 on a single node with PHD 3.3.2.0 > (YARN 2.7.1) > > -- > Alexey Grishchenko, http://0x0fff.com > -- Alexey Grishchenko, http://0x0fff.com
gpdb-2015-11-27_061656.csv.gz
Description: GNU Zip compressed data
