[
https://issues.apache.org/jira/browse/YARN-10899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407699#comment-17407699
]
Eric Payne commented on YARN-10899:
-----------------------------------
{quote}
When node label expression is empty string, only default partition without
non-exclusive allocation is used,
when node label expression is null, only it allowed non-exclusive allocation.
{quote}
I am concerned that this change does not conform to the intent of the
requirements of the partition label feature.
Exclusivity and non-exclusivity are associated with a partition when it is
created. Queues can be associated with these partitions and the default
behavior in those queues is defined by the queue's partition labels and their
attributes. I feel that it is improper to change the behavior based on whether
or not the user has specified an empty string or a null.
> control whether non-exclusive allocation is used
> ------------------------------------------------
>
> Key: YARN-10899
> URL: https://issues.apache.org/jira/browse/YARN-10899
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: KWON BYUNGCHANG
> Priority: Major
> Attachments: YARN-10899.001.patch, YARN-10899.002.patch,
> YARN-10899.003.patch, YARN-10899.004.patch
>
>
> A non-exclusive partition has the advantage of increasing resource
> utilization.
> But, it is not useful in all use cases.
> In the case of a long-running container,
> if it is allocated with non-exclusive allocation, it is more likely to be
> preempted and the overhead of repeating the same operation occurs.
> A function that can control whether non-exclusive allocation is used from the
> user's point of view is required.
> I suggest:
> When node label expression is empty string, only default partition without
> non-exclusive allocation is used,
> when node label expression is null, only it allowed non-exclusive allocation.
> I will attach patch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
