[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2016-12-08 Thread Alexander Rukletsov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-1718:
---
Priority: Critical  (was: Major)

> Command executor can overcommit the slave.
> --
>
> Key: MESOS-1718
> URL: https://issues.apache.org/jira/browse/MESOS-1718
> Project: Mesos
>  Issue Type: Bug
>  Components: agent
>Reporter: Benjamin Mahler
>Priority: Critical
>
> Currently we give a small amount of resources to the command executor, in 
> addition to resources used by the command task:
> https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
> {code: title=}
> ExecutorInfo Slave::getExecutorInfo(
> const FrameworkID& frameworkId,
> const TaskInfo& task)
> {
>   ...
> // Add an allowance for the command executor. This does lead to a
> // small overcommit of resources.
> executor.mutable_resources()->MergeFrom(
> Resources::parse(
>   "cpus:" + stringify(DEFAULT_EXECUTOR_CPUS) + ";" +
>   "mem:" + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
>   ...
> }
> {code}
> This leads to an overcommit of the slave. Ideally, for command tasks we can 
> "transfer" all of the task resources to the executor at the slave / isolation 
> level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2016-07-09 Thread Klaus Ma (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Klaus Ma updated MESOS-1718:

Assignee: (was: Klaus Ma)

> Command executor can overcommit the slave.
> --
>
> Key: MESOS-1718
> URL: https://issues.apache.org/jira/browse/MESOS-1718
> Project: Mesos
>  Issue Type: Bug
>  Components: slave
>Reporter: Benjamin Mahler
>
> Currently we give a small amount of resources to the command executor, in 
> addition to resources used by the command task:
> https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
> {code: title=}
> ExecutorInfo Slave::getExecutorInfo(
> const FrameworkID& frameworkId,
> const TaskInfo& task)
> {
>   ...
> // Add an allowance for the command executor. This does lead to a
> // small overcommit of resources.
> executor.mutable_resources()->MergeFrom(
> Resources::parse(
>   "cpus:" + stringify(DEFAULT_EXECUTOR_CPUS) + ";" +
>   "mem:" + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
>   ...
> }
> {code}
> This leads to an overcommit of the slave. Ideally, for command tasks we can 
> "transfer" all of the task resources to the executor at the slave / isolation 
> level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2016-01-13 Thread Ian Downes (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Downes updated MESOS-1718:
--
Assignee: (was: Ian Downes)

> Command executor can overcommit the slave.
> --
>
> Key: MESOS-1718
> URL: https://issues.apache.org/jira/browse/MESOS-1718
> Project: Mesos
>  Issue Type: Bug
>  Components: slave
>Reporter: Benjamin Mahler
>
> Currently we give a small amount of resources to the command executor, in 
> addition to resources used by the command task:
> https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
> {code: title=}
> ExecutorInfo Slave::getExecutorInfo(
> const FrameworkID& frameworkId,
> const TaskInfo& task)
> {
>   ...
> // Add an allowance for the command executor. This does lead to a
> // small overcommit of resources.
> executor.mutable_resources()->MergeFrom(
> Resources::parse(
>   "cpus:" + stringify(DEFAULT_EXECUTOR_CPUS) + ";" +
>   "mem:" + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
>   ...
> }
> {code}
> This leads to an overcommit of the slave. Ideally, for command tasks we can 
> "transfer" all of the task resources to the executor at the slave / isolation 
> level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2014-12-15 Thread Dominic Hamon (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominic Hamon updated MESOS-1718:
-
Sprint: Twitter Mesos Q4 Sprint 3, Twitter Mesos Q4 Sprint 4, Twitter Mesos 
Q4 Sprint 5, Twitter Mesos Q4 Sprint 6  (was: Twitter Mesos Q4 Sprint 3, 
Twitter Mesos Q4 Sprint 4, Twitter Mesos Q4 Sprint 5)

 Command executor can overcommit the slave.
 --

 Key: MESOS-1718
 URL: https://issues.apache.org/jira/browse/MESOS-1718
 Project: Mesos
  Issue Type: Bug
  Components: slave
Reporter: Benjamin Mahler
Assignee: Ian Downes

 Currently we give a small amount of resources to the command executor, in 
 addition to resources used by the command task:
 https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
 {code: title=}
 ExecutorInfo Slave::getExecutorInfo(
 const FrameworkID frameworkId,
 const TaskInfo task)
 {
   ...
 // Add an allowance for the command executor. This does lead to a
 // small overcommit of resources.
 executor.mutable_resources()-MergeFrom(
 Resources::parse(
   cpus: + stringify(DEFAULT_EXECUTOR_CPUS) + ; +
   mem: + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
   ...
 }
 {code}
 This leads to an overcommit of the slave. Ideally, for command tasks we can 
 transfer all of the task resources to the executor at the slave / isolation 
 level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2014-12-01 Thread Dominic Hamon (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominic Hamon updated MESOS-1718:
-
Sprint: Twitter Mesos Q4 Sprint 3, Twitter Mesos Q4 Sprint 4, Twitter Mesos 
Q4 Sprint 5  (was: Twitter Mesos Q4 Sprint 3, Twitter Mesos Q4 Sprint 4)

 Command executor can overcommit the slave.
 --

 Key: MESOS-1718
 URL: https://issues.apache.org/jira/browse/MESOS-1718
 Project: Mesos
  Issue Type: Bug
  Components: slave
Reporter: Benjamin Mahler
Assignee: Ian Downes

 Currently we give a small amount of resources to the command executor, in 
 addition to resources used by the command task:
 https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
 {code: title=}
 ExecutorInfo Slave::getExecutorInfo(
 const FrameworkID frameworkId,
 const TaskInfo task)
 {
   ...
 // Add an allowance for the command executor. This does lead to a
 // small overcommit of resources.
 executor.mutable_resources()-MergeFrom(
 Resources::parse(
   cpus: + stringify(DEFAULT_EXECUTOR_CPUS) + ; +
   mem: + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
   ...
 }
 {code}
 This leads to an overcommit of the slave. Ideally, for command tasks we can 
 transfer all of the task resources to the executor at the slave / isolation 
 level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2014-11-17 Thread Dominic Hamon (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominic Hamon updated MESOS-1718:
-
Sprint: Twitter Mesos Q4 Sprint 3, Twitter Mesos Q4 Sprint 4  (was: Twitter 
Mesos Q4 Sprint 3)

 Command executor can overcommit the slave.
 --

 Key: MESOS-1718
 URL: https://issues.apache.org/jira/browse/MESOS-1718
 Project: Mesos
  Issue Type: Bug
  Components: slave
Reporter: Benjamin Mahler
Assignee: Ian Downes

 Currently we give a small amount of resources to the command executor, in 
 addition to resources used by the command task:
 https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
 {code: title=}
 ExecutorInfo Slave::getExecutorInfo(
 const FrameworkID frameworkId,
 const TaskInfo task)
 {
   ...
 // Add an allowance for the command executor. This does lead to a
 // small overcommit of resources.
 executor.mutable_resources()-MergeFrom(
 Resources::parse(
   cpus: + stringify(DEFAULT_EXECUTOR_CPUS) + ; +
   mem: + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
   ...
 }
 {code}
 This leads to an overcommit of the slave. Ideally, for command tasks we can 
 transfer all of the task resources to the executor at the slave / isolation 
 level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2014-11-03 Thread Dominic Hamon (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominic Hamon updated MESOS-1718:
-
Sprint: Twitter Mesos Q4 Sprint 3

 Command executor can overcommit the slave.
 --

 Key: MESOS-1718
 URL: https://issues.apache.org/jira/browse/MESOS-1718
 Project: Mesos
  Issue Type: Bug
  Components: slave
Reporter: Benjamin Mahler
Assignee: Ian Downes

 Currently we give a small amount of resources to the command executor, in 
 addition to resources used by the command task:
 https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
 {code: title=}
 ExecutorInfo Slave::getExecutorInfo(
 const FrameworkID frameworkId,
 const TaskInfo task)
 {
   ...
 // Add an allowance for the command executor. This does lead to a
 // small overcommit of resources.
 executor.mutable_resources()-MergeFrom(
 Resources::parse(
   cpus: + stringify(DEFAULT_EXECUTOR_CPUS) + ; +
   mem: + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
   ...
 }
 {code}
 This leads to an overcommit of the slave. Ideally, for command tasks we can 
 transfer all of the task resources to the executor at the slave / isolation 
 level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2014-11-03 Thread Dominic Hamon (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominic Hamon updated MESOS-1718:
-
Story Points: 3

 Command executor can overcommit the slave.
 --

 Key: MESOS-1718
 URL: https://issues.apache.org/jira/browse/MESOS-1718
 Project: Mesos
  Issue Type: Bug
  Components: slave
Reporter: Benjamin Mahler
Assignee: Ian Downes

 Currently we give a small amount of resources to the command executor, in 
 addition to resources used by the command task:
 https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
 {code: title=}
 ExecutorInfo Slave::getExecutorInfo(
 const FrameworkID frameworkId,
 const TaskInfo task)
 {
   ...
 // Add an allowance for the command executor. This does lead to a
 // small overcommit of resources.
 executor.mutable_resources()-MergeFrom(
 Resources::parse(
   cpus: + stringify(DEFAULT_EXECUTOR_CPUS) + ; +
   mem: + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
   ...
 }
 {code}
 This leads to an overcommit of the slave. Ideally, for command tasks we can 
 transfer all of the task resources to the executor at the slave / isolation 
 level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2014-09-22 Thread Dominic Hamon (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominic Hamon updated MESOS-1718:
-
Shepherd: Benjamin Mahler

 Command executor can overcommit the slave.
 --

 Key: MESOS-1718
 URL: https://issues.apache.org/jira/browse/MESOS-1718
 Project: Mesos
  Issue Type: Bug
  Components: slave
Reporter: Benjamin Mahler
Assignee: Ian Downes

 Currently we give a small amount of resources to the command executor, in 
 addition to resources used by the command task:
 https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
 {code: title=}
 ExecutorInfo Slave::getExecutorInfo(
 const FrameworkID frameworkId,
 const TaskInfo task)
 {
   ...
 // Add an allowance for the command executor. This does lead to a
 // small overcommit of resources.
 executor.mutable_resources()-MergeFrom(
 Resources::parse(
   cpus: + stringify(DEFAULT_EXECUTOR_CPUS) + ; +
   mem: + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
   ...
 }
 {code}
 This leads to an overcommit of the slave. Ideally, for command tasks we can 
 transfer all of the task resources to the executor at the slave / isolation 
 level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1718) Command executor can overcommit the slave.

2014-08-19 Thread Vinod Kone (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-1718:
--

Assignee: (was: Vinod Kone)

 Command executor can overcommit the slave.
 --

 Key: MESOS-1718
 URL: https://issues.apache.org/jira/browse/MESOS-1718
 Project: Mesos
  Issue Type: Bug
  Components: slave
Reporter: Benjamin Mahler

 Currently we give a small amount of resources to the command executor, in 
 addition to resources used by the command task:
 https://github.com/apache/mesos/blob/0.20.0-rc1/src/slave/slave.cpp#L2448
 {code: title=}
 ExecutorInfo Slave::getExecutorInfo(
 const FrameworkID frameworkId,
 const TaskInfo task)
 {
   ...
 // Add an allowance for the command executor. This does lead to a
 // small overcommit of resources.
 executor.mutable_resources()-MergeFrom(
 Resources::parse(
   cpus: + stringify(DEFAULT_EXECUTOR_CPUS) + ; +
   mem: + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
   ...
 }
 {code}
 This leads to an overcommit of the slave. Ideally, for command tasks we can 
 transfer all of the task resources to the executor at the slave / isolation 
 level.



--
This message was sent by Atlassian JIRA
(v6.2#6252)