[jira] [Commented] (YARN-7664) Several javadoc errors
[
https://issues.apache.org/jira/browse/YARN-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293346#comment-16293346
]
Sean Mackrory commented on YARN-7664:
-
I checked the output for CSQueueUtils.html and IntelFpgaOpenclPlugin.html to
check the resulting angle bracketing and bulleted list. They look correct to
me. Other changes were trivial by comparison.
> Several javadoc errors
> --
>
> Key: YARN-7664
> URL: https://issues.apache.org/jira/browse/YARN-7664
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Sean Mackrory
>Priority: Blocker
> Attachments: YARN-7664.001.patch
>
>
> Not sure if I'm somehow on a different version as our Yetus infra or what,
> but I'm unable to build Hadoop due to some recent changes that are throwing
> JavaDoc errors. Most significantly:
> {code}
> [ERROR]
> /home/sean/src/apache/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateResponse.java:379:
> error: self-closing element not allowed
> [ERROR] *
> [ERROR] ^
> [ERROR]
> /home/sean/src/apache/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateResponse.java:397:
> error: self-closing element not allowed
> [ERROR] *
> [ERROR] ^
> [ERROR]
> /home/sean/src/apache/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceUtils.java:425:
> error: reference not found
> [ERROR] * @throws IllegalArgumentExcpetion if units contain non alpha
> characters
> [ERROR] ^
> {code}
--
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
[jira] [Updated] (YARN-7664) Several javadoc errors
[
https://issues.apache.org/jira/browse/YARN-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated YARN-7664:
Attachment: YARN-7664.001.patch
It's possible I'm only seeing these errors because I happened to be building
with -Pdist today - I suspect Yetus doesn't do that. Attaching a patch that
allows me to build successfully. I haven't checked the actual Javadocs output...
> Several javadoc errors
> --
>
> Key: YARN-7664
> URL: https://issues.apache.org/jira/browse/YARN-7664
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Sean Mackrory
>Priority: Blocker
> Attachments: YARN-7664.001.patch
>
>
> Not sure if I'm somehow on a different version as our Yetus infra or what,
> but I'm unable to build Hadoop due to some recent changes that are throwing
> JavaDoc errors. Most significantly:
> {code}
> [ERROR]
> /home/sean/src/apache/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateResponse.java:379:
> error: self-closing element not allowed
> [ERROR] *
> [ERROR] ^
> [ERROR]
> /home/sean/src/apache/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateResponse.java:397:
> error: self-closing element not allowed
> [ERROR] *
> [ERROR] ^
> [ERROR]
> /home/sean/src/apache/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceUtils.java:425:
> error: reference not found
> [ERROR] * @throws IllegalArgumentExcpetion if units contain non alpha
> characters
> [ERROR] ^
> {code}
--
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
[jira] [Created] (YARN-7664) Several javadoc errors
Sean Mackrory created YARN-7664:
---
Summary: Several javadoc errors
Key: YARN-7664
URL: https://issues.apache.org/jira/browse/YARN-7664
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 3.1.0
Reporter: Sean Mackrory
Priority: Blocker
Not sure if I'm somehow on a different version as our Yetus infra or what, but
I'm unable to build Hadoop due to some recent changes that are throwing JavaDoc
errors. Most significantly:
{code}
[ERROR]
/home/sean/src/apache/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateResponse.java:379:
error: self-closing element not allowed
[ERROR] *
[ERROR] ^
[ERROR]
/home/sean/src/apache/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/AllocateResponse.java:397:
error: self-closing element not allowed
[ERROR] *
[ERROR] ^
[ERROR]
/home/sean/src/apache/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceUtils.java:425:
error: reference not found
[ERROR] * @throws IllegalArgumentExcpetion if units contain non alpha characters
[ERROR] ^
{code}
--
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
[jira] [Commented] (YARN-7465) start-yarn.sh fails to start ResourceManager unless running as root
[
https://issues.apache.org/jira/browse/YARN-7465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244896#comment-16244896
]
Sean Mackrory commented on YARN-7465:
-
I suspect Yetus will complain that there are no tests - but this is a trivial
typo introduced by a major rewrite of the script that is caught by the tests
I'm trying to commit in HDFS-11096.
> start-yarn.sh fails to start ResourceManager unless running as root
> ---
>
> Key: YARN-7465
> URL: https://issues.apache.org/jira/browse/YARN-7465
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.0.0, 3.1.0
>Reporter: Sean Mackrory
>Priority: Blocker
> Attachments: YARN-7465.001.patch
>
>
> This was found when testing rolling upgrades in HDFS-11096. It manifests as
> the following:
> {quote}Starting resourcemanagers on [ container-8.docker container-9.docker]
> /home/hadoop/hadoop-3.0.0-SNAPSHOT/sbin/../libexec/hadoop-functions.sh: line
> 298: --config: command not found{quote}
--
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
[jira] [Updated] (YARN-7465) start-yarn.sh fails to start ResourceManager unless running as root
[
https://issues.apache.org/jira/browse/YARN-7465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated YARN-7465:
Attachment: YARN-7465.001.patch
> start-yarn.sh fails to start ResourceManager unless running as root
> ---
>
> Key: YARN-7465
> URL: https://issues.apache.org/jira/browse/YARN-7465
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.0.0, 3.1.0
>Reporter: Sean Mackrory
>Priority: Blocker
> Attachments: YARN-7465.001.patch
>
>
> This was found when testing rolling upgrades in HDFS-11096. It manifests as
> the following:
> {quote}Starting resourcemanagers on [ container-8.docker container-9.docker]
> /home/hadoop/hadoop-3.0.0-SNAPSHOT/sbin/../libexec/hadoop-functions.sh: line
> 298: --config: command not found{quote}
--
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
[jira] [Created] (YARN-7465) start-yarn.sh fails to start ResourceManager unless running as root
Sean Mackrory created YARN-7465:
---
Summary: start-yarn.sh fails to start ResourceManager unless
running as root
Key: YARN-7465
URL: https://issues.apache.org/jira/browse/YARN-7465
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 3.0.0, 3.1.0
Reporter: Sean Mackrory
Priority: Blocker
This was found when testing rolling upgrades in HDFS-11096. It manifests as the
following:
{quote}Starting resourcemanagers on [ container-8.docker container-9.docker]
/home/hadoop/hadoop-3.0.0-SNAPSHOT/sbin/../libexec/hadoop-functions.sh: line
298: --config: command not found{quote}
--
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
[jira] [Commented] (YARN-1601) 3rd party JARs are missing from hadoop-dist output
[ https://issues.apache.org/jira/browse/YARN-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13872235#comment-13872235 ] Sean Mackrory commented on YARN-1601: - +1 (non-committer) - I can confirm the problem from a Bigtop perspective. If you were to try and build the hadoop-client package it would break because there wouldn't be any other Hadoop package that would provide one of the dependencies Maven determined was needed for a YARN client (specifically, stax-api 1.0-2, which has a different group ID than stax-api 1.0.1). 3rd party JARs are missing from hadoop-dist output -- Key: YARN-1601 URL: https://issues.apache.org/jira/browse/YARN-1601 Project: Hadoop YARN Issue Type: Bug Affects Versions: 3.0.0, 2.4.0 Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Attachments: YARN-1601.patch With the build changes of YARN-888 we are leaving out all 3rd party JArs used directly by YARN under /share/hadoop/yarn/lib/. We did not notice this when running minicluster because they all happen to be in the classpath from hadoop-common and hadoop-yarn. As 3d party JARs are not 'public' interfaces we cannot rely on them being provided to yarn by common and hdfs. (ie if common and hdfs stop using a 3rd party dependency that yarn uses this would break yarn if yarn does not pull that dependency explicitly). Also, this will break bigtop hadoop build when they move to use branch-2 as they expect to find jars in /share/hadoop/yarn/lib/ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
