You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have a graph instance with about 80m vertex. The graph is backed by hbase, running on a CDH cluster.
I would like to re-index a composite index of vertex property, choose MR for this due to the graph size. The map-reduce started properly, but failed after running for a while. The error message is basically saying all map tasks timed out, And here is some example message:
"AttempID:attempt_xxxxx timed out after 600 sec."
The map-reduce framework expects regular progress update, and would consider the attempt failed after a configurable amount of time (600 sec, by default).
I would propose a fix by adding some counter indicating elements already processed. But would like to have more input from the community.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I have a graph instance with about 80m vertex. The graph is backed by hbase, running on a CDH cluster.
I would like to re-index a composite index of vertex property, choose MR for this due to the graph size. The map-reduce started properly, but failed after running for a while. The error message is basically saying all map tasks timed out, And here is some example message:
"AttempID:attempt_xxxxx timed out after 600 sec."
The map-reduce framework expects regular progress update, and would consider the attempt failed after a configurable amount of time (600 sec, by default).
I would propose a fix by adding some counter indicating elements already processed. But would like to have more input from the community.
Thanks!
Jaguar
All reactions