[
https://issues.apache.org/jira/browse/GIRAPH-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615447#comment-14615447
]
Hudson commented on GIRAPH-1019:
--------------------------------
FAILURE: Integrated in Giraph-trunk-Commit #1556 (See
[https://builds.apache.org/job/Giraph-trunk-Commit/1556/])
[GIRAPH-1019] Optimizing and debugging vertex mutation mechanism (aching:
http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=1a4756b66bbd219943dce80a95dd46f44f46cbeb)
* giraph-core/src/main/java/org/apache/giraph/comm/netty/NettyWorkerServer.java
* giraph-examples/src/test/java/org/apache/giraph/TestMutateGraph.java
*
giraph-core/src/main/java/org/apache/giraph/comm/requests/SendPartitionMutationsRequest.java
* giraph-core/src/main/java/org/apache/giraph/graph/GraphTaskManager.java
* giraph-core/src/test/java/org/apache/giraph/comm/RequestTest.java
*
giraph-core/src/main/java/org/apache/giraph/comm/netty/NettyWorkerClientRequestProcessor.java
* giraph-core/src/main/java/org/apache/giraph/comm/SendMutationsCache.java
* CHANGELOG
*
giraph-examples/src/main/java/org/apache/giraph/examples/SimpleMutateGraphComputation.java
* giraph-core/src/main/java/org/apache/giraph/comm/ServerData.java
* giraph-core/src/main/java/org/apache/giraph/graph/ComputeCallable.java
> Optimizing and debugging vertex mutation
> ----------------------------------------
>
> Key: GIRAPH-1019
> URL: https://issues.apache.org/jira/browse/GIRAPH-1019
> Project: Giraph
> Issue Type: Improvement
> Components: graph
> Reporter: Hassan Eslami
> Assignee: Hassan Eslami
> Labels: core, migration, multi-threading
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Currently vertex mutations happen while preparing a superstep execution in a
> single-threaded manner. This is extremely inefficient specially for the case
> of out-of-core as we have to go over all the partitions, load them, and test
> if they have any applicable mutation. Also, there is an unexpected behavior
> in cases where a mutation happen to a vertex and some messages being
> delivered to that vertex at the same time (current implementation fails the
> job in that case).
> In order to fix/optimize this, mutations should happen in a multi-threaded
> fashion right before start of processing of a partition. Also, while
> partition migration happens, mutation requests should migrate along with the
> partition and its messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
