[jira] [Updated] (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 updated YARN-10864: - Description: Introduce NodeHealthDetails (NHD) to NodeHealthStatus. NHD will contain information about the node in form of a Map. This Map is of . This is done in order to reduce the size of the map. The Key Values can be retrieved by Enum/Strings representing the key to get the corresponding resource value. Based on this information ResourceManager can utilize this value and schedule or take appropriate action on the node like decomissioning the node (can be based on overallValue in NodeHealthDetailsProto as well) was: Introduce NodeHealthDetails (NHD) to NodeHealthStatus. NHD will contain information about the node in form of a Map. This Map is of . This is done in order to reduce the size of the map. The Key Values can be retrieved by Enum/Strings representing the key to get the corresponding resource value. Based on this information ResourceManager can utilize this value and schedule or take appropriate action on the node like decomissioning the node (can be based on overallValue in NodeHealthDetailsProto) > 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 > > Introduce NodeHealthDetails (NHD) to NodeHealthStatus. > NHD will contain information about the node in form of a Map. This Map is of > . This is done in order to reduce the size of the map. The Key > Values can be retrieved by Enum/Strings representing the key to get the > corresponding resource value. Based on this information ResourceManager can > utilize this value and schedule or take appropriate action on the node like > decomissioning the node (can be based on overallValue in > NodeHealthDetailsProto as well) > -- 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-10864) Implement NodeHealthDetails for NodeHealthStatus
[ https://issues.apache.org/jira/browse/YARN-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10864: - Description: Introduce NodeHealthDetails (NHD) to NodeHealthStatus. NHD will contain information about the node in form of a Map. This Map is of . This is done in order to reduce the size of the map. The Key Values can be retrieved by Enum/Strings representing the key to get the corresponding resource value. Based on this information ResourceManager can utilize this value and schedule or take appropriate action on the node like decomissioning the node (can be based on overallValue in NodeHealthDetailsProto) > 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 > > Introduce NodeHealthDetails (NHD) to NodeHealthStatus. > NHD will contain information about the node in form of a Map. This Map is of > . This is done in order to reduce the size of the map. The Key > Values can be retrieved by Enum/Strings representing the key to get the > corresponding resource value. Based on this information ResourceManager can > utilize this value and schedule or take appropriate action on the node like > decomissioning the node (can be based on overallValue in > NodeHealthDetailsProto) > -- 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-10865) Add UI support to display NodeHealthDetails in NodePage
[ https://issues.apache.org/jira/browse/YARN-10865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10865: - Attachment: (was: image-2021-07-20-12-42-59-013.png) > Add UI support to display NodeHealthDetails in NodePage > --- > > Key: YARN-10865 > URL: https://issues.apache.org/jira/browse/YARN-10865 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Attachments: image-2021-07-20-12-43-41-273.png > > > Add support to display NodeHealthDetails resource information on Node Page. > Sample Page: > !image-2021-07-20-12-43-41-273.png|width=1423,height=250! -- 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-10865) Add UI support to display NodeHealthDetails in NodePage
[ https://issues.apache.org/jira/browse/YARN-10865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10865: - Attachment: image-2021-07-20-12-43-41-273.png > Add UI support to display NodeHealthDetails in NodePage > --- > > Key: YARN-10865 > URL: https://issues.apache.org/jira/browse/YARN-10865 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Attachments: image-2021-07-20-12-42-59-013.png, > image-2021-07-20-12-43-41-273.png > > -- 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-10865) Add UI support to display NodeHealthDetails in NodePage
[ https://issues.apache.org/jira/browse/YARN-10865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10865: - Description: Add support to display NodeHealthDetails resource information on Node Page. Sample Page: !image-2021-07-20-12-43-41-273.png|width=1423,height=250! > Add UI support to display NodeHealthDetails in NodePage > --- > > Key: YARN-10865 > URL: https://issues.apache.org/jira/browse/YARN-10865 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Attachments: image-2021-07-20-12-42-59-013.png, > image-2021-07-20-12-43-41-273.png > > > Add support to display NodeHealthDetails resource information on Node Page. > Sample Page: > !image-2021-07-20-12-43-41-273.png|width=1423,height=250! -- 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-10865) Add UI support to display NodeHealthDetails in NodePage
[ https://issues.apache.org/jira/browse/YARN-10865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10865: - Attachment: image-2021-07-20-12-42-59-013.png > Add UI support to display NodeHealthDetails in NodePage > --- > > Key: YARN-10865 > URL: https://issues.apache.org/jira/browse/YARN-10865 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Attachments: image-2021-07-20-12-42-59-013.png, > image-2021-07-20-12-43-41-273.png > > -- 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-10865) Add UI support to display NodeHealthDetails in NodePage
[ https://issues.apache.org/jira/browse/YARN-10865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson reassigned YARN-10865: Assignee: Cyrus Jackson > Add UI support to display NodeHealthDetails in NodePage > --- > > Key: YARN-10865 > URL: https://issues.apache.org/jira/browse/YARN-10865 > 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-10865) Add UI support to display NodeHealthDetails in NodePage
Cyrus Jackson created YARN-10865: Summary: Add UI support to display NodeHealthDetails in NodePage Key: YARN-10865 URL: https://issues.apache.org/jira/browse/YARN-10865 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] [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-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] [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 ] 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-10769) Reconnect transition in RMNodeImpl all containers are considered as G
[ https://issues.apache.org/jira/browse/YARN-10769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10769: - Attachment: YARN-10769.003.patch > Reconnect transition in RMNodeImpl all containers are considered as G > -- > > Key: YARN-10769 > URL: https://issues.apache.org/jira/browse/YARN-10769 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bibin Chundatt >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10769.001.patch, YARN-10769.002.patch, > YARN-10769.003.patch > > > In RMNodeImpl#handleNMContainerStatus *createContainerStatus* is not > considering the container execution type for creating ContainerStatus -- 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-10769) Reconnect transition in RMNodeImpl all containers are considered as G
[ https://issues.apache.org/jira/browse/YARN-10769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10769: - Attachment: YARN-10769.002.patch > Reconnect transition in RMNodeImpl all containers are considered as G > -- > > Key: YARN-10769 > URL: https://issues.apache.org/jira/browse/YARN-10769 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bibin Chundatt >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10769.001.patch, YARN-10769.002.patch > > > In RMNodeImpl#handleNMContainerStatus *createContainerStatus* is not > considering the container execution type for creating ContainerStatus -- 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-10769) Reconnect transition in RMNodeImpl all containers are considered as G
[ https://issues.apache.org/jira/browse/YARN-10769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10769: - Attachment: YARN-10769.001.patch > Reconnect transition in RMNodeImpl all containers are considered as G > -- > > Key: YARN-10769 > URL: https://issues.apache.org/jira/browse/YARN-10769 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bibin Chundatt >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10769.001.patch > > > In RMNodeImpl#handleNMContainerStatus *createContainerStatus* is not > considering the container execution type for creating ContainerStatus -- 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-10769) Reconnect transition in RMNodeImpl all containers are considered as G
[ https://issues.apache.org/jira/browse/YARN-10769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17345897#comment-17345897 ] Cyrus Jackson commented on YARN-10769: -- I would like to work on it. Assigning it to me. > Reconnect transition in RMNodeImpl all containers are considered as G > -- > > Key: YARN-10769 > URL: https://issues.apache.org/jira/browse/YARN-10769 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bibin Chundatt >Priority: Minor > > In RMNodeImpl#handleNMContainerStatus *createContainerStatus* is not > considering the container execution type for creating ContainerStatus -- 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-10769) Reconnect transition in RMNodeImpl all containers are considered as G
[ https://issues.apache.org/jira/browse/YARN-10769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson reassigned YARN-10769: Assignee: Cyrus Jackson > Reconnect transition in RMNodeImpl all containers are considered as G > -- > > Key: YARN-10769 > URL: https://issues.apache.org/jira/browse/YARN-10769 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bibin Chundatt >Assignee: Cyrus Jackson >Priority: Minor > > In RMNodeImpl#handleNMContainerStatus *createContainerStatus* is not > considering the container execution type for creating ContainerStatus -- 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Attachment: YARN-10476.005.patch > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Labels: pull-request-available > Attachments: YARN-10476.001.patch, YARN-10476.002.patch, > YARN-10476.003.patch, YARN-10476.004.patch, YARN-10476.005.patch > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Right now we do not have separate metrics for unmanaged applications. All > application metrics come as part of Queue Metrics (Managed and UnManaged), > This Jira aims to emit unmanaged metrics along with managed apps -- 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: - Attachment: YARN-10335.005.patch > 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 > Attachments: YARN-10335.001.patch, YARN-10335.002.patch, > YARN-10335.003.patch, YARN-10335.004.patch, YARN-10335.005.patch > > > 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-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: - Attachment: (was: YARN-10335.005.patch) > 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 > Attachments: YARN-10335.001.patch, YARN-10335.002.patch, > YARN-10335.003.patch, YARN-10335.004.patch, YARN-10335.005.patch > > > 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-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: - Attachment: YARN-10335.005.patch > 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 > Attachments: YARN-10335.001.patch, YARN-10335.002.patch, > YARN-10335.003.patch, YARN-10335.004.patch, YARN-10335.005.patch > > > 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Description: Right now we do not have separate metrics for unmanaged applications. All application metrics come as part of Queue Metrics (Managed and UnManaged), This Jira aims to emit unmanaged metrics along with managed apps (was: Right now we do not have separate metrics unmanaged applications. All application metrics come as part of Queue (Managed and UnManaged), This Jira aims to show them separately.) > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch, YARN-10476.002.patch, > YARN-10476.003.patch, YARN-10476.004.patch > > > Right now we do not have separate metrics for unmanaged applications. All > application metrics come as part of Queue Metrics (Managed and UnManaged), > This Jira aims to emit unmanaged metrics along with managed apps -- 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Attachment: YARN-10476.004.patch > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch, YARN-10476.002.patch, > YARN-10476.003.patch, YARN-10476.004.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10533) Display managed apps and unmanaged apps on RM UI
[ https://issues.apache.org/jira/browse/YARN-10533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10533: - Summary: Display managed apps and unmanaged apps on RM UI (was: Separate metrics on RM UI for managed apps and unmanaged apps) > Display managed apps and unmanaged apps on RM UI > > > Key: YARN-10533 > URL: https://issues.apache.org/jira/browse/YARN-10533 > Project: Hadoop YARN > Issue Type: Improvement >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-10533) Separate metrics on RM UI for managed apps and unmanaged apps
Cyrus Jackson created YARN-10533: Summary: Separate metrics on RM UI for managed apps and unmanaged apps Key: YARN-10533 URL: https://issues.apache.org/jira/browse/YARN-10533 Project: Hadoop YARN Issue Type: Improvement 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Attachment: YARN-10476.003.patch > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch, YARN-10476.002.patch, > YARN-10476.003.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Attachment: (was: YARN-10476.003.patch) > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch, YARN-10476.002.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Attachment: YARN-10476.003.patch > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch, YARN-10476.002.patch, > YARN-10476.003.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223011#comment-17223011 ] Cyrus Jackson commented on YARN-10476: -- Instead of using rmContext to get the unmanagedAM as its an overkill. In patch 2, I'm getting unmanagedAM flag from scheduler side itself. > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch, YARN-10476.002.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Attachment: YARN-10476.002.patch > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch, YARN-10476.002.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Attachment: (was: YARN-10476.001.patch) > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics for Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Summary: Queue metrics for Unmanaged applications (was: Queue metrics of Unmanaged applications) > Queue metrics for Unmanaged applications > - > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics of Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222721#comment-17222721 ] Cyrus Jackson commented on YARN-10476: -- Submitting initial patch for unit tests. > Queue metrics of Unmanaged applications > > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics of Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Attachment: YARN-10476.001.patch > Queue metrics of Unmanaged applications > > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10476.001.patch > > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics of Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Issue Type: Improvement (was: Bug) > Queue metrics of Unmanaged applications > > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics of Unmanaged applications
[ https://issues.apache.org/jira/browse/YARN-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10476: - Description: Right now we do not have separate metrics unmanaged applications. All application metrics come as part of Queue (Managed and UnManaged), This Jira aims to show them separately. > Queue metrics of Unmanaged applications > > > Key: YARN-10476 > URL: https://issues.apache.org/jira/browse/YARN-10476 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > > Right now we do not have separate metrics unmanaged applications. All > application metrics come as part of Queue (Managed and UnManaged), This Jira > aims to show them separately. -- 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-10476) Queue metrics of Unmanaged applications
Cyrus Jackson created YARN-10476: Summary: Queue metrics of Unmanaged applications Key: YARN-10476 URL: https://issues.apache.org/jira/browse/YARN-10476 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager 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-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: - Attachment: YARN-10335.004.patch > 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 > Attachments: YARN-10335.001.patch, YARN-10335.002.patch, > YARN-10335.003.patch, YARN-10335.004.patch > > > 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-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: - Attachment: YARN-10335.003.patch > 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 > Attachments: YARN-10335.001.patch, YARN-10335.002.patch, > YARN-10335.003.patch > > > 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-10351) finishedApplications and runningApplications should be of Set data type
[ https://issues.apache.org/jira/browse/YARN-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10351: - Priority: Minor (was: Major) > finishedApplications and runningApplications should be of Set data type > --- > > Key: YARN-10351 > URL: https://issues.apache.org/jira/browse/YARN-10351 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > > finishedApplications and runningApplications should be moved to a Set instead > of List for performance improvement -- 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-10351) finishedApplications and runningApplications should be of Set data type
[ https://issues.apache.org/jira/browse/YARN-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson reassigned YARN-10351: Assignee: Cyrus Jackson > finishedApplications and runningApplications should be of Set data type > --- > > Key: YARN-10351 > URL: https://issues.apache.org/jira/browse/YARN-10351 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > > finishedApplications and runningApplications should be moved to a Set instead > of List for performance improvement -- 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-10351) finishedApplications and runningApplications should be of Set data type
Cyrus Jackson created YARN-10351: Summary: finishedApplications and runningApplications should be of Set data type Key: YARN-10351 URL: https://issues.apache.org/jira/browse/YARN-10351 Project: Hadoop YARN Issue Type: Sub-task Reporter: Cyrus Jackson finishedApplications and runningApplications should be moved to a Set instead of List for performance improvement -- 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=17151863#comment-17151863 ] Cyrus Jackson commented on YARN-10335: -- Thanks [~bibinchundatt] for your inputs. I have worked on the working patch with the changes. Please give your thoughts on the approach. The current approach is to have a new NodeHealthDetail which holds the additional information such as SSD, HDD, SKU... etc. The overallScore is generated based on these values from the NodeHealthCheckerService. This is then stored to RmNodeImpl. The overallScore can be used for scheduling nodes on the RM side. NodeHealthService is added to make the NodeHealthCheckerService pluggable to support custom implementations. > 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 > Attachments: YARN-10335.001.patch > > > 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-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: - Attachment: YARN-10335.001.patch > 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 > Attachments: YARN-10335.001.patch > > > 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-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: - Attachment: (was: yarn_DE.patch) > 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 > > 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-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: - Attachment: yarn_DE.patch > 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 > Attachments: yarn_DE.patch > > > 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-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 reassigned YARN-10335: Assignee: Cyrus Jackson > 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 > > 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] [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=17149190#comment-17149190 ] Cyrus Jackson commented on YARN-10335: -- I would like to work on this. [~bibinchundatt] > 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 >Priority: Major > > 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Attachment: (was: YARN-10216.001.patch) > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Attachments: YARN-10216.001.patch, image-2020-04-06-09-50-51-948.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The purpose of this feature is to let individual classes which are > interested in observing this configuration changes, to be notified when the > conf is reloaded from the disk. This is similar to how Hbase has done. > *Class Diagram* > !image-2020-04-06-09-50-51-948.png! > > *APPROACH DETAILS* > The approach is based on the adaption of Hbase Online Configuration. In this > case, the configuration file is monitored for any changes on the disk. If the > file has changed, the properties of Configuration is reloaded and all the > observers are notified. > The classes that implements the observers updates the necessary values if > required. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Attachment: YARN-10216.001.patch > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Major > Attachments: YARN-10216.001.patch, image-2020-04-06-09-50-51-948.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The purpose of this feature is to let individual classes which are > interested in observing this configuration changes, to be notified when the > conf is reloaded from the disk. This is similar to how Hbase has done. > *Class Diagram* > !image-2020-04-06-09-50-51-948.png! > > *APPROACH DETAILS* > The approach is based on the adaption of Hbase Online Configuration. In this > case, the configuration file is monitored for any changes on the disk. If the > file has changed, the properties of Configuration is reloaded and all the > observers are notified. > The classes that implements the observers updates the necessary values if > required. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Description: There should be a way to dynamically reload the configuration properties from the disk. The purpose of this feature is to let individual classes which are interested in observing this configuration changes, to be notified when the conf is reloaded from the disk. This is similar to how Hbase has done. *Class Diagram* !image-2020-04-06-09-50-51-948.png! *APPROACH DETAILS* The approach is based on the adaption of Hbase Online Configuration. In this case, the configuration file is monitored for any changes on the disk. If the file has changed, the properties of Configuration is reloaded and all the observers are notified. The classes that implements the observers updates the necessary values if required. was: There should be a way to dynamically reload the configuration properties from the disk. The purpose of this feature is to let individual classes which are interested in observing this configuration changes, to be notified when the conf is reloaded from the disk. This is similar to how Hbase has done. *Class Diagram* !image-2020-04-06-09-50-51-948.png! *APPROACH DETAILS* The approach is based on the adaption of Hbase Online Configuration. In this case, the configuration file is monitored for any changes. If the file has changed, the properties of Configuration is reloaded from the disk and the observers are notified. The classes that implements the observers are required to update the necessary values. > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > Attachments: image-2020-04-06-09-50-51-948.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The purpose of this feature is to let individual classes which are > interested in observing this configuration changes, to be notified when the > conf is reloaded from the disk. This is similar to how Hbase has done. > *Class Diagram* > !image-2020-04-06-09-50-51-948.png! > > *APPROACH DETAILS* > The approach is based on the adaption of Hbase Online Configuration. In this > case, the configuration file is monitored for any changes on the disk. If the > file has changed, the properties of Configuration is reloaded and all the > observers are notified. > The classes that implements the observers updates the necessary values if > required. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Description: There should be a way to dynamically reload the configuration properties from the disk. The purpose of this feature is to let individual classes which are interested in observing this configuration changes, to be notified when the conf is reloaded from the disk. This is similar to how Hbase has done. *Class Diagram* !image-2020-04-06-09-50-51-948.png! *APPROACH DETAILS* The approach is based on the adaption of Hbase Online Configuration. In this case, the configuration file is monitored for any changes. If the file has changed, the properties of Configuration is reloaded from the disk and the observers are notified. The classes that implements the observers are required to update the necessary values. was: There should be a way to dynamically reload the configuration properties from the disk. The purpose of this feature is to let individual classes which are interested in observing this configuration changes, to be notified when the conf is reloaded from the desk. This is similar to how Hbase has done. *Class Diagram* !image-2020-04-06-09-50-51-948.png! *APPROACH DETAILS* The approach is based on the adaption of Hbase Online Configuration. In this case, the configuration file is monitored for any changes. If the file has changed, the properties of Configuration is reloaded from the disk and the observers are notified. The classes that implements the observers are required to update the necessary values. > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > Attachments: image-2020-04-06-09-50-51-948.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The purpose of this feature is to let individual classes which are > interested in observing this configuration changes, to be notified when the > conf is reloaded from the disk. This is similar to how Hbase has done. > *Class Diagram* > !image-2020-04-06-09-50-51-948.png! > > *APPROACH DETAILS* > The approach is based on the adaption of Hbase Online Configuration. In this > case, the configuration file is monitored for any changes. If the file has > changed, the properties of Configuration is reloaded from the disk and the > observers are notified. > The classes that implements the observers are required to update the > necessary values. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Attachment: (was: image-2020-04-06-09-42-32-221.png) > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > Attachments: image-2020-04-06-09-50-51-948.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The purpose of this feature is to let individual classes which are > interested in observing this configuration changes, to be notified when the > conf is reloaded from the desk. This is similar to how Hbase has done. > *Class Diagram* > !image-2020-04-06-09-50-51-948.png! > > *APPROACH DETAILS* > The approach is based on the adaption of Hbase Online Configuration. In this > case, the configuration file is monitored for any changes. If the file has > changed, the properties of Configuration is reloaded from the disk and the > observers are notified. > The classes that implements the observers are required to update the > necessary values. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Description: There should be a way to dynamically reload the configuration properties from the disk. The purpose of this feature is to let individual classes which are interested in observing this configuration changes, to be notified when the conf is reloaded from the desk. This is similar to how Hbase has done. *Class Diagram* !image-2020-04-06-09-50-51-948.png! *APPROACH DETAILS* The approach is based on the adaption of Hbase Online Configuration. In this case, the configuration file is monitored for any changes. If the file has changed, the properties of Configuration is reloaded from the disk and the observers are notified. The classes that implements the observers are required to update the necessary values. was: There should be a way to dynamically reload the configuration properties from the disk. The approach is to notify the individual classes that the Configuration is reloaded and make the changes on the fly. The purpose of this feature is to let individual classes which are interested in observing this configuration changes, to be notified when the conf is reloaded from the desk. This is similar to how Hbase has done. > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > Attachments: image-2020-04-06-09-50-51-948.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The purpose of this feature is to let individual classes which are > interested in observing this configuration changes, to be notified when the > conf is reloaded from the desk. This is similar to how Hbase has done. > *Class Diagram* > !image-2020-04-06-09-50-51-948.png! > > *APPROACH DETAILS* > The approach is based on the adaption of Hbase Online Configuration. In this > case, the configuration file is monitored for any changes. If the file has > changed, the properties of Configuration is reloaded from the disk and the > observers are notified. > The classes that implements the observers are required to update the > necessary values. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Attachment: image-2020-04-06-09-50-51-948.png > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > Attachments: image-2020-04-06-09-42-32-221.png, > image-2020-04-06-09-50-51-948.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The approach is to notify the individual classes that the > Configuration is reloaded and make the changes on the fly. The purpose of > this feature is to let individual classes which are interested in observing > this configuration changes, to be notified when the conf is reloaded from the > desk. This is similar to how Hbase has done. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Attachment: (was: image-2020-04-06-09-42-09-452.png) > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > Attachments: image-2020-04-06-09-42-32-221.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The approach is to notify the individual classes that the > Configuration is reloaded and make the changes on the fly. The purpose of > this feature is to let individual classes which are interested in observing > this configuration changes, to be notified when the conf is reloaded from the > desk. This is similar to how Hbase has done. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Attachment: image-2020-04-06-09-42-09-452.png > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > Attachments: image-2020-04-06-09-42-09-452.png, > image-2020-04-06-09-42-32-221.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The approach is to notify the individual classes that the > Configuration is reloaded and make the changes on the fly. The purpose of > this feature is to let individual classes which are interested in observing > this configuration changes, to be notified when the conf is reloaded from the > desk. This is similar to how Hbase has done. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Attachment: image-2020-04-06-09-42-32-221.png > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > Attachments: image-2020-04-06-09-42-09-452.png, > image-2020-04-06-09-42-32-221.png > > > There should be a way to dynamically reload the configuration properties from > the disk. The approach is to notify the individual classes that the > Configuration is reloaded and make the changes on the fly. The purpose of > this feature is to let individual classes which are interested in observing > this configuration changes, to be notified when the conf is reloaded from the > desk. This is similar to how Hbase has done. > -- 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
[ https://issues.apache.org/jira/browse/YARN-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10214: - Attachment: YARN-10214.003.patch > Separate TaskRunner for AM and NM tasks in SLS. > > > Key: YARN-10214 > URL: https://issues.apache.org/jira/browse/YARN-10214 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler-load-simulator >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10214.001.patch, YARN-10214.002.patch, > YARN-10214.003.patch > > > NM simulator and AM simulator uses the same TaskRunner Pool currently. > Defining separate pools for AM and NM will improve the run times. -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Description: There should be a way to dynamically reload the configuration properties from the disk. The approach is to notify the individual classes that the Configuration is reloaded and make the changes on the fly. The purpose of this feature is to let individual classes which are interested in observing this configuration changes, to be notified when the conf is reloaded from the desk. This is similar to how Hbase has done. was: There should be a way to dynamically reload the configuration properties from the disk. The approach is to notify the individual classes that the Configuration is reloaded and make the changes on the fly. This is similar to how Hbase has done. > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > > There should be a way to dynamically reload the configuration properties from > the disk. The approach is to notify the individual classes that the > Configuration is reloaded and make the changes on the fly. The purpose of > this feature is to let individual classes which are interested in observing > this configuration changes, to be notified when the conf is reloaded from the > desk. This is similar to how Hbase has done. > -- 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
[ https://issues.apache.org/jira/browse/YARN-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10214: - Attachment: YARN-10214.002.patch > Separate TaskRunner for AM and NM tasks in SLS. > > > Key: YARN-10214 > URL: https://issues.apache.org/jira/browse/YARN-10214 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler-load-simulator >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10214.001.patch, YARN-10214.002.patch > > > NM simulator and AM simulator uses the same TaskRunner Pool currently. > Defining separate pools for AM and NM will improve the run times. -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Description: There should be a way to dynamically reload the configuration properties from the disk. The approach is to notify the individual classes that the Configuration is reloaded and make the changes on the fly. This is similar to how Hbase has done. was: There should be a way to dynamically reload the configuration properties from the disk. The approach is to notify the individual classes that the Configuration is reloaded. This is similar to how Hbase has done. > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > > There should be a way to dynamically reload the configuration properties from > the disk. The approach is to notify the individual classes that the > Configuration is reloaded and make the changes on the fly. This is similar to > how Hbase has done. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Description: There should be a way to dynamically reload the configuration properties from the disk. The approach is to notify the individual classes that the Configuration is reloaded. This is similar to how Hbase has done. was:Right > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > > There should be a way to dynamically reload the configuration properties from > the disk. The approach is to notify the individual classes that the > Configuration is reloaded. This is similar to how Hbase has done. > -- 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-10216) Utility to dynamically reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Summary: Utility to dynamically reload Configuration on the disk (was: Utility to reload Configuration on the disk) > Utility to dynamically reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > > Right -- 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-10216) Utility to reload Configuration on the disk
[ https://issues.apache.org/jira/browse/YARN-10216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10216: - Description: Right > Utility to reload Configuration on the disk > --- > > Key: YARN-10216 > URL: https://issues.apache.org/jira/browse/YARN-10216 > Project: Hadoop YARN > Issue Type: New Feature >Reporter: Cyrus Jackson >Priority: Major > > Right -- 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-10216) Utility to reload Configuration on the disk
Cyrus Jackson created YARN-10216: Summary: Utility to reload Configuration on the disk Key: YARN-10216 URL: https://issues.apache.org/jira/browse/YARN-10216 Project: Hadoop YARN Issue Type: New Feature 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
[ https://issues.apache.org/jira/browse/YARN-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10214: - Attachment: (was: YARN-10214.001.patch) > Separate TaskRunner for AM and NM tasks in SLS. > > > Key: YARN-10214 > URL: https://issues.apache.org/jira/browse/YARN-10214 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler-load-simulator >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10214.001.patch > > > NM simulator and AM simulator uses the same TaskRunner Pool currently. > Defining separate pools for AM and NM will improve the run times. -- 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
[ https://issues.apache.org/jira/browse/YARN-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10214: - Attachment: YARN-10214.001.patch > Separate TaskRunner for AM and NM tasks in SLS. > > > Key: YARN-10214 > URL: https://issues.apache.org/jira/browse/YARN-10214 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler-load-simulator >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10214.001.patch > > > NM simulator and AM simulator uses the same TaskRunner Pool currently. > Defining separate pools for AM and NM will improve the run times. -- 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
[ https://issues.apache.org/jira/browse/YARN-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10214: - Description: NM simulator and AM simulator uses the same TaskRunner Pool currently. Defining separate pools for AM and NM will improve the run times. (was: NM simulator and AM simulator uses the same TaskRunner Pool currently. Defining separate pool for AM and NM will improve the run times.) > Separate TaskRunner for AM and NM tasks in SLS. > > > Key: YARN-10214 > URL: https://issues.apache.org/jira/browse/YARN-10214 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler-load-simulator >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > > NM simulator and AM simulator uses the same TaskRunner Pool currently. > Defining separate pools for AM and NM will improve the run times. -- 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
[ https://issues.apache.org/jira/browse/YARN-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson reassigned YARN-10214: Assignee: Cyrus Jackson > Separate TaskRunner for AM and NM tasks in SLS. > > > Key: YARN-10214 > URL: https://issues.apache.org/jira/browse/YARN-10214 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler-load-simulator >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > > NM simulator and AM simulator uses the same TaskRunner Pool currently. > Defining separate pool for AM and NM will improve the run times. -- 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
[ https://issues.apache.org/jira/browse/YARN-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10214: - Priority: Minor (was: Major) > Separate TaskRunner for AM and NM tasks in SLS. > > > Key: YARN-10214 > URL: https://issues.apache.org/jira/browse/YARN-10214 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler-load-simulator >Reporter: Cyrus Jackson >Priority: Minor > > NM simulator and AM simulator uses the same TaskRunner Pool currently. > Defining separate pool for AM and NM -- 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
[ https://issues.apache.org/jira/browse/YARN-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10214: - Description: NM simulator and AM simulator uses the same TaskRunner Pool currently. Defining separate pool for AM and NM > Separate TaskRunner for AM and NM tasks in SLS. > > > Key: YARN-10214 > URL: https://issues.apache.org/jira/browse/YARN-10214 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler-load-simulator >Reporter: Cyrus Jackson >Priority: Major > > NM simulator and AM simulator uses the same TaskRunner Pool currently. > Defining separate pool for AM and NM -- 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
[ https://issues.apache.org/jira/browse/YARN-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10214: - Description: NM simulator and AM simulator uses the same TaskRunner Pool currently. Defining separate pool for AM and NM will improve the run times. (was: NM simulator and AM simulator uses the same TaskRunner Pool currently. Defining separate pool for AM and NM) > Separate TaskRunner for AM and NM tasks in SLS. > > > Key: YARN-10214 > URL: https://issues.apache.org/jira/browse/YARN-10214 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler-load-simulator >Reporter: Cyrus Jackson >Priority: Minor > > NM simulator and AM simulator uses the same TaskRunner Pool currently. > Defining separate pool for AM and NM will improve the run times. -- 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-10214) Separate TaskRunner for AM and NM tasks in SLS.
Cyrus Jackson created YARN-10214: Summary: Separate TaskRunner for AM and NM tasks in SLS. Key: YARN-10214 URL: https://issues.apache.org/jira/browse/YARN-10214 Project: Hadoop YARN Issue Type: Improvement Components: scheduler-load-simulator 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] [Commented] (YARN-10172) Default ApplicationPlacementType class should be configurable
[ https://issues.apache.org/jira/browse/YARN-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070680#comment-17070680 ] Cyrus Jackson commented on YARN-10172: -- Thanks [~bibinchundatt] for reviewing the patch. I have made the changes. > Default ApplicationPlacementType class should be configurable > - > > Key: YARN-10172 > URL: https://issues.apache.org/jira/browse/YARN-10172 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10172.001.patch, YARN-10172.002.patch > > > This can be useful in scheduling apps based on the configured placement type > class rather than resorting to LocalityAppPlacementAllocator -- 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-10172) Default ApplicationPlacementType class should be configurable
[ https://issues.apache.org/jira/browse/YARN-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10172: - Attachment: YARN-10172.002.patch > Default ApplicationPlacementType class should be configurable > - > > Key: YARN-10172 > URL: https://issues.apache.org/jira/browse/YARN-10172 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10172.001.patch, YARN-10172.002.patch > > > This can be useful in scheduling apps based on the configured placement type > class rather than resorting to LocalityAppPlacementAllocator -- 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-10172) Default ApplicationPlacementType class should be configurable
[ https://issues.apache.org/jira/browse/YARN-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10172: - Attachment: (was: YARN-10172.001.patch) > Default ApplicationPlacementType class should be configurable > - > > Key: YARN-10172 > URL: https://issues.apache.org/jira/browse/YARN-10172 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10172.001.patch > > > This can be useful in scheduling apps based on the configured placement type > class rather than resorting to LocalityAppPlacementAllocator -- 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-10172) Default ApplicationPlacementType class should be configurable
[ https://issues.apache.org/jira/browse/YARN-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10172: - Target Version/s: (was: 3.1.3) > Default ApplicationPlacementType class should be configurable > - > > Key: YARN-10172 > URL: https://issues.apache.org/jira/browse/YARN-10172 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10172.001.patch > > > This can be useful in scheduling apps based on the configured placement type > class rather than resorting to LocalityAppPlacementAllocator -- 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-10172) Default ApplicationPlacementType class should be configurable
[ https://issues.apache.org/jira/browse/YARN-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10172: - Attachment: (was: YARN-10172.001.patch) > Default ApplicationPlacementType class should be configurable > - > > Key: YARN-10172 > URL: https://issues.apache.org/jira/browse/YARN-10172 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10172.001.patch > > > This can be useful in scheduling apps based on the configured placement type > class rather than resorting to LocalityAppPlacementAllocator -- 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] [Issue Comment Deleted] (YARN-10172) Default ApplicationPlacementType class should be configurable
[ https://issues.apache.org/jira/browse/YARN-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10172: - Comment: was deleted (was: [~hadoopqa]) > Default ApplicationPlacementType class should be configurable > - > > Key: YARN-10172 > URL: https://issues.apache.org/jira/browse/YARN-10172 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10172.001.patch > > > This can be useful in scheduling apps based on the configured placement type > class rather than resorting to LocalityAppPlacementAllocator -- 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-10172) Default ApplicationPlacementType class should be configurable
[ https://issues.apache.org/jira/browse/YARN-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065439#comment-17065439 ] Cyrus Jackson commented on YARN-10172: -- [~hadoopqa] > Default ApplicationPlacementType class should be configurable > - > > Key: YARN-10172 > URL: https://issues.apache.org/jira/browse/YARN-10172 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10172.001.patch > > > This can be useful in scheduling apps based on the configured placement type > class rather than resorting to LocalityAppPlacementAllocator -- 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-10172) Default ApplicationPlacementType class should be configurable
[ https://issues.apache.org/jira/browse/YARN-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10172: - Attachment: (was: YARN-10172.001.patch) > Default ApplicationPlacementType class should be configurable > - > > Key: YARN-10172 > URL: https://issues.apache.org/jira/browse/YARN-10172 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10172.001.patch > > > This can be useful in scheduling apps based on the configured placement type > class rather than resorting to LocalityAppPlacementAllocator -- 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-10172) Default ApplicationPlacementType class should be configurable
[ https://issues.apache.org/jira/browse/YARN-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-10172: - Attachment: YARN-10172.001.patch > Default ApplicationPlacementType class should be configurable > - > > Key: YARN-10172 > URL: https://issues.apache.org/jira/browse/YARN-10172 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Cyrus Jackson >Assignee: Cyrus Jackson >Priority: Minor > Attachments: YARN-10172.001.patch > > > This can be useful in scheduling apps based on the configured placement type > class rather than resorting to LocalityAppPlacementAllocator -- 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-10172) Default ApplicationPlacementType class should be configurable
Cyrus Jackson created YARN-10172: Summary: Default ApplicationPlacementType class should be configurable Key: YARN-10172 URL: https://issues.apache.org/jira/browse/YARN-10172 Project: Hadoop YARN Issue Type: Improvement Reporter: Cyrus Jackson Assignee: Cyrus Jackson This can be useful in scheduling apps based on the configured placement type class rather than resorting to LocalityAppPlacementAllocator -- 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-9908) Make ZK calls in parallel to load application states.
[ https://issues.apache.org/jira/browse/YARN-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson reassigned YARN-9908: --- Assignee: Cyrus Jackson (was: Abhishek Modi) > Make ZK calls in parallel to load application states. > - > > Key: YARN-9908 > URL: https://issues.apache.org/jira/browse/YARN-9908 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Abhishek Modi >Assignee: Cyrus Jackson >Priority: Major > > At present, all the application states are fetched linearly from ZooKeeper. > This can be optimized by using a threadpool to fetch application states from > Zookeeper. -- 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-6997) org.apache.hadoop.yarn.client.SCMAdmin wrong package name
[ https://issues.apache.org/jira/browse/YARN-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994469#comment-16994469 ] Cyrus Jackson commented on YARN-6997: - [~Honda] I have created a patch for the same. If you are not working on this, can I please take it up? > org.apache.hadoop.yarn.client.SCMAdmin wrong package name > - > > Key: YARN-6997 > URL: https://issues.apache.org/jira/browse/YARN-6997 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Reporter: Miklos Szegedi >Assignee: HondaWei >Priority: Critical > Attachments: YARN-6997.001.patch > > > It should be org.apache.hadoop.yarn.client.cli.SCMAdmin to follow the current > naming standard. This may cause appcompat issues in the future. -- 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-6997) org.apache.hadoop.yarn.client.SCMAdmin wrong package name
[ https://issues.apache.org/jira/browse/YARN-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-6997: Attachment: YARN-6997.001.patch > org.apache.hadoop.yarn.client.SCMAdmin wrong package name > - > > Key: YARN-6997 > URL: https://issues.apache.org/jira/browse/YARN-6997 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager >Reporter: Miklos Szegedi >Assignee: HondaWei >Priority: Critical > Attachments: YARN-6997.001.patch > > > It should be org.apache.hadoop.yarn.client.cli.SCMAdmin to follow the current > naming standard. This may cause appcompat issues in the future. -- 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-2442) ResourceManager JMX UI does not give HA State
[ https://issues.apache.org/jira/browse/YARN-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-2442: Attachment: YARN-2442.004.patch > ResourceManager JMX UI does not give HA State > - > > Key: YARN-2442 > URL: https://issues.apache.org/jira/browse/YARN-2442 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 2.5.0, 2.6.0, 2.7.0 >Reporter: Nishan Shetty >Assignee: Rohith Sharma K S >Priority: Major > Labels: oct16-easy > Attachments: 0001-YARN-2442.patch, YARN-2442.003.patch, > YARN-2442.004.patch, YARN-2442.02.patch > > > ResourceManager JMX UI can show the haState (INITIALIZING, ACTIVE, STANDBY, > STOPPED) -- 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-2442) ResourceManager JMX UI does not give HA State
[ https://issues.apache.org/jira/browse/YARN-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-2442: Attachment: (was: YARN-2442.004.patch) > ResourceManager JMX UI does not give HA State > - > > Key: YARN-2442 > URL: https://issues.apache.org/jira/browse/YARN-2442 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 2.5.0, 2.6.0, 2.7.0 >Reporter: Nishan Shetty >Assignee: Rohith Sharma K S >Priority: Major > Labels: oct16-easy > Attachments: 0001-YARN-2442.patch, YARN-2442.003.patch, > YARN-2442.02.patch > > > ResourceManager JMX UI can show the haState (INITIALIZING, ACTIVE, STANDBY, > STOPPED) -- 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-2442) ResourceManager JMX UI does not give HA State
[ https://issues.apache.org/jira/browse/YARN-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-2442: Attachment: YARN-2442.004.patch > ResourceManager JMX UI does not give HA State > - > > Key: YARN-2442 > URL: https://issues.apache.org/jira/browse/YARN-2442 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 2.5.0, 2.6.0, 2.7.0 >Reporter: Nishan Shetty >Assignee: Rohith Sharma K S >Priority: Major > Labels: oct16-easy > Attachments: 0001-YARN-2442.patch, YARN-2442.003.patch, > YARN-2442.004.patch, YARN-2442.02.patch > > > ResourceManager JMX UI can show the haState (INITIALIZING, ACTIVE, STANDBY, > STOPPED) -- 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-2442) ResourceManager JMX UI does not give HA State
[ https://issues.apache.org/jira/browse/YARN-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrus Jackson updated YARN-2442: Attachment: YARN-2442.003.patch > ResourceManager JMX UI does not give HA State > - > > Key: YARN-2442 > URL: https://issues.apache.org/jira/browse/YARN-2442 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager >Affects Versions: 2.5.0, 2.6.0, 2.7.0 >Reporter: Nishan Shetty >Assignee: Rohith Sharma K S >Priority: Major > Labels: oct16-easy > Attachments: 0001-YARN-2442.patch, YARN-2442.003.patch, > YARN-2442.02.patch > > > ResourceManager JMX UI can show the haState (INITIALIZING, ACTIVE, STANDBY, > STOPPED) -- 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
