I updated patch (remove check) in
https://issues.apache.org/jira/browse/GIRAPH-819. Could you please take a
look.
Should I create a separate ticket for correct memory check?
On Sat, Jan 4, 2014 at 2:19 AM, Mohammad Islam wrote:
> I agree with Eric and Rafal's assessment. You can send a patch a
I agree with Eric and Rafal's assessment. You can send a patch about this.
Regards,
Mohammad
On Friday, January 3, 2014 1:13 PM, Rafal Wojdyla wrote:
I had the same problem, and I have created this ticket:
https://issues.apache.org/jira/browse/GIRAPH-819
First I thought it's just operator p
I had the same problem, and I have created this ticket:
https://issues.apache.org/jira/browse/GIRAPH-819
First I thought it's just operator problem, then I got to the same
conclusion as you, and removed the if check.
Btw - what was the purpose of that check, in the same function we check
whether th
I am running on hadoop 2.2.0-cdh5.0.0-beta-1 with pure yarn mode. I =
have noticed two issues in org.apache.giraph.yarn.GiraphYarnClient
giraph code base is 1.1.0-SNAPSHOT, downloaded on Jan 2, 2014
looking at the checkPerNodeResourcesAvailable Method.
The first issue is that the number of con
