Mailing-List: contact user-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hama.apache.org
Received-SPF: pass (athena.apache.org: domain of menonsuraj5@gmail.com
 designates 209.85.161.175 as permitted sender)
MIME-Version: 1.0
Sender: menonsuraj5@gmail.com
In-Reply-To: 
 <CAJ-=ys=Jsv72RUkKwR_bp6FKOAaO-JrC0DmMgZBoeJ4pmmhGsQ@mail.gmail.com>
References: 
 <CAGQgZQQ9CDHTiJSy8BXAnVVMkMbwJyb09bL=vBmk2rvjd5ADDQ@mail.gmail.com>
	<CAJ-=ys=Jsv72RUkKwR_bp6FKOAaO-JrC0DmMgZBoeJ4pmmhGsQ@mail.gmail.com>
Date: Fri, 15 Jun 2012 09:02:20 -0400
Message-ID: 
 <CALis4o7E4BK85=uXzWi92s+DpNeF7CAuqY_Ydo=4-+q3_LF+3g@mail.gmail.com>
Subject: Re: deregisterFromBarrier()
From: Suraj Menon <surajsmenon@apache.org>
To: user@hama.apache.org
Content-Type: multipart/alternative; boundary=20cf302d49be34a9c104c2826d69

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

In my opinion, this function is useful when you want to relieve a BSP Peer
to close and free the Task slot on Groomserver while other peers have few
more superstep to work on. I know our current barrier implementation would
fail with that. Will be working on this as a part of the BSP Peer API
improvements.

For fault tolerance, especially when checkpointing received  messages, I
did not need this function. The nodes being ephemeral gets deleted in the
scenario when I restart peer processes.

On Fri, Jun 15, 2012 at 8:30 AM, Thomas Jungblut <
thomas.jungblut@googlemail.com> wrote:

> That's (probably) used in Suraj's fault tolerance works when a task needs
> to be removed from the host lists and the barrier.
>
> 2012/6/15 Edward J. Yoon <edwardyoon@apache.org>
>
> > Just found this function in SyncClient.
> >
> > Is there more detail plan for this?
> > --
> > Best Regards, Edward J. Yoon
> > @eddieyoon
> >
>
>
>
> --
> Thomas Jungblut
> Berlin <thomas.jungblut@gmail.com>
>

--20cf302d49be34a9c104c2826d69--