[
https://issues.apache.org/jira/browse/GIRAPH-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547180#comment-13547180
]
Eli Reisman commented on GIRAPH-473:
------------------------------------
Nice! I had a conversation on an older thread with Avery about this a while
back. When running on a ZK quorum with more than a single instance, it causes
significant slowdowns when the hashes collide and workers (and now threads with
the multithreading) contend for splits.
> 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
>
>
> 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
