You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Avery Ching (JIRA)" <ji...@apache.org> on 2013/01/29 23:35:12 UTC
[jira] [Commented] (GIRAPH-492) Saving vertices has no status
report, making it hard to find DFS issues
[ https://issues.apache.org/jira/browse/GIRAPH-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565896#comment-13565896 ]
Avery Ching commented on GIRAPH-492:
------------------------------------
https://reviews.apache.org/r/9138/
> Saving vertices has no status report, making it hard to find DFS issues
> -----------------------------------------------------------------------
>
> Key: GIRAPH-492
> URL: https://issues.apache.org/jira/browse/GIRAPH-492
> Project: Giraph
> Issue Type: Bug
> Reporter: Avery Ching
> Assignee: Avery Ching
>
> Adds status updates to saving of the vertices and improve the overall logic of when to print status of loading/storing the graph (every 250k vertices or 15 secs). This will help us to see which are the slow workers when saving output. This updates the Hadoop status messages as well as prints to the task log. I also made this consistent for the loading.
> Task log messages look like the following:
> org.apache.giraph.worker.BspServiceWorker - saveVertices: Saved 598753 out of 1000000 vertices, on partition 14 out of 24
> INFO 2013-01-29 12:54:02,072 [main] org.apache.giraph.worker.BspServiceWorker - saveVertices: Saved 848754 out of 1000000 vertices, on partition 20 out of 24
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira