Figured out the issue via the container log file:
container_1426433168188_0001_01_01/gam-stdout.log. Too much virtual
memory was trying to be used (I am using a micro instance on EC2 so there
is not much to work with) causing an "exitCode: 143". Apparently, there is
a limit on the virtual memor
Thanks Phil, I appreciate the help. Your posts over the past couple days
have already been quite helpful.
There were a few things I was going to play with as well, perhaps it is
some configuration issue as you mentioned earlier. I had some issues with
EC2 today and I will look at it again tomorrow
Steve:
I'm not 100% sure what to tell you, and I don't have access to my
cluster right this minute. But later this evening I can log in and
see if I can find anything that might be
useful to you.
Also, as an FYI, I'll be doing a presentation on Giraph at the
Triangle Java User's Group meeting th
Hey Phil,
I have been having the exact same problems as you (I am also setting up
Giraph on EC2), but this solution did not work for me.
Do you recall what error you saw in resourcemanager logs? I am also looking
at these logs, but nothing is standing out to me. In fact, it almost seems
like the
OK, this was easy enough to fix, once I understood what
was actually happening. Since I'm running on EC2 nodes on
AWS, it is not the case that any give node can talk to any other
node on any port (at least not by default). I had tried to
cherry-pick which ports to whitelist in the security group,
