Return-Path: 
 <yarn-dev-return-3361-apmail-hadoop-yarn-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 957C510324
	for <apmail-hadoop-yarn-dev-archive@minotaur.apache.org>;
 Mon, 29 Jul 2013 14:58:42 +0000 (UTC)
Received: (qmail 7848 invoked by uid 500); 29 Jul 2013 14:58:37 -0000
Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org
Received: (qmail 7759 invoked by uid 500); 29 Jul 2013 14:58:36 -0000
Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-dev@hadoop.apache.org>
List-Id: <yarn-dev.hadoop.apache.org>
Reply-To: yarn-dev@hadoop.apache.org
Delivered-To: mailing list yarn-dev@hadoop.apache.org
Received: (qmail 7272 invoked by uid 99); 29 Jul 2013 14:58:35 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jul 2013 14:58:35 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of ozawa.tsuyoshi@gmail.com
 designates 74.125.82.181 as permitted sender)
Received: from [74.125.82.181] (HELO mail-we0-f181.google.com) (74.125.82.181)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jul 2013 14:58:29 +0000
Received: by mail-we0-f181.google.com with SMTP id p58so4124900wes.12
        for <multiple recipients>; Mon, 29 Jul 2013 07:58:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=o7LyRvbE8LM8mpThnScpc84t8tmh3/fMQIZktFHFgoE=;
        b=ZgLUL6qr7VMvALeoqdTPjUrH7uiSzS6Fh4ojGq51EYP37HMvdYjJ/ple3ELeZpKxdm
         kGQU0AlJj0T3PaW5yq3vbG6pyES+MzuwlqExUOnZVxU754uPr6BA5ler72DVib5Tz81f
         yTZUHozVmBMfCa1nyab+acnmmqyQO62YPFB0S86B601zhxr/wirFKMQtZXS/uFnbxV4H
         WyxKQcGTpkONi1xtoOcYivV2ACm9MxD7zp5wnIELPeG7UChdb5Kk9TXLOEhDaedQpZj9
         1jxFiHyEufLzAZbOOLVefeMNAvrwD719t0N5v5juLiU/Viq3XMJcmj1Q8zkR7DQT0jhf
         sGEw==
MIME-Version: 1.0
X-Received: by 10.180.73.103 with SMTP id k7mr7469661wiv.24.1375109889423;
 Mon, 29 Jul 2013 07:58:09 -0700 (PDT)
Received: by 10.216.156.194 with HTTP; Mon, 29 Jul 2013 07:58:09 -0700 (PDT)
In-Reply-To: 
 <CAOcnVr1AnzDAxZY3UM86ix5A0VOZt6arLvGfZoNPYgXR0nCy5Q@mail.gmail.com>
References: 
 <CAAD07OLom2SUHBwHKmpQ0YNsQtQTAM9-4igcui+rjkJz3XN7jQ@mail.gmail.com>
	<CAOcnVr1AnzDAxZY3UM86ix5A0VOZt6arLvGfZoNPYgXR0nCy5Q@mail.gmail.com>
Date: Mon, 29 Jul 2013 23:58:09 +0900
Message-ID: 
 <CAAD07OLbNRBb=JByKGQC4PKFa32KfjzDSNoOPcNqLnetsh0+SQ@mail.gmail.com>
Subject: Re: Abstraction layer to support both YARN and Mesos
From: Tsuyoshi OZAWA <ozawa.tsuyoshi@gmail.com>
To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Cc: "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
 user@mesos.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

I thought some high availability and resource isolation features in
Mesos are more matured. If no one is interested in this topic, MR
should go with YARN.

On Fri, Jul 26, 2013 at 7:14 PM, Harsh J <harsh@cloudera.com> wrote:
> Do we have a good reason to prefer Mesos over YARN for scheduling MR
> specifically? At what times would one prefer the other?
>
> On Fri, Jul 26, 2013 at 11:43 AM, Tsuyoshi OZAWA
> <ozawa.tsuyoshi@gmail.com> wrote:
>> Hi,
>>
>> Now, Apache Mesos, an distributed resource manager, is top-level
>> apache project. Meanwhile, As you know, Hadoop has own resource
>> manager - YARN. IMHO, we should make resource manager pluggable in
>> MRv2, because there are their own field users of MapReduce would like
>> to use. I think this work is useful for MapReduce users. On the other
>> hand, this work can also be large, because MRv2's code base is tightly
>> coupled with YARN currently. Thoughts?
>>
>> - Tsuyoshi
>
>
>
> --
> Harsh J



-- 
- Tsuyoshi