[jira] [Updated] (YARN-1681) When "banned.users" is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
[
https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated YARN-1681:
--
Target Version/s: (was: 2.7.2, 2.6.2)
> When "banned.users" is not set in LCE's container-executor.cfg, submit job
> with user in DEFAULT_BANNED_USERS will receive unclear error message
> ---
>
> Key: YARN-1681
> URL: https://issues.apache.org/jira/browse/YARN-1681
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
>Affects Versions: 2.2.0
>Reporter: Zhichun Wu
>Assignee: Zhichun Wu
> Labels: container, usability
> Attachments: YARN-1681.patch
>
>
> When using LCE in a secure setup, if "banned.users" is not set in
> container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS
> ("mapred", "hdfs", "bin", 0) will receive unclear error message.
> for example, if we use hdfs to submit a mr job, we may see the following the
> yarn app overview page:
> {code}
> appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
> Application application_1391353981633_0003 initialization failed
> (exitCode=139) with output:
> {code}
> while the prefer error message may look like:
> {code}
> appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
> Application application_1391353981633_0003 initialization failed
> (exitCode=139) with output: Requested user hdfs is banned
> {code}
> just a minor bug and I would like to start contributing to hadoop-common with
> it:)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-1681) When banned.users is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
[
https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated YARN-1681:
--
Target Version/s: 2.7.2, 2.6.2 (was: 2.6.1, 2.7.2)
When banned.users is not set in LCE's container-executor.cfg, submit job
with user in DEFAULT_BANNED_USERS will receive unclear error message
---
Key: YARN-1681
URL: https://issues.apache.org/jira/browse/YARN-1681
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 2.2.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu
Labels: container, usability
Attachments: YARN-1681.patch
When using LCE in a secure setup, if banned.users is not set in
container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS
(mapred, hdfs, bin, 0) will receive unclear error message.
for example, if we use hdfs to submit a mr job, we may see the following the
yarn app overview page:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output:
{code}
while the prefer error message may look like:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output: Requested user hdfs is banned
{code}
just a minor bug and I would like to start contributing to hadoop-common with
it:)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-1681) When banned.users is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
[
https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated YARN-1681:
--
Unless the patch is ready to go and the JIRA is a critical fix, we'll defer it
to 2.6.2. Let me know if you have comments. Thanks!
When banned.users is not set in LCE's container-executor.cfg, submit job
with user in DEFAULT_BANNED_USERS will receive unclear error message
---
Key: YARN-1681
URL: https://issues.apache.org/jira/browse/YARN-1681
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 2.2.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu
Labels: container, usability
Attachments: YARN-1681.patch
When using LCE in a secure setup, if banned.users is not set in
container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS
(mapred, hdfs, bin, 0) will receive unclear error message.
for example, if we use hdfs to submit a mr job, we may see the following the
yarn app overview page:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output:
{code}
while the prefer error message may look like:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output: Requested user hdfs is banned
{code}
just a minor bug and I would like to start contributing to hadoop-common with
it:)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-1681) When banned.users is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
[
https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-1681:
--
Target Version/s: 2.6.1, 2.7.2 (was: 2.6.0)
Moving all tickets targeted for the already closed release 2.6.0 into
2.6.1/2.7.2.
When banned.users is not set in LCE's container-executor.cfg, submit job
with user in DEFAULT_BANNED_USERS will receive unclear error message
---
Key: YARN-1681
URL: https://issues.apache.org/jira/browse/YARN-1681
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 2.2.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu
Labels: container, usability
Attachments: YARN-1681.patch
When using LCE in a secure setup, if banned.users is not set in
container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS
(mapred, hdfs, bin, 0) will receive unclear error message.
for example, if we use hdfs to submit a mr job, we may see the following the
yarn app overview page:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output:
{code}
while the prefer error message may look like:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output: Requested user hdfs is banned
{code}
just a minor bug and I would like to start contributing to hadoop-common with
it:)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-1681) When banned.users is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
[
https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian He updated YARN-1681:
--
Priority: Major (was: Minor)
When banned.users is not set in LCE's container-executor.cfg, submit job
with user in DEFAULT_BANNED_USERS will receive unclear error message
---
Key: YARN-1681
URL: https://issues.apache.org/jira/browse/YARN-1681
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 2.2.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu
Labels: container, usability
Attachments: YARN-1681.patch
When using LCE in a secure setup, if banned.users is not set in
container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS
(mapred, hdfs, bin, 0) will receive unclear error message.
for example, if we use hdfs to submit a mr job, we may see the following the
yarn app overview page:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output:
{code}
while the prefer error message may look like:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output: Requested user hdfs is banned
{code}
just a minor bug and I would like to start contributing to hadoop-common with
it:)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-1681) When banned.users is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
[
https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated YARN-1681:
---
Target Version/s: 2.6.0 (was: 2.5.0)
When banned.users is not set in LCE's container-executor.cfg, submit job
with user in DEFAULT_BANNED_USERS will receive unclear error message
---
Key: YARN-1681
URL: https://issues.apache.org/jira/browse/YARN-1681
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 2.2.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu
Priority: Minor
Labels: container, usability
Attachments: YARN-1681.patch
When using LCE in a secure setup, if banned.users is not set in
container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS
(mapred, hdfs, bin, 0) will receive unclear error message.
for example, if we use hdfs to submit a mr job, we may see the following the
yarn app overview page:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output:
{code}
while the prefer error message may look like:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output: Requested user hdfs is banned
{code}
just a minor bug and I would like to start contributing to hadoop-common with
it:)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (YARN-1681) When banned.users is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
[
https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-1681:
--
Target Version/s: 2.5.0 (was: 2.4.1)
When banned.users is not set in LCE's container-executor.cfg, submit job
with user in DEFAULT_BANNED_USERS will receive unclear error message
---
Key: YARN-1681
URL: https://issues.apache.org/jira/browse/YARN-1681
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 2.2.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu
Priority: Minor
Labels: container, usability
Attachments: YARN-1681.patch
When using LCE in a secure setup, if banned.users is not set in
container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS
(mapred, hdfs, bin, 0) will receive unclear error message.
for example, if we use hdfs to submit a mr job, we may see the following the
yarn app overview page:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output:
{code}
while the prefer error message may look like:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output: Requested user hdfs is banned
{code}
just a minor bug and I would like to start contributing to hadoop-common with
it:)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (YARN-1681) When banned.users is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
[
https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-1681:
--
Labels: container usability (was: container)
When banned.users is not set in LCE's container-executor.cfg, submit job
with user in DEFAULT_BANNED_USERS will receive unclear error message
---
Key: YARN-1681
URL: https://issues.apache.org/jira/browse/YARN-1681
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 2.2.0
Reporter: Zhichun Wu
Priority: Minor
Labels: container, usability
Attachments: YARN-1681.patch
When using LCE in a secure setup, if banned.users is not set in
container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS
(mapred, hdfs, bin, 0) will receive unclear error message.
for example, if we use hdfs to submit a mr job, we may see the following the
yarn app overview page:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output:
{code}
while the prefer error message may look like:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output: Requested user hdfs is banned
{code}
just a minor bug and I would like to start contributing to hadoop-common with
it:)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (YARN-1681) When banned.users is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message
[
https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhichun Wu updated YARN-1681:
-
Attachment: YARN-1681.patch
When banned.users is not set in LCE's container-executor.cfg, submit job
with user in DEFAULT_BANNED_USERS will receive unclear error message
---
Key: YARN-1681
URL: https://issues.apache.org/jira/browse/YARN-1681
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 2.2.0
Reporter: Zhichun Wu
Priority: Minor
Labels: container
Attachments: YARN-1681.patch
When using LCE in a secure setup, if banned.users is not set in
container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS
(mapred, hdfs, bin, 0) will receive unclear error message.
for example, if we use hdfs to submit a mr job, we may see the following the
yarn app overview page:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output:
{code}
while the prefer error message may look like:
{code}
appattempt_1391353981633_0003_02 exited with exitCode: -1000 due to:
Application application_1391353981633_0003 initialization failed
(exitCode=139) with output: Requested user hdfs is banned
{code}
just a minor bug and I would like to start contributing to hadoop-common with
it:)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
