Hi,
Try finding master and check what is it doing in jobtracker.
Lukas
On 2.4.2014 23:58, Suijian Zhou wrote:
Hi,
Why the giraph program will stuck when loading input graph( the size
of the graph is 500MB, not so big)? No matter how I try different
number of workers( from -w 2 to -w 30) or the -Xmx parameter of
mapred.child.java.opts or mapred.tasktracker.map.tasks.maximum, the
program always stuck there(has already loaded ~95% of the whole
graph). Any possible reasons( other parameters to tune)? The input
data itself and the giraph program are correct as tested on very small
portion of the graph. Each node has 16GB of RAM.
14/04/02 16:43:59 INFO job.JobProgressTracker: Data from 2 workers -
Loading data: 4258452 vertices loaded, 86 vertex input splits loaded;
0 edges loaded, 0 edge input splits loaded; min free memory on worker
2 - 128.71MB, average 162.83MB
14/04/02 16:44:04 INFO job.JobProgressTracker: Data from 2 workers -
Loading data: 4258452 vertices loaded, 86 vertex input splits loaded;
0 edges loaded, 0 edge input splits loaded; min free memory on worker
2 - 123.49MB, average 160.22MB
14/04/02 16:44:09 INFO job.JobProgressTracker: Data from 2 workers -
Loading data: 4258452 vertices loaded, 86 vertex input splits loaded;
0 edges loaded, 0 edge input splits loaded; min free memory on worker
2 - 123.49MB, average 159.53MB
14/04/02 16:44:14 INFO job.JobProgressTracker: Data from 2 workers -
Loading data: 4258452 vertices loaded, 86 vertex input splits loaded;
0 edges loaded, 0 edge input splits loaded; min free memory on worker
2 - 123.49MB, average 159.53MB
Best Regards,
Suijian
