Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 114C117683 for ; Mon, 29 Sep 2014 21:35:49 +0000 (UTC) Received: (qmail 59287 invoked by uid 500); 29 Sep 2014 21:35:25 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 59243 invoked by uid 500); 29 Sep 2014 21:35:25 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 59215 invoked by uid 99); 29 Sep 2014 21:35:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2014 21:35:25 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.214.180] (HELO mail-ob0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2014 21:35:20 +0000 Received: by mail-ob0-f180.google.com with SMTP id va2so1384502obc.11 for ; Mon, 29 Sep 2014 14:35:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=L8cb0UP4/zbtnUrE02klNsXstfxNEfzX9yH4jTrQNmY=; b=EHF+y36l908bPhYEij8yeRUYKtiAz4ngRUgEVdhY92p7nTW0Vb2gPTRCSYhTDZW3dM 5kfUVHJ2WSwX1Hm+49vH/L0+3Jt97RmFEjlpltHdWK6iAUbRZcJg9dwRmgqkyYbrKe76 phqPl5G0hHTMuDBfdq9sEs97YMPBSey8loSbzfx1LLKzcE18yNDOCvzk6axhxtr83GEj OeNg4LavCGQqgz+rof5RkCAWD2uY9CRgM5YxmvKqyvZVigONIG9WF921SpcKgiNbx4mz jTBx+1V/gvafAgeU81Jp6bKanmvwbIpjfGz7DTXZpZNjyKD3Xxf9WkQeabfNNu4pDbfg anjA== X-Gm-Message-State: ALoCoQnkVwI0VQWB2NfysO5Ff/8iAXx7+xS91eUm0OaMHhNb8uiz2+B2Sj+Gb9mAq3wA8FaNmE+0 MIME-Version: 1.0 X-Received: by 10.182.236.65 with SMTP id us1mr43217928obc.38.1412026500015; Mon, 29 Sep 2014 14:35:00 -0700 (PDT) Received: by 10.202.14.204 with HTTP; Mon, 29 Sep 2014 14:34:59 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Sep 2014 15:34:59 -0600 Message-ID: Subject: Re: Mesos master failure question From: Andy Grove To: user@mesos.apache.org Content-Type: multipart/alternative; boundary=001a11c2f9acf288e005043b0903 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2f9acf288e005043b0903 Content-Type: text/plain; charset=UTF-8 Thanks, Vinod. That is good to hear. Thanks, Andy. -- Andy Grove VP Engineering CodeFutures Corporation On Mon, Sep 29, 2014 at 11:59 AM, Vinod Kone wrote: > Executors/tasks will keep running when the master is down. Any status > updates sent by executors will be cached by the slaves and retried upon a > new master being elected as leader. > > > -- Vinod > > On Mon, Sep 29, 2014 at 10:11 AM, Andy Grove > wrote: > >> Hi, >> >> I'd like to clarify how master failures are handled. Do executors and >> tasks continue operating while the master is down? >> >> For example, if I have 3 master nodes and my scheduler causes a mysql >> server to start on a slave and then the leader master fails, will mysql >> keep running through this failure? >> >> I read an article that said the slave stops all running tasks in the >> event of a master failure, but I can't find that article now, and other >> articles indicate otherwise. I couldn't find a conclusive answer in the >> mesos docs either. >> >> Thanks, >> >> Andy. >> >> -- >> Andy Grove >> VP Engineering >> CodeFutures Corporation >> >> >> > --001a11c2f9acf288e005043b0903 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks, Vinod. That is good to hear.

Thanks,

Andy.

--
Andy Grove
VP Engineerin= g
CodeFutures Corporation



On Mon, Sep 29, 2014 at 11:59 AM, Vinod Kone= <vinodkone@gmail.com> wrote:
Executors/tasks will keep running when the master is dow= n. Any status updates sent by executors will be cached by the slaves and re= tried upon a new master being elected as leader.


-- Vinod

On Mon, Sep 29, 2014 at 10:11 AM, Andy Grove= <andy.grove@codefutures.com> wrote:
Hi,

I'd like to= clarify how master failures are handled. Do executors and tasks continue o= perating while the master is down?

For example, if= I have 3 master nodes and my scheduler causes a mysql server to start on a= slave and then the leader master fails, will mysql keep running through th= is failure?

I read an article that said the slave = stops all running tasks in the event of a master failure, but I can't f= ind that article now, and other articles indicate otherwise. I couldn't= find a conclusive answer in the mesos docs either.

Thanks,

Andy.

--
Andy Grove
VP Engineering
CodeFutures Corporation




--001a11c2f9acf288e005043b0903--