[jira] [Updated] (YARN-10053) Placement rules do not use correct group service init
[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-10053: - Fix Version/s: 3.1.4 3.2.2 3.3.0 > Placement rules do not use correct group service init > - > > Key: YARN-10053 > URL: https://issues.apache.org/jira/browse/YARN-10053 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 3.1.3 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: Reviewed > Fix For: 3.3.0, 3.2.2, 3.1.4 > > Attachments: YARN-10053-branch-3.1.001.patch, > YARN-10053-branch-3.1.002.patch, YARN-10053-branch-3.1.003.patch, > YARN-10053-branch-3.2.001.patch, YARN-10053-branch-3.2.002.patch, > YARN-10053.001.patch, YARN-10053.002.patch > > > The placement rules, CS and FS, all create a new group service instead of > using the shared group mapping service. This means that the cache for the > placement rules is not same as for the ACL and other parts of the RM service. > It also could cause an issue with the configuration that is passed in to > create the cache: the scheduler config might not have the same values as the > service config and could thus cause issues. This second issue just seems to > affect the CS not the FS. -- 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-10053) Placement rules do not use correct group service init
[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-10053: - Labels: Reviewed (was: ) > Placement rules do not use correct group service init > - > > Key: YARN-10053 > URL: https://issues.apache.org/jira/browse/YARN-10053 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 3.1.3 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: Reviewed > Attachments: YARN-10053-branch-3.1.001.patch, > YARN-10053-branch-3.1.002.patch, YARN-10053-branch-3.1.003.patch, > YARN-10053-branch-3.2.001.patch, YARN-10053-branch-3.2.002.patch, > YARN-10053.001.patch, YARN-10053.002.patch > > > The placement rules, CS and FS, all create a new group service instead of > using the shared group mapping service. This means that the cache for the > placement rules is not same as for the ACL and other parts of the RM service. > It also could cause an issue with the configuration that is passed in to > create the cache: the scheduler config might not have the same values as the > service config and could thus cause issues. This second issue just seems to > affect the CS not the FS. -- 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-10053) Placement rules do not use correct group service init
[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.2.002.patch > Placement rules do not use correct group service init > - > > Key: YARN-10053 > URL: https://issues.apache.org/jira/browse/YARN-10053 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 3.1.3 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Attachments: YARN-10053-branch-3.1.001.patch, > YARN-10053-branch-3.1.002.patch, YARN-10053-branch-3.1.003.patch, > YARN-10053-branch-3.2.001.patch, YARN-10053-branch-3.2.002.patch, > YARN-10053.001.patch, YARN-10053.002.patch > > > The placement rules, CS and FS, all create a new group service instead of > using the shared group mapping service. This means that the cache for the > placement rules is not same as for the ACL and other parts of the RM service. > It also could cause an issue with the configuration that is passed in to > create the cache: the scheduler config might not have the same values as the > service config and could thus cause issues. This second issue just seems to > affect the CS not the FS. -- 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-10053) Placement rules do not use correct group service init
[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.1.003.patch > Placement rules do not use correct group service init > - > > Key: YARN-10053 > URL: https://issues.apache.org/jira/browse/YARN-10053 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 3.1.3 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Attachments: YARN-10053-branch-3.1.001.patch, > YARN-10053-branch-3.1.002.patch, YARN-10053-branch-3.1.003.patch, > YARN-10053-branch-3.2.001.patch, YARN-10053.001.patch, YARN-10053.002.patch > > > The placement rules, CS and FS, all create a new group service instead of > using the shared group mapping service. This means that the cache for the > placement rules is not same as for the ACL and other parts of the RM service. > It also could cause an issue with the configuration that is passed in to > create the cache: the scheduler config might not have the same values as the > service config and could thus cause issues. This second issue just seems to > affect the CS not the FS. -- 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-10053) Placement rules do not use correct group service init
[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.2.001.patch > Placement rules do not use correct group service init > - > > Key: YARN-10053 > URL: https://issues.apache.org/jira/browse/YARN-10053 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 3.1.3 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Attachments: YARN-10053-branch-3.1.001.patch, > YARN-10053-branch-3.1.002.patch, YARN-10053-branch-3.2.001.patch, > YARN-10053.001.patch, YARN-10053.002.patch > > > The placement rules, CS and FS, all create a new group service instead of > using the shared group mapping service. This means that the cache for the > placement rules is not same as for the ACL and other parts of the RM service. > It also could cause an issue with the configuration that is passed in to > create the cache: the scheduler config might not have the same values as the > service config and could thus cause issues. This second issue just seems to > affect the CS not the FS. -- 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-10053) Placement rules do not use correct group service init
[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.1.002.patch > Placement rules do not use correct group service init > - > > Key: YARN-10053 > URL: https://issues.apache.org/jira/browse/YARN-10053 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 3.1.3 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Attachments: YARN-10053-branch-3.1.001.patch, > YARN-10053-branch-3.1.002.patch, YARN-10053.001.patch, YARN-10053.002.patch > > > The placement rules, CS and FS, all create a new group service instead of > using the shared group mapping service. This means that the cache for the > placement rules is not same as for the ACL and other parts of the RM service. > It also could cause an issue with the configuration that is passed in to > create the cache: the scheduler config might not have the same values as the > service config and could thus cause issues. This second issue just seems to > affect the CS not the FS. -- 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-10053) Placement rules do not use correct group service init
[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053.002.patch > Placement rules do not use correct group service init > - > > Key: YARN-10053 > URL: https://issues.apache.org/jira/browse/YARN-10053 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 3.1.3 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Attachments: YARN-10053-branch-3.1.001.patch, YARN-10053.001.patch, > YARN-10053.002.patch > > > The placement rules, CS and FS, all create a new group service instead of > using the shared group mapping service. This means that the cache for the > placement rules is not same as for the ACL and other parts of the RM service. > It also could cause an issue with the configuration that is passed in to > create the cache: the scheduler config might not have the same values as the > service config and could thus cause issues. This second issue just seems to > affect the CS not the FS. -- 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-10053) Placement rules do not use correct group service init
[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.1.001.patch > Placement rules do not use correct group service init > - > > Key: YARN-10053 > URL: https://issues.apache.org/jira/browse/YARN-10053 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 3.1.3 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Attachments: YARN-10053-branch-3.1.001.patch, YARN-10053.001.patch > > > The placement rules, CS and FS, all create a new group service instead of > using the shared group mapping service. This means that the cache for the > placement rules is not same as for the ACL and other parts of the RM service. > It also could cause an issue with the configuration that is passed in to > create the cache: the scheduler config might not have the same values as the > service config and could thus cause issues. This second issue just seems to > affect the CS not the FS. -- 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
