[jira] [Created] (HDFS-8218) Move classes that used by ClientProtocol into hdfs-client

Haohui Mai created HDFS-8218: Summary: Move classes that used by ClientProtocol into hdfs-client Key: HDFS-8218 URL: https://issues.apache.org/jira/browse/HDFS-8218 Project: Hadoop HDFS Issue Typ

[jira] [Created] (HDFS-8217) During block recovery for truncate Log new Block Id in case of copy-on-truncate is true.

Vinayakumar B created HDFS-8217: --- Summary: During block recovery for truncate Log new Block Id in case of copy-on-truncate is true. Key: HDFS-8217 URL: https://issues.apache.org/jira/browse/HDFS-8217 Pr

Re: Set minimum version of Hadoop 3 to JDK 8

Suppose we configure maven-compiler-plugin with set to 1.7 but set to 1.8 in trunk. I believe this would have the effect of generating JDK 8 bytecode, but enforcing that our code sticks to JDK 7 compatibility at compile time. Does that still satisfy requirements for HADOOP-11858? I'd prefer to

[jira] [Resolved] (HDFS-8212) DistributedFileSystem.createErasureCodingZone should pass schema in FileSystemLinkResolver

[ https://issues.apache.org/jira/browse/HDFS-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang resolved HDFS-8212. - Resolution: Fixed Fix Version/s: HDFS-7285 Hadoop Flags: Reviewed > DistributedFileSystem.creat

[jira] [Resolved] (HDFS-8216) TestDFSStripedOutputStream should use BlockReaderTestUtil to create BlockReader

[ https://issues.apache.org/jira/browse/HDFS-8216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang resolved HDFS-8216. - Resolution: Fixed Hadoop Flags: Reviewed > TestDFSStripedOutputStream should use BlockReaderTestUtil

Re: Set minimum version of Hadoop 3 to JDK 8

A few options: * Only change the builds for master to use jdk8 * build with both jdk7 and jdk8 by copying jobs * build with both jdk7 and jdk8 using a jenkins matrix build Robert, if you'd like help with any of these please send me a ping off-list. On Tue, Apr 21, 2015 at 8:19 PM, Vinod Kumar Va

Re: Set minimum version of Hadoop 3 to JDK 8

We don't want JDK 8 only code going into branch-2 line. Moving Jenkins to 1.8 right-away will shield such code, how do we address that? Thanks, +Vinod On Apr 21, 2015, at 5:54 PM, Robert Kanter wrote: > Sure, I'll try to change the Jenkins builds to 1.8 first. > > On Tue, Apr 21, 2015 at 3:31

Re: Set minimum version of Hadoop 3 to JDK 8

Sure, I'll try to change the Jenkins builds to 1.8 first. On Tue, Apr 21, 2015 at 3:31 PM, Andrew Wang wrote: > Hey Robert, > > As a first step, could we try switching all our precommit and nightly > builds over to use 1.8? This is a prerequisite for HADOOP-11858, and safe > to do in any case si

[jira] [Resolved] (HDFS-8204) Balancer: 2 replicas ends in same node after running balance.

[ https://issues.apache.org/jira/browse/HDFS-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Walter Su resolved HDFS-8204. - Resolution: Duplicate > Balancer: 2 replicas ends in same node after running balance. > ---

[jira] [Created] (HDFS-8216) TestDFSStripedOutputStream should use BlockReaderTestUtil to create BlockReader

Tsz Wo Nicholas Sze created HDFS-8216: - Summary: TestDFSStripedOutputStream should use BlockReaderTestUtil to create BlockReader Key: HDFS-8216 URL: https://issues.apache.org/jira/browse/HDFS-8216

[jira] [Created] (HDFS-8215) Refactor NamenodeFsck#check method

Takanobu Asanuma created HDFS-8215: -- Summary: Refactor NamenodeFsck#check method Key: HDFS-8215 URL: https://issues.apache.org/jira/browse/HDFS-8215 Project: Hadoop HDFS Issue Type: Improvem

[jira] [Created] (HDFS-8214) Secondary NN Web UI shows wrong date for Last Checkpoint

Charles Lamb created HDFS-8214: -- Summary: Secondary NN Web UI shows wrong date for Last Checkpoint Key: HDFS-8214 URL: https://issues.apache.org/jira/browse/HDFS-8214 Project: Hadoop HDFS Issue

Re: [DISCUSS] Looking to a 2.8.0 release

Sure, I agree it's better to have clear guidelines and scheme. Let me fork this thread about that. Re 2.7.0, I just forgot about the naming initially though I was clear in the discussion/voting. I so had to end up calling it alpha outside of the release artifact naming. Thanks +Vinod On Apr

Re: [DISCUSS] Looking to a 2.8.0 release

Thanks for your comment Karthik. Here's my take. Feature based release is going to put us back into the same prolonged release cycle. That is why I am proposing that we look at 2-3 months time and get whatever is ready. If we don't have even a single feature in by then, clearly we can drop the

Re: [DISCUSS] Looking to a 2.8.0 release

I would also like to support Karthik's proposal on the release thread about version numbering. 2.7.0 being "alpha" is pretty confusing since all of the other 2.x releases since GA have been stable. I think users would prefer a version like "2.8.0-alpha1" instead, which is very clear and similar to

Re: Set minimum version of Hadoop 3 to JDK 8

Hey Robert, As a first step, could we try switching all our precommit and nightly builds over to use 1.8? This is a prerequisite for HADOOP-11858, and safe to do in any case since it'll still target 1.7. I'll note that HADOOP-10530 details the pain Steve went through switching us to JDK7. Might b

Re: Set minimum version of Hadoop 3 to JDK 8

+ yarn-dev, hdfs-dev, mapred-dev On Tue, Apr 21, 2015 at 3:14 PM, Robert Kanter wrote: > Hi all, > > Moving forward on some of the discussions on Hadoop 3, I've created > HADOOP-11858 to set the minimum version of Hadoop 3 to JDK 8. I just > wanted to let everyone know in case there's some reas

Re: [DISCUSS] Looking to a 2.8.0 release

The feature set here seems pretty long, even for 2 - 3 months. Can we come up with a minimum set of features (or a number of features) that justify a new minor release, and start stabilizing as soon as those are in? On Tue, Apr 21, 2015 at 2:39 PM, Vinod Kumar Vavilapalli wrote: > With 2.7.0 out

Re: committing HADOOP-11746 test-patch improvements

FYI, MAPREDUCE-6324 is the first JIRA to be tested with the new code in place if someone hasn’t seen the new output. On Apr 21, 2015, at 9:06 PM, Allen Wittenauer wrote: > > > Just a heads up that I’ll be committing this to trunk and branch-2 here > in a bit. I’ll watch it over the n

[DISCUSS] Looking to a 2.8.0 release

With 2.7.0 out of the way, and with more maintenance releases to stabilize it, I propose we start thinking about 2.8.0. Here's my first cut of the proposal, will update the Roadmap wiki. - Support *both* JDK7 and JDK8 runtimes: HADOOP-11090 - Compatibility tools to catch backwards, forwards comp

[jira] [Created] (HDFS-8213) DFSClient should not instantiate SpanReceiverHost

Billie Rinaldi created HDFS-8213: Summary: DFSClient should not instantiate SpanReceiverHost Key: HDFS-8213 URL: https://issues.apache.org/jira/browse/HDFS-8213 Project: Hadoop HDFS Issue Typ

[jira] [Created] (HDFS-8212) DistributedFileSystem.createErasureCodingZone should pass schema in FileSystemLinkResolver

Tsz Wo Nicholas Sze created HDFS-8212: - Summary: DistributedFileSystem.createErasureCodingZone should pass schema in FileSystemLinkResolver Key: HDFS-8212 URL: https://issues.apache.org/jira/browse/HDFS-8212

[jira] [Created] (HDFS-8210) Ozone: Implement storage container manager

Jitendra Nath Pandey created HDFS-8210: -- Summary: Ozone: Implement storage container manager Key: HDFS-8210 URL: https://issues.apache.org/jira/browse/HDFS-8210 Project: Hadoop HDFS Iss

[jira] [Created] (HDFS-8211) DataNode UUID is always null in the JMX counter

Anu Engineer created HDFS-8211: -- Summary: DataNode UUID is always null in the JMX counter Key: HDFS-8211 URL: https://issues.apache.org/jira/browse/HDFS-8211 Project: Hadoop HDFS Issue Type: Bug

Re: committing HADOOP-11746 test-patch improvements

Just a heads up that I’ll be committing this to trunk and branch-2 here in a bit. I’ll watch it over the next hour or two before heading off to bed. (I’m in London at the moment.) If there are any issues, revert and drop a note in HADOOP-11746 with any issues. Despite what will hope

[jira] [Created] (HDFS-8208) Namenode reports stale block locations during decommissioning

James Mulcahy created HDFS-8208: --- Summary: Namenode reports stale block locations during decommissioning Key: HDFS-8208 URL: https://issues.apache.org/jira/browse/HDFS-8208 Project: Hadoop HDFS

[jira] [Resolved] (HDFS-3108) [UI] Few Namenode links are not working

[ https://issues.apache.org/jira/browse/HDFS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved HDFS-3108. Resolution: Duplicate > [UI] Few Namenode links are not working > ---

[jira] [Created] (HDFS-8206) Fix the typos in hadoop-hdfs-httpfs

Brahma Reddy Battula created HDFS-8206: -- Summary: Fix the typos in hadoop-hdfs-httpfs Key: HDFS-8206 URL: https://issues.apache.org/jira/browse/HDFS-8206 Project: Hadoop HDFS Issue Type:

Build failed in Jenkins: Hadoop-Hdfs-trunk-Java8 #161

See Changes: [jianhe] YARN-3497. ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy. Contributed by Jason Lowe [rkanter] MAPREDUCE-6238. MR2 can't run local jobs with -libjars command options whic

Hadoop-Hdfs-trunk-Java8 - Build # 161 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/161/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 5188 lines...] [INFO] Executed tasks [INFO] [INFO]

Hadoop-Hdfs-trunk - Build # 2102 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2102/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 5188 lines...] [INFO] Executed tasks [INFO] [INFO] --- m

Build failed in Jenkins: Hadoop-Hdfs-trunk #2102

See Changes: [jianhe] YARN-3497. ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy. Contributed by Jason Lowe [rkanter] MAPREDUCE-6238. MR2 can't run local jobs with -libjars command options which is

[jira] [Created] (HDFS-8205) fs -count -q -t -v -h displays wrong information

Peter Shi created HDFS-8205: --- Summary: fs -count -q -t -v -h displays wrong information Key: HDFS-8205 URL: https://issues.apache.org/jira/browse/HDFS-8205 Project: Hadoop HDFS Issue Type: Bug

A replica waiting to be recovered does not provision read

One block has three replicas, I restart all DataNodes, so the three replicas all are RWR state, When one dfs client read the file , that throw IOException. The visible length of RWR state replica is -1, why is not BytesOnDisk? Thanks, LiuLei

[jira] [Created] (HDFS-8204) Balancer: 2 replicas ends in same node after running balance.

Walter Su created HDFS-8204: --- Summary: Balancer: 2 replicas ends in same node after running balance. Key: HDFS-8204 URL: https://issues.apache.org/jira/browse/HDFS-8204 Project: Hadoop HDFS Issue

[jira] [Created] (HDFS-8203) Erasure Coding: Seek and other Ops in DFSStripedInputStream.

Yi Liu created HDFS-8203: Summary: Erasure Coding: Seek and other Ops in DFSStripedInputStream. Key: HDFS-8203 URL: https://issues.apache.org/jira/browse/HDFS-8203 Project: Hadoop HDFS Issue Type: S