Hey Stephen,
I was on vacation last week, I'm looking over the logs this week. I've got
a few ideas for a first but may take me a while as I get back into work.
Darin
On Fri, Jul 1, 2016 at 2:43 AM, Stephen Gran
wrote:
> Hi,
>
> It's not a problem at all. Anything I can do to help.
>
> I've
Hi,
It's not a problem at all. Anything I can do to help.
I've attached the log file for the relevant time period. This is hadoop
2.7.2 - you have a good memory :)
Cheers,
On 30/06/16 22:56, Darin Johnson wrote:
> Hey Steven,
>
> Looks like this might be slightly different t
Hey Steven,
Looks like this might be slightly different than what I was originally
expecting. Sorry to keep asking for more info but it will help me recreate
the issue. Could you possibly get me more of the ResourceManager logs? In
particular, I'm trying to figure out where upgradeNodeCapacity
Hi,
Yes - the imaginatively named slave2 was a zero-sized nm at that point -
I am looking at how small a pool of reserved resource I can get away
with, and use FGS for burst activity.
Here are all the logs related to that host:port combination around that
time:
2016-06-30 19:47:43,756 INFO
Steven, thanks. I thought I had fixed that but perhaps a regression was
made in another merge. I'll look into it, can you answer a few questions?
Was the node (slave2) a zero sided nodemanager (for fgs)? In the node
manager logs had it recently become unhealthy? I'm pretty concerned about
this
Hi,
Just playing with the 0.2.0 release (congratulations, by the way!)
I have seen this twice now, although it is by no means consistent - I
will have a dozen successful runs, and then one of these. This exits
the RM, which makes it rather noticable.
2016-06-30 19:47:43,952 INFO
org.apache.hado
