[jira] [Commented] (HADOOP-11827) Speed-up distcp buildListing() using threadpool
[ https://issues.apache.org/jira/browse/HADOOP-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996139#comment-14996139 ] Zoran Dimitrijevic commented on HADOOP-11827: - I did this long time ago... I have no preference about using - or --. I think I did it the way all other command line arguments in distcp were done, so if we need any fix it will probably be for all options? > Speed-up distcp buildListing() using threadpool > --- > > Key: HADOOP-11827 > URL: https://issues.apache.org/jira/browse/HADOOP-11827 > Project: Hadoop Common > Issue Type: Improvement > Components: tools/distcp >Affects Versions: 2.7.0, 2.7.1 >Reporter: Zoran Dimitrijevic >Assignee: Zoran Dimitrijevic > Fix For: 2.8.0 > > Attachments: HADOOP-11827-02.patch, HADOOP-11827-03.patch, > HADOOP-11827-04.patch, HADOOP-11827.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > For very large source trees on s3 distcp is taking long time to build file > listing (client code, before starting mappers). For a dataset I used (1.5M > files, 50K dirs) it was taking 65 minutes before my fix in HADOOP-11785 and > 36 minutes after the fix). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-12526) [Branch-2] there are duplicate dependency definitions in pom's
[ https://issues.apache.org/jira/browse/HADOOP-12526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated HADOOP-12526: - Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.7.3 2.6.3 2.8.0 Status: Resolved (was: Patch Available) Committed the patch to branch-2, branch-2.7, and branch-2.6. Thanks [~ste...@apache.org] for your review! > [Branch-2] there are duplicate dependency definitions in pom's > -- > > Key: HADOOP-12526 > URL: https://issues.apache.org/jira/browse/HADOOP-12526 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 2.8.0, 2.7.1, 2.6.2 >Reporter: Sangjin Lee >Assignee: Sangjin Lee > Fix For: 2.8.0, 2.6.3, 2.7.3 > > Attachments: HADOOP-12526-branch-2.001.patch, > HADOOP-12526-branch-2.6.001.patch > > > There are several places where dependencies are defined multiple times within > pom's, and are causing maven build warnings. They should be fixed. This is > specific to branch-2.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-10134) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
[ https://issues.apache.org/jira/browse/HADOOP-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated HADOOP-10134: - Fix Version/s: 2.6.3 Committed it to branch-2.6 as well. > [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments > -- > > Key: HADOOP-10134 > URL: https://issues.apache.org/jira/browse/HADOOP-10134 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 2.3.0, 3.0.0 >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Minor > Fix For: 2.7.0, 2.6.3 > > Attachments: 10134-branch-2.patch, 10134-branch-2.patch, > 10134-trunk.patch, 10134-trunk.patch, 10134-trunk.patch, > HADOOP-10134.000.patch > > > Javadoc is more strict by default in JDK8 and will error out on malformed or > illegal tags found in doc comments. Although tagged as JDK8 all of the > required changes are generic Javadoc cleanups. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995917#comment-14995917 ] Hudson commented on HADOOP-11684: - FAILURE: Integrated in Hadoop-Hdfs-trunk #2524 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2524/]) Fix CHANGES.txt for HADOOP-11684. (lei: rev 655d43442f5cc0ba54597d283cdfa576a76ae3ed) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12526) [Branch-2] there are duplicate dependency definitions in pom's
[ https://issues.apache.org/jira/browse/HADOOP-12526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995903#comment-14995903 ] Sangjin Lee commented on HADOOP-12526: -- Yes, that's prior to the patch I believe: https://builds.apache.org/job/PreCommit-HADOOP-Build/8051/artifact/patchprocess/branch-javadoc-hadoop-common-project_hadoop-auth-jdk1.8.0_60.txt The patched javadoc output does not have that problem. > [Branch-2] there are duplicate dependency definitions in pom's > -- > > Key: HADOOP-12526 > URL: https://issues.apache.org/jira/browse/HADOOP-12526 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 2.8.0, 2.7.1, 2.6.2 >Reporter: Sangjin Lee >Assignee: Sangjin Lee > Attachments: HADOOP-12526-branch-2.001.patch, > HADOOP-12526-branch-2.6.001.patch > > > There are several places where dependencies are defined multiple times within > pom's, and are causing maven build warnings. They should be fixed. This is > specific to branch-2.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995881#comment-14995881 ] Hudson commented on HADOOP-11684: - FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #585 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/585/]) Fix CHANGES.txt for HADOOP-11684. (lei: rev 655d43442f5cc0ba54597d283cdfa576a76ae3ed) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995866#comment-14995866 ] Hudson commented on HADOOP-11684: - FAILURE: Integrated in Hadoop-Mapreduce-trunk #2584 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2584/]) Fix CHANGES.txt for HADOOP-11684. (lei: rev 655d43442f5cc0ba54597d283cdfa576a76ae3ed) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12526) [Branch-2] there are duplicate dependency definitions in pom's
[ https://issues.apache.org/jira/browse/HADOOP-12526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995828#comment-14995828 ] Steve Loughran commented on HADOOP-12526: - Javadoc + java8 problems are fixed in HADOOP-10134; feel free to cherry pick that as its just a javadoc patch > [Branch-2] there are duplicate dependency definitions in pom's > -- > > Key: HADOOP-12526 > URL: https://issues.apache.org/jira/browse/HADOOP-12526 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 2.8.0, 2.7.1, 2.6.2 >Reporter: Sangjin Lee >Assignee: Sangjin Lee > Attachments: HADOOP-12526-branch-2.001.patch, > HADOOP-12526-branch-2.6.001.patch > > > There are several places where dependencies are defined multiple times within > pom's, and are causing maven build warnings. They should be fixed. This is > specific to branch-2.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12526) [Branch-2] there are duplicate dependency definitions in pom's
[
https://issues.apache.org/jira/browse/HADOOP-12526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995825#comment-14995825
]
Steve Loughran commented on HADOOP-12526:
-
BTW, log on javadoc still says some duplicates are there
{code}
mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-branch-2.6-1 -Pdocs
-DskipTests clean javadoc:javadoc -DskipTests=true
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.hadoop:hadoop-auth:jar:2.6.3-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must
be unique: org.mortbay.jetty:jetty-util:jar -> duplicate declaration of version
(?) @ line 60, column 17
{code}
> [Branch-2] there are duplicate dependency definitions in pom's
> --
>
> Key: HADOOP-12526
> URL: https://issues.apache.org/jira/browse/HADOOP-12526
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
>Affects Versions: 2.8.0, 2.7.1, 2.6.2
>Reporter: Sangjin Lee
>Assignee: Sangjin Lee
> Attachments: HADOOP-12526-branch-2.001.patch,
> HADOOP-12526-branch-2.6.001.patch
>
>
> There are several places where dependencies are defined multiple times within
> pom's, and are causing maven build warnings. They should be fixed. This is
> specific to branch-2.6.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12526) [Branch-2] there are duplicate dependency definitions in pom's
[ https://issues.apache.org/jira/browse/HADOOP-12526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995823#comment-14995823 ] Steve Loughran commented on HADOOP-12526: - +1: whatever is breaking the builds, I don't think it's this pom diff > [Branch-2] there are duplicate dependency definitions in pom's > -- > > Key: HADOOP-12526 > URL: https://issues.apache.org/jira/browse/HADOOP-12526 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 2.8.0, 2.7.1, 2.6.2 >Reporter: Sangjin Lee >Assignee: Sangjin Lee > Attachments: HADOOP-12526-branch-2.001.patch, > HADOOP-12526-branch-2.6.001.patch > > > There are several places where dependencies are defined multiple times within > pom's, and are causing maven build warnings. They should be fixed. This is > specific to branch-2.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12548) read s3 creds from a Credential Provider
[ https://issues.apache.org/jira/browse/HADOOP-12548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995822#comment-14995822 ] Steve Loughran commented on HADOOP-12548: - it wasn't you larry, don't worry. A different patch went in where the failure of the javadoc wasn't treated as a veto on the commit. Fixed now. > read s3 creds from a Credential Provider > > > Key: HADOOP-12548 > URL: https://issues.apache.org/jira/browse/HADOOP-12548 > Project: Hadoop Common > Issue Type: New Feature > Components: fs/s3 >Reporter: Allen Wittenauer >Assignee: Larry McCay > Attachments: CredentialProviderAPIforS3FS-002.pdf, > HADOOP-12548-01.patch, HADOOP-12548-02.patch, HADOOP-12548-03.patch, > HADOOP-12548-04.patch > > > It would be good if we could read s3 creds from a source other than via a > java property/Hadoop configuration option -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995820#comment-14995820 ] Hudson commented on HADOOP-11684: - SUCCESS: Integrated in Hadoop-Yarn-trunk #1377 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1377/]) Fix CHANGES.txt for HADOOP-11684. (lei: rev 655d43442f5cc0ba54597d283cdfa576a76ae3ed) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995795#comment-14995795 ] Hudson commented on HADOOP-11684: - FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #643 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/643/]) Fix CHANGES.txt for HADOOP-11684. (lei: rev 655d43442f5cc0ba54597d283cdfa576a76ae3ed) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995781#comment-14995781 ] Hudson commented on HADOOP-11684: - FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #654 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/654/]) Fix CHANGES.txt for HADOOP-11684. (lei: rev 655d43442f5cc0ba54597d283cdfa576a76ae3ed) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995776#comment-14995776 ] Hudson commented on HADOOP-11684: - FAILURE: Integrated in Hadoop-trunk-Commit #8776 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8776/]) Fix CHANGES.txt for HADOOP-11684. (lei: rev 655d43442f5cc0ba54597d283cdfa576a76ae3ed) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995770#comment-14995770 ] Lei (Eddy) Xu commented on HADOOP-11684: [~ajisakaa] Thanks a lot for this note. I put the changes into 3.0.0 section in CHANGES.txt. Really sorry for all these troubles. > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12553) [JDK8] Fix javadoc error caused by illegal tag
[
https://issues.apache.org/jira/browse/HADOOP-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995715#comment-14995715
]
Hudson commented on HADOOP-12553:
-
FAILURE: Integrated in Hadoop-Hdfs-trunk #2522 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2522/])
HADOOP-12553. [JDK8] Fix javadoc error caused by illegal tag. (aajisaka)
(aajisaka: rev 3ae82863f045d27b3e29cea2f622e229e7f00690)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java
> [JDK8] Fix javadoc error caused by illegal tag
> --
>
> Key: HADOOP-12553
> URL: https://issues.apache.org/jira/browse/HADOOP-12553
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, documentation
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12553.00.patch
>
>
> After HADOOP-11684, {{mvn package -Pdist -DskipTests}} fails on JDK8.
> {noformat}
> [ERROR] Exit code: 1 -
> /testptch/hadoop/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java:50:
> error: invalid uri: "https://github
> [ERROR] * This is inspired by https://github
> [ERROR] ^
> [ERROR] .com/apache/incubator-s4/blob/master/subprojects
> [ERROR] /s4-comm/src/main/java/org/apache/s4/comm/staging
> [ERROR] /BlockingThreadPoolExecutorService.java"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12556) KafkaSink jar files are created but not copied to target dist
[
https://issues.apache.org/jira/browse/HADOOP-12556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995695#comment-14995695
]
Hadoop QA commented on HADOOP-12556:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 12s
{color} | {color:blue} docker + precommit patch detected. {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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
14s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 10s
{color} | {color:green} trunk passed with JDK v1.8.0_60 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 10s
{color} | {color:green} trunk passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 9s
{color} | {color:green} trunk passed with JDK v1.8.0_60 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 11s
{color} | {color:green} trunk passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
13s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 9s
{color} | {color:green} the patch passed with JDK v1.8.0_60 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 9s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 10s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 10s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 0s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 9s
{color} | {color:green} the patch passed with JDK v1.8.0_60 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 11s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 9s
{color} | {color:green} hadoop-tools-dist in the patch passed with JDK
v1.8.0_60. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 11s
{color} | {color:green} hadoop-tools-dist in the patch passed with JDK
v1.7.0_79. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 7m 1s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.7.1 Server=1.7.1
Image:test-patch-base-hadoop-date2015-11-08 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12771062/HADOOP-12556.patch |
| JIRA Issue | HADOOP-12556 |
| Optional Tests | asflicense javac javadoc mvninstall unit xml compile
|
| uname | Linux 39ef64c026b6 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/patchprocess/apache-yetus-ee5baeb/precommit/personality/hadoop.sh
|
| git revision | trunk / 6d2332a |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /usr/lib/jvm/java-8-oracle:1.8.0_60
/usr/lib/jvm/java-7-openjdk-amd64:1.7.0_79 |
| JDK v1.7.0_79 Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/8052/testReport/ |
| modules | C: hadoop-tools/hadoop-tools-dist U: hadoop-tools/hadoop-tools-dist
|
| Max memory used | 227MB |
| Powered by | Apache Yetus http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/8052/con
[jira] [Updated] (HADOOP-12556) KafkaSink jar files are created but not copied to target dist
[ https://issues.apache.org/jira/browse/HADOOP-12556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-12556: -- Status: Patch Available (was: Open) > KafkaSink jar files are created but not copied to target dist > - > > Key: HADOOP-12556 > URL: https://issues.apache.org/jira/browse/HADOOP-12556 > Project: Hadoop Common > Issue Type: Bug >Reporter: Babak Behzad >Assignee: Babak Behzad > Attachments: HADOOP-12556.patch > > > There is a hadoop-kafka artifact missing from hadoop-tools-dist's pom.xml > which was causing the compiled Kafka jar files not to be copied to the target > dist directory. The new patch adds this in order to complete this fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12557) Add information in BUILDING.txt about the need for the FINDBUGS_HOME environment variable for docs builds.
[
https://issues.apache.org/jira/browse/HADOOP-12557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995656#comment-14995656
]
Allen Wittenauer commented on HADOOP-12557:
---
bq. Should really findbugs details be part of distro in anyway?
That's exactly what I meant by remove. I guess folks didn't understand what
"before test-patch" meant either.. the only way hadoop committers got findbugs
output was *after* doing a full dist build back in the 0.x days. There was no
test-patch to do findbugs analysis during patch review!
This is a great example of everyone reading code and assuming it is actually
correct. :D But once you take a step back, you realize that it completely
bonkers to be putting findbugs output in the distribution documentation.
> Add information in BUILDING.txt about the need for the FINDBUGS_HOME
> environment variable for docs builds.
> --
>
> Key: HADOOP-12557
> URL: https://issues.apache.org/jira/browse/HADOOP-12557
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.7.1
>Reporter: Chris Nauroth
>Assignee: huangzheng
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HADOOP-12557.patch
>
>
> BUILDING.txt mentions Findbugs 1.3.9 as a requirement, but it doesn't mention
> that the {{FINDBUGS_HOME}} environment variable must point to the base
> directory of the Findbugs installation when running builds with {{-Pdocs}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12553) [JDK8] Fix javadoc error caused by illegal tag
[
https://issues.apache.org/jira/browse/HADOOP-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995646#comment-14995646
]
Hudson commented on HADOOP-12553:
-
FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #583 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/583/])
HADOOP-12553. [JDK8] Fix javadoc error caused by illegal tag. (aajisaka)
(aajisaka: rev 3ae82863f045d27b3e29cea2f622e229e7f00690)
*
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> [JDK8] Fix javadoc error caused by illegal tag
> --
>
> Key: HADOOP-12553
> URL: https://issues.apache.org/jira/browse/HADOOP-12553
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, documentation
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12553.00.patch
>
>
> After HADOOP-11684, {{mvn package -Pdist -DskipTests}} fails on JDK8.
> {noformat}
> [ERROR] Exit code: 1 -
> /testptch/hadoop/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java:50:
> error: invalid uri: "https://github
> [ERROR] * This is inspired by https://github
> [ERROR] ^
> [ERROR] .com/apache/incubator-s4/blob/master/subprojects
> [ERROR] /s4-comm/src/main/java/org/apache/s4/comm/staging
> [ERROR] /BlockingThreadPoolExecutorService.java"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12553) [JDK8] Fix javadoc error caused by illegal tag
[
https://issues.apache.org/jira/browse/HADOOP-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995619#comment-14995619
]
Hudson commented on HADOOP-12553:
-
FAILURE: Integrated in Hadoop-Yarn-trunk #1376 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/1376/])
HADOOP-12553. [JDK8] Fix javadoc error caused by illegal tag. (aajisaka)
(aajisaka: rev 3ae82863f045d27b3e29cea2f622e229e7f00690)
*
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> [JDK8] Fix javadoc error caused by illegal tag
> --
>
> Key: HADOOP-12553
> URL: https://issues.apache.org/jira/browse/HADOOP-12553
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, documentation
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12553.00.patch
>
>
> After HADOOP-11684, {{mvn package -Pdist -DskipTests}} fails on JDK8.
> {noformat}
> [ERROR] Exit code: 1 -
> /testptch/hadoop/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java:50:
> error: invalid uri: "https://github
> [ERROR] * This is inspired by https://github
> [ERROR] ^
> [ERROR] .com/apache/incubator-s4/blob/master/subprojects
> [ERROR] /s4-comm/src/main/java/org/apache/s4/comm/staging
> [ERROR] /BlockingThreadPoolExecutorService.java"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12553) [JDK8] Fix javadoc error caused by illegal tag
[
https://issues.apache.org/jira/browse/HADOOP-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995613#comment-14995613
]
Hudson commented on HADOOP-12553:
-
FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #652 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/652/])
HADOOP-12553. [JDK8] Fix javadoc error caused by illegal tag. (aajisaka)
(aajisaka: rev 3ae82863f045d27b3e29cea2f622e229e7f00690)
*
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> [JDK8] Fix javadoc error caused by illegal tag
> --
>
> Key: HADOOP-12553
> URL: https://issues.apache.org/jira/browse/HADOOP-12553
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, documentation
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12553.00.patch
>
>
> After HADOOP-11684, {{mvn package -Pdist -DskipTests}} fails on JDK8.
> {noformat}
> [ERROR] Exit code: 1 -
> /testptch/hadoop/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java:50:
> error: invalid uri: "https://github
> [ERROR] * This is inspired by https://github
> [ERROR] ^
> [ERROR] .com/apache/incubator-s4/blob/master/subprojects
> [ERROR] /s4-comm/src/main/java/org/apache/s4/comm/staging
> [ERROR] /BlockingThreadPoolExecutorService.java"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12553) [JDK8] Fix javadoc error caused by illegal tag
[
https://issues.apache.org/jira/browse/HADOOP-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995610#comment-14995610
]
Hudson commented on HADOOP-12553:
-
FAILURE: Integrated in Hadoop-Mapreduce-trunk #2582 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2582/])
HADOOP-12553. [JDK8] Fix javadoc error caused by illegal tag. (aajisaka)
(aajisaka: rev 3ae82863f045d27b3e29cea2f622e229e7f00690)
*
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> [JDK8] Fix javadoc error caused by illegal tag
> --
>
> Key: HADOOP-12553
> URL: https://issues.apache.org/jira/browse/HADOOP-12553
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, documentation
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12553.00.patch
>
>
> After HADOOP-11684, {{mvn package -Pdist -DskipTests}} fails on JDK8.
> {noformat}
> [ERROR] Exit code: 1 -
> /testptch/hadoop/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java:50:
> error: invalid uri: "https://github
> [ERROR] * This is inspired by https://github
> [ERROR] ^
> [ERROR] .com/apache/incubator-s4/blob/master/subprojects
> [ERROR] /s4-comm/src/main/java/org/apache/s4/comm/staging
> [ERROR] /BlockingThreadPoolExecutorService.java"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12553) [JDK8] Fix javadoc error caused by illegal tag
[
https://issues.apache.org/jira/browse/HADOOP-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995608#comment-14995608
]
Hudson commented on HADOOP-12553:
-
FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #642 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/642/])
HADOOP-12553. [JDK8] Fix javadoc error caused by illegal tag. (aajisaka)
(aajisaka: rev 3ae82863f045d27b3e29cea2f622e229e7f00690)
*
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> [JDK8] Fix javadoc error caused by illegal tag
> --
>
> Key: HADOOP-12553
> URL: https://issues.apache.org/jira/browse/HADOOP-12553
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, documentation
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12553.00.patch
>
>
> After HADOOP-11684, {{mvn package -Pdist -DskipTests}} fails on JDK8.
> {noformat}
> [ERROR] Exit code: 1 -
> /testptch/hadoop/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java:50:
> error: invalid uri: "https://github
> [ERROR] * This is inspired by https://github
> [ERROR] ^
> [ERROR] .com/apache/incubator-s4/blob/master/subprojects
> [ERROR] /s4-comm/src/main/java/org/apache/s4/comm/staging
> [ERROR] /BlockingThreadPoolExecutorService.java"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12557) Add information in BUILDING.txt about the need for the FINDBUGS_HOME environment variable for docs builds.
[
https://issues.apache.org/jira/browse/HADOOP-12557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995602#comment-14995602
]
Vinayakumar B commented on HADOOP-12557:
bq. Looking at hadoop-project-dist/pom.xml, it looks like the intent is for
findbugs.html to show up in the distro with -Pdocs.
Should really findbugs details be part of distro in anyway?
> Add information in BUILDING.txt about the need for the FINDBUGS_HOME
> environment variable for docs builds.
> --
>
> Key: HADOOP-12557
> URL: https://issues.apache.org/jira/browse/HADOOP-12557
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.7.1
>Reporter: Chris Nauroth
>Assignee: huangzheng
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HADOOP-12557.patch
>
>
> BUILDING.txt mentions Findbugs 1.3.9 as a requirement, but it doesn't mention
> that the {{FINDBUGS_HOME}} environment variable must point to the base
> directory of the Findbugs installation when running builds with {{-Pdocs}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995601#comment-14995601 ] Akira AJISAKA commented on HADOOP-11684: Hi [~eddyxu], would you move the section in CHANGES.txt from 2.8.0 to 3.0.0? > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12545) Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider, DefaultImpersonationProvider and DistCp
[
https://issues.apache.org/jira/browse/HADOOP-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995596#comment-14995596
]
Akira AJISAKA commented on HADOOP-12545:
Cancelling my +1. Would you remove {{@Public}} from
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/tools/package-info.java
and add {{@Public}} to
hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/package-info.java?
Since DistCp is in hadoop-distcp package, it's better to add the annotation
there.
> Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider,
> DefaultImpersonationProvider and DistCp
>
>
> Key: HADOOP-12545
> URL: https://issues.apache.org/jira/browse/HADOOP-12545
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.7.1
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
> Attachments: HADOOP-12545-01.patch
>
>
> 1) open hadoop-2.7.1\share\doc\hadoop\api\index.html
> 2) Click on "All Classes"
> 3) Click on "AccessControlList", The page shows "This page can’t be displayed"
> Same error for DistCp, ImpersonationProvider and DefaultImpersonationProvider
> also.
> Javadoc generated from Trunk has the same problem
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12545) Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider, DefaultImpersonationProvider and DistCp
[ https://issues.apache.org/jira/browse/HADOOP-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated HADOOP-12545: --- Hadoop Flags: (was: Reviewed) > Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider, > DefaultImpersonationProvider and DistCp > > > Key: HADOOP-12545 > URL: https://issues.apache.org/jira/browse/HADOOP-12545 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.1 >Reporter: Arshad Mohammad >Assignee: Arshad Mohammad > Attachments: HADOOP-12545-01.patch > > > 1) open hadoop-2.7.1\share\doc\hadoop\api\index.html > 2) Click on "All Classes" > 3) Click on "AccessControlList", The page shows "This page can’t be displayed" > Same error for DistCp, ImpersonationProvider and DefaultImpersonationProvider > also. > Javadoc generated from Trunk has the same problem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-12545) Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider, DefaultImpersonationProvider and DistCp
[ https://issues.apache.org/jira/browse/HADOOP-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated HADOOP-12545: --- Hadoop Flags: Reviewed > Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider, > DefaultImpersonationProvider and DistCp > > > Key: HADOOP-12545 > URL: https://issues.apache.org/jira/browse/HADOOP-12545 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.1 >Reporter: Arshad Mohammad >Assignee: Arshad Mohammad > Attachments: HADOOP-12545-01.patch > > > 1) open hadoop-2.7.1\share\doc\hadoop\api\index.html > 2) Click on "All Classes" > 3) Click on "AccessControlList", The page shows "This page can’t be displayed" > Same error for DistCp, ImpersonationProvider and DefaultImpersonationProvider > also. > Javadoc generated from Trunk has the same problem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12545) Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider, DefaultImpersonationProvider and DistCp
[ https://issues.apache.org/jira/browse/HADOOP-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995592#comment-14995592 ] Akira AJISAKA commented on HADOOP-12545: LGTM, +1. Thanks [~arshad.mohammad]. > Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider, > DefaultImpersonationProvider and DistCp > > > Key: HADOOP-12545 > URL: https://issues.apache.org/jira/browse/HADOOP-12545 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.1 >Reporter: Arshad Mohammad >Assignee: Arshad Mohammad > Attachments: HADOOP-12545-01.patch > > > 1) open hadoop-2.7.1\share\doc\hadoop\api\index.html > 2) Click on "All Classes" > 3) Click on "AccessControlList", The page shows "This page can’t be displayed" > Same error for DistCp, ImpersonationProvider and DefaultImpersonationProvider > also. > Javadoc generated from Trunk has the same problem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-12545) Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider, DefaultImpersonationProvider and DistCp
[ https://issues.apache.org/jira/browse/HADOOP-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated HADOOP-12545: --- Affects Version/s: 2.7.1 > Hadoop Javadoc has broken link for AccessControlList, ImpersonationProvider, > DefaultImpersonationProvider and DistCp > > > Key: HADOOP-12545 > URL: https://issues.apache.org/jira/browse/HADOOP-12545 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.7.1 >Reporter: Arshad Mohammad >Assignee: Arshad Mohammad > Attachments: HADOOP-12545-01.patch > > > 1) open hadoop-2.7.1\share\doc\hadoop\api\index.html > 2) Click on "All Classes" > 3) Click on "AccessControlList", The page shows "This page can’t be displayed" > Same error for DistCp, ImpersonationProvider and DefaultImpersonationProvider > also. > Javadoc generated from Trunk has the same problem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12557) Add information in BUILDING.txt about the need for the FINDBUGS_HOME environment variable for docs builds.
[
https://issues.apache.org/jira/browse/HADOOP-12557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995590#comment-14995590
]
Akira AJISAKA commented on HADOOP-12557:
I tried to remove findbugs dependency for building docs in HADOOP-11468,
however, the issue is 'won't fix' by license problem. Please see [the comment|
https://issues.apache.org/jira/browse/HADOOP-11468?focusedCommentId=14368236&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14368236].
[~aw], do you have any good idea to remove the dependency?
> Add information in BUILDING.txt about the need for the FINDBUGS_HOME
> environment variable for docs builds.
> --
>
> Key: HADOOP-12557
> URL: https://issues.apache.org/jira/browse/HADOOP-12557
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.7.1
>Reporter: Chris Nauroth
>Assignee: huangzheng
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HADOOP-12557.patch
>
>
> BUILDING.txt mentions Findbugs 1.3.9 as a requirement, but it doesn't mention
> that the {{FINDBUGS_HOME}} environment variable must point to the base
> directory of the Findbugs installation when running builds with {{-Pdocs}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-11684) S3a to use thread pool that blocks clients
[ https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated HADOOP-11684: --- Fix Version/s: (was: 2.8.0) > S3a to use thread pool that blocks clients > -- > > Key: HADOOP-11684 > URL: https://issues.apache.org/jira/browse/HADOOP-11684 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.7.0 >Reporter: Thomas Demoor >Assignee: Thomas Demoor > Fix For: 3.0.0 > > Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch, > HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch, > HADOOP-11684-006.patch > > > Currently, if fs.s3a.max.total.tasks are queued and another (part)upload > wants to start, a RejectedExecutionException is thrown. > We should use a threadpool that blocks clients, nicely throtthling them, > rather than throwing an exception. F.i. something similar to > https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12553) [JDK8] Fix javadoc error caused by illegal tag
[
https://issues.apache.org/jira/browse/HADOOP-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995583#comment-14995583
]
Akira AJISAKA commented on HADOOP-12553:
Committed this to trunk. Thanks Allen, Aaron, Eddy, and Brahma for reviewing
the patch.
bq. still jenkins shows following..
I don't know why jenkins build is still failing. I tested my patch and it
worked well.
bq. please fix the check-style issue
The warning "the line is longer than 80 chars" is unavoidable. If we are to
render the line, we need to break the tag.
> [JDK8] Fix javadoc error caused by illegal tag
> --
>
> Key: HADOOP-12553
> URL: https://issues.apache.org/jira/browse/HADOOP-12553
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, documentation
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12553.00.patch
>
>
> After HADOOP-11684, {{mvn package -Pdist -DskipTests}} fails on JDK8.
> {noformat}
> [ERROR] Exit code: 1 -
> /testptch/hadoop/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java:50:
> error: invalid uri: "https://github
> [ERROR] * This is inspired by https://github
> [ERROR] ^
> [ERROR] .com/apache/incubator-s4/blob/master/subprojects
> [ERROR] /s4-comm/src/main/java/org/apache/s4/comm/staging
> [ERROR] /BlockingThreadPoolExecutorService.java"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12553) [JDK8] Fix javadoc error caused by illegal tag
[
https://issues.apache.org/jira/browse/HADOOP-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995581#comment-14995581
]
Hudson commented on HADOOP-12553:
-
FAILURE: Integrated in Hadoop-trunk-Commit #8774 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/8774/])
HADOOP-12553. [JDK8] Fix javadoc error caused by illegal tag. (aajisaka)
(aajisaka: rev 3ae82863f045d27b3e29cea2f622e229e7f00690)
*
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> [JDK8] Fix javadoc error caused by illegal tag
> --
>
> Key: HADOOP-12553
> URL: https://issues.apache.org/jira/browse/HADOOP-12553
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, documentation
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12553.00.patch
>
>
> After HADOOP-11684, {{mvn package -Pdist -DskipTests}} fails on JDK8.
> {noformat}
> [ERROR] Exit code: 1 -
> /testptch/hadoop/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java:50:
> error: invalid uri: "https://github
> [ERROR] * This is inspired by https://github
> [ERROR] ^
> [ERROR] .com/apache/incubator-s4/blob/master/subprojects
> [ERROR] /s4-comm/src/main/java/org/apache/s4/comm/staging
> [ERROR] /BlockingThreadPoolExecutorService.java"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12553) [JDK8] Fix javadoc error caused by illegal tag
[
https://issues.apache.org/jira/browse/HADOOP-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira AJISAKA updated HADOOP-12553:
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.0.0
Target Version/s: 3.0.0 (was: 2.8.0)
Status: Resolved (was: Patch Available)
> [JDK8] Fix javadoc error caused by illegal tag
> --
>
> Key: HADOOP-12553
> URL: https://issues.apache.org/jira/browse/HADOOP-12553
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, documentation
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12553.00.patch
>
>
> After HADOOP-11684, {{mvn package -Pdist -DskipTests}} fails on JDK8.
> {noformat}
> [ERROR] Exit code: 1 -
> /testptch/hadoop/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/BlockingThreadPoolExecutorService.java:50:
> error: invalid uri: "https://github
> [ERROR] * This is inspired by https://github
> [ERROR] ^
> [ERROR] .com/apache/incubator-s4/blob/master/subprojects
> [ERROR] /s4-comm/src/main/java/org/apache/s4/comm/staging
> [ERROR] /BlockingThreadPoolExecutorService.java"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
