Return-Path: X-Original-To: apmail-mesos-issues-archive@minotaur.apache.org Delivered-To: apmail-mesos-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 593F818DB0 for ; Mon, 1 Feb 2016 19:18:41 +0000 (UTC) Received: (qmail 61632 invoked by uid 500); 1 Feb 2016 19:18:40 -0000 Delivered-To: apmail-mesos-issues-archive@mesos.apache.org Received: (qmail 61401 invoked by uid 500); 1 Feb 2016 19:18:40 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 61224 invoked by uid 99); 1 Feb 2016 19:18:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Feb 2016 19:18:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1A4402C1F5B for ; Mon, 1 Feb 2016 19:18:40 +0000 (UTC) Date: Mon, 1 Feb 2016 19:18:40 +0000 (UTC) From: "Artem Harutyunyan (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MESOS-3583) Introduce sessions in HTTP Scheduler API Subscribed Responses MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MESOS-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-3583: ------------------------------------- Sprint: (was: Mesosphere Sprint 28) > Introduce sessions in HTTP Scheduler API Subscribed Responses > ------------------------------------------------------------- > > Key: MESOS-3583 > URL: https://issues.apache.org/jira/browse/MESOS-3583 > Project: Mesos > Issue Type: Task > Reporter: Anand Mazumdar > Labels: mesosphere, tech-debt > > Currently, the HTTP Scheduler API has no concept of Sessions aka {{SessionID}} or a {{TokenID}}. This is useful in some failure scenarios. As of now, if a framework fails over and then subscribes again with the same {{FrameworkID}} with the {{force}} option set, the Mesos master would subscribe it. > If the previous instance of the framework/scheduler tries to send a Call , e.g. {{Call::KILL}} with the same previous {{FrameworkID}} set, it would be still accepted by the master leading to erroneously killing a task. > This is possible because we do not have a way currently of distinguishing connections. It used to work in the previous driver implementation due to the master also performing a {{UPID}} check to verify if they matched and only then allowing the call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)