Return-Path: X-Original-To: apmail-aurora-issues-archive@minotaur.apache.org Delivered-To: apmail-aurora-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 6D5C31795D for ; Tue, 21 Apr 2015 22:11:59 +0000 (UTC) Received: (qmail 45706 invoked by uid 500); 21 Apr 2015 22:11:59 -0000 Delivered-To: apmail-aurora-issues-archive@aurora.apache.org Received: (qmail 45510 invoked by uid 500); 21 Apr 2015 22:11:59 -0000 Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list issues@aurora.apache.org Received: (qmail 45358 invoked by uid 99); 21 Apr 2015 22:11:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2015 22:11:59 +0000 Date: Tue, 21 Apr 2015 22:11:59 +0000 (UTC) From: "zane silver (JIRA)" To: issues@aurora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (AURORA-1289) Preclude co-scheduling of multiple tasks with the same static port 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/AURORA-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zane silver reassigned AURORA-1289: ----------------------------------- Assignee: Bill Farner > Preclude co-scheduling of multiple tasks with the same static port > ------------------------------------------------------------------ > > Key: AURORA-1289 > URL: https://issues.apache.org/jira/browse/AURORA-1289 > Project: Aurora > Issue Type: Story > Reporter: zane silver > Assignee: Bill Farner > > The current documentation states that, > "Static ports should be used cautiously as Aurora does nothing to prevent two tasks with the same static port allocations from being co-scheduled". > http://aurora.apache.org/documentation/latest/configuration-reference/#announcer-objects > Is there a benefit to being able to co-schedule two (or more) tasks with the same static port number to the same machine? It would seem that this is a bug. The proper functionality should treat static ports as a resource: once the port is acquired by a task, it will not be offered to any other task until the port resource is released. Therefore, no two tasks with the same port can be co-scheduled to the same machine. > The current implementation requires that clients using the Aurora scheduler have global knowledge of all static port allocations. This is clearly impossible for a large and scalable system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)