Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9FC5F200B32 for ; Wed, 25 May 2016 07:28:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9E45C160A36; Wed, 25 May 2016 05:28:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B2CB7160A35 for ; Wed, 25 May 2016 07:27:59 +0200 (CEST) Received: (qmail 8392 invoked by uid 500); 25 May 2016 05:27:58 -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 8382 invoked by uid 99); 25 May 2016 05:27:58 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 May 2016 05:27:58 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 4E603C0DC7 for ; Wed, 25 May 2016 05:27:58 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.129 X-Spam-Level: ** X-Spam-Status: No, score=2.129 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id OVX_2hJ2ng-E for ; Wed, 25 May 2016 05:27:54 +0000 (UTC) Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C1C4C5FBBD for ; Wed, 25 May 2016 05:27:53 +0000 (UTC) Received: by mail-it0-f46.google.com with SMTP id z189so57594363itg.0 for ; Tue, 24 May 2016 22:27:53 -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; bh=J/sGUAPaH9FUgsMvG6IRjhxmzZvo2jqRvRcaz4sl6jM=; b=OzfiMnY1O+75rb99FXnk8QU4+iA32qS7PWQwnnSUkpkgOvnIzf1Zfww/X72mJjeFUU UazVUIcutrhQ/rYct8orAJzxU3UURNwt1eIDRsAUaL/EHAxiRcAdocO7CCX2XZpZDw9I 7IPV5OsXIb3EbSpKp0AaH38azn6ajC3M3d9/oBqOZIWN7mELqHc9iYCSAFzL+E7Wsd8E eQoFUyC6brNmVTO1jDxjObbBtUzGKxg0v1hxsdh+YmInqhdhOK4HCgr5bmXoGvYRp6cP 9EeLtB86LHDF3rywwPBFG5xIg5Aitpy6FOz/HTa1PhmeEcEegzrnB/LT13mzqo5WudH0 Ij1A== 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; bh=J/sGUAPaH9FUgsMvG6IRjhxmzZvo2jqRvRcaz4sl6jM=; b=GSzmze8pB5V6g45LGrA/65RCEFKzDfY0ID0A4+p6OAmItKgUxVlTvUOsuHGf15mi5X rQmA4BqTRrJTSpV164Z4XK2EKQtRFBUluHfELW8BhYwDvQm/XJaj4+9QHLafZvfs/xRQ vy/tdDk48KBe/KluQiYMt8gjsth66BT7Zpq04o9y+qOIcbOWJpe2zCru4K5UiAvVOvl1 /5EUSdJpyEa77BteW8FGnNLkZ4d/4lwpT6yImazjtBLVK8GFQaMFqfpbpnPc+b0S0WeX PK3CSiGoAYPqwAJYdi4JuEQlE0Y1j/efUF5IyrtCxKeLOxN55ze+9QYXB7G5fV7VcqMz c0QA== X-Gm-Message-State: ALyK8tLV8qqFPfdLTGFbDKnNUH91b8lSRmNX8yzKqak8R7GeChWY4klKsnjJ7eAWymTWit0/fqJBW+YS9h9nSg== MIME-Version: 1.0 X-Received: by 10.36.127.1 with SMTP id r1mr2195290itc.52.1464154072747; Tue, 24 May 2016 22:27:52 -0700 (PDT) Received: by 10.64.24.240 with HTTP; Tue, 24 May 2016 22:27:52 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 May 2016 13:27:52 +0800 Message-ID: Subject: Re: "Appropriating" an existing process into mesos task From: Guangya Liu To: user@mesos.apache.org Content-Type: multipart/alternative; boundary=001a1147cb726717060533a3efa2 archived-at: Wed, 25 May 2016 05:28:00 -0000 --001a1147cb726717060533a3efa2 Content-Type: text/plain; charset=UTF-8 Hi Krishnanarayanan, How did you create your VM on baremetal servers with Mesos? Are you leveraging mesos executor or some other components? The framework have checkpoint logic which can recover tasks in one framework back to original state, please refer to https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L233-L237 , does this help? Thanks, Guangya On Wed, May 25, 2016 at 12:25 PM, Krishnanarayanan VR < krishnanvr@phonepe.com> wrote: > > Hello: > > We've been using mesos to allocate kvm VMs on our baremetal servers. > > The high level flow is as below: > o user requests a VM with nCpus and mMem. > o framework picks up an appropriate offer and spins a new VM > o the baremetal on which the VM was spun is noted into a json file. > cpu/mem resources are also noted in the same file. > o In the event that the framework dies and restarts, the file is processed > first and a VM needs to be created iff the VM does not exist ( for whatever > reason ). data for each VM is stored in a file likewise. > > My question/requirement is: > > The framework restart does not have any impact on the individual kvm VMs > on the mesos slave baremetal servers. when the framework restarts, if the > VM is already present, I'd just like to add it to the TASK_RUNNING status > with the noted resources, without having to go through the actual executor. > > Any pointers on how this can be achieved ? > > Thanks > --001a1147cb726717060533a3efa2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Krishnanarayanan,

How did you create= your VM on baremetal servers with Mesos? Are you leveraging mesos executor= or some other components?

The framework have chec= kpoint logic which can recover tasks in one framework back to original stat= e, please refer to=C2=A0https://github.com/apache/mesos/bl= ob/master/include/mesos/mesos.proto#L233-L237 , does this help?

Thanks,

Guangya

On Wed, May 25, 2016 a= t 12:25 PM, Krishnanarayanan VR <krishnanvr@phonepe.com> wrote:

Hello:=C2=A0

We'= ve been using mesos to allocate kvm VMs on our baremetal servers. =C2=A0

The high level flow is as below:
o u= ser requests a VM with nCpus and mMem.
o framework picks up an appropriate offer and spins a new VM
o the baremetal on which the VM was spun is noted i= nto a json file. =C2=A0cpu/mem resources are also noted in the same file.= =C2=A0
o In the event that the framewo= rk dies and restarts, the file is processed first and a VM needs to be crea= ted iff the VM does not exist ( for whatever reason ). =C2=A0data for each = VM is stored in a file likewise.=C2=A0

My question/requirement is:

= The framework restart does not have any impact on the individual kvm VMs on= the mesos slave baremetal servers. when the framework restarts, if the VM = is already present, I'd just like to add it to the TASK_RUNNING status = with the noted resources, without having to go through the actual executor.= =C2=A0

Any pointers on how this can be achieved ?=C2=A0

Thanks

--001a1147cb726717060533a3efa2--