[jira] [Updated] (YARN-7274) Ability to disable elasticity at leaf queue level
[
https://issues.apache.org/jira/browse/YARN-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Payne updated YARN-7274:
-
Fix Version/s: 3.0.4
2.8.5
2.9.2
2.10.0
> Ability to disable elasticity at leaf queue level
> -
>
> Key: YARN-7274
> URL: https://issues.apache.org/jira/browse/YARN-7274
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
>Reporter: Scott Brokaw
>Assignee: Zian Chen
>Priority: Major
> Fix For: 3.1.0, 2.10.0, 2.9.2, 2.8.5, 3.0.4
>
> Attachments: YARN-7274.2.patch, YARN-7274.wip.1.patch
>
>
> The
> [documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
> defines yarn.scheduler.capacity..maximum-capacity as "Maximum
> queue capacity in percentage (%) as a float. This limits the elasticity for
> applications in the queue. Defaults to -1 which disables it."
> However, setting this value to -1 sets maximum capacity to 100% but I thought
> (perhaps incorrectly) that the intention of the -1 setting is that it would
> disable elasticity. This is confirmed looking at the code:
> {code:java}
> public static final float MAXIMUM_CAPACITY_VALUE = 100;
> public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
> ..
> maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
> MAXIMUM_CAPACITY_VALUE : maxCapacity;
> {code}
> The sum of yarn.scheduler.capacity..capacity for all queues, at
> each level, must be equal to 100 but for
> yarn.scheduler.capacity..maximum-capacity this value is actually
> a percentage of the entire cluster not just the parent queue. Yet it can not
> be set lower then the leaf queue's capacity setting. This seems to make it
> impossible to disable elasticity at a leaf queue level.
> This improvement is proposing that YARN have the ability to have elasticity
> disabled at a leaf queue level even if a parent queue permits elasticity by
> having a yarn.scheduler.capacity..maximum-capacity greater then
> it's yarn.scheduler.capacity..capacity
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7274) Ability to disable elasticity at leaf queue level
[
https://issues.apache.org/jira/browse/YARN-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zian Chen updated YARN-7274:
Attachment: YARN-7274.2.patch
> Ability to disable elasticity at leaf queue level
> -
>
> Key: YARN-7274
> URL: https://issues.apache.org/jira/browse/YARN-7274
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
>Reporter: Scott Brokaw
>Assignee: Zian Chen
> Attachments: YARN-7274.2.patch, YARN-7274.wip.1.patch
>
>
> The
> [documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
> defines yarn.scheduler.capacity..maximum-capacity as "Maximum
> queue capacity in percentage (%) as a float. This limits the elasticity for
> applications in the queue. Defaults to -1 which disables it."
> However, setting this value to -1 sets maximum capacity to 100% but I thought
> (perhaps incorrectly) that the intention of the -1 setting is that it would
> disable elasticity. This is confirmed looking at the code:
> {code:java}
> public static final float MAXIMUM_CAPACITY_VALUE = 100;
> public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
> ..
> maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
> MAXIMUM_CAPACITY_VALUE : maxCapacity;
> {code}
> The sum of yarn.scheduler.capacity..capacity for all queues, at
> each level, must be equal to 100 but for
> yarn.scheduler.capacity..maximum-capacity this value is actually
> a percentage of the entire cluster not just the parent queue. Yet it can not
> be set lower then the leaf queue's capacity setting. This seems to make it
> impossible to disable elasticity at a leaf queue level.
> This improvement is proposing that YARN have the ability to have elasticity
> disabled at a leaf queue level even if a parent queue permits elasticity by
> having a yarn.scheduler.capacity..maximum-capacity greater then
> it's yarn.scheduler.capacity..capacity
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7274) Ability to disable elasticity at leaf queue level
[
https://issues.apache.org/jira/browse/YARN-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zian Chen updated YARN-7274:
Attachment: YARN-7274.wip.1.patch
> Ability to disable elasticity at leaf queue level
> -
>
> Key: YARN-7274
> URL: https://issues.apache.org/jira/browse/YARN-7274
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
>Reporter: Scott Brokaw
>Assignee: Zian Chen
> Attachments: YARN-7274.wip.1.patch
>
>
> The
> [documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
> defines yarn.scheduler.capacity..maximum-capacity as "Maximum
> queue capacity in percentage (%) as a float. This limits the elasticity for
> applications in the queue. Defaults to -1 which disables it."
> However, setting this value to -1 sets maximum capacity to 100% but I thought
> (perhaps incorrectly) that the intention of the -1 setting is that it would
> disable elasticity. This is confirmed looking at the code:
> {code:java}
> public static final float MAXIMUM_CAPACITY_VALUE = 100;
> public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
> ..
> maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
> MAXIMUM_CAPACITY_VALUE : maxCapacity;
> {code}
> The sum of yarn.scheduler.capacity..capacity for all queues, at
> each level, must be equal to 100 but for
> yarn.scheduler.capacity..maximum-capacity this value is actually
> a percentage of the entire cluster not just the parent queue. Yet it can not
> be set lower then the leaf queue's capacity setting. This seems to make it
> impossible to disable elasticity at a leaf queue level.
> This improvement is proposing that YARN have the ability to have elasticity
> disabled at a leaf queue level even if a parent queue permits elasticity by
> having a yarn.scheduler.capacity..maximum-capacity greater then
> it's yarn.scheduler.capacity..capacity
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7274) Ability to disable elasticity at leaf queue level
[
https://issues.apache.org/jira/browse/YARN-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Brokaw updated YARN-7274:
---
Description:
The
[documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
defines yarn.scheduler.capacity..maximum-capacity as "Maximum
queue capacity in percentage (%) as a float. This limits the elasticity for
applications in the queue. Defaults to -1 which disables it."
However, setting this value to -1 sets maximum capacity to 100% but I thought
(perhaps incorrectly) that the intention of the -1 setting is that it would
disable elasticity. This is confirmed looking at the code:
{code:java}
public static final float MAXIMUM_CAPACITY_VALUE = 100;
public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
..
maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
MAXIMUM_CAPACITY_VALUE : maxCapacity;
{code}
The sum of yarn.scheduler.capacity..capacity for all queues, at
each level, must be equal to 100 but for
yarn.scheduler.capacity..maximum-capacity this value is actually a
percentage of the entire cluster not just the parent queue. Yet it can not be
set lower then the leaf queue's capacity setting. This seems to make it
impossible to disable elasticity at a leaf queue level.
This improvement is proposing that YARN have the ability to have elasticity
disabled at a leaf queue level even if a parent queue permits elasticity by
having a yarn.scheduler.capacity..maximum-capacity greater then
it's yarn.scheduler.capacity..capacity
was:
The [documentation
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
defines yarn.scheduler.capacity..maximum-capacity as "Maximum
queue capacity in percentage (%) as a float. This limits the elasticity for
applications in the queue. Defaults to -1 which disables it."
However, setting this value to -1 sets maximum capacity to 100% but I thought
(perhaps incorrectly) that the intention of the -1 setting is that it would
disable elasticity. This is confirmed looking at the code:
{code:java}
public static final float MAXIMUM_CAPACITY_VALUE = 100;
public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
..
maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
MAXIMUM_CAPACITY_VALUE : maxCapacity;
{code}
The sum of yarn.scheduler.capacity..capacity for all queues, at
each level, must be equal to 100 but for
yarn.scheduler.capacity..maximum-capacity this value is actually a
percentage of the entire cluster not just the parent queue. Yet it can not be
set lower then the leaf queue's capacity setting. This seems to make it
impossible to disable elasticity at a leaf queue level.
This improvement is proposing that YARN have the ability to have elasticity
disabled at a leaf queue level even if a parent queue permits elasticity by
having a yarn.scheduler.capacity..maximum-capacity greater then
it's yarn.scheduler.capacity..capacity
> Ability to disable elasticity at leaf queue level
> -
>
> Key: YARN-7274
> URL: https://issues.apache.org/jira/browse/YARN-7274
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
>Reporter: Scott Brokaw
>
> The
> [documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
> defines yarn.scheduler.capacity..maximum-capacity as "Maximum
> queue capacity in percentage (%) as a float. This limits the elasticity for
> applications in the queue. Defaults to -1 which disables it."
> However, setting this value to -1 sets maximum capacity to 100% but I thought
> (perhaps incorrectly) that the intention of the -1 setting is that it would
> disable elasticity. This is confirmed looking at the code:
> {code:java}
> public static final float MAXIMUM_CAPACITY_VALUE = 100;
> public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
> ..
> maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
> MAXIMUM_CAPACITY_VALUE : maxCapacity;
> {code}
> The sum of yarn.scheduler.capacity..capacity for all queues, at
> each level, must be equal to 100 but for
> yarn.scheduler.capacity..maximum-capacity this value is actually
> a percentage of the entire cluster not just the parent queue. Yet it can not
> be set lower then the leaf queue's capacity setting. This seems to make it
> impossible to disable elasticity at a leaf queue level.
> This improvement is proposing that YARN have the ability to have elasticity
> disabled at a leaf queue level even if a parent queue permits elasticity by
> having a yarn.scheduler.capacity..maximum-capacity greater then
> it's yarn.scheduler.capacity..capacity
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (YARN-7274) Ability to disable elasticity at leaf queue level
[
https://issues.apache.org/jira/browse/YARN-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Brokaw updated YARN-7274:
---
Description:
The [documentation
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
defines yarn.scheduler.capacity..maximum-capacity as "Maximum
queue capacity in percentage (%) as a float. This limits the elasticity for
applications in the queue. Defaults to -1 which disables it."
However, setting this value to -1 sets maximum capacity to 100% but I thought
(perhaps incorrectly) that the intention of the -1 setting is that it would
disable elasticity. This is confirmed looking at the code:
{code:java}
public static final float MAXIMUM_CAPACITY_VALUE = 100;
public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
..
maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
MAXIMUM_CAPACITY_VALUE : maxCapacity;
{code}
The sum of yarn.scheduler.capacity..capacity for all queues, at
each level, must be equal to 100 but for
yarn.scheduler.capacity..maximum-capacity this value is actually a
percentage of the entire cluster not just the parent queue. Yet it can not be
set lower then the leaf queue's capacity setting. This seems to make it
impossible to disable elasticity at a leaf queue level.
This improvement is proposing that YARN have the ability to have elasticity
disabled at a leaf queue level even if a parent queue permits elasticity by
having a yarn.scheduler.capacity..maximum-capacity greater then
it's yarn.scheduler.capacity..capacity
was:
The documentation
[https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
defines yarn.scheduler.capacity..maximum-capacity as "Maximum
queue capacity in percentage (%) as a float. This limits the elasticity for
applications in the queue. Defaults to -1 which disables it."
However, setting this value to -1 sets maximum capacity to 100% but I thought
(perhaps incorrectly) that the intention of the -1 setting is that it would
disable elasticity. This is confirmed looking at the code:
{code:java}
public static final float MAXIMUM_CAPACITY_VALUE = 100;
public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
..
maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
MAXIMUM_CAPACITY_VALUE : maxCapacity;
{code}
The sum of yarn.scheduler.capacity..capacity for all queues, at
each level, must be equal to 100 but for
yarn.scheduler.capacity..maximum-capacity this value is actually a
percentage of the entire cluster not just the parent queue. Yet it can not be
set lower then the leaf queue's capacity setting. This seems to make it
impossible to disable elasticity at a leaf queue level.
This improvement is proposing that YARN have the ability to have elasticity
disabled at a leaf queue level even if a parent queue permits elasticity by
having a yarn.scheduler.capacity..maximum-capacity greater then
it's yarn.scheduler.capacity..capacity
> Ability to disable elasticity at leaf queue level
> -
>
> Key: YARN-7274
> URL: https://issues.apache.org/jira/browse/YARN-7274
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
>Reporter: Scott Brokaw
>
> The [documentation
> https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
> defines yarn.scheduler.capacity..maximum-capacity as "Maximum
> queue capacity in percentage (%) as a float. This limits the elasticity for
> applications in the queue. Defaults to -1 which disables it."
> However, setting this value to -1 sets maximum capacity to 100% but I thought
> (perhaps incorrectly) that the intention of the -1 setting is that it would
> disable elasticity. This is confirmed looking at the code:
> {code:java}
> public static final float MAXIMUM_CAPACITY_VALUE = 100;
> public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
> ..
> maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
> MAXIMUM_CAPACITY_VALUE : maxCapacity;
> {code}
> The sum of yarn.scheduler.capacity..capacity for all queues, at
> each level, must be equal to 100 but for
> yarn.scheduler.capacity..maximum-capacity this value is actually
> a percentage of the entire cluster not just the parent queue. Yet it can not
> be set lower then the leaf queue's capacity setting. This seems to make it
> impossible to disable elasticity at a leaf queue level.
> This improvement is proposing that YARN have the ability to have elasticity
> disabled at a leaf queue level even if a parent queue permits elasticity by
> having a yarn.scheduler.capacity..maximum-capacity greater then
> it's yarn.scheduler.capacity..capacity
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (YARN-7274) Ability to disable elasticity at leaf queue level
[
https://issues.apache.org/jira/browse/YARN-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Brokaw updated YARN-7274:
---
Description:
The documentation
[https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
defines yarn.scheduler.capacity..maximum-capacity as "Maximum
queue capacity in percentage (%) as a float. This limits the elasticity for
applications in the queue. Defaults to -1 which disables it."
However, setting this value to -1 sets maximum capacity to 100% but I thought
(perhaps incorrectly) that the intention of the -1 setting is that it would
disable elasticity. This is confirmed looking at the code:
{code:java}
public static final float MAXIMUM_CAPACITY_VALUE = 100;
public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
..
maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
MAXIMUM_CAPACITY_VALUE : maxCapacity;
{code}
The sum of yarn.scheduler.capacity..capacity for all queues, at
each level, must be equal to 100 but for
yarn.scheduler.capacity..maximum-capacity this value is actually a
percentage of the entire cluster not just the parent queue. Yet it can not be
set lower then the leaf queue's capacity setting. This seems to make it
impossible to disable elasticity at a leaf queue level.
This improvement is proposing that YARN have the ability to have elasticity
disabled at a leaf queue level even if a parent queue permits elasticity by
having a yarn.scheduler.capacity..maximum-capacity greater then
it's yarn.scheduler.capacity..capacity
was:
The
documentation[https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
defines yarn.scheduler.capacity..maximum-capacity as "Maximum
queue capacity in percentage (%) as a float. This limits the elasticity for
applications in the queue. Defaults to -1 which disables it."
However, setting this value to -1 sets maximum capacity to 100% but I thought
(perhaps incorrectly) that the intention of the -1 setting is that it would
disable elasticity. This is confirmed looking at the code:
{code:java}
public static final float MAXIMUM_CAPACITY_VALUE = 100;
public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
..
maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
MAXIMUM_CAPACITY_VALUE : maxCapacity;
{code}
The sum of yarn.scheduler.capacity..capacity for all queues, at
each level, must be equal to 100 but for
yarn.scheduler.capacity..maximum-capacity this value is actually a
percentage of the entire cluster not just the parent queue. Yet it can not be
set lower then the leaf queue's capacity setting. This seems to make it
impossible to disable elasticity at a leaf queue level.
This improvement is proposing that YARN have the ability to have elasticity
disabled at a leaf queue level even if a parent queue permits elasticity by
having a yarn.scheduler.capacity..maximum-capacity greater then
it's yarn.scheduler.capacity..capacity
> Ability to disable elasticity at leaf queue level
> -
>
> Key: YARN-7274
> URL: https://issues.apache.org/jira/browse/YARN-7274
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
>Reporter: Scott Brokaw
>
> The documentation
> [https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
> defines yarn.scheduler.capacity..maximum-capacity as "Maximum
> queue capacity in percentage (%) as a float. This limits the elasticity for
> applications in the queue. Defaults to -1 which disables it."
> However, setting this value to -1 sets maximum capacity to 100% but I thought
> (perhaps incorrectly) that the intention of the -1 setting is that it would
> disable elasticity. This is confirmed looking at the code:
> {code:java}
> public static final float MAXIMUM_CAPACITY_VALUE = 100;
> public static final float DEFAULT_MAXIMUM_CAPACITY_VALUE = -1.0f;
> ..
> maxCapacity = (maxCapacity == DEFAULT_MAXIMUM_CAPACITY_VALUE) ?
> MAXIMUM_CAPACITY_VALUE : maxCapacity;
> {code}
> The sum of yarn.scheduler.capacity..capacity for all queues, at
> each level, must be equal to 100 but for
> yarn.scheduler.capacity..maximum-capacity this value is actually
> a percentage of the entire cluster not just the parent queue. Yet it can not
> be set lower then the leaf queue's capacity setting. This seems to make it
> impossible to disable elasticity at a leaf queue level.
> This improvement is proposing that YARN have the ability to have elasticity
> disabled at a leaf queue level even if a parent queue permits elasticity by
> having a yarn.scheduler.capacity..maximum-capacity greater then
> it's yarn.scheduler.capacity..capacity
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
