[jira] [Created] (HDFS-12198) Document missing namenode metrics that added recently

2017-07-25 Thread Yiqun Lin (JIRA)
Yiqun Lin created HDFS-12198: Summary: Document missing namenode metrics that added recently Key: HDFS-12198 URL: https://issues.apache.org/jira/browse/HDFS-12198 Project: Hadoop HDFS Issue

Re: Pre-Commit build is failing

2017-07-25 Thread Sean Busbey
-dev@yetus to bcc, since I think this is a Hadoop issue and not a yetus issue. Please review/commit HADOOP-14686 (which I am providing as a volunteer/contributor on the Hadoop project). On Tue, Jul 25, 2017 at 7:54 PM, Allen Wittenauer wrote: > > Again: just

Re: Pre-Commit build is failing

2017-07-25 Thread Allen Wittenauer
Again: just grab the .gitignore file from trunk and update it in branch-2.7. It hasn't been touched (outside of one patch) in years. The existing jobs should then work. The rest of this stuff, yes, I know and yes it's intentional. The directory structure was inherited from

Re: Pre-Commit build is failing

2017-07-25 Thread suraj acharya
Hi, Seems like the issue was incorrect/unclean checkout. I made a few changes[1] to the directories the checkout happens to and it is now running. Of course, this build[2] will take some time to run, but at the moment, it is running maven install. I am not sure who sets up/ manages the jenkins

Re: Pre-Commit build is failing

2017-07-25 Thread suraj acharya
For anyone looking. I created another job here. [1]. Set it with debug to see the issue. The error is being seen here[2]. >From the looks of it, it looks like, the way the checkout is happening is not very clean. I will continue to look at it, but in case anyone wants to jump in. [1] :

Re: Pre-Commit build is failing

2017-07-25 Thread Konstantin Shvachko
Hi Yetus developers, We cannot build Hadoop branch-2.7 anymore. Here is a recent example of a failed build: https://builds.apache.org/job/PreCommit-HDFS-Build/20409/console It seems the build is failing because Yetus cannot apply the patch from the jira. ERROR: HDFS-11896 does not apply to

Re: Running HDFS from source broken since HDFS-11596

2017-07-25 Thread Andrew Wang
I looked into this more and filed HDFS-12197 with a possible solution. Thanks for the report, Lars! On Fri, Jul 21, 2017 at 12:51 AM, Lars Francke wrote: > Thanks John, that was helpful. I see that you're using the hadoop-dist > directory while the wiki points directly

[jira] [Created] (HDFS-12197) Do the HDFS dist stitching in hadoop-hdfs-project

2017-07-25 Thread Andrew Wang (JIRA)
Andrew Wang created HDFS-12197: -- Summary: Do the HDFS dist stitching in hadoop-hdfs-project Key: HDFS-12197 URL: https://issues.apache.org/jira/browse/HDFS-12197 Project: Hadoop HDFS Issue

[jira] [Resolved] (HDFS-12097) libhdfs++: add Clang build and tests to the CI system

2017-07-25 Thread Anatoli Shein (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-12097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anatoli Shein resolved HDFS-12097. -- Resolution: Fixed Fixed as part of HDFS-12026. > libhdfs++: add Clang build and tests to the

[jira] [Created] (HDFS-12196) Ozone: DeleteKey-2: Implement container recycling service to delete stale blocks at background

2017-07-25 Thread Weiwei Yang (JIRA)
Weiwei Yang created HDFS-12196: -- Summary: Ozone: DeleteKey-2: Implement container recycling service to delete stale blocks at background Key: HDFS-12196 URL: https://issues.apache.org/jira/browse/HDFS-12196

[jira] [Created] (HDFS-12195) Ozone: DeleteKey-1: KSM replies delete key request asynchronously

2017-07-25 Thread Weiwei Yang (JIRA)
Weiwei Yang created HDFS-12195: -- Summary: Ozone: DeleteKey-1: KSM replies delete key request asynchronously Key: HDFS-12195 URL: https://issues.apache.org/jira/browse/HDFS-12195 Project: Hadoop HDFS

[DISCUSS] Merge Storage Policy Satisfier (SPS) [HDFS-10285] feature branch to trunk

2017-07-25 Thread Gangumalla, Uma
Dear All, I would like to propose Storage Policy Satisfier(SPS) feature merge into trunk. We have been working on this feature from last several months. This feature received the contributions from different companies. All of the feature development happened smoothly and collaboratively in