[jira] [Commented] (MESOS-4811) Reusable/Cacheable Offer

2016-09-06 Thread Klaus Ma (JIRA)

[ 
https://issues.apache.org/jira/browse/MESOS-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469385#comment-15469385
 ] 

Klaus Ma commented on MESOS-4811:
-

The requirement is different :). Although we can improve performance by batch, 
it's still some downgrade here; and it's heavy for master to let each workload 
go through Mesos master.

> Reusable/Cacheable Offer
> 
>
> Key: MESOS-4811
> URL: https://issues.apache.org/jira/browse/MESOS-4811
> Project: Mesos
>  Issue Type: Bug
>  Components: allocation
>Reporter: Klaus Ma
>Assignee: Abhishek Dasgupta
>  Labels: tech-debt
>
> Currently, the resources are return back to allocator when task finished; and 
> those resources are not allocated to framework until next allocation cycle. 
> The performance is low for short running tasks (MESOS-3078). The proposed 
> solution is to let framework keep using the offer until allocator decide to 
> rescind it.



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


[jira] [Commented] (MESOS-4811) Reusable/Cacheable Offer

2016-09-06 Thread Guangya Liu (JIRA)

[ 
https://issues.apache.org/jira/browse/MESOS-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469367#comment-15469367
 ] 

Guangya Liu commented on MESOS-4811:


Based on requirement description, this is duplicate with MESOS-3078 , 
[~klaus1982] [~abi...@gmail.com] please help confirm. Thanks.

> Reusable/Cacheable Offer
> 
>
> Key: MESOS-4811
> URL: https://issues.apache.org/jira/browse/MESOS-4811
> Project: Mesos
>  Issue Type: Bug
>  Components: allocation
>Reporter: Klaus Ma
>Assignee: Abhishek Dasgupta
>  Labels: tech-debt
>
> Currently, the resources are return back to allocator when task finished; and 
> those resources are not allocated to framework until next allocation cycle. 
> The performance is low for short running tasks (MESOS-3078). The proposed 
> solution is to let framework keep using the offer until allocator decide to 
> rescind it.



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


[jira] [Commented] (MESOS-4811) Reusable/Cacheable Offer

2016-07-13 Thread Klaus Ma (JIRA)

[ 
https://issues.apache.org/jira/browse/MESOS-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374550#comment-15374550
 ] 

Klaus Ma commented on MESOS-4811:
-

[~a10gupta], thanks for your interesting on this EPIC; this EPIC dependent on 
several other EPICs, e.g. "Manage offer in allocator" (MESOS-4553), Revocable 
by default, performance improvement of Resources/Sorter.

So I'd suggest to join the discussion other EPICs before the working on this 
one :). Currently, we're focus on performance improvement of Resources/Sorter 
as discussion in dev@.

> Reusable/Cacheable Offer
> 
>
> Key: MESOS-4811
> URL: https://issues.apache.org/jira/browse/MESOS-4811
> Project: Mesos
>  Issue Type: Bug
>  Components: allocation
>Reporter: Klaus Ma
>Assignee: Abhishek Dasgupta
>  Labels: tech-debt
>
> Currently, the resources are return back to allocator when task finished; and 
> those resources are not allocated to framework until next allocation cycle. 
> The performance is low for short running tasks (MESOS-3078). The proposed 
> solution is to let framework keep using the offer until allocator decide to 
> rescind it.



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


[jira] [Commented] (MESOS-4811) Reusable/Cacheable Offer

2016-07-12 Thread Abhishek Dasgupta (JIRA)

[ 
https://issues.apache.org/jira/browse/MESOS-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372651#comment-15372651
 ] 

Abhishek Dasgupta commented on MESOS-4811:
--

Anyone actively working on this?? I may take up this issue if not.

> Reusable/Cacheable Offer
> 
>
> Key: MESOS-4811
> URL: https://issues.apache.org/jira/browse/MESOS-4811
> Project: Mesos
>  Issue Type: Bug
>  Components: allocation
>Reporter: Klaus Ma
>Assignee: Abhishek Dasgupta
>  Labels: tech-debt
>
> Currently, the resources are return back to allocator when task finished; and 
> those resources are not allocated to framework until next allocation cycle. 
> The performance is low for short running tasks (MESOS-3078). The proposed 
> solution is to let framework keep using the offer until allocator decide to 
> rescind it.



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


[jira] [Commented] (MESOS-4811) Reusable/Cacheable Offer

2016-02-29 Thread Qian Zhang (JIRA)

[ 
https://issues.apache.org/jira/browse/MESOS-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15172892#comment-15172892
 ] 

Qian Zhang commented on MESOS-4811:
---

So the idea is when framework launches a task with an offer, the unused 
resources in the offer should not be recovered back to allocator, and framework 
can continue to use those resources for launching other subsequent tasks?

> Reusable/Cacheable Offer
> 
>
> Key: MESOS-4811
> URL: https://issues.apache.org/jira/browse/MESOS-4811
> Project: Mesos
>  Issue Type: Bug
>  Components: allocation
>Reporter: Klaus Ma
>
> Currently, the resources are return back to allocator when task finished; and 
> those resources are not allocated to framework until next allocation cycle. 
> The performance is low for short running tasks (MESOS-3078). The proposed 
> solution is to let framework keep using the offer until allocator decide to 
> rescind it.



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