Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/ No changes -1 overall The following subsystems voted -1: findbugs unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: FindBugs : module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api org.apache.hadoop.yarn.api.records.Resource.getResources() may expose internal representation by returning Resource.resources At Resource.java:by returning Resource.resources At Resource.java:[line 234] Failed junit tests : hadoop.crypto.key.kms.server.TestKMS hadoop.hdfs.TestDFSStripedOutputStreamWithFailure hadoop.hdfs.web.TestWebHdfsTimeouts hadoop.hdfs.server.namenode.TestDecommissioningStatus hadoop.fs.http.server.TestHttpFSServerWebServer hadoop.yarn.server.nodemanager.webapp.TestContainerLogsPage hadoop.yarn.sls.TestSLSRunner cc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/diff-compile-cc-root.txt [4.0K] javac: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/diff-compile-javac-root.txt [280K] checkstyle: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/diff-checkstyle-root.txt [17M] pylint: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/diff-patch-pylint.txt [24K] shellcheck: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/diff-patch-shellcheck.txt [20K] shelldocs: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/diff-patch-shelldocs.txt [12K] whitespace: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/whitespace-eol.txt [9.2M] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/whitespace-tabs.txt [288K] xml: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/xml.txt [4.0K] findbugs: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-warnings.html [8.0K] javadoc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/diff-javadoc-javadoc-root.txt [760K] unit: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/patch-unit-hadoop-common-project_hadoop-kms.txt [12K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt [296K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-httpfs.txt [24K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt [48K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-jobclient.txt [88K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-applications_hadoop-yarn-services_hadoop-yarn-services-core.txt [28K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/700/artifact/out/patch-unit-hadoop-tools_hadoop-sls.txt [12K] Powered by Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15254) Correct the wrong word spelling 'intialize'
fang zhenyi created HADOOP-15254: Summary: Correct the wrong word spelling 'intialize' Key: HADOOP-15254 URL: https://issues.apache.org/jira/browse/HADOOP-15254 Project: Hadoop Common Issue Type: Bug Reporter: fang zhenyi Assignee: fang zhenyi -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Re: [VOTE] Release Apache Hadoop 3.0.1 (RC0)
Hi, All Thank you so much for the votes so far! I will make a new RC1 in the next few days to include the latest fixes. Please wait and vote for the new RC1. Best regards, On Thu, Feb 22, 2018 at 1:17 PM, Ajay Kumarwrote: > +1 non-binding > > > > Build from source in CentOs7. > Deployed 4 node secure federated cluster (HDFS HA,Non-HA YARN) > Run TestDFSIO(write/read), pi and wordcount. > Verified basic hdfs command > > > > Thanks, > > Ajay > > > > On 2/20/18, 11:16 PM, "Vinayakumar B" wrote: > > > > +1 Binding, > > > > 1. Checked out code from tag. > > 2. Built and deployed a 3-node docker cluster in secure mode (HDFS HA, > > Non-HA YARN). Docker script available in [1], if anyone need, > > 3. Ran wordcount job successfully. > > 4. Verified basic webhdfs commands using curl. > > 5. Verified basic HDFS commands > > > > > > [1] https://github.com/vinayakumarb/docker-cluster-deployer > > > > Thanks, > > -Vinay > > > > On Wed, Feb 21, 2018 at 5:41 AM, Lei Xu wrote: > > > > > Dear PMC and committers > > > > > > Please help to verify and vote this release. I will extend the voting > > > period to Friday (Feb 23th) of this week. > > > > > > Thanks! > > > > > > On Thu, Feb 15, 2018 at 3:36 PM, Lei Xu wrote: > > > > Hi, all > > > > > > > > I've created release candidate 0 for Apache Hadoop 3.0.1 > > > > > > > > Apache Hadoop 3.0.1 will be the first bug fix release for Apache > > > > Hadoop 3.0 release. It includes 49 bug fixes, which include 10 > > > > blockers and 8 are critical. > > > > > > > > Please note: > > > > * HDFS-12990. Change default NameNode RPC port back to 8020. It > makes > > > > incompatible changes to Hadoop 3.0.0. After 3.0.1 releases, Apache > > > > Hadoop 3.0.0 will be deprecated due to this change. > > > > > > > > The release page is: > > > > > https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.0+Release > > > > > > > > New RC is available at: > http://home.apache.org/~lei/hadoop-3.0.1-RC0/ > > > > > > > > The git tag is release-3.0.1-RC0, and the latest commit is > > > > 494d075055b52b0cc922bc25237e231bb3771c90 > > > > > > > > The maven artifacts are available: > > > > > https://repository.apache.org/content/repositories/orgapachehadoop-1078/ > > > > > > > > Please try the release and vote; the vote will run for the usual 5 > > > > days, ending on 2/20/2017 6pm PST time. > > > > > > > > Thanks! > > > > > > > > -- > >> > Lei (Eddy) Xu > > > > > > > > > > > > -- > > > Lei (Eddy) Xu > > > Software Engineer, Cloudera > > > > > > - > > > To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org > > > For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org > > > > > > > > -- Lei (Eddy) Xu Software Engineer, Cloudera - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15253) Should update maxQueueSize when refresh call queue
Tao Jie created HADOOP-15253: Summary: Should update maxQueueSize when refresh call queue Key: HADOOP-15253 URL: https://issues.apache.org/jira/browse/HADOOP-15253 Project: Hadoop Common Issue Type: Improvement Reporter: Tao Jie Assignee: Tao Jie When calling {{dfsadmin -refreshCallQueue}} to update CallQueue instance, {{maxQueueSize}} should also be updated. In case of changing CallQueue instance to FairCallQueue, the length of each queue in FairCallQueue would be 1/priorityLevels of original length of DefaultCallQueue. So it would be helpful for us to set the length of callqueue to a proper value. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Re: [VOTE] Release Apache Hadoop 3.0.1 (RC0)
Hi Lei Xu, Thanks for driving this. +1 binding -Installed 3Node HA cluster -Verified basic shell commands -Ran word-count,pi jobs Regards Brahma Reddy Battula On Fri, Feb 16, 2018 at 5:06 AM, Lei Xuwrote: > Hi, all > > I've created release candidate 0 for Apache Hadoop 3.0.1 > > Apache Hadoop 3.0.1 will be the first bug fix release for Apache > Hadoop 3.0 release. It includes 49 bug fixes, which include 10 > blockers and 8 are critical. > > Please note: > * HDFS-12990. Change default NameNode RPC port back to 8020. It makes > incompatible changes to Hadoop 3.0.0. After 3.0.1 releases, Apache > Hadoop 3.0.0 will be deprecated due to this change. > > The release page is: > https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.0+Release > > New RC is available at: http://home.apache.org/~lei/hadoop-3.0.1-RC0/ > > The git tag is release-3.0.1-RC0, and the latest commit is > 494d075055b52b0cc922bc25237e231bb3771c90 > > The maven artifacts are available: > https://repository.apache.org/content/repositories/orgapachehadoop-1078/ > > Please try the release and vote; the vote will run for the usual 5 > days, ending on 2/20/2017 6pm PST time. > > Thanks! > > -- > Lei (Eddy) Xu > > - > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > -- --Brahma Reddy Battula
[DISCUSS] Apache Hadoop 2.7.6 Release Plan
Planning to do a maintenance 2.7.6 release with close to 40 changes since the last release. If there are no objections I'll start preparations. Please let me know if there are blockers: https://issues.apache.org/jira/browse/HDFS-12641?filter=12343253 Thanks, --Konstantin
Re: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk
Hi Sanjay, With respect to Ozone my two main concerns were: 1. Wether Ozone can help scaling out the namespace service in handling higher RPC workloads. I think we came to common conclusion that using Ozone as a block management layer is a reasonable path to scaling HDFS. The discussions are in-progress and probably will go on for a while. 2. Releasing Hadoop with components that don't have security. I was asking for a design doc at a minimum. I think the document Anu published addresses it. Thanks, Konstantin On Tue, Feb 20, 2018 at 3:06 PM, sanjay Radiawrote: > > > > Konstantine > > > Thanks for your feedback and comments over the last few months. Have we > addressed all your issues and concerns? > > sanjay > > > > On Feb 13, 2018, at 6:28 PM, sanjay Radia wrote: > > > > Sorry the formatting got messed by my email client. Here it is again > > > > > > Dear > > Hadoop Community Members, > > > > We had multiple community discussions, a few meetings in smaller groups > and also jira discussions with respect to this thread. We express our > gratitude for participation and valuable comments. > > > > The key questions raised were following > > 1) How the new block storage layer and OzoneFS benefit HDFS and we were > asked to chalk out a roadmap towards the goal of a scalable namenode > working with the new storage layer > > 2) We were asked to provide a security design > > 3)There were questions around stability given ozone brings in a large > body of code. > > 4) Why can’t they be separate projects forever or merged in when > production ready? > > > > We have responded to all the above questions with detailed explanations > and answers on the jira as well as in the discussions. We believe that > should sufficiently address community’s concerns. > > > > Please see the summary below: > > > > 1) The new code base benefits HDFS scaling and a roadmap has been > provided. > > > > Summary: > > - New block storage layer addresses the scalability of the block layer. > We have shown how existing NN can be connected to the new block layer and > its benefits. We have shown 2 milestones, 1st milestone is much simpler > than 2nd milestone while giving almost the same scaling benefits. > Originally we had proposed simply milestone 2 and the community felt that > removing the FSN/BM lock was was a fair amount of work and a simpler > solution would be useful > > - We provide a new K-V namespace called Ozone FS with > FileSystem/FileContext plugins to allow the users to use the new system. > BTW Hive and Spark work very well on KV-namespaces on the cloud. This will > facilitate stabilizing the new block layer. > > - The new block layer has a new netty based protocol engine in the > Datanode which, when stabilized, can be used by the old hdfs block layer. > See details below on sharing of code. > > > > > > 2) Stability impact on the existing HDFS code base and code separation. > The new block layer and the OzoneFS are in modules that are separate from > old HDFS code - currently there are no calls from HDFS into Ozone except > for DN starting the new block layer module if configured to do so. It does > not add instability (the instability argument has been raised many times). > Over time as we share code, we will ensure that the old HDFS continues to > remains stable. (for example we plan to stabilize the new netty based > protocol engine in the new block layer before sharing it with HDFS’s old > block layer) > > > > > > 3) In the short term and medium term, the new system and HDFS will be > used side-by-side by users. Side by-side usage in the short term for > testing and side-by-side in the medium term for actual production use till > the new system has feature parity with old HDFS. During this time, sharing > the DN daemon and admin functions between the two systems is operationally > important: > > - Sharing DN daemon to avoid additional operational daemon lifecycle > management > > - Common decommissioning of the daemon and DN: One place to decommission > for a node and its storage. > > - Replacing failed disks and internal balancing capacity across disks - > this needs to be done for both the current HDFS blocks and the new > block-layer blocks. > > - Balancer: we would like use the same balancer and provide a common way > to balance and common management of the bandwidth used for balancing > > - Security configuration setup - reuse existing set up for DNs rather > then a new one for an independent cluster. > > > > > > 4) Need to easily share the block layer code between the two systems > when used side-by-side. Areas where sharing code is desired over time: > > - Sharing new block layer’s new netty based protocol engine for old > HDFS DNs (a long time sore issue for HDFS block layer). > > - Shallow data copy from old system to new system is practical only if > within same project and daemon otherwise have to deal with security setting > and coordinations across
Re: [VOTE] Release Apache Hadoop 3.0.1 (RC0)
+1 non-binding 1. Build from source in CentOs7. 2. Deployed 4 node secure federated cluster (HDFS HA,Non-HA YARN) 3. Run TestDFSIO(write/read), pi and wordcount. 4. Verified basic hdfs command Thanks, Ajay On 2/20/18, 11:16 PM, "Vinayakumar B"wrote: +1 Binding, 1. Checked out code from tag. 2. Built and deployed a 3-node docker cluster in secure mode (HDFS HA, Non-HA YARN). Docker script available in [1], if anyone need, 3. Ran wordcount job successfully. 4. Verified basic webhdfs commands using curl. 5. Verified basic HDFS commands [1] https://github.com/vinayakumarb/docker-cluster-deployer Thanks, -Vinay On Wed, Feb 21, 2018 at 5:41 AM, Lei Xu wrote: > Dear PMC and committers > > Please help to verify and vote this release. I will extend the voting > period to Friday (Feb 23th) of this week. > > Thanks! > > On Thu, Feb 15, 2018 at 3:36 PM, Lei Xu wrote: > > Hi, all > > > > I've created release candidate 0 for Apache Hadoop 3.0.1 > > > > Apache Hadoop 3.0.1 will be the first bug fix release for Apache > > Hadoop 3.0 release. It includes 49 bug fixes, which include 10 > > blockers and 8 are critical. > > > > Please note: > > * HDFS-12990. Change default NameNode RPC port back to 8020. It makes > > incompatible changes to Hadoop 3.0.0. After 3.0.1 releases, Apache > > Hadoop 3.0.0 will be deprecated due to this change. > > > > The release page is: > > https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.0+Release > > > > New RC is available at: http://home.apache.org/~lei/hadoop-3.0.1-RC0/ > > > > The git tag is release-3.0.1-RC0, and the latest commit is > > 494d075055b52b0cc922bc25237e231bb3771c90 > > > > The maven artifacts are available: > > https://repository.apache.org/content/repositories/orgapachehadoop-1078/ > > > > Please try the release and vote; the vote will run for the usual 5 > > days, ending on 2/20/2017 6pm PST time. > > > > Thanks! > > > > -- > > Lei (Eddy) Xu > > > > -- > Lei (Eddy) Xu > Software Engineer, Cloudera > > - > To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org > >
Re: What's the difference between branch-3 and branch-3.0?
branch-3 has reappeared. Filed INFRA-16086 [1]. -C [1]: https://issues.apache.org/jira/browse/INFRA-16086 On Wed, Jan 17, 2018 at 12:32 PM, Jason Lowewrote: > I filed INFRA-15859 to have branch-3 deleted. > > Jason > > On Wed, Jan 17, 2018 at 1:23 PM, Eric Payne < > eric.payne1...@yahoo.com.invalid> wrote: > >> +1 for removing the branch-3 branch. It should be done soon so more >> confusion can be avoided. Thanks Jason for tracking this down. >> -Eric >> >> >> From: Jason Lowe >> To: Hadoop Common ; ma...@cloudera.com >> Sent: Wednesday, January 17, 2018 12:42 PM >> Subject: Re: What's the difference between branch-3 and branch-3.0? >> >> This was created accidentally when HDFS-11847 was committed. As such we >> should delete the branch-3 branch and port over the commits that went into >> branch-3 instead of branch-3.0. For the former, I'm assuming that requires >> an INFRA ticket since I would hope any committer would not have the ability >> to destroy a branch-* branch. Unfortunately even after it's deleted I >> suspect we will see it reappear if someone pushes up their old copy of >> branch-3 again, so committers will need to be vigilant. >> >> I'll work on porting the missing changes below from branch-3 over to >> branch-3.0. I'll wait for some more consensus on the branch-3 deletion >> before filing the INFRA ticket since deleting a branch shouldn't be done >> lightly. >> >> Jason >> >> >> commit 0802d8afa355d9a0683fdb2e9c4963e8fea8644f >> Author: Vinayakumar B >> Date: Wed Jan 17 14:16:48 2018 +0530 >> >> HDFS-9049. Make Datanode Netty reverse proxy port to be configurable. >> Contributed by Vinayakumar B. >> >> (cherry picked from commit 09efdfe9e13c9695867ce4034aa6ec970c2032f1) >> >> commit db8345fa9cd124728d935f725525e2626438b4c1 >> Author: Lei Xu >> Date: Tue Jan 16 15:15:11 2018 -0800 >> >> HDFS-13004. TestLeaseRecoveryStriped.testLeaseRecovery is failing when >> safeLength is 0MB or larger than the test file. (Zsolt Venczel via lei) >> >> (cherry picked from commit 3bd9ea63df769345a9d02a404cfb61323a4cd7e3) >> >> commit 82741091a78d7ce62c240ec3e7f81a3a9a3fee36 >> Author: Inigo Goiri >> Date: Mon Jan 15 12:21:24 2018 -0800 >> >> HDFS-12919. RBF: Support erasure coding methods in RouterRpcServer. >> Contributed by Inigo Goiri. >> >> commit d3fbcd92fe53192a319683b9ac72179cb28bd978 >> Author: Yiqun Lin >> Date: Sat Jan 6 14:31:08 2018 +0800 >> >> HDFS-11848. Enhance dfsadmin listOpenFiles command to list files under >> a given path. Contributed by Yiqun Lin. >> >> commit ee44783515a55ab9fd368660c5cc2c2bc392132e >> Author: Manoj Govindassamy >> Date: Tue Jan 2 14:59:36 2018 -0800 >> >> HDFS-11847. Enhance dfsadmin listOpenFiles command to list files >> blocking datanode decommissioning. >> >> >> >> On Wed, Jan 17, 2018 at 10:53 AM, Brahma Reddy Battula >> wrote: >> >> > IMHO,we no need to have *branch-3* still trunk moves.Shall we remove as >> it >> > make confuses.?? >> > >> > >> > >> > >> > Brahma Reddy Battula >> > >> > On Wed, Jan 17, 2018 at 9:41 PM, Jason Lowe >> > wrote: >> > >> > > I recently noticed some committers posting commits to branch-3 and >> > marking >> > > the JIRA as fixed in 3.0.1. I thought branch-3.0 was tracking 3.0.x >> > > releases, including branch-3.0.1 as of now, so I am confused what >> > branch-3 >> > > is for. The versions in the poms between branch-3 and branch-3.0 both >> > say >> > > they are 3.0.1-SNAPSHOT. >> > > >> > > I recall we discussed _not_ creating branch-3 until it is necessary, >> and >> > it >> > > is only necessary for branch-3 to exist when trunk stop tracking 3.x >> > > releases (i.e.: when trunk moves to 4.0.0-SNAPSHOT). >> > > >> > > Jason >> > > >> > >> > >> > >> > -- >> > >> > >> > >> > --Brahma Reddy Battula >> > >> >> >> >> - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15252) Checkstyle version is not compatible with IDEA's checkstyle plugin
Andras Bokor created HADOOP-15252: - Summary: Checkstyle version is not compatible with IDEA's checkstyle plugin Key: HADOOP-15252 URL: https://issues.apache.org/jira/browse/HADOOP-15252 Project: Hadoop Common Issue Type: Improvement Reporter: Andras Bokor Assignee: Andras Bokor After upgrading to the latest IDEA the IDE throws error messages in every few minutes like {code:java} The Checkstyle rules file could not be parsed. SuppressionCommentFilter is not allowed as a child in Checker The file has been blacklisted for 60s.{code} This is caused by some backward incompatible changes in checkstyle source code: [http://checkstyle.sourceforge.net/releasenotes.html] * 8.1: Make SuppressionCommentFilter and SuppressWithNearbyCommentFilter children of TreeWalker. * 8.2: remove FileContentsHolder module as FileContents object is available for filters on TreeWalker in TreeWalkerAudit Event. IDEA uses checkstyle 8.8 We should upgrade our checkstyle version to be compatible with IDEA's checkstyle plugin. Also it's a good time to upgrade maven-checkstyle-plugin as well to brand new 3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/ [Feb 21, 2018 2:18:58 AM] (arp) HADOOP-12897. KerberosAuthenticator.authenticate to include URL on IO [Feb 21, 2018 3:16:30 AM] (aengineer) HDFS-13175. Add more information for checking argument in [Feb 21, 2018 8:46:45 AM] (sunilg) YARN-7223. Document GPU isolation feature. Contributed by Wangda Tan. [Feb 21, 2018 9:05:57 AM] (sunilg) YARN-7947. Capacity Scheduler intra-queue preemption can NPE for [Feb 21, 2018 10:40:42 AM] (stevel) HADOOP-15247. Move commons-net up to 3.6. Contributed by Steve Loughran. [Feb 21, 2018 7:42:51 PM] (yufei) YARN-5028. RMStateStore should trim down app state for completed [Feb 21, 2018 7:57:14 PM] (mackrorysd) HADOOP-6852. apparent bug in concatenated-bzip2 support (decoding). [Feb 21, 2018 10:54:02 PM] (jlowe) YARN-7916. Remove call to docker logs on failure in container-executor. -1 overall The following subsystems voted -1: findbugs unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: FindBugs : module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api org.apache.hadoop.yarn.api.records.Resource.getResources() may expose internal representation by returning Resource.resources At Resource.java:by returning Resource.resources At Resource.java:[line 234] Failed junit tests : hadoop.crypto.key.kms.server.TestKMS hadoop.hdfs.TestDFSStripedOutputStreamWithFailure hadoop.hdfs.server.balancer.TestBalancer hadoop.hdfs.server.federation.router.TestRouterSafemode hadoop.hdfs.TestDFSStripedOutputStreamWithFailure030 hadoop.hdfs.server.datanode.TestDirectoryScanner hadoop.hdfs.web.TestWebHdfsTimeouts hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting hadoop.hdfs.TestErasureCodingPolicies hadoop.hdfs.TestDecommission hadoop.fs.http.client.TestHttpFSFileSystemLocalFileSystem hadoop.fs.http.server.TestHttpFSServerWebServer hadoop.hdfs.nfs.nfs3.TestExportsTable hadoop.yarn.server.nodemanager.webapp.TestContainerLogsPage hadoop.yarn.applications.distributedshell.TestDistributedShell cc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/diff-compile-cc-root.txt [4.0K] javac: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/diff-compile-javac-root.txt [280K] checkstyle: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/diff-checkstyle-root.txt [17M] pylint: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/diff-patch-pylint.txt [24K] shellcheck: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/diff-patch-shellcheck.txt [20K] shelldocs: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/diff-patch-shelldocs.txt [12K] whitespace: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/whitespace-eol.txt [9.2M] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/whitespace-tabs.txt [288K] xml: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/xml.txt [4.0K] findbugs: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-warnings.html [8.0K] javadoc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/diff-javadoc-javadoc-root.txt [760K] unit: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/patch-unit-hadoop-common-project_hadoop-kms.txt [12K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt [396K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-httpfs.txt [28K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-nfs.txt [28K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt [48K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/699/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-applications_hadoop-yarn-applications-distributedshell.txt [12K]