giraph-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pascal Jäger <>
Subject Re: resolveMutations error
Date Wed, 14 May 2014 19:06:42 GMT
I get the error as well but couldn’t figure out why.

Did you check if all your vertices are present after the exception would have been thrown?



Am 14.05.2014 um 17:05 schrieb Jyotirmoy Sundi <<>>:

   Not throwing the exception in resolveMutations worked for me. Is it possible to get some
understanding of what effects it would have if any because the results are working as expected.

for (I vertexId : destinations) {
          if (partition.getVertex(vertexId) == null) {
            if (!resolveVertexIndices.put(partitionId, vertexId)) {
              //throw new IllegalStateException(
              //    "resolveMutations: Already has missing vertex on this " +
              //        "worker for " + vertexId);

On Wed, May 14, 2014 at 7:23 AM, Jyotirmoy Sundi <<>>

Hi Folks,

        I am seeing this error recently in jobs, can you please throw some light on what resolveMutations
in tries to achieve ?


Caused by: java.lang.IllegalStateException: resolveMutations: Already has missing vertex on
this worker for 8345381246748292335
        at org.apache.giraph.comm.netty.NettyWorkerServer.resolveMutations(
        at org.apache.giraph.comm.netty.NettyWorkerServer.prepareSuperstep(
        at org.apache.giraph.worker.BspServiceWorker.startSuperstep(
        at org.apache.giraph.graph.GraphTaskManager.execute(

Best Regards,
Jyotirmoy Sundi

Best Regards,
Jyotirmoy Sundi

View raw message