You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hama.apache.org by "Edward J. Yoon" <ed...@apache.org> on 2012/06/15 14:14:27 UTC

deregisterFromBarrier()

Just found this function in SyncClient.

Is there more detail plan for this?
-- 
Best Regards, Edward J. Yoon
@eddieyoon

Re: deregisterFromBarrier()

Posted by "Edward J. Yoon" <ed...@apache.org>.
> Will be working on this as a part of the BSP Peer API
> improvements.

Like :)

On Fri, Jun 15, 2012 at 10:02 PM, Suraj Menon <su...@apache.org> wrote:
> 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 <ed...@apache.org>
>>
>> > Just found this function in SyncClient.
>> >
>> > Is there more detail plan for this?
>> > --
>> > Best Regards, Edward J. Yoon
>> > @eddieyoon
>> >
>>
>>
>>
>> --
>> Thomas Jungblut
>> Berlin <th...@gmail.com>
>>



-- 
Best Regards, Edward J. Yoon
@eddieyoon

Re: deregisterFromBarrier()

Posted by Suraj Menon <su...@apache.org>.
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 <ed...@apache.org>
>
> > Just found this function in SyncClient.
> >
> > Is there more detail plan for this?
> > --
> > Best Regards, Edward J. Yoon
> > @eddieyoon
> >
>
>
>
> --
> Thomas Jungblut
> Berlin <th...@gmail.com>
>

Re: deregisterFromBarrier()

Posted by Thomas Jungblut <th...@googlemail.com>.
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 <ed...@apache.org>

> Just found this function in SyncClient.
>
> Is there more detail plan for this?
> --
> Best Regards, Edward J. Yoon
> @eddieyoon
>



-- 
Thomas Jungblut
Berlin <th...@gmail.com>