[jira] [Created] (YARN-10388) RMNode updatedCapability flag not set while RecommissionNodeTransition
Pranjal Protim Borah created YARN-10388: --- Summary: RMNode updatedCapability flag not set while RecommissionNodeTransition Key: YARN-10388 URL: https://issues.apache.org/jira/browse/YARN-10388 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Reporter: Pranjal Protim Borah Assignee: Pranjal Protim Borah RMNode updatedCapability flag is not set while RecommissionNodeTransition happens. RM gets updated of new totalcapability when recommissioning of node happens. But the nodemanager still has old totalcapability and is not aware of the change. Setting this flag while RecommissionNodeTransition would update nodemanager of totalcapability change as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-10387) Implement logic which returns MappingRule objects based on mapping rules
Peter Bacsko created YARN-10387: --- Summary: Implement logic which returns MappingRule objects based on mapping rules Key: YARN-10387 URL: https://issues.apache.org/jira/browse/YARN-10387 Project: Hadoop YARN Issue Type: Sub-task Reporter: Peter Bacsko Assignee: Peter Bacsko -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-10386) Create new JSON schema for Placement Rules
Peter Bacsko created YARN-10386: --- Summary: Create new JSON schema for Placement Rules Key: YARN-10386 URL: https://issues.apache.org/jira/browse/YARN-10386 Project: Hadoop YARN Issue Type: Sub-task Components: capacity scheduler, capacityscheduler Reporter: Peter Bacsko Assignee: Peter Bacsko -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
[jira] [Created] (YARN-10385) spelling mistakes in method getReservationContinueLook
wangxiangchun created YARN-10385:
Summary: spelling mistakes in method getReservationContinueLook
Key: YARN-10385
URL: https://issues.apache.org/jira/browse/YARN-10385
Project: Hadoop YARN
Issue Type: Bug
Components: capacity scheduler
Affects Versions: 3.2.1
Reporter: wangxiangchun
Attachments: 0805.patch
there is a small spelling mistake in the method :
it makes readers confused .
/*
* Returns whether we should continue to look at all heart beating nodes even
* after the reservation limit was hit. The node heart beating in could
* satisfy the request thus could be a better pick then waiting for the
* reservation to be fullfilled. This config is refreshable.
*/
public boolean getReservationContinueLook() {
return getBoolean(RESERVE_CONT_LOOK_ALL_NODES,
DEFAULT_RESERVE_CONT_LOOK_ALL_NODES);
}
then --> than
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
