[jira] [Resolved] (HDFS-8221) HDFS have two Standby NNs because ActiveStandbyElectorLock ephemeralOwner in ZK is different with the sessionId stored in ZKFC

[ https://issues.apache.org/jira/browse/HDFS-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved HDFS-8221. Resolution: Duplicate > HDFS have two Standby NNs because ActiveStandbyElectorLock ep

[jira] [Created] (HDFS-8227) BlockCollection should return Block instead of BlockInfoContiguous in the interfaces

Haohui Mai created HDFS-8227: Summary: BlockCollection should return Block instead of BlockInfoContiguous in the interfaces Key: HDFS-8227 URL: https://issues.apache.org/jira/browse/HDFS-8227 Project: Had

[jira] [Created] (HDFS-8226) Non-HA rollback compatibility broken

J.Andreina created HDFS-8226: Summary: Non-HA rollback compatibility broken Key: HDFS-8226 URL: https://issues.apache.org/jira/browse/HDFS-8226 Project: Hadoop HDFS Issue Type: Bug Re

[jira] [Reopened] (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 reopened HDFS-8204: - > Balancer: 2 replicas ends in same node after running balance. > -

Re: [RESULT][VOTE] Release Apache Hadoop 2.7.0 RC0

It took a while for the artifact distribution to come around, I initially had trouble pushing them from home too. Anyways, I just updated the website too. Sending an announcement now.. Thanks, +Vinod On Apr 20, 2015, at 8:06 PM, Vinod Kumar Vavilapalli wrote: > With 22 +1s (7 binding), one +

Re: Set minimum version of Hadoop 3 to JDK 8

You're absolutely right Steve. We should get the jobs under control. At the very least, before we move to JDK 8 in Jenkins, we should get the Java8 nightly builds working. I didn't realize we had these, and I had thought all compiling and most test issues with JDK8 were already fixed based on wh

RE: IMPORTANT: testing patches for branches

Hi Allen, This sounds great. >> Naming a patch foo-HDFS-7285.00.patch should get tested on the HDFS-7285 >> branch. Does it happen locally in developer's machine when running test-patch.sh, or also mean something in Hadoop Jenkins building when a JIRA becoming patch available? Thanks. Regard

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

Approach (1) seems like a good way to handle stability concerns people might have. If we explicitly distinguish between current and stable (i.e., not set them both to the latest release). It would be nice to do a VOTE for calling a release stable. I would use approach (2) for compatibility concern

[jira] [Created] (HDFS-8225) EC client code should not print info log message

Tsz Wo Nicholas Sze created HDFS-8225: - Summary: EC client code should not print info log message Key: HDFS-8225 URL: https://issues.apache.org/jira/browse/HDFS-8225 Project: Hadoop HDFS

[jira] [Resolved] (HDFS-8156) Add/implement necessary APIs even we just have the system default schema

[ https://issues.apache.org/jira/browse/HDFS-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang resolved HDFS-8156. - Resolution: Fixed Hadoop Flags: Reviewed Thanks Kai for the contribution and Nicholas for the thoroug

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

Thanks for forking this Vinod, Linux used to do the odd/even minor versions for unstable/stable, but that went away when 2.6 lasted forever. With the 3.x and 4.x I think it's just always stable. The odd/even though was at least a convention everyone knew about. Stack can comment better than I abo

[DISCUSS] Release numbering for stable 2.8 and beyond

Forking the thread. In the previous 2.7.1 thread [1], there were enough yays to my proposal to wait for a bug-fix release or two before calling a 2.x release stable. There were some concerns about the naming. We have two options, taking 2.8 as an example (1) Release 2.8.0, call it as an alpha

Re: [DISCUSS] Looking to a 2.8.0 release

+dev lists. Forgot about that, sure. I added this and my initial list to the Roadmap wiki. Thank +Vinod On Apr 21, 2015, at 9:34 PM, Rohith Sharma K S wrote: > Dear Vinod > > Regarding the road map of Hadoop-2.8.0, Can basic Application priority > working model includes in next releas

Re: IMPORTANT: testing patches for branches

Oh, this is also in the release notes, but one can use a git reference # as well. :) (with kudos to OOM for the idea.) On Apr 22, 2015, at 8:57 PM, Allen Wittenauer wrote: > > More than likely. It probably needs more testing (esp under Jenkins). > > It should be noted that the code in test

Re: IMPORTANT: testing patches for branches

More than likely. It probably needs more testing (esp under Jenkins). It should be noted that the code in test-patch.sh has lots of problems with branch-0, minor, and micro releases. But for major releases, it seems to work well for me. :) On Apr 22, 2015, at 8:45 PM, Vinod Kumar Vavilapa

[jira] [Created] (HDFS-8224) Any IOException in DataTransfer#run() will run diskError thread even if it is not disk error

Rushabh S Shah created HDFS-8224: Summary: Any IOException in DataTransfer#run() will run diskError thread even if it is not disk error Key: HDFS-8224 URL: https://issues.apache.org/jira/browse/HDFS-8224

Re: IMPORTANT: testing patches for branches

Does this mean HADOOP-7435 is no longer needed / closeable as dup? Thanks +Vinod On Apr 22, 2015, at 12:34 PM, Allen Wittenauer wrote: > > Hey gang, > > Just so everyone is aware, if you are working on a patch for either a > feature branch or a major branch, if you name the patc

IMPORTANT: testing patches for branches

Hey gang, Just so everyone is aware, if you are working on a patch for either a feature branch or a major branch, if you name the patch with the branch name following the spec in HowToContribute (and a few other ways… test-patch tries to figure it out!), test-patch.sh *should*

Re: committing HADOOP-11746 test-patch improvements

I believe this is not a regression -- I've seen some tests failed miserably because the build artifacts are destroyed during the execution of the unit tests. ~Haohui On Wed, Apr 22, 2015 at 12:10 AM, Allen Wittenauer wrote: > > Some status: > > * So far, HADOOP-11627 was filed which is luckily a

Re: Non-HA rollback compatibility broken

Hello Andreina, Thank you for reporting this. Would you please go ahead and open a jira issue? We'll definitely need to do something to address this (either a code fix or a documentation update), so it would be good to track it in jira. Chris Nauroth Hortonworks http://hortonworks.com/ From

Re: committing HADOOP-11746 test-patch improvements

On Wed, Apr 22, 2015 at 2:10 AM, Allen Wittenauer wrote: > > > * There have been a few runs which seems to indicate that *something* is > destroying the artifact directory in the middle of runs…. which is very > very odd and something I hadn’t seen in any of my testing. In any case, I > clearly

[jira] [Resolved] (HDFS-8024) Erasure Coding: ECworker frame, basics, bootstraping and configuration

[ https://issues.apache.org/jira/browse/HDFS-8024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G resolved HDFS-8024. --- Resolution: Fixed Fix Version/s: HDFS-7285 Hadoop Flags: Reviewed > Erasure

[jira] [Created] (HDFS-8223) Should calculate checksum for parity blocks in DFSStripedOutputStream

Yi Liu created HDFS-8223: Summary: Should calculate checksum for parity blocks in DFSStripedOutputStream Key: HDFS-8223 URL: https://issues.apache.org/jira/browse/HDFS-8223 Project: Hadoop HDFS Issu

[jira] [Created] (HDFS-8222) Remove usage of "dfsadmin -upgradeProgress " from document which is no longer supported

J.Andreina created HDFS-8222: Summary: Remove usage of "dfsadmin -upgradeProgress " from document which is no longer supported Key: HDFS-8222 URL: https://issues.apache.org/jira/browse/HDFS-8222 Project

Non-HA rollback compatibility broken

Hi , In HA while performing rollback , we use “hdfs namenode �Crollback” which would prompt user for confirmation. ( Implemented as part of HDFS-5138) For Non-HA , as per doc if we perform rollback using “start-dfs.sh �Crollback” , then namenode startup hangs ( As it tries to start namenode i

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

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/162/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 5196 lines...] [INFO] --- maven-site-plugin:3.4:atta

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

See Changes: [arp] HDFS-8163. Using monotonicNow for block report scheduling causes test failures on recently restarted systems. (Arpit Agarwal) [Arun Suresh] HADOOP-11704. DelegationTokenAuthenticationFilter must pass ipaddre

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

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2103/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 5195 lines...] [INFO] --- maven-site-plugin:3.4:attach-de

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

See Changes: [arp] HDFS-8163. Using monotonicNow for block report scheduling causes test failures on recently restarted systems. (Arpit Agarwal) [Arun Suresh] HADOOP-11704. DelegationTokenAuthenticationFilter must pass ipaddress in

Re: Set minimum version of Hadoop 3 to JDK 8

> On 21 Apr 2015, at 23:31, 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 since it'll still target 1.7. +1 we have jenkin builds runni

[jira] [Created] (HDFS-8221) HDFS have two Standby NNs because ActiveStandbyElectorLock ephemeralOwner in ZK is different with the sessionId stored in ZKFC

shenxingfeng created HDFS-8221: -- Summary: HDFS have two Standby NNs because ActiveStandbyElectorLock ephemeralOwner in ZK is different with the sessionId stored in ZKFC Key: HDFS-8221 URL: https://issues.apache.org/

[jira] [Created] (HDFS-8220) Erasure Coding: StripedDataStreamer fails to handle the blocklocations which doesn't satisfy BlockGroupSize

Rakesh R created HDFS-8220: -- Summary: Erasure Coding: StripedDataStreamer fails to handle the blocklocations which doesn't satisfy BlockGroupSize Key: HDFS-8220 URL: https://issues.apache.org/jira/browse/HDFS-8220

[jira] [Created] (HDFS-8219) setStoragePolicy with folder behavior is different after cluster restart

Peter Shi created HDFS-8219: --- Summary: setStoragePolicy with folder behavior is different after cluster restart Key: HDFS-8219 URL: https://issues.apache.org/jira/browse/HDFS-8219 Project: Hadoop HDFS

Re: committing HADOOP-11746 test-patch improvements

Err, first jira mentioned should be HADOOP-11861. On Apr 22, 2015, at 8:10 AM, Allen Wittenauer wrote: > > Some status: > > * So far, HADOOP-11627 was filed which is luckily an extremely easy bug to > fix. > > * There have been a few runs which seems to indicate that *something* is > destr

Re: committing HADOOP-11746 test-patch improvements

Some status: * So far, HADOOP-11627 was filed which is luckily an extremely easy bug to fix. * There have been a few runs which seems to indicate that *something* is destroying the artifact directory in the middle of runs…. which is very very odd and something I hadn’t seen in any of my testi