[jira] [Updated] (YARN-6429) Revisit implementation of LocalitySchedulingPlacementSet to avoid invoke methods of AppSchedulingInfo
[ https://issues.apache.org/jira/browse/YARN-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shilun Fan updated YARN-6429: - Target Version/s: 3.5.0 (was: 3.4.0) > Revisit implementation of LocalitySchedulingPlacementSet to avoid invoke > methods of AppSchedulingInfo > - > > Key: YARN-6429 > URL: https://issues.apache.org/jira/browse/YARN-6429 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Wangda Tan >Assignee: Wangda Tan >Priority: Major > > An example is, LocalitySchedulingPlacementSet#decrementOutstanding: it calls > appSchedulingInfo directly, which could potentially cause trouble since it > tries to modify parent from child. Is it possible to move this logic to > AppSchedulingInfo#allocate. > Need to check other methods as well. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6429) Revisit implementation of LocalitySchedulingPlacementSet to avoid invoke methods of AppSchedulingInfo
[ https://issues.apache.org/jira/browse/YARN-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-6429: --- Target Version/s: 3.4.0 (was: 3.3.0) Bulk update: moved all 3.3.0 non-blocker issues, please move back if it is a blocker. > Revisit implementation of LocalitySchedulingPlacementSet to avoid invoke > methods of AppSchedulingInfo > - > > Key: YARN-6429 > URL: https://issues.apache.org/jira/browse/YARN-6429 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Wangda Tan >Assignee: Wangda Tan >Priority: Major > > An example is, LocalitySchedulingPlacementSet#decrementOutstanding: it calls > appSchedulingInfo directly, which could potentially cause trouble since it > tries to modify parent from child. Is it possible to move this logic to > AppSchedulingInfo#allocate. > Need to check other methods 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-6429) Revisit implementation of LocalitySchedulingPlacementSet to avoid invoke methods of AppSchedulingInfo
[ https://issues.apache.org/jira/browse/YARN-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-6429: - Target Version/s: 3.3.0 (was: 3.2.0) Bulk update: moved all 3.2.0 non-blocker issues, please move back if it is a blocker. > Revisit implementation of LocalitySchedulingPlacementSet to avoid invoke > methods of AppSchedulingInfo > - > > Key: YARN-6429 > URL: https://issues.apache.org/jira/browse/YARN-6429 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Wangda Tan >Assignee: Wangda Tan >Priority: Major > > An example is, LocalitySchedulingPlacementSet#decrementOutstanding: it calls > appSchedulingInfo directly, which could potentially cause trouble since it > tries to modify parent from child. Is it possible to move this logic to > AppSchedulingInfo#allocate. > Need to check other methods as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6429) Revisit implementation of LocalitySchedulingPlacementSet to avoid invoke methods of AppSchedulingInfo
[ https://issues.apache.org/jira/browse/YARN-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-6429: -- Target Version/s: 3.1.0 (was: 2.9.0, 3.0.0) > Revisit implementation of LocalitySchedulingPlacementSet to avoid invoke > methods of AppSchedulingInfo > - > > Key: YARN-6429 > URL: https://issues.apache.org/jira/browse/YARN-6429 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Wangda Tan >Assignee: Wangda Tan > > An example is, LocalitySchedulingPlacementSet#decrementOutstanding: it calls > appSchedulingInfo directly, which could potentially cause trouble since it > tries to modify parent from child. Is it possible to move this logic to > AppSchedulingInfo#allocate. > Need to check other methods as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org