Add a new sorter for revocable resources in allocator

[Guangya Liu]

Hi,

The current logic of roleSorter is that when it do role sorter, the resources in it will include both regular resources and revocable resources, and this may not accurate for some cases, take the following case as an instance:

1) framework1 and framework2. 

2) framework1 got 1 reserved cpu and 9 revocable cpu. cpu(r1):1;cpu(*){REV}:9

3) framework2 got 9 reserved cpus: cpu(r1):9

When allocator allocate resources in next cycle, framework2 will be handled first as it has less SCALAR resources than framework1, but this may not be right for some cases as framework1 is using only 1 reserved resources and other resources are revocable which can be easily got evicted.

A proposal here is introducing a new sorter for revocable resources so as to distinguish the sorter for regular resources and revocable resources. To the built in allocator, the logic would be as this:

1) Quota Role Sorter

2) non-revocable Role Sorter

3) Revocable Role Sorter

I cannot access JIRA and will file a issue in JIRA to trace this, please show your comments if any.

Thanks,

Guangya

[Guangya Liu]

I filed a JIRA here 

https://issues.apache.org/jira/browse/MESOS-4923

在 2016年3月12日星期六 UTC+8上午10:59:54，Guangya Liu写道：

[Benjamin Mahler]

It would be helpful to clarify this ticket, if I glance at it I can't quickly tell what the idea is behind the suggestion.

For example, "Treat revocable resources as a separate pool when considering fairness" might be a more helpful title.

--
You received this message because you are subscribed to the Google Groups "Mesos Resource Allocation Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mesos-allocati...@googlegroups.com.
To post to this group, send email to mesos-al...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mesos-allocation/050df151-43a0-4705-be90-a97f2c0a1e13%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Guangya Liu]

Thanks Ben, updated the JIRA ticket.

在 2016年3月15日星期二 UTC+8上午9:54:13，Benjamin Mahler写道：

It would be helpful to clarify this ticket, if I glance at it I can't quickly tell what the idea is behind the suggestion.

For example, "Treat revocable resources as a separate pool when considering fairness" might be a more helpful title.

On Sat, Mar 12, 2016 at 7:29 PM, Guangya Liu <gyli...@gmail.com> wrote:

I filed a JIRA here 

https://issues.apache.org/jira/browse/MESOS-4923

在 2016年3月12日星期六 UTC+8上午10:59:54，Guangya Liu写道：

Hi,

The current logic of roleSorter is that when it do role sorter, the resources in it will include both regular resources and revocable resources, and this may not accurate for some cases, take the following case as an instance:

1) framework1 and framework2. 

2) framework1 got 1 reserved cpu and 9 revocable cpu. cpu(r1):1;cpu(*){REV}:9

3) framework2 got 9 reserved cpus: cpu(r1):9

When allocator allocate resources in next cycle, framework2 will be handled first as it has less SCALAR resources than framework1, but this may not be right for some cases as framework1 is using only 1 reserved resources and other resources are revocable which can be easily got evicted.

A proposal here is introducing a new sorter for revocable resources so as to distinguish the sorter for regular resources and revocable resources. To the built in allocator, the logic would be as this:

1) Quota Role Sorter

2) non-revocable Role Sorter

3) Revocable Role Sorter

I cannot access JIRA and will file a issue in JIRA to trace this, please show your comments if any.

Thanks,

Guangya

--
You received this message because you are subscribed to the Google Groups "Mesos Resource Allocation Working Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mesos-allocation+unsubscribe@googlegroups.com.
To post to this group, send email to mesos-allocation@googlegroups.com.