[
https://issues.apache.org/jira/browse/GIRAPH-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550609#comment-13550609
]
Hudson commented on GIRAPH-473:
-------------------------------
Integrated in Giraph-trunk-Commit #590 (See
[https://builds.apache.org/job/Giraph-trunk-Commit/590/])
GIRAPH-473: InputSplitPathOrganizer should be aware of multiple threads
(apresta via ereisman) (Revision a5bc5bb35a84a2c61623da9269842985e7cc9da5)
Result = FAILURE
ereisman :
http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=a5bc5bb35a84a2c61623da9269842985e7cc9da5
Files :
*
giraph-core/src/main/java/org/apache/giraph/worker/VertexInputSplitsCallable.java
*
giraph-core/src/main/java/org/apache/giraph/worker/InputSplitPathOrganizer.java
* CHANGELOG
*
giraph-core/src/main/java/org/apache/giraph/worker/EdgeInputSplitsCallable.java
* giraph-core/src/main/java/org/apache/giraph/worker/BspServiceWorker.java
*
giraph-core/src/main/java/org/apache/giraph/worker/EdgeInputSplitsCallableFactory.java
* giraph-core/src/test/java/org/apache/giraph/TestBspBasic.java
*
giraph-core/src/main/java/org/apache/giraph/worker/InputSplitsCallableFactory.java
*
giraph-core/src/main/java/org/apache/giraph/worker/VertexInputSplitsCallableFactory.java
* giraph-core/src/main/java/org/apache/giraph/worker/InputSplitsCallable.java
> InputSplitPathOrganizer should be aware of multiple threads
> -----------------------------------------------------------
>
> Key: GIRAPH-473
> URL: https://issues.apache.org/jira/browse/GIRAPH-473
> Project: Giraph
> Issue Type: Improvement
> Reporter: Alessandro Presta
> Assignee: Alessandro Presta
> Priority: Minor
> Attachments: GIRAPH-473.patch, GIRAPH-473.patch, GIRAPH-473.patch
>
>
> The starting offset for iterating over input splits is obtained by hashing
> the worker's hostname and port. When multiple input threads are used, they
> get the same offset.
> We should hash the thread id as well.
--
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
