Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Thu, 10 Jan 2013 21:10:13 +0000 (UTC)
From: "Eli Reisman (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12626833.1357759994272.115789.1357852213198@arcas>
In-Reply-To: <JIRA.12626833.1357759994272@arcas>
References: <JIRA.12626833.1357759994272@arcas>
Subject: [jira] [Commented] (GIRAPH-477) Fetching locality info in
 InputSplitPathOrganizer causes jobs to hang
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GIRAPH-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550416#comment-13550416 ] 

Eli Reisman commented on GIRAPH-477:
------------------------------------

lets do 473 first, this is smaller. Sound good?

                
> Fetching locality info in InputSplitPathOrganizer causes jobs to hang
> ---------------------------------------------------------------------
>
>                 Key: GIRAPH-477
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-477
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Alessandro Presta
>            Assignee: Alessandro Presta
>         Attachments: GIRAPH-477.patch
>
>
> In the presence of many input splits (>6000 in our case) and input split threads (3000), the loop that fetches locality info for all splits from ZooKeeper becomes a bottleneck. A few workers aren't able to even iterate once over the list, run into increased GC pauses, and eventually time out.
> Furthermore, depending on the cluster configuration, it's not always possible/useful to exploit locality.
> We should add a flag so that the feature can be optionally disabled.

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