Re: Adding MasterCompute object causes "failed to report status" errors

However, I think the behavior described above is not correct. If there is some other cause for the behavior I'm seeing please let me know. Thanks, Nick On Aug 21, 2012, at 2:28 PM, Nick West wrote: Thank you both for the replies. I have checked out the most recent version of the code and am

Re: Adding MasterCompute object causes "failed to report status" errors

code, but you can give it a try and see if it solves your issue. Regards, Kaushik On Mon, Aug 20, 2012 at 3:04 PM, Nick West mailto:nick.w...@benchmarksolutions.com>> wrote: I'm a little confused by the examples in SimpleMasterComputeVertex.java. To me it looks like this is a

Re: Adding MasterCompute object causes "failed to report status" errors

rds, Kaushik On Mon, Aug 20, 2012 at 1:26 PM, Nick West mailto:nick.w...@benchmarksolutions.com>> wrote: Hi, I have a giraph application that runs fine; however, when I add a MasterCompute object (definition following) all of the map tasks time out. I have hadoop configured to run with 8 m

Adding MasterCompute object causes "failed to report status" errors

p and vote to halt ... agg.aggregate(stop) } } Is there some other method that I am not calling that I should? Or some step that I'm missing? Any suggestions as to why/how these additions are causing the processes to block would be appreciated! Thanks, Nick West Benchmark Solutions

Re: Termination Conditions

ighbors is invoked, it can read the state of its direct neighbors. I think that the Pregel model is simply not suited for such algorithms (unfortunately), let me know if you find a clever workaround. Best, Sebastian 2012/8/3 Nick West mailto:nick.w...@benchmarksolutions.com>> Thanks for the

Re: Termination Conditions

never received any messages after then, in which case they are never reactivated. In other words, I think you can rephrase that as: 1. All vertices are halted after a given superstep 2. No messages were sent in that superstep Hope it helps. Alessandro From: Nick West mailto:n

Termination Conditions

e two conditions must both hold for the global BSP algorithm to terminate: 1) All vertices vote to halt in a given superstep 2) No messages are sent in that supersetp Is that correct? Thanks, Nick West Benchmark Solutions 101 Park Avenue - 7th Floor New York, NY 10178 Tel +1.212.220.4739 | M

Re: package-private methods in Vertex/BasicVertex

essandro Presta wrote: Hi Nick, Thanks for pointing this out. Here's a relevant discussion that was just recently started: https://issues.apache.org/jira/browse/GIRAPH-272. Hopefully we get this sorted out soon. Alessandro From: Nick West mailto:nick.w...@benchmarksolutions.com>> Reply-T

package-private methods in Vertex/BasicVertex

s are declared final, limiting the amount of customization one can make to these classes. If you have any alternative suggestions, I'd be happy to hear them. Thanks, Nick West Benchmark Solutions 101 Park Avenue - 7th Floor New York, NY 10178 Tel +1.212.220.4739 | Mobile +1.64

Re: Heterogeneous Vertex Types

I am guessing it is because Giraph needs to move vertices around and needs to construct them before it reads in their serialization. I am new to Giraph myself so this may be incorrect. Maybe Avery could comment. Jon On Fri, Jul 27, 2012 at 6:32 AM, Nick West mailto:nick.w...@benchmarksolution

Re: Heterogeneous Vertex Types

both behaviours for you? Same for edge and message classes. This should be enough do what you want. Jon On Wed, Jul 25, 2012 at 3:29 PM, Nick West mailto:nick.w...@benchmarksolutions.com>> wrote: Hi, I'm working on implementing a belief propagation algorithm over Giraph. (Do yo

Heterogeneous Vertex Types

lection - could that be a cause? Thanks, Nick West Stack Trace: ./bin/hadoop jar ~/code/watchdog/modules/inference/target/inference-assembly-1.0.jar bmrk.inference.giraph.IdiotRunner ising ising_out 4 Input arguments: [0] = ising [1] = ising_out [2] = 4 setting