[jira] [Updated] (YARN-4026) FiCaSchedulerApp: ContainerAllocator should be able to choose how to order pending resource requests

2015-08-06 Thread Wangda Tan (JIRA)

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

Wangda Tan updated YARN-4026:
-
Summary: FiCaSchedulerApp: ContainerAllocator should be able to choose how 
to order pending resource requests  (was: FiCaSchedulerApp: Revisit 
ContainerAllocator interface design)

> FiCaSchedulerApp: ContainerAllocator should be able to choose how to order 
> pending resource requests
> 
>
> Key: YARN-4026
> URL: https://issues.apache.org/jira/browse/YARN-4026
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>
> After YARN-3983, we have an extensible ContainerAllocator which can be used 
> by FiCaSchedulerApp to decide how to allocate resources.
> While working on YARN-1651 (allocate resource to increase container), I found 
> one thing in existing logic not flexible enough:
> - ContainerAllocator decides what to allocate for a given node and priority: 
> To support different kinds of resource allocation, for example, priority as 
> weight / skip priority or not, etc. It's better to let ContainerAllocator to 
> choose how to order resource request according to priorities.



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


[jira] [Updated] (YARN-4026) FiCaSchedulerApp: ContainerAllocator should be able to choose how to order pending resource requests

2015-08-06 Thread Wangda Tan (JIRA)

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

Wangda Tan updated YARN-4026:
-
Description: 
After YARN-3983, we have an extensible ContainerAllocator which can be used by 
FiCaSchedulerApp to decide how to allocate resources.

While working on YARN-1651 (allocate resource to increase container), I found 
one thing in existing logic not flexible enough:
- ContainerAllocator decides what to allocate for a given node and priority: To 
support different kinds of resource allocation, for example, priority as weight 
/ skip priority or not, etc. It's better to let ContainerAllocator to choose 
how to order pending resource requests.

  was:
After YARN-3983, we have an extensible ContainerAllocator which can be used by 
FiCaSchedulerApp to decide how to allocate resources.

While working on YARN-1651 (allocate resource to increase container), I found 
one thing in existing logic not flexible enough:
- ContainerAllocator decides what to allocate for a given node and priority: To 
support different kinds of resource allocation, for example, priority as weight 
/ skip priority or not, etc. It's better to let ContainerAllocator to choose 
how to order resource request according to priorities.



> FiCaSchedulerApp: ContainerAllocator should be able to choose how to order 
> pending resource requests
> 
>
> Key: YARN-4026
> URL: https://issues.apache.org/jira/browse/YARN-4026
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>
> After YARN-3983, we have an extensible ContainerAllocator which can be used 
> by FiCaSchedulerApp to decide how to allocate resources.
> While working on YARN-1651 (allocate resource to increase container), I found 
> one thing in existing logic not flexible enough:
> - ContainerAllocator decides what to allocate for a given node and priority: 
> To support different kinds of resource allocation, for example, priority as 
> weight / skip priority or not, etc. It's better to let ContainerAllocator to 
> choose how to order pending resource requests.



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


[jira] [Updated] (YARN-4026) FiCaSchedulerApp: ContainerAllocator should be able to choose how to order pending resource requests

2015-08-06 Thread Wangda Tan (JIRA)

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

Wangda Tan updated YARN-4026:
-
Attachment: YARN-4026.1.patch

Attached initial patch to be reviewed.

> FiCaSchedulerApp: ContainerAllocator should be able to choose how to order 
> pending resource requests
> 
>
> Key: YARN-4026
> URL: https://issues.apache.org/jira/browse/YARN-4026
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
> Attachments: YARN-4026.1.patch
>
>
> After YARN-3983, we have an extensible ContainerAllocator which can be used 
> by FiCaSchedulerApp to decide how to allocate resources.
> While working on YARN-1651 (allocate resource to increase container), I found 
> one thing in existing logic not flexible enough:
> - ContainerAllocator decides what to allocate for a given node and priority: 
> To support different kinds of resource allocation, for example, priority as 
> weight / skip priority or not, etc. It's better to let ContainerAllocator to 
> choose how to order pending resource requests.



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


[jira] [Updated] (YARN-4026) FiCaSchedulerApp: ContainerAllocator should be able to choose how to order pending resource requests

2015-08-11 Thread Wangda Tan (JIRA)

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

Wangda Tan updated YARN-4026:
-
Attachment: YARN-4026.2.patch

Thanks for comments [~jianhe], attached ver.2 patch.

> FiCaSchedulerApp: ContainerAllocator should be able to choose how to order 
> pending resource requests
> 
>
> Key: YARN-4026
> URL: https://issues.apache.org/jira/browse/YARN-4026
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
> Attachments: YARN-4026.1.patch, YARN-4026.2.patch
>
>
> After YARN-3983, we have an extensible ContainerAllocator which can be used 
> by FiCaSchedulerApp to decide how to allocate resources.
> While working on YARN-1651 (allocate resource to increase container), I found 
> one thing in existing logic not flexible enough:
> - ContainerAllocator decides what to allocate for a given node and priority: 
> To support different kinds of resource allocation, for example, priority as 
> weight / skip priority or not, etc. It's better to let ContainerAllocator to 
> choose how to order pending resource requests.



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


[jira] [Updated] (YARN-4026) FiCaSchedulerApp: ContainerAllocator should be able to choose how to order pending resource requests

2015-08-11 Thread Wangda Tan (JIRA)

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

Wangda Tan updated YARN-4026:
-
Attachment: YARN-4026.3.patch

Attached ver.3, added more comments and fixed findbugs warning.

> FiCaSchedulerApp: ContainerAllocator should be able to choose how to order 
> pending resource requests
> 
>
> Key: YARN-4026
> URL: https://issues.apache.org/jira/browse/YARN-4026
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
> Attachments: YARN-4026.1.patch, YARN-4026.2.patch, YARN-4026.3.patch
>
>
> After YARN-3983, we have an extensible ContainerAllocator which can be used 
> by FiCaSchedulerApp to decide how to allocate resources.
> While working on YARN-1651 (allocate resource to increase container), I found 
> one thing in existing logic not flexible enough:
> - ContainerAllocator decides what to allocate for a given node and priority: 
> To support different kinds of resource allocation, for example, priority as 
> weight / skip priority or not, etc. It's better to let ContainerAllocator to 
> choose how to order pending resource requests.



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