[jira] [Commented] (YARN-10863) CGroupElasticMemoryController is not work
[
https://issues.apache.org/jira/browse/YARN-10863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383791#comment-17383791
]
chaosju commented on YARN-10863:
cc [~haibochen] Please take a look at it, Its may be relate to YARN-8930
> CGroupElasticMemoryController is not work
> -
>
> Key: YARN-10863
> URL: https://issues.apache.org/jira/browse/YARN-10863
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
>Affects Versions: 3.3.1
>Reporter: LuoGe
>Priority: Major
>
> When following the
> [documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/NodeManagerCGroupsMemory.html]
> configuring elastic memory resource control,
> yarn.nodemanager.elastic-memory-control.enabled set true,
> yarn.nodemanager.resource.memory.enforced set to false,
> yarn.nodemanager.pmem-check-enabled set true, and
> yarn.nodemanager.resource.memory.enabled set true to use cgroup control
> memory, but elastic memory control is not work.
> I see the code ContainersMonitorImpl.java, in checkLimit function, the skip
> logic have some problem. The return condition is strictMemoryEnforcement is
> true and elasticMemoryEnforcement is false. So, following the document set
> use elastic memory control, the check logic will continue, when container
> memory used over limit will killed by checkLimit.
> {code:java}
> if (strictMemoryEnforcement && !elasticMemoryEnforcement) {
> // When cgroup-based strict memory enforcement is used alone without
> // elastic memory control, the oom-kill would take care of it.
> // However, when elastic memory control is also enabled, the oom killer
> // would be disabled at the root yarn container cgroup level (all child
> // cgroups would inherit that setting). Hence, we fall back to the
> // polling-based mechanism.
> return;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-10860) Make max container per heartbeat configs refreshable
[
https://issues.apache.org/jira/browse/YARN-10860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383789#comment-17383789
]
Qi Zhu edited comment on YARN-10860 at 7/20/21, 5:55 AM:
-
Thanks [~ebadger] for filling this.
I totally agree with you that these should be refreshable.
And the patch LGTM, we do not need a unit test, it's clear.
was (Author: zhuqi):
Thanks [~ebadger] for filling this.
I totally agree with you that these should be refreshable.
> Make max container per heartbeat configs refreshable
>
>
> Key: YARN-10860
> URL: https://issues.apache.org/jira/browse/YARN-10860
> Project: Hadoop YARN
> Issue Type: Improvement
>Reporter: Eric Badger
>Assignee: Eric Badger
>Priority: Major
> Attachments: YARN-10860.001.patch, YARN-10860.branch-2.10.001.patch
>
>
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-container-assignments}}
> and
> {{yarn.scheduler.capacity.per-node-heartbeat.multiple-assignments-enabled}}
> are currently *not* refreshable configs, but I believe they should be. This
> JIRA is to turn these into refreshable configs, just like
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-offswitch-assignments}}
> is.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10860) Make max container per heartbeat configs refreshable
[
https://issues.apache.org/jira/browse/YARN-10860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383789#comment-17383789
]
Qi Zhu commented on YARN-10860:
---
Thanks [~ebadger] for filling this.
I totally agree with you that these should be refreshable.
> Make max container per heartbeat configs refreshable
>
>
> Key: YARN-10860
> URL: https://issues.apache.org/jira/browse/YARN-10860
> Project: Hadoop YARN
> Issue Type: Improvement
>Reporter: Eric Badger
>Assignee: Eric Badger
>Priority: Major
> Attachments: YARN-10860.001.patch, YARN-10860.branch-2.10.001.patch
>
>
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-container-assignments}}
> and
> {{yarn.scheduler.capacity.per-node-heartbeat.multiple-assignments-enabled}}
> are currently *not* refreshable configs, but I believe they should be. This
> JIRA is to turn these into refreshable configs, just like
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-offswitch-assignments}}
> is.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383778#comment-17383778 ] Qi Zhu commented on YARN-10858: --- Thanks [~aajisaka] for backport. > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Masatake Iwasaki >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 3.2.3, 3.3.2 > > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > Time Spent: 40m > Remaining Estimate: 0h > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as intended. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YARN-10858: - Fix Version/s: 3.3.2 3.2.3 Since YARN-10826 is committed to branch-3.3 and branch-3.2, backported it to the branches. > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Masatake Iwasaki >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 3.2.3, 3.3.2 > > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > Time Spent: 40m > Remaining Estimate: 0h > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as intended. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-10864) Implement NodeHealthDetails for NodeHealthStatus
[ https://issues.apache.org/jira/browse/YARN-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson reassigned YARN-10864: Assignee: Cyrus Jackson > Implement NodeHealthDetails for NodeHealthStatus > > > Key: YARN-10864 > URL: https://issues.apache.org/jira/browse/YARN-10864 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10864) Implement NodeHealthDetails for NodeHealthStatus
Cyrus Jackson created YARN-10864: Summary: Implement NodeHealthDetails for NodeHealthStatus Key: YARN-10864 URL: https://issues.apache.org/jira/browse/YARN-10864 Project: Hadoop YARN Issue Type: Sub-task Reporter: Cyrus Jackson -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10335) Improve scheduling of containers based on node health
[ https://issues.apache.org/jira/browse/YARN-10335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10335: - Issue Type: New Feature (was: Improvement) > Improve scheduling of containers based on node health > - > > Key: YARN-10335 > URL: https://issues.apache.org/jira/browse/YARN-10335 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Bibin Chundatt >Assignee: Cyrus Jackson >Priority: Major > Labels: pull-request-available > Attachments: YARN-10335.001.patch, YARN-10335.002.patch, > YARN-10335.003.patch, YARN-10335.004.patch, YARN-10335.005.patch > > Time Spent: 50m > Remaining Estimate: 0h > > YARN-7494 supports providing interface to choose nodeset for scheduler > allocation. > We could leverage the same to support allocation of containers based on node > health value send from nodemanagers -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10861) Make NodeHealthCheckerService pluggable in NodeManager
[ https://issues.apache.org/jira/browse/YARN-10861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10861: - Description: Add support to NodeHealthCheckerService inorder to make it as a pluggable interface in NodeManager. The default implementation NodeHealthCheckerServiceImpl should be used if the class is not set. (was: Add support to NodeHealthCheckerService inorder to make it as a pluggable interface in NodeManager. ) > Make NodeHealthCheckerService pluggable in NodeManager > -- > > Key: YARN-10861 > URL: https://issues.apache.org/jira/browse/YARN-10861 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Add support to NodeHealthCheckerService inorder to make it as a pluggable > interface in NodeManager. The default implementation > NodeHealthCheckerServiceImpl should be used if the class is not set. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10863) CGroupElasticMemoryController is not work
[
https://issues.apache.org/jira/browse/YARN-10863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
LuoGe updated YARN-10863:
-
Description:
When following the
[documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/NodeManagerCGroupsMemory.html]
configuring elastic memory resource control,
yarn.nodemanager.elastic-memory-control.enabled set true,
yarn.nodemanager.resource.memory.enforced set to false,
yarn.nodemanager.pmem-check-enabled set true, and
yarn.nodemanager.resource.memory.enabled set true to use cgroup control memory,
but elastic memory control is not work.
I see the code ContainersMonitorImpl.java, in checkLimit function, the skip
logic have some problem. The return condition is strictMemoryEnforcement is
true and elasticMemoryEnforcement is false. So, following the document set use
elastic memory control, the check logic will continue, when container memory
used over limit will killed by checkLimit.
{code:java}
if (strictMemoryEnforcement && !elasticMemoryEnforcement) {
// When cgroup-based strict memory enforcement is used alone without
// elastic memory control, the oom-kill would take care of it.
// However, when elastic memory control is also enabled, the oom killer
// would be disabled at the root yarn container cgroup level (all child
// cgroups would inherit that setting). Hence, we fall back to the
// polling-based mechanism.
return;
}
{code}
was:
When following the
[documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/NodeManagerCGroupsMemory.html]
configuring elastic memory resource control,
yarn.nodemanager.elastic-memory-control.enabled set true,
yarn.nodemanager.resource.memory.enforced set to false,
yarn.nodemanager.pmem-check-enabled set true, and
yarn.nodemanager.resource.memory.enabled set true to use cgroup control memory,
but elastic memory control is not work.
so, I see the code ContainersMonitorImpl.java, in checkLimit function, the
skip logic have some problem. The return condition is strictMemoryEnforcement
is true and elasticMemoryEnforcement is false. So, following the document set
use elastic memory control, the check logic will continue, when container
memory used over limit will killed by checkLimit.
{code:java}
if (strictMemoryEnforcement && !elasticMemoryEnforcement) {
// When cgroup-based strict memory enforcement is used alone without
// elastic memory control, the oom-kill would take care of it.
// However, when elastic memory control is also enabled, the oom killer
// would be disabled at the root yarn container cgroup level (all child
// cgroups would inherit that setting). Hence, we fall back to the
// polling-based mechanism.
return;
}
{code}
> CGroupElasticMemoryController is not work
> -
>
> Key: YARN-10863
> URL: https://issues.apache.org/jira/browse/YARN-10863
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
>Affects Versions: 3.3.1
>Reporter: LuoGe
>Priority: Major
>
> When following the
> [documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/NodeManagerCGroupsMemory.html]
> configuring elastic memory resource control,
> yarn.nodemanager.elastic-memory-control.enabled set true,
> yarn.nodemanager.resource.memory.enforced set to false,
> yarn.nodemanager.pmem-check-enabled set true, and
> yarn.nodemanager.resource.memory.enabled set true to use cgroup control
> memory, but elastic memory control is not work.
> I see the code ContainersMonitorImpl.java, in checkLimit function, the skip
> logic have some problem. The return condition is strictMemoryEnforcement is
> true and elasticMemoryEnforcement is false. So, following the document set
> use elastic memory control, the check logic will continue, when container
> memory used over limit will killed by checkLimit.
> {code:java}
> if (strictMemoryEnforcement && !elasticMemoryEnforcement) {
> // When cgroup-based strict memory enforcement is used alone without
> // elastic memory control, the oom-kill would take care of it.
> // However, when elastic memory control is also enabled, the oom killer
> // would be disabled at the root yarn container cgroup level (all child
> // cgroups would inherit that setting). Hence, we fall back to the
> // polling-based mechanism.
> return;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10863) CGroupElasticMemoryController is not work
[
https://issues.apache.org/jira/browse/YARN-10863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
LuoGe updated YARN-10863:
-
Description:
When following the
[documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/NodeManagerCGroupsMemory.html]
configuring elastic memory resource control,
yarn.nodemanager.elastic-memory-control.enabled set true,
yarn.nodemanager.resource.memory.enforced set to false,
yarn.nodemanager.pmem-check-enabled set true, and
yarn.nodemanager.resource.memory.enabled set true to use cgroup control memory,
but elastic memory control is not work.
so, I see the code ContainersMonitorImpl.java, in checkLimit function, the
skip logic have some problem. The return condition is strictMemoryEnforcement
is true and elasticMemoryEnforcement is false. So, following the document set
use elastic memory control, the check logic will continue, when container
memory used over limit will killed by checkLimit.
{code:java}
if (strictMemoryEnforcement && !elasticMemoryEnforcement) {
// When cgroup-based strict memory enforcement is used alone without
// elastic memory control, the oom-kill would take care of it.
// However, when elastic memory control is also enabled, the oom killer
// would be disabled at the root yarn container cgroup level (all child
// cgroups would inherit that setting). Hence, we fall back to the
// polling-based mechanism.
return;
}
{code}
was:
When following the
[documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/NodeManagerCGroupsMemory.html]
configuring elastic memory resource control,
yarn.nodemanager.elastic-memory-control.enabled set true,
yarn.nodemanager.resource.memory.enforced set to false,
yarn.nodemanager.pmem-check-enabled set true, and
yarn.nodemanager.resource.memory.enabled set true to use cgroup control memory,
but elastic memory control is not work.
so, I see the code ContainersMonitorImpl.java, in checkLimit function, the skip
logic have some problem. The return condition is strictMemoryEnforcement is
true and elasticMemoryEnforcement is false. So, following the document set use
elastic memory control, the check logic will continue, when container memory
used over limit will killed by checkLimit.
{code:java}
if (strictMemoryEnforcement && !elasticMemoryEnforcement) {
// When cgroup-based strict memory enforcement is used alone without
// elastic memory control, the oom-kill would take care of it.
// However, when elastic memory control is also enabled, the oom killer
// would be disabled at the root yarn container cgroup level (all child
// cgroups would inherit that setting). Hence, we fall back to the
// polling-based mechanism.
return;
}
{code}
> CGroupElasticMemoryController is not work
> -
>
> Key: YARN-10863
> URL: https://issues.apache.org/jira/browse/YARN-10863
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
>Affects Versions: 3.3.1
>Reporter: LuoGe
>Priority: Major
>
> When following the
> [documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/NodeManagerCGroupsMemory.html]
> configuring elastic memory resource control,
> yarn.nodemanager.elastic-memory-control.enabled set true,
> yarn.nodemanager.resource.memory.enforced set to false,
> yarn.nodemanager.pmem-check-enabled set true, and
> yarn.nodemanager.resource.memory.enabled set true to use cgroup control
> memory, but elastic memory control is not work.
> so, I see the code ContainersMonitorImpl.java, in checkLimit function, the
> skip logic have some problem. The return condition is
> strictMemoryEnforcement is true and elasticMemoryEnforcement is false. So,
> following the document set use elastic memory control, the check logic will
> continue, when container memory used over limit will killed by checkLimit.
> {code:java}
> if (strictMemoryEnforcement && !elasticMemoryEnforcement) {
> // When cgroup-based strict memory enforcement is used alone without
> // elastic memory control, the oom-kill would take care of it.
> // However, when elastic memory control is also enabled, the oom killer
> // would be disabled at the root yarn container cgroup level (all child
> // cgroups would inherit that setting). Hence, we fall back to the
> // polling-based mechanism.
> return;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10863) CGroupElasticMemoryController is not work
LuoGe created YARN-10863:
Summary: CGroupElasticMemoryController is not work
Key: YARN-10863
URL: https://issues.apache.org/jira/browse/YARN-10863
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 3.3.1
Reporter: LuoGe
When following the
[documentation|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/NodeManagerCGroupsMemory.html]
configuring elastic memory resource control,
yarn.nodemanager.elastic-memory-control.enabled set true,
yarn.nodemanager.resource.memory.enforced set to false,
yarn.nodemanager.pmem-check-enabled set true, and
yarn.nodemanager.resource.memory.enabled set true to use cgroup control memory,
but elastic memory control is not work.
so, I see the code ContainersMonitorImpl.java, in checkLimit function, the skip
logic have some problem. The return condition is strictMemoryEnforcement is
true and elasticMemoryEnforcement is false. So, following the document set use
elastic memory control, the check logic will continue, when container memory
used over limit will killed by checkLimit.
{code:java}
if (strictMemoryEnforcement && !elasticMemoryEnforcement) {
// When cgroup-based strict memory enforcement is used alone without
// elastic memory control, the oom-kill would take care of it.
// However, when elastic memory control is also enabled, the oom killer
// would be disabled at the root yarn container cgroup level (all child
// cgroups would inherit that setting). Hence, we fall back to the
// polling-based mechanism.
return;
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10862) Add new proto changes required for NodeHealthDetails in NodeHealthStatus
[
https://issues.apache.org/jira/browse/YARN-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrus Jackson updated YARN-10862:
-
Description:
Proto changes for NodeHealthDetails.
In order to make it generic resources information from NodeManager to
ResourceManager, a map data structure is used. This way multiple resource
values can be sent
i.e
{code:java}
message IntLongMapProto {
required int32 key = 1;
required int64 value = 2;
}{code}
Here Int32 as key will be used in order to avoid sending Strings as it becomes
difficult to parse on ResoureManager standpoint.
was:Proto changes for NodeHealthDetails.
> Add new proto changes required for NodeHealthDetails in NodeHealthStatus
>
>
> Key: YARN-10862
> URL: https://issues.apache.org/jira/browse/YARN-10862
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Cyrus Jackson
>Assignee: Cyrus Jackson
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Proto changes for NodeHealthDetails.
> In order to make it generic resources information from NodeManager to
> ResourceManager, a map data structure is used. This way multiple resource
> values can be sent
> i.e
> {code:java}
> message IntLongMapProto {
> required int32 key = 1;
> required int64 value = 2;
> }{code}
> Here Int32 as key will be used in order to avoid sending Strings as it
> becomes difficult to parse on ResoureManager standpoint.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10862) Add new proto changes required for NodeHealthDetails in NodeHealthStatus
[ https://issues.apache.org/jira/browse/YARN-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10862: - Description: Proto changes for NodeHealthDetails. > Add new proto changes required for NodeHealthDetails in NodeHealthStatus > > > Key: YARN-10862 > URL: https://issues.apache.org/jira/browse/YARN-10862 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Proto changes for NodeHealthDetails. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10861) Make NodeHealthCheckerService pluggable in NodeManager
[ https://issues.apache.org/jira/browse/YARN-10861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10861: - Description: Add support to NodeHealthCheckerService inorder to make it as a pluggable interface in NodeManager. (was: Add support to NodeHealthCheckerService as pluggable interface. ) > Make NodeHealthCheckerService pluggable in NodeManager > -- > > Key: YARN-10861 > URL: https://issues.apache.org/jira/browse/YARN-10861 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Add support to NodeHealthCheckerService inorder to make it as a pluggable > interface in NodeManager. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Resolved] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qi Zhu resolved YARN-10858. --- Fix Version/s: 3.4.0 Resolution: Fixed > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Masatake Iwasaki >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > Time Spent: 40m > Remaining Estimate: 0h > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as intended. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383726#comment-17383726 ] Qi Zhu commented on YARN-10858: --- Thanks [~iwasakims] for fix, and [~gandras] [~aajisaka] for review. Committed to trunk. > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Masatake Iwasaki >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > Time Spent: 40m > Remaining Estimate: 0h > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as intended. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-10630) [UI2] Ambiguous queue name resolution
[ https://issues.apache.org/jira/browse/YARN-10630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383720#comment-17383720 ] Qi Zhu edited comment on YARN-10630 at 7/20/21, 3:37 AM: - Thanks [~gandras] for work. Patch LGTM, i will commit it if no other comment. was (Author: zhuqi): Thanks [~zhuqi] for work. Patch LGTM, i will commit it if no other comment. > [UI2] Ambiguous queue name resolution > - > > Key: YARN-10630 > URL: https://issues.apache.org/jira/browse/YARN-10630 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2021-07-19 at 15.30.38.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Yarn UIv2 uses queueName instead of queuePath (which was added in the > scheduler response in YARN-10610), which makes the queue resolution ambiguous > in case of identical queue short names (eg. root.a.b <-> root.b). This causes > invalid behaviour in multiple places. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10630) [UI2] Ambiguous queue name resolution
[ https://issues.apache.org/jira/browse/YARN-10630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383720#comment-17383720 ] Qi Zhu commented on YARN-10630: --- Thanks [~zhuqi] for work. Patch LGTM, i will commit it if no other comment. > [UI2] Ambiguous queue name resolution > - > > Key: YARN-10630 > URL: https://issues.apache.org/jira/browse/YARN-10630 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2021-07-19 at 15.30.38.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Yarn UIv2 uses queueName instead of queuePath (which was added in the > scheduler response in YARN-10610), which makes the queue resolution ambiguous > in case of identical queue short names (eg. root.a.b <-> root.b). This causes > invalid behaviour in multiple places. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10862) Add new proto changes required for NodeHealthDetails in NodeHealthStatus
[ https://issues.apache.org/jira/browse/YARN-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-10862: -- Labels: pull-request-available (was: ) > Add new proto changes required for NodeHealthDetails in NodeHealthStatus > > > Key: YARN-10862 > URL: https://issues.apache.org/jira/browse/YARN-10862 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10862) Add new proto changes required for NodeHealthDetails in NodeHealthStatus
[ https://issues.apache.org/jira/browse/YARN-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10862: - Summary: Add new proto changes required for NodeHealthDetails in NodeHealthStatus (was: Add new proto changes required for NodeHealthDetails in NodeStatus) > Add new proto changes required for NodeHealthDetails in NodeHealthStatus > > > Key: YARN-10862 > URL: https://issues.apache.org/jira/browse/YARN-10862 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10335) Improve scheduling of containers based on node health
[ https://issues.apache.org/jira/browse/YARN-10335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383640#comment-17383640 ] Cyrus Jackson commented on YARN-10335: -- Since, it is becoming cumbersome to review the PR. I'm breaking it down to multiple subtasks and converting this to Epic. > Improve scheduling of containers based on node health > - > > Key: YARN-10335 > URL: https://issues.apache.org/jira/browse/YARN-10335 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Bibin Chundatt >Assignee: Cyrus Jackson >Priority: Major > Labels: pull-request-available > Attachments: YARN-10335.001.patch, YARN-10335.002.patch, > YARN-10335.003.patch, YARN-10335.004.patch, YARN-10335.005.patch > > Time Spent: 50m > Remaining Estimate: 0h > > YARN-7494 supports providing interface to choose nodeset for scheduler > allocation. > We could leverage the same to support allocation of containers based on node > health value send from nodemanagers -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-10862) Add new proto changes required for NodeHealthDetails in NodeStatus
[ https://issues.apache.org/jira/browse/YARN-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson reassigned YARN-10862: Assignee: Cyrus Jackson > Add new proto changes required for NodeHealthDetails in NodeStatus > -- > > Key: YARN-10862 > URL: https://issues.apache.org/jira/browse/YARN-10862 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10862) Add new proto changes required for NodeHealthDetails in NodeStatus
Cyrus Jackson created YARN-10862: Summary: Add new proto changes required for NodeHealthDetails in NodeStatus Key: YARN-10862 URL: https://issues.apache.org/jira/browse/YARN-10862 Project: Hadoop YARN Issue Type: Sub-task Reporter: Cyrus Jackson -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10861) Make NodeHealthCheckerService pluggable in NodeManager
[ https://issues.apache.org/jira/browse/YARN-10861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-10861: -- Labels: pull-request-available (was: ) > Make NodeHealthCheckerService pluggable in NodeManager > -- > > Key: YARN-10861 > URL: https://issues.apache.org/jira/browse/YARN-10861 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Add support to NodeHealthCheckerService as pluggable interface. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10861) Make NodeHealthCheckerService pluggable in NodeManager
[ https://issues.apache.org/jira/browse/YARN-10861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10861: - Description: Add support to NodeHealthCheckerService as pluggable interface. > Make NodeHealthCheckerService pluggable in NodeManager > -- > > Key: YARN-10861 > URL: https://issues.apache.org/jira/browse/YARN-10861 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > > Add support to NodeHealthCheckerService as pluggable interface. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10861) Make NodeHealthCheckerService pluggable in NodeManager
Cyrus Jackson created YARN-10861: Summary: Make NodeHealthCheckerService pluggable in NodeManager Key: YARN-10861 URL: https://issues.apache.org/jira/browse/YARN-10861 Project: Hadoop YARN Issue Type: Sub-task Components: nodemanager Reporter: Cyrus Jackson Assignee: Cyrus Jackson -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10860) Make max container per heartbeat configs refreshable
[
https://issues.apache.org/jira/browse/YARN-10860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger updated YARN-10860:
---
Attachment: YARN-10860.branch-2.10.001.patch
> Make max container per heartbeat configs refreshable
>
>
> Key: YARN-10860
> URL: https://issues.apache.org/jira/browse/YARN-10860
> Project: Hadoop YARN
> Issue Type: Improvement
>Reporter: Eric Badger
>Assignee: Eric Badger
>Priority: Major
> Attachments: YARN-10860.001.patch, YARN-10860.branch-2.10.001.patch
>
>
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-container-assignments}}
> and
> {{yarn.scheduler.capacity.per-node-heartbeat.multiple-assignments-enabled}}
> are currently *not* refreshable configs, but I believe they should be. This
> JIRA is to turn these into refreshable configs, just like
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-offswitch-assignments}}
> is.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10860) Make max container per heartbeat configs refreshable
[
https://issues.apache.org/jira/browse/YARN-10860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger updated YARN-10860:
---
Attachment: YARN-10860.001.patch
> Make max container per heartbeat configs refreshable
>
>
> Key: YARN-10860
> URL: https://issues.apache.org/jira/browse/YARN-10860
> Project: Hadoop YARN
> Issue Type: Improvement
>Reporter: Eric Badger
>Assignee: Eric Badger
>Priority: Major
> Attachments: YARN-10860.001.patch
>
>
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-container-assignments}}
> and
> {{yarn.scheduler.capacity.per-node-heartbeat.multiple-assignments-enabled}}
> are currently *not* refreshable configs, but I believe they should be. This
> JIRA is to turn these into refreshable configs, just like
> {{yarn.scheduler.capacity.per-node-heartbeat.maximum-offswitch-assignments}}
> is.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10860) Make max container per heartbeat configs refreshable
Eric Badger created YARN-10860:
--
Summary: Make max container per heartbeat configs refreshable
Key: YARN-10860
URL: https://issues.apache.org/jira/browse/YARN-10860
Project: Hadoop YARN
Issue Type: Improvement
Reporter: Eric Badger
Assignee: Eric Badger
{{yarn.scheduler.capacity.per-node-heartbeat.maximum-container-assignments}}
and {{yarn.scheduler.capacity.per-node-heartbeat.multiple-assignments-enabled}}
are currently *not* refreshable configs, but I believe they should be. This
JIRA is to turn these into refreshable configs, just like
{{yarn.scheduler.capacity.per-node-heartbeat.maximum-offswitch-assignments}} is.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10630) [UI2] Ambiguous queue name resolution
[ https://issues.apache.org/jira/browse/YARN-10630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori updated YARN-10630: Attachment: Screenshot 2021-07-19 at 15.30.38.png > [UI2] Ambiguous queue name resolution > - > > Key: YARN-10630 > URL: https://issues.apache.org/jira/browse/YARN-10630 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2021-07-19 at 15.30.38.png > > Time Spent: 10m > Remaining Estimate: 0h > > Yarn UIv2 uses queueName instead of queuePath (which was added in the > scheduler response in YARN-10610), which makes the queue resolution ambiguous > in case of identical queue short names (eg. root.a.b <-> root.b). This causes > invalid behaviour in multiple places. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10630) [UI2] Ambiguous queue name resolution
[ https://issues.apache.org/jira/browse/YARN-10630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-10630: -- Labels: pull-request-available (was: ) > [UI2] Ambiguous queue name resolution > - > > Key: YARN-10630 > URL: https://issues.apache.org/jira/browse/YARN-10630 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Yarn UIv2 uses queueName instead of queuePath (which was added in the > scheduler response in YARN-10610), which makes the queue resolution ambiguous > in case of identical queue short names (eg. root.a.b <-> root.b). This causes > invalid behaviour in multiple places. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10630) [UI2] Ambiguous queue name resolution
[ https://issues.apache.org/jira/browse/YARN-10630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori updated YARN-10630: Summary: [UI2] Ambiguous queue name resolution (was: Ambiguous queue name resolution in Yarn UIv2) > [UI2] Ambiguous queue name resolution > - > > Key: YARN-10630 > URL: https://issues.apache.org/jira/browse/YARN-10630 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > > Yarn UIv2 uses queueName instead of queuePath (which was added in the > scheduler response in YARN-10610), which makes the queue resolution ambiguous > in case of identical queue short names (eg. root.a.b <-> root.b). This causes > invalid behaviour in multiple places. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383371#comment-17383371 ] Andras Gyori commented on YARN-10858: - Thanks [~iwasakims] for the quick response. I agree with your solution, lets keep it simple if we do not need the latest emberjs release. > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Masatake Iwasaki >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > Time Spent: 20m > Remaining Estimate: 0h > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as intended. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10859) [UI2] Extend Applications with queue path instead of queue name
Andras Gyori created YARN-10859: --- Summary: [UI2] Extend Applications with queue path instead of queue name Key: YARN-10859 URL: https://issues.apache.org/jira/browse/YARN-10859 Project: Hadoop YARN Issue Type: Improvement Components: capacity scheduler, yarn-ui-v2 Reporter: Andras Gyori Assignee: Andras Gyori YARN-10630 discovered a bug in UI2, where ambiguous queues (root.a.b <-> root.b) could not be handled properly. It would also eliminate any further inconsistency if we replaced queue names with queue paths. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori reassigned YARN-10858: --- Assignee: Masatake Iwasaki (was: Andras Gyori) > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Masatake Iwasaki >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > Time Spent: 10m > Remaining Estimate: 0h > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as intended. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383328#comment-17383328 ] Masatake Iwasaki commented on YARN-10858: - Thanks for reporting this, [~gandras]. I could reproduce the issue. Quick fix I found was downgrading ember a bit like [#3213|https://github.com/apache/hadoop/pull/3213]. > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > Time Spent: 10m > Remaining Estimate: 0h > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as intended. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-10858: -- Labels: pull-request-available (was: ) > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > Time Spent: 10m > Remaining Estimate: 0h > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as intended. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori updated YARN-10858: Description: With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab is broken and loads an empty page. After reverting the commit, the page is working as intended. We need to investigate what causes this issue, and how we could mitigate it without reverting the commit back. cc. [~iwasakims] [~aajisaka] was: With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab is broken and loads an empty page. After reverting the commit, the page is working as inteded. We need to investigate what causes this issue, and how we could mitigate it without reverting the commit back. cc. [~iwasakims] [~aajisaka] > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as intended. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori updated YARN-10858: Description: With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab is broken and loads an empty page. After reverting the commit, the page is working as inteded. We need to investigate what causes this issue, and how we could mitigate it without reverting the commit back. cc. [~iwasakims] [~aajisaka] was: With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab is broken and loads an empty page. We need to investigate what causes this issue, and how we could mitigate it without reverting the commit back. cc. [~iwasakims] [~aajisaka] > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. After reverting the commit, the page is > working as inteded. > We need to investigate what causes this issue, and how we could mitigate it > without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori updated YARN-10858: Description: With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab is broken and loads an empty page. We need to investigate what causes this issue, and how we could mitigate it without reverting the commit back. (was: With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab is broken and loads an empty page. We need to investigate what causes this issue, and how we could mitigate it without reverting it back.) > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. We need to investigate what causes this > issue, and how we could mitigate it without reverting the commit back. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10858) [UI2] YARN-10826 breaks Queue view
[ https://issues.apache.org/jira/browse/YARN-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori updated YARN-10858: Description: With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab is broken and loads an empty page. We need to investigate what causes this issue, and how we could mitigate it without reverting the commit back. cc. [~iwasakims] [~aajisaka] was:With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab is broken and loads an empty page. We need to investigate what causes this issue, and how we could mitigate it without reverting the commit back. > [UI2] YARN-10826 breaks Queue view > -- > > Key: YARN-10858 > URL: https://issues.apache.org/jira/browse/YARN-10858 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Attachments: Screenshot 2021-07-19 at 11.40.57.png > > > With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab > is broken and loads an empty page. We need to investigate what causes this > issue, and how we could mitigate it without reverting the commit back. > cc. > [~iwasakims] [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10858) [UI2] YARN-10826 breaks Queue view
Andras Gyori created YARN-10858: --- Summary: [UI2] YARN-10826 breaks Queue view Key: YARN-10858 URL: https://issues.apache.org/jira/browse/YARN-10858 Project: Hadoop YARN Issue Type: Improvement Components: yarn-ui-v2 Reporter: Andras Gyori Assignee: Andras Gyori Attachments: Screenshot 2021-07-19 at 11.40.57.png With YARN-10826, UIv2 was upgraded to EmberJS 2.11.3. However, the Queues tab is broken and loads an empty page. We need to investigate what causes this issue, and how we could mitigate it without reverting it back. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10838) Implement an optimised version of Configuration getPropsWithPrefix
[
https://issues.apache.org/jira/browse/YARN-10838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383217#comment-17383217
]
Hadoop QA commented on YARN-10838:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Logfile || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
41s{color} | {color:blue}{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} || ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green}{color} | {color:green} No case conflicting files
found. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green}{color} | {color:green} The patch does not contain any
@author tags. {color} |
| {color:green}+1{color} | {color:green} {color} | {color:green} 0m 0s{color}
| {color:green}test4tests{color} | {color:green} The patch appears to include 3
new or modified test files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} || ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 23m
42s{color} | {color:green}{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
18s{color} | {color:green}{color} | {color:green} trunk passed with JDK
Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
5s{color} | {color:green}{color} | {color:green} trunk passed with JDK Private
Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
58s{color} | {color:green}{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
6s{color} | {color:green}{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
19m 54s{color} | {color:green}{color} | {color:green} branch has no errors when
building and testing our client artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
50s{color} | {color:green}{color} | {color:green} trunk passed with JDK
Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
46s{color} | {color:green}{color} | {color:green} trunk passed with JDK Private
Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10 {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 23m
47s{color} | {color:blue}{color} | {color:blue} Both FindBugs and SpotBugs are
enabled, using SpotBugs. {color} |
| {color:green}+1{color} | {color:green} spotbugs {color} | {color:green} 2m
17s{color} | {color:green}{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} || ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
59s{color} | {color:green}{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
6s{color} | {color:green}{color} | {color:green} the patch passed with JDK
Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 1m 6s{color}
|
{color:red}https://ci-hadoop.apache.org/job/PreCommit-YARN-Build/1125/artifact/out/diff-compile-javac-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkUbuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04.txt{color}
| {color:red}
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkUbuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04
with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 generated 1 new + 54 unchanged
- 1 fixed = 55 total (was 55) {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
58s{color} | {color:green}{color} | {color:green} the patch passed with JDK
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
58s{color} | {color:green}{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 55s{color} |
{color:orange}https://ci-hadoop.apache.org/job/PreCommit-YARN-Build/1125/artifact/out/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt{color}
| {color:orange}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
The patch generated 3 new + 109 unchanged - 0 fixed = 112 total (was 109)
{color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
14s{color} | {color:green}{color} | {color:green} the
[jira] [Assigned] (YARN-10856) Prevent ATS v2 health check REST API call if the ATS service itself is disabled.
[
https://issues.apache.org/jira/browse/YARN-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Ahuja reassigned YARN-10856:
--
Assignee: (was: Siddharth Ahuja)
> Prevent ATS v2 health check REST API call if the ATS service itself is
> disabled.
>
>
> Key: YARN-10856
> URL: https://issues.apache.org/jira/browse/YARN-10856
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn-ui-v2
>Affects Versions: 3.3.1
>Reporter: Siddharth Ahuja
>Priority: Major
>
> Currently, even if {{yarn.timeline-service.enabled}} is disabled, the UI2
> code still goes ahead and performs timeline health check REST API calls, see
> [1], [2] and [3].
> This is un-necessary and can cause slowness issues with RM UI2 page loading
> if a firewall is dropping packets on the ATS v2 port (as it is not meant to
> be available e.g. 8188/8190) in the background and the timeout is not yet hit.
> This ATSv2 health check REST API call is redundant and should be prevented if
> the service itself is disabled.
> [1]
> https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/adapters/timeline-health.js
> [2]
> https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/routes/application.js#L34
> [3]
> https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/routes/yarn-app/logs.js#L40
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10838) Implement an optimised version of Configuration getPropsWithPrefix
[ https://issues.apache.org/jira/browse/YARN-10838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori updated YARN-10838: Attachment: (was: YARN-10838.001.patch) > Implement an optimised version of Configuration getPropsWithPrefix > -- > > Key: YARN-10838 > URL: https://issues.apache.org/jira/browse/YARN-10838 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Andras Gyori >Assignee: Andras Gyori >Priority: Major > Attachments: YARN-10838.001.patch > > > AutoCreatedQueueTemplate also has multiple call to > Configuration#getPropsWithPrefix. It must be eliminated in order to improve > the performance on reinitialisation. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
