This one seems related https://issues.apache.org/jira/browse/YARN-4538
Yet to ascertain if it actually fixes this issue. On Thu, Mar 10, 2016 at 11:43 PM, Gopal Vijayaraghavan <gop...@apache.org> wrote: > > > This seems to be something YARN fair-scheduler reporting it this way.. > >although Tez doesn't seem to handle. > > Pepperdata? > > > > I did come across HIVE-12957, in which the fix patch seems to only > >report the error better instead of doing anything about it. > ... > > Now comes my question, is this in an expected failure case ? Is there a > >bug I should know about in YARN scheduling or am I misunderstanding the > >issue? > > YARN is reporting -ve head-room, this means your cluster is running with > negative-capacity for some strange reason. > > That is a bug somewhere in the FairScheduler's internal state. > > The issue was never reproduced after we switched over to the > CapacityScheduler, so it's in limbo. > > Cheers, > Gopal > > > -- "If you really want something in this life, you have to work for it. Now, quiet! They're about to announce the lottery numbers..."
