incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Jungblut <thomas.jungb...@googlemail.com>
Subject Re: [DISCUSS] Rearrange our roadmap
Date Fri, 10 Jun 2011 17:56:27 GMT
Without know what is inside MR-279. The "ϕ accrual failure detector"
sounds like a reasonable way to detect faults.
Can someone please point out what features the MR-279 branch has?
Links to Jira issues would be very cool.

Thanks in advance :)

2011/6/10 Edward J. Yoon <edwardyoon@apache.org>:
> As far as I can recall, there was no conclusion.
>
> http://www.mail-archive.com/hama-dev@incubator.apache.org/msg03742.html
>
> and "ϕ accrual failure detector" also.
>
> On Fri, Jun 10, 2011 at 11:46 AM, ChiaHung Lin <chl501@nuk.edu.tw> wrote:
>> I remember there was discussion that Hama would not adapt to MR-279. Is this still
the case?
>>
>> -----Original message-----
>> From:Steve Loughran <stevel@apache.org>
>> To:hama-dev@incubator.apache.org
>> Date:Wed, 08 Jun 2011 12:15:14 +0100
>> Subject:Re: [DISCUSS] Rearrange our roadmap
>>
>> On 06/08/2011 06:22 AM, Edward J. Yoon wrote:
>>> Hi all,
>>>
>>> I would suggest that we have to focus on performance improvements and
>>> basic communication parts of BSP framework. So I've little edited our
>>> roadmap page.
>>>
>>> http://wiki.apache.org/hama/RoadMap
>>>
>>> If you have any comments or other opinions, let's discuss here.
>>>
>>> Thanks.
>>
>> I'd recommend targeting running the fault tolerant code under the MR-279
>> engine (hadoop 0.22 or .23?), as this will deploy more than just the MR
>> engine, and handle liveness -so you don't need to replicate core modules.
>>
>> the big thing for BSP engines is checkpointing, where the sync point
>> becomes the thing you can checkpoint.
>>
>>
>> --
>> ChiaHung Lin
>> Department of Information Management
>> National University of Kaohsiung
>> Taiwan
>>
>
>
>
> --
> Best Regards, Edward J. Yoon
> @eddieyoon
>



-- 
Thomas Jungblut
Berlin

mobile: 0170-3081070

business: thomas.jungblut@testberichte.de
private: thomas.jungblut@gmail.com

Mime
View raw message