aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zane silver (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AURORA-1289) Preclude co-scheduling of multiple tasks with the same static port
Date Tue, 21 Apr 2015 22:07:58 GMT
zane silver created AURORA-1289:
-----------------------------------

             Summary: 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


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)

Mime
View raw message