[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] [Commented] (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:comment-tabpanel=17002141#comment-17002141 ] Wilfred Spiegelenburg commented on YARN-10053: -- Some tests were overriding the group resolution in a way that does not work anymore. Updating the test initialisation. > 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] [Commented] (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:comment-tabpanel=17002106#comment-17002106
]
Hadoop QA commented on YARN-10053:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 18m
46s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} branch-3.1 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m
30s{color} | {color:green} branch-3.1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
46s{color} | {color:green} branch-3.1 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
32s{color} | {color:green} branch-3.1 passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
48s{color} | {color:green} branch-3.1 passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
13m 39s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
15s{color} | {color:green} branch-3.1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} branch-3.1 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
27s{color} | {color:green}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11) {color}
|
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
13m 16s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
25s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 71m 32s{color}
| {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
25s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}146m 10s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler |
| |
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerAutoQueueCreation
|
| |
hadoop.yarn.server.resourcemanager.scheduler.fair.TestQueuePlacementPolicy |
| |
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.5 Server=19.03.5 Image:yetus/hadoop:70a0ef5d4a6 |
| JIRA Issue | YARN-10053 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12989362/YARN-10053-branch-3.1.001.patch
|
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux 6326b1bd2295 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1
05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision |
[jira] [Commented] (YARN-10054) Upgrade yarn to the latest version in Dockerfile
[ https://issues.apache.org/jira/browse/YARN-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002102#comment-17002102 ] Hudson commented on YARN-10054: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17787 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/17787/]) YARN-10054. Upgrade yarn to 1.21.1 in Dockerfile. (#1777) (GitHub: rev c44943d1fc3b6178360093f0068824f2f362ca05) * (edit) dev-support/docker/Dockerfile > Upgrade yarn to the latest version in Dockerfile > > > Key: YARN-10054 > URL: https://issues.apache.org/jira/browse/YARN-10054 > Project: Hadoop YARN > Issue Type: Bug > Components: build, yarn-ui-v2 >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Fix For: 3.3.0 > > > YARN-10036 wrongly installed yarn 1.12.1. Upgrade to 1.21.1. -- 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-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:comment-tabpanel=17002099#comment-17002099
]
Hadoop QA commented on YARN-10053:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
54s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m
46s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
42s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
34s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
45s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
14m 12s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
21s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
28s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
28s{color} | {color:green}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
The patch generated 0 new + 6 unchanged - 1 fixed = 6 total (was 7) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
14m 28s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 86m 45s{color}
| {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
45s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}146m 2s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerAutoQueueCreation
|
| |
hadoop.yarn.server.resourcemanager.scheduler.fair.TestQueuePlacementPolicy |
| |
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.5 Server=19.03.5 Image:yetus/hadoop:bc825b9628f |
| JIRA Issue | YARN-10053 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12989357/YARN-10053.001.patch |
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux 812528479f3e 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1
05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / bc825b9 |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_232 |
| findbugs | v3.1.0-RC1 |
| unit |
[jira] [Assigned] (YARN-10055) bower install fails
[
https://issues.apache.org/jira/browse/YARN-10055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka reassigned YARN-10055:
Assignee: Akira Ajisaka
> bower install fails
> ---
>
> Key: YARN-10055
> URL: https://issues.apache.org/jira/browse/YARN-10055
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, yarn-ui-v2
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
>
> bower install is failing.
> {noformat}
> bower ENOTFOUND Package abdmob/x2js=abdmob/x2js not found
> {noformat}
> I ran the following commands:
> {noformat}
> $ ./start-build.env.sh
> $ cd hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp
> $ bower install
> {noformat}
--
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-10055) bower install fails
Akira Ajisaka created YARN-10055:
Summary: bower install fails
Key: YARN-10055
URL: https://issues.apache.org/jira/browse/YARN-10055
Project: Hadoop YARN
Issue Type: Bug
Components: build, yarn-ui-v2
Reporter: Akira Ajisaka
bower install is failing.
{noformat}
bower ENOTFOUND Package abdmob/x2js=abdmob/x2js not found
{noformat}
I ran the following commands:
{noformat}
$ ./start-build.env.sh
$ cd hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp
$ bower install
{noformat}
--
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-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:comment-tabpanel=17002074#comment-17002074 ] Wilfred Spiegelenburg commented on YARN-10053: -- Patch for the same issue that applies to the 3.1 and 3.2 branches > 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
[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
[jira] [Commented] (YARN-10036) Install yarnpkg and upgrade nodejs in Dockerfile
[ https://issues.apache.org/jira/browse/YARN-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002046#comment-17002046 ] Hudson commented on YARN-10036: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17786 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/17786/]) YARN-10036. Install yarnpkg and upgrade nodejs in Dockerfile (#1772) (GitHub: rev bc825b9628f2fca9d250f91728d4aebb155f1331) * (edit) dev-support/docker/Dockerfile > Install yarnpkg and upgrade nodejs in Dockerfile > > > Key: YARN-10036 > URL: https://issues.apache.org/jira/browse/YARN-10036 > Project: Hadoop YARN > Issue Type: Improvement > Components: buid, yarn-ui-v2 >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Fix For: 3.3.0 > > > Now node.js is installed in Dockerfile but yarnpkg is not installed. > I'd like to run "yarn upgade" command in the build env to manage and upgrade > the dependencies. -- 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-10054) Upgrade yarn to the latest version in Dockerfile
Akira Ajisaka created YARN-10054: Summary: Upgrade yarn to the latest version in Dockerfile Key: YARN-10054 URL: https://issues.apache.org/jira/browse/YARN-10054 Project: Hadoop YARN Issue Type: Bug Components: build, yarn-ui-v2 Reporter: Akira Ajisaka Assignee: Akira Ajisaka YARN-10036 wrongly installed yarn 1.12.1. Upgrade to 1.21.1. -- 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-10037) Upgrade build tools for YARN Web UI v2
[ https://issues.apache.org/jira/browse/YARN-10037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YARN-10037: - Description: The versions of the build tools are too old and have some vulnerabilities. Update. * node: 5.12.0 (latest: 12.13.1 LTS) * yarn: 0.21.3 (latest: 1.21.1) was: The versions of the build tools are too old and have some vulnerabilities. Update. * node: 5.12.0 (latest: 12.13.1 LTS) * yarn: 0.21.3 (latest: 1.12.1) > Upgrade build tools for YARN Web UI v2 > -- > > Key: YARN-10037 > URL: https://issues.apache.org/jira/browse/YARN-10037 > Project: Hadoop YARN > Issue Type: Bug > Components: build, security, yarn-ui-v2 >Reporter: Akira Ajisaka >Assignee: Masatake Iwasaki >Priority: Major > Fix For: 3.3.0 > > Attachments: YARN-10037.001.patch > > > The versions of the build tools are too old and have some vulnerabilities. > Update. > * node: 5.12.0 (latest: 12.13.1 LTS) > * yarn: 0.21.3 (latest: 1.21.1) -- 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-10036) Install yarnpkg and upgrade nodejs in Dockerfile
[ https://issues.apache.org/jira/browse/YARN-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YARN-10036: - Release Note: In the Dockerfile, nodejs is upgraded to 8.17.0 and yarn 1.12.1 is installed. > Install yarnpkg and upgrade nodejs in Dockerfile > > > Key: YARN-10036 > URL: https://issues.apache.org/jira/browse/YARN-10036 > Project: Hadoop YARN > Issue Type: Improvement > Components: buid, yarn-ui-v2 >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Fix For: 3.3.0 > > > Now node.js is installed in Dockerfile but yarnpkg is not installed. > I'd like to run "yarn upgade" command in the build env to manage and upgrade > the dependencies. -- 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-10036) Install yarnpkg and upgrade nodejs in Dockerfile
[ https://issues.apache.org/jira/browse/YARN-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YARN-10036: - Summary: Install yarnpkg and upgrade nodejs in Dockerfile (was: Install yarnpkg in Dockerfile) > Install yarnpkg and upgrade nodejs in Dockerfile > > > Key: YARN-10036 > URL: https://issues.apache.org/jira/browse/YARN-10036 > Project: Hadoop YARN > Issue Type: Improvement > Components: buid, yarn-ui-v2 >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > > Now node.js is installed in Dockerfile but yarnpkg is not installed. > I'd like to run "yarn upgade" command in the build env to manage and upgrade > the dependencies. -- 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-10053) Placement rules do not use correct group service init
Wilfred Spiegelenburg created YARN-10053: Summary: 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 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] [Resolved] (YARN-7012) yarn refuses application if a user has no groups associated
[ https://issues.apache.org/jira/browse/YARN-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-7012. - Assignee: Wilfred Spiegelenburg Resolution: Not A Bug The group mapping you configure should handle the local and non local users. A user must have at least a primary group, it is needed for ownership of files etc. The exception you see shows that the user is not considered valid and this is supposed to happen. > yarn refuses application if a user has no groups associated > --- > > Key: YARN-7012 > URL: https://issues.apache.org/jira/browse/YARN-7012 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 2.7.3 > Environment: redhat 7.3 >Reporter: Michael Salmon >Assignee: Wilfred Spiegelenburg >Priority: Major > > When an application is submitted the list of queue mappings is searched for > the default queue for the user submitting the application. If there is a > queue mapping for a group and the user does not have any groups then an > exception is thrown and the application is rejected: > org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit application > application_1499325026025_0002 submitted by user hive reason: No groups found > for user hive > at UserGroupMappingPlacementRule.java:153 although the lookup is at line 122. > This problem arises when using local users and AD groups. > Users without groups should be treated as users with no matching groups -- 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
