Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Received-SPF: pass (athena.apache.org: domain of praveensripati@gmail.com
 designates 209.85.212.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADYHM8xrnbKbXe7P7mR1b4oVX9mzh=nnEUE1oxV1GjZpQdKjuA@mail.gmail.com>
References: 
 <CADYHM8xrnbKbXe7P7mR1b4oVX9mzh=nnEUE1oxV1GjZpQdKjuA@mail.gmail.com>
Date: Sat, 30 Jun 2012 23:17:26 +0530
Message-ID: 
 <CADYHM8xtTBEDufAunJpOKpnoUv3CK1=d5xdMa0OrnwNf3f-SCA@mail.gmail.com>
Subject: Re: How does scaling work in Giraph?
From: Praveen Sripati <praveensripati@gmail.com>
To: dev@giraph.apache.org
Content-Type: multipart/alternative; boundary=bcaec51b18e36d229b04c3b4286e

--bcaec51b18e36d229b04c3b4286e
Content-Type: text/plain; charset=ISO-8859-1

Could someone respond to the below mail please?

Thanks,
Praveen

On Thu, Jun 28, 2012 at 7:04 PM, Praveen Sripati
<praveensripati@gmail.com>wrote:

>
> During the 24th minute of the recent Hadoop Summit Video [1] Avery Ching
> talks about how Giraph is made scalable. I am interested in Hama which is
> also based on the BSP model and would like to know more details on how
> Giraph is made scalable.
>
> Basically, at the end of each super step, the BSP tasks sends some metrics
> to the master and the master partitions the data in the most loaded BSP
> tasks and uses the free map available slot to process them.
>
> 1) Where is the code for the above logic? I am new to Giraph.
>
> 2) What is the logic behind the partitioning of the data in the master
> after the super step? Let's say that the data has been partitioned using
> Hash partitioning.
>
> 3) Similarly will Giraph also scale down? Will the partitions be merged?
>
> Thanks,
> Praveen
>
> [1] - http://www.youtube.com/watch?v=b5Qmz4zPj-M
>

--bcaec51b18e36d229b04c3b4286e--