[jira] [Resolved] (GIRAPH-1019) Optimizing and debugging vertex mutation

["Avery Ching (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GIRAPH-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Avery Ching resolved GIRAPH-1019.
---------------------------------
    Resolution: Fixed

Thanks Hassan for the diff and Dionysios for the review.  Committed!

> 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)