[ANNOUNCE] New Hadoop PMC member - Mukund Thakur

and welcome, Mukund ! -Vinayakumar B -- -Vinay

Re: [DISCUSS] Race condition in ProtobufRpcEngine2

Call.toString() was used only while sending the response, in the response processor thread. At this point, header would be already read and processed. So no chance of race conditions. This race condition was not introduced by the HADOOP-17046 ,

Re: [VOTE] Release Apache Hadoop 3.3.1 RC3

+1 (Binding) 1. Built from Tag. 2. Successful Native Build on Ubuntu 20.04 3. Verified Checksums 4. Deployed the docker cluster with 3 nodes 5. Ran sample MR Jobs -Vinay On Sat, Jun 12, 2021 at 6:40 PM Ayush Saxena wrote: > +1, > Built from Source. > Successful Native Build on Ubuntu 20.04 >

Re: [DISCUSS] Hadoop 3.3.1 release

Hi David, >> Still hoping for help here: >> https://issues.apache.org/jira/browse/HDFS-15790 I will raise a PR for the said solution soon (in a day or two). -Vinay On Thu, 11 Mar 2021 at 5:39 AM, David wrote: > Hello, > > Still hoping for help here: > >

Re: Wire compatibility between Hadoop 3.x client and 2.x server

iled jira https://issues.apache.org/jira/browse/HDFS-15660 for details > > > 2020年10月28日 17:08，Vinayakumar B 写道： > > Hi Wu,Jianliang, > Have you created the Jira for the issue you mentioned due to > getContentSummary? > > I might have a fix for this. Of-course it needs t

Re: Wire compatibility between Hadoop 3.x client and 2.x server

Hi Wu,Jianliang, Have you created the Jira for the issue you mentioned due to getContentSummary? I might have a fix for this. Of-course it needs to be applied both client and server side. Let me know. -Vinay On Wed, Oct 14, 2020 at 12:26 PM Wu,Jianliang(vip.com) < jianliang...@vipshop.com>

Re: Collect feedback for HDFS-15638

IIUC, hive renames are from hive’s staging directory during write to final destination within table. Why not set the default ACLs of staging directory to whatever expected, and then continue write remaining files. In this way even after rename you will have expected ACLs on the final files.

Re: [VOTE] Release Apache Hadoop 2.10.1 (RC0)

Apologies for delayed voting. +1 (Binding) 1. Verified the signature. Signatures are good. 2. Verified the sha512 checksum (I tried to use the sha512sum tool to verify. But ".sha512" files doesn't have the expected format. I guess these files are regenerated using "gpg --print-md",

[ANNOUNCE] New Apache Hadoop PMC member : Ayush Saxena

Hi all, I am very glad to announce that Ayush Saxena was voted to join Apache Hadoop PMC. Congratulations Ayush! Well deserved and thank you for your dedication to the project. Please keep up the good work. Thanks, -Vinay

Re: [VOTE] Release Apache Hadoop 3.3.0 - RC0

+1 (Binding) -Verified all checksums and Signatures. -Verified site, Release notes and Change logs + May be changelog and release notes could be grouped based on the project at second level for better look (this needs to be supported from yetus) -Tested in x86 local 3-node docker cluster. +

Re: [NOTICE] Removal of protobuf classes from Hadoop Token's public APIs' signature

rotocolPB/StorageContainerLocationProtocolClientSideTranslatorPB.java:[116,47] > > incompatible types: com.google.protobuf.ServiceException cannot be > > converted to org.apache.hadoop.thirdparty.protobuf.ServiceException > > 17:01:19 2020/04/16 00:01:19 INFO: [INFO] 2 errors > > > > > > There's anoth

Re: [DISCUSS] making Ozone a separate Apache project

+1 -Vinay On Thu, 14 May 2020, 12:20 pm Surendra Singh Lilhore, < surendralilh...@gmail.com> wrote: > +1 > > -Surendra > > > On Thu, 14 May, 2020, 9:30 am yisheng lien, wrote: > > > +1 > > > > Thank you Marton for the detailed description. > > > > > > Wanqiang Ji 於 2020年5月14日 週四 上午11:27 寫道： >

Re: [NOTICE] Removal of protobuf classes from Hadoop Token's public APIs' signature

ier. > > Other downstreamers that break with the relocated protobuf include: Ozone > and HBase. but neither of them use the removed Token API. > > > On Wed, Jan 8, 2020 at 4:40 AM Vinayakumar B > wrote: > >> Hi All, >> >>This mail

Re: [RESULT] [VOTE] Release Apache Hadoop Thirdparty 1.0.0 - RC1

Thanks brahma. So total 5 +1s (4 binding, 1 non-binding). Done with pushing bits. Should get mirrored in next 24 hours. -Vinay On Thu, Mar 19, 2020 at 12:55 AM Brahma Reddy Battula wrote: > > My late +1.. I missed this.. > > > On Thu, 19 Mar 2020 at 12:43 AM, Vinayak

[RESULT] [VOTE] Release Apache Hadoop Thirdparty 1.0.0 - RC1

trunk with hadoop-thirdparty 1.0.0 >> - Checked rat files and documents >> - Checked LICENSE and NOTICE files >> >> Thanks, >> Akira >> >> On Thu, Mar 12, 2020 at 5:26 AM Vinayakumar B >> wrote: >> >> > Hi folks, >> &g

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

Making ARM artifact optional, makes the release process simpler for RM and unblocks release process (if there is unavailability of ARM resources). Still there are possible options to collaborate with RM ( as brahma mentioned earlier) and provide ARM artifact may be before or after vote. If

[VOTE] Release Apache Hadoop Thirdparty 1.0.0 - RC1

Hi folks, Thanks to everyone's help on this release. I have re-created a release candidate (RC1) for Apache Hadoop Thirdparty 1.0.0. RC Release artifacts are available at : http://home.apache.org/~vinayakumarb/release/hadoop-thirdparty-1.0.0-RC1/ Maven artifacts are available in staging

Re: [VOTE] Release Apache Hadoop Thirdparty 1.0.0

checksums and tried building from source. > Everything seems to be working fine. > But I feel the concerns regarding licences are valid. > IMO we should fix them and include HADOOP-16895 too in the release > > -Ayush > > > On 29-Feb-2020, at 1:45 AM, Vinayakumar B > wrote

Re: [VOTE] Release Apache Hadoop Thirdparty 1.0.0

https://issues.apache.org/jira/browse/HADOOP-16895 jira created for handling LICENCE and NOTICEs PR also has been raised for a proposal. Please validate https://github.com/apache/hadoop-thirdparty/pull/6 -Vinay On Fri, Feb 28, 2020 at 11:48 PM Vinayakumar B wrote: > Thanks Elek for detai

Re: [VOTE] Release Apache Hadoop Thirdparty 1.0.0

> > ps: I am not experienced with licensing enough to judge which one of > these are blocking and I might be wrong. > > IMO, none of these should be blocking and can be handled before next release. Still if someone feels this should be fixed and RC should be cut again, I am open to it.

[VOTE] Release Apache Hadoop Thirdparty 1.0.0

Hi folks, Thanks to everyone's help on this release. I have created a release candidate (RC0) for Apache Hadoop Thirdparty 1.0.0. RC Release artifacts are available at : http://home.apache.org/~vinayakumarb/release/hadoop-thirdparty-1.0.0-RC0/ Maven artifacts are available in staging repo:

[DISCUSS] hadoop-thirdparty 1.0.0 release

Hi All, Since Hadoop-3.3.0 release is around the corner, its time to release hadoop-thirdparty's first ever release, without which hadoop-3.3.0 cannot proceed for release. Below are the tentative date for RC and release. Since there is no much activity in this repo (other than the opentracing

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

unification we can think > > parallel thread as Vinay mentioned). > > > > > > > > On Mon, 6 Jan 2020 at 6:21 PM, Vinayakumar B > > wrote: > > > >> Hi Sree, > >> > >>> apache/hadoop-thirdparty, How would it fit into ASF ? As an Incubating >

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

st course of action.I am looking at, no projects > > should ever had to shade any artifacts except as an absolute necessary > > alternative. > > > > > > Thank you./Sree > > > > > > > > On Saturday, January 4, 2020, 7:49:18 AM PST, Vinayakumar B < > > v

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

? Looking at HBase > as an example, it looks like everything that are known to break a lot after > an update get shaded into the hbase-thirdparty artifact: guava, netty, ... > etc. > Is it the purpose to isolate these naughty dependencies? > > On Wed, Oct 9, 2019 at 12:38 PM Vinayakumar B

Re: [DISCUSS] ARM/aarch64 support for Hadoop

, > > On Fri, Sep 6, 2019 at 6:11 AM Vinayakumar B > wrote: > >> Thanks @Anu >> >> I understand the concern. I took it in different manner. >> >> Anyway, since protobuf upgrade looks huge, and need everyone's eyes on >> changes as early as possible,

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

> > > https://lists.apache.org/thread.html/f12c589baabbc79c7fb2843422d4590bea982cd102e2bd9d21e9884b@%3Cdev.hbase.apache.org%3E > > > Thanks. > > Vinayakumar B 于2019年9月28日周六 上午1:28写道： > > > Please find replies inline. > > > > -Vinay > > > > On Fri

Re: Daily Builds Getting Aborted Due To Timeout

Thanks Ayush, I think possible other ways are improving the test runtime. 1. try "parallel-tests" profile if applicable on all modules whichever is okay with tests running in parallel. This may reduce the total unit tests runtime drastically. ex: I can see hadoop-hdfs-rbf takes around ~22 min.

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

llowed in HBase. May be people involved in HBase can add some points here. Thoughts? > > .. Owen > > On Fri, Sep 27, 2019 at 8:38 AM Vinayakumar B > wrote: > >> Hi All, >> >>I wanted to discuss about the separate repo for thirdparty dependencies >> which

[DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

ed with the proposal. -Thanks, Vinay On Fri, Sep 27, 2019 at 11:54 AM Vinod Kumar Vavilapalli wrote: > Moving the thread to the dev lists. > > Thanks > +Vinod > > > On Sep 23, 2019, at 11:43 PM, Vinayakumar B > wrote: > > > > Thanks Marto

Re: [NOTICE] Building trunk needs protoc 3.7.1

this only when there are changes related to shaded dependencies. -Vinay On Sun, 22 Sep 2019, 10:11 pm Steve Loughran, wrote: > > > On Sun, Sep 22, 2019 at 3:22 PM Vinayakumar B > wrote: > >>Protobuf provides Wire compatibility between releases.. but not >

Re: [NOTICE] Building trunk needs protoc 3.7.1

> On Sep 21, 2019, at 9:55 AM, Vinayakumar B > wrote: > > > > @Wangda Tan , > > Sorry for the confusion. HADOOP-13363 is umbrella jira to track multiple > > stages of protobuf upgrade in subtasks. (jar upgrade, Docker update, > plugin > > upgrade, sha

Re: [NOTICE] Building trunk needs protoc 3.7.1

Hi Vinay, > > > > A bit confused, I saw the HADOOP-13363 is still pending. Do we need to > > upgrade protobuf version to 3.7.1 NOW or once HADOOP-13363 is completed? > > > > Thanks, > > Wangda > > > > On Fri, Sep 20, 2019 at 8:11 AM Vinayakumar B >

Re: [DISCUSS] ARM/aarch64 support for Hadoop

t even without ARM, this is a > great idea. > > If you like we can get together during one of the HDFS meetups hosted by > Wei-chiu. > > Thanks > Anu > > > > On Thu, Sep 5, 2019 at 3:19 AM Vinayakumar B > wrote: > >> Hi all, >> >> Thanks fo

Re: [DISCUSS] ARM/aarch64 support for Hadoop

t;> separate >> >> >>> branch with it's own ARM CI seems a really good idea. >> >> >>> By doing this we won't break any of the undergoing development in >> >> trunk >> >> >> and >> >> >>> a CI can be a very

Re: [VOTE] Moving Submarine to a separate Apache project proposal

+1 Thanks for the proposal. Its very interesting project and looks very promising one by looking at the participations from various companies and the speed of development. I would also like to participate in the project. Please add me as well. Thanks, -Vinay On Tue, 3 Sep 2019, 12:38 pm Rakesh

[DISCUSS] ARM/aarch64 support for Hadoop

Hi Folks, ARM is becoming famous lately in its processing capability and has got the potential to run Bigdata workloads. Many users have been moving to ARM machines due to its low cost. In the past there were attempts to compile Hadoop on ARM (Rasberry PI) for experimental purposes. Today ARM

[ANNOUNCE] New Apache Hadoop Committer - Ayush Saxena

Congratulations & Welcome aboard Ayush! Vinayakumar B (On behalf of the Hadoop PMC)

Re: [VOTE]: Support for RBF data locality Solution

+1 for approach A. On Thu, 11 Apr 2019, 12:23 pm Akira Ajisaka, wrote: > The Approach A looks good to me. > > Thanks, > Akira > > On Thu, Apr 11, 2019 at 2:30 PM Xiaoqiao He wrote: > > > > Hi forks, > > > > The current implementation of RBF is not sensitive about data locality, > > since

Re: Including Original Author in git commits.

So.. if we started doing that already.. we can encourage contributors to attach formatted patch.. or create PRs. And update wiki to follow exact steps to contribute and commit. -Vinay On Thu, 14 Feb 2019, 4:54 pm Steve Loughran I've been trying to do that recently, though as it forces me to

Including Original Author in git commits.

Hi all, Right now we are committing with commitrer name as author and adding contributor name in commit message. This way of committing will not reflect in contributors git profile. I believe current way of crediting.. is based on SVN days.. Since now all apache repos are following git.. we can

Re: [VOTE] Release Apache Hadoop 3.1.2 - RC1

Sorry for being late. Thanks everyone for the Release efforts. +1 (Binding) -Built from tag on Ubuntu-18.04 -Successful Native build. -Deployed a 3-Node docker cluster with kerberos Security Enabled on Centos7 images. -Verified basic HDFS Commands -Ran basic wordcount Job. -Vinay On Wed, Feb

Re: [DISCUSS] Move to gitbox

+1 -Vinay On Mon, 10 Dec 2018, 1:22 pm Elek, Marton > Thanks Akira, > > +1 (non-binding) > > I think it's better to do it now at a planned date. > > If I understood well the only bigger task here is to update all the > jenkins jobs. (I am happy to help/contribute what I can do) > > > Marton > >

[jira] [Created] (HDFS-13983) TestOfflineImageViewer crashes in windows

Vinayakumar B created HDFS-13983: Summary: TestOfflineImageViewer crashes in windows Key: HDFS-13983 URL: https://issues.apache.org/jira/browse/HDFS-13983 Project: Hadoop HDFS Issue Type

Re: HADOOP-14163 proposal for new hadoop.apache.org

+1, New site looks great. Just one nit in README '--refresh' flag for hugo server no longer available. -Vinay On Mon, 3 Sep 2018, 10:21 am Shashikant Banerjee, wrote: > +1 > > Thanks > Shashi > > On 9/3/18, 9:23 AM, "Mukul Kumar Singh" wrote: > > +1, Thanks for working on this Marton. >

[jira] [Created] (HDFS-13816) dfs.getQuotaUsage() throws NPE on non-existent dir instead of FileNotFoundException

Vinayakumar B created HDFS-13816: Summary: dfs.getQuotaUsage() throws NPE on non-existent dir instead of FileNotFoundException Key: HDFS-13816 URL: https://issues.apache.org/jira/browse/HDFS-13816

Re: 回复：[VOTE] Merge Storage Policy Satisfier (SPS) [HDFS-10285] feature branch to trunk

+1 Great work guys. -Vinay On Tue, 7 Aug 2018, 7:20 pm Anu Engineer, wrote: > +1, Sorry for the late vote. Thanks for the perseverance and seeing this > thru. > > --Anu > > > On 8/7/18, 1:04 AM, "郑锴(铁杰)" wrote: > > +1 for the work to be in. Thanks Uma and folks for the hard taking! > >

Re: [VOTE] Adopt HDSL as a new Hadoop subproject

+1 for the subproject of HDSL Instead of maintaining directly as part of main repo itself, may be we can explore 'git submodules' -Vinay On 23 Mar 2018 11:47 am, "Takanobu Asanuma" wrote: +1 (non-binding). Thanks, -Takanobu Asanuma > All, > > Following our

Re: [DISCUSS] Merging HDFS-8707 (C++ HDFS client) to trunk

Definitely this would be great addition. Kudos to everyone's contributions. I am not a C++ expert. So cannot vote on code. ---A libhdfs/libhdfs3 compatible C API that allows libhdfs++ to serve as a drop-in replacement for clients that only need read support (until libhdfs++ also supports

Re: does it make sense to get remaining space by sum all the ones of the datanode

gt; for(DatanodeStorageInfo s : getStorageInfos()) { > if (s.getStorageType() == t) { > remaining += s.getRemaining(); > } > } > return remaining; > } > > > On Mon, Jan 29, 2018 at 6:12 PM, Vinayakumar B <vinayakum...@apache.org> > wrote: > >>

Re: does it make sense to get remaining space by sum all the ones of the datanode

in which version of Hadoop you are seeing this? -Vinay On 29 Jan 2018 3:26 pm, "Xie Gang" wrote: Hello, We recently hit a issue that almost all the disk of the datanode got full even we configured the du .reserved. After tracking down the code, found that when we choose

[jira] [Created] (HDFS-13027) Handle NPE due to deleted blocks in race condition

Vinayakumar B created HDFS-13027: Summary: Handle NPE due to deleted blocks in race condition Key: HDFS-13027 URL: https://issues.apache.org/jira/browse/HDFS-13027 Project: Hadoop HDFS Issue

[jira] [Created] (HDFS-13011) Support replacing multiple nodes during pipeline recovery and append

Vinayakumar B created HDFS-13011: Summary: Support replacing multiple nodes during pipeline recovery and append Key: HDFS-13011 URL: https://issues.apache.org/jira/browse/HDFS-13011 Project: Hadoop

Re: When permission is disabled, why setOwner() && setPermission() still check the permission?

Hi Brahma, Thanks for bringing this up. According to history of git, there is no historical reasons found for me. May be someone with branch-1 experience, can answer this ..? -Vinay On Tue, Aug 1, 2017 at 6:50 PM, Brahma Reddy Battula < brahmareddy.batt...@huawei.com> wrote: > Hi All > > why

[jira] [Created] (HDFS-12212) Options.Rename.To_TRASH is considered even when Options.Rename.NONE is specified

Vinayakumar B created HDFS-12212: Summary: Options.Rename.To_TRASH is considered even when Options.Rename.NONE is specified Key: HDFS-12212 URL: https://issues.apache.org/jira/browse/HDFS-12212

[jira] [Created] (HDFS-12157) Do fsyncDirectory(..) outside of FSDataset lock

Vinayakumar B created HDFS-12157: Summary: Do fsyncDirectory(..) outside of FSDataset lock Key: HDFS-12157 URL: https://issues.apache.org/jira/browse/HDFS-12157 Project: Hadoop HDFS Issue

[jira] [Created] (HDFS-12120) Use new block for pre-RollingUpgrade files` append requests

Vinayakumar B created HDFS-12120: Summary: Use new block for pre-RollingUpgrade files` append requests Key: HDFS-12120 URL: https://issues.apache.org/jira/browse/HDFS-12120 Project: Hadoop HDFS

[jira] [Created] (HDFS-11898) DFSClient#isHedgedReadsEnabled() should be per client flag

Vinayakumar B created HDFS-11898: Summary: DFSClient#isHedgedReadsEnabled() should be per client flag Key: HDFS-11898 URL: https://issues.apache.org/jira/browse/HDFS-11898 Project: Hadoop HDFS

Re: RollingUpgrade Rollback openfiles issue

age trash, up on append while in a RU. What do you think about truncate? Unlike append, it is utilizing the block recovery /commitBlockSynchronization facility. Then what about regular block recoveries? Kihwal ________ From: Vinayakumar B <vinayakumar...@huawei.c

RE: RollingUpgrade Rollback openfiles issue

considering these usecases. Any thoughts? -Vinay From: Kihwal Lee [mailto:kih...@yahoo-inc.com] Sent: 25 May 2017 22:16 To: Vinayakumar B <vinayakumar...@huawei.com>; hdfs-dev@hadoop.apache.org Subject: Re: RollingUpgrade Rollback openfiles issue Hi Vinay, If I rephrase the question, Does a RU ro

[jira] [Created] (HDFS-11889) Datanodes should skip reading replicas from cache during Rollback

Vinayakumar B created HDFS-11889: Summary: Datanodes should skip reading replicas from cache during Rollback Key: HDFS-11889 URL: https://issues.apache.org/jira/browse/HDFS-11889 Project: Hadoop HDFS

RollingUpgrade Rollback openfiles issue

Hi all, Have a doubt with expected behavior in case of RollingUpgrade and rollback. Scenario: 1. file was being written before rolling upgrade started and written some bytes, say X, with hsync(). 2. Rolling upgrade done and writer continued to write and added some more bytes and file closed

Need Help with review

Hi, Please help in reviewing below Jiras https://issues.apache.org/jira/browse/HDFS-5042 https://issues.apache.org/jira/browse/HDFS-11875 https://issues.apache.org/jira/browse/HDFS-11856 https://issues.apache.org/jira/browse/HDFS-11708 https://issues.apache.org/jira/browse/HDFS-11738

[jira] [Created] (HDFS-11875) Sort last block's locations for append

Vinayakumar B created HDFS-11875: Summary: Sort last block's locations for append Key: HDFS-11875 URL: https://issues.apache.org/jira/browse/HDFS-11875 Project: Hadoop HDFS Issue Type: Bug

[jira] [Created] (HDFS-11856) Ability to re-add Upgrading Nodes (remote) to pipeline for future pipeline updates

Vinayakumar B created HDFS-11856: Summary: Ability to re-add Upgrading Nodes (remote) to pipeline for future pipeline updates Key: HDFS-11856 URL: https://issues.apache.org/jira/browse/HDFS-11856

[jira] [Created] (HDFS-11710) hadoop-hdfs-native-client build fails in trunk after HDFS-11529

Vinayakumar B created HDFS-11710: Summary: hadoop-hdfs-native-client build fails in trunk after HDFS-11529 Key: HDFS-11710 URL: https://issues.apache.org/jira/browse/HDFS-11710 Project: Hadoop HDFS

[jira] [Created] (HDFS-11708) positional read will fail if replicas moved to different DNs after stream is opened

Vinayakumar B created HDFS-11708: Summary: positional read will fail if replicas moved to different DNs after stream is opened Key: HDFS-11708 URL: https://issues.apache.org/jira/browse/HDFS-11708

[jira] [Created] (HDFS-11674) reserveSpaceForReplicas is not released if append request failed due to mirror down and replica recovered

Vinayakumar B created HDFS-11674: Summary: reserveSpaceForReplicas is not released if append request failed due to mirror down and replica recovered Key: HDFS-11674 URL: https://issues.apache.org/jira/browse/HDFS

[jira] [Created] (HDFS-11621) Rename 'seq.io.sort.mb' and 'seq.io.sort.factor' with prefix 'io.seqfile'

Vinayakumar B created HDFS-11621: Summary: Rename 'seq.io.sort.mb' and 'seq.io.sort.factor' with prefix 'io.seqfile' Key: HDFS-11621 URL: https://issues.apache.org/jira/browse/HDFS-11621 Project

[jira] [Created] (HDFS-11224) Lifeline message should be ignored for dead nodes

Vinayakumar B created HDFS-11224: Summary: Lifeline message should be ignored for dead nodes Key: HDFS-11224 URL: https://issues.apache.org/jira/browse/HDFS-11224 Project: Hadoop HDFS Issue

[jira] [Created] (HDFS-11213) FilterFileSystem should override rename(.., options) to take effect of Rename options called via FilterFileSystem implementations

Vinayakumar B created HDFS-11213: Summary: FilterFileSystem should override rename(.., options) to take effect of Rename options called via FilterFileSystem implementations Key: HDFS-11213 URL: https

[jira] [Created] (HDFS-11212) FilterFileSystem should override rename(.., options) to take effect of Rename options called via FilterFileSystem implementations

Vinayakumar B created HDFS-11212: Summary: FilterFileSystem should override rename(.., options) to take effect of Rename options called via FilterFileSystem implementations Key: HDFS-11212 URL: https

[jira] [Created] (HDFS-11098) Datanode in tests cannot start in Windows after HDFS-10368

Vinayakumar B created HDFS-11098: Summary: Datanode in tests cannot start in Windows after HDFS-10368 Key: HDFS-11098 URL: https://issues.apache.org/jira/browse/HDFS-11098 Project: Hadoop HDFS

[jira] [Created] (HDFS-11067) DFS#listStatusIterator(..) should throw FileNotFoundException if the directory deleted before fetching next batch of entries

Vinayakumar B created HDFS-11067: Summary: DFS#listStatusIterator(..) should throw FileNotFoundException if the directory deleted before fetching next batch of entries Key: HDFS-11067 URL: https

[jira] [Created] (HDFS-10957) Retire BKJM from trunk

Vinayakumar B created HDFS-10957: Summary: Retire BKJM from trunk Key: HDFS-10957 URL: https://issues.apache.org/jira/browse/HDFS-10957 Project: Hadoop HDFS Issue Type: Task

[jira] [Created] (HDFS-10901) QJM should not consider stale/failed txn available in any one of JNs.

Vinayakumar B created HDFS-10901: Summary: QJM should not consider stale/failed txn available in any one of JNs. Key: HDFS-10901 URL: https://issues.apache.org/jira/browse/HDFS-10901 Project: Hadoop

[jira] [Created] (HDFS-10902) QJM should not consider stale/failed txn available in any one of JNs.

Vinayakumar B created HDFS-10902: Summary: QJM should not consider stale/failed txn available in any one of JNs. Key: HDFS-10902 URL: https://issues.apache.org/jira/browse/HDFS-10902 Project: Hadoop

[DISCUSS] Retire BKJM from trunk?

Hi All, BKJM was Active and made much stable when the NameNode HA was implemented and there was no QJM implemented. Now QJM is present and is much stable which is adopted by many production environment. I wonder whether it would be a good time to retire BKJM from trunk? Are there

RE: [VOTE] Release Apache Hadoop 2.7.3 RC0

+1 (binding) 1. Downloaded and Built from branch-2.7.3 2. Started up HDFS and YARN in Single Node cluster. 3. Ran WordCount job multiple times and Success. 4. Verified the "Release Notes" available at the URL mentioned by Vinod. Apart from that, Faced same issues as Andrew wang, while running

[jira] [Created] (HDFS-10570) Netty-all jar should be first in class path while running tests in eclipse

Vinayakumar B created HDFS-10570: Summary: Netty-all jar should be first in class path while running tests in eclipse Key: HDFS-10570 URL: https://issues.apache.org/jira/browse/HDFS-10570 Project

[jira] [Created] (HDFS-10384) MiniDFSCluster doesnt support multiple HTTPS server instances

Vinayakumar B created HDFS-10384: Summary: MiniDFSCluster doesnt support multiple HTTPS server instances Key: HDFS-10384 URL: https://issues.apache.org/jira/browse/HDFS-10384 Project: Hadoop HDFS

[jira] [Created] (HDFS-10274) Move NameSystem#isInStartupSafeMode() to BlockManagerSafeMode

Vinayakumar B created HDFS-10274: Summary: Move NameSystem#isInStartupSafeMode() to BlockManagerSafeMode Key: HDFS-10274 URL: https://issues.apache.org/jira/browse/HDFS-10274 Project: Hadoop HDFS

[jira] [Created] (HDFS-10273) Remove duplicate logSync() and log message in FSN#enterSafemode()

Vinayakumar B created HDFS-10273: Summary: Remove duplicate logSync() and log message in FSN#enterSafemode() Key: HDFS-10273 URL: https://issues.apache.org/jira/browse/HDFS-10273 Project: Hadoop HDFS

[jira] [Resolved] (HDFS-10252) Is DataNode aware of the name of the file that it is going to store?

[ https://issues.apache.org/jira/browse/HDFS-10252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B resolved HDFS-10252. -- Resolution: Invalid > Is DataNode aware of the name of the file that it is going to st

RE: Rise of the Dragon

I think, he cloned main HDFS-7285 jira. By default, "clone all subtasks" will be enabled. So in one shot all 206 subtasks also cloned, Creating huge mess in mails. Anyway I have deleted the cloned Jira, along with subtasks. -Vinay -Original Message- From: Zhe Zhang

[jira] [Created] (HDFS-9952) Expose FSNamesystem lock wait time as metrics

Vinayakumar B created HDFS-9952: --- Summary: Expose FSNamesystem lock wait time as metrics Key: HDFS-9952 URL: https://issues.apache.org/jira/browse/HDFS-9952 Project: Hadoop HDFS Issue Type

[jira] [Resolved] (HDFS-8578) On upgrade, Datanode should process all storage/data dirs in parallel

[ https://issues.apache.org/jira/browse/HDFS-8578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B resolved HDFS-8578. - Resolution: Fixed Fixed the compilation in branch-2.7 > On upgrade, Datanode should process

[jira] [Resolved] (HDFS-9783) DataNode deadlocks after running hdfs mover

[ https://issues.apache.org/jira/browse/HDFS-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B resolved HDFS-9783. - Resolution: Duplicate Resolving as duplicate. Feel free to re-open if fix in HDFS-9661 doesnt work

[jira] [Created] (HDFS-9776) Truncate block recovery will never happen if the Namenode goes down immediately after truncate

Vinayakumar B created HDFS-9776: --- Summary: Truncate block recovery will never happen if the Namenode goes down immediately after truncate Key: HDFS-9776 URL: https://issues.apache.org/jira/browse/HDFS-9776

[jira] [Created] (HDFS-9536) OOM errors during parallel upgrade to Block-ID based layout

Vinayakumar B created HDFS-9536: --- Summary: OOM errors during parallel upgrade to Block-ID based layout Key: HDFS-9536 URL: https://issues.apache.org/jira/browse/HDFS-9536 Project: Hadoop HDFS

[jira] [Resolved] (HDFS-9127) Re-replication for files with enough replicas in single rack

[ https://issues.apache.org/jira/browse/HDFS-9127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B resolved HDFS-9127. - Resolution: Invalid This problem doesnt exist on latest code. Feel free to re-open if found again

RE: [VOTE] Release Apache Hadoop 2.7.2 RC0

I think one recent critical issue HDFS-9413, getContentSummary() on standby should throw StandbyException, Found by Brahma, is a good candidate for 2.7.2 as well. -vinay On Nov 14, 2015 5:20 AM, "Naganarasimha G R (Naga)" < garlanaganarasi...@huawei.com> wrote: > Hi Vinod, > > Can you also look

[jira] [Created] (HDFS-9411) HDFS ZoneLabel support

Vinayakumar B created HDFS-9411: --- Summary: HDFS ZoneLabel support Key: HDFS-9411 URL: https://issues.apache.org/jira/browse/HDFS-9411 Project: Hadoop HDFS Issue Type: New Feature

RE: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk]

ext release vehicle. I > >>do plan to revive the 3.0 schedule some time next year. With EC and > >>JDK8 in a good spot, the only big feature remaining is classpath > >>isolation. > >> > >> EC is also a pretty fundamental change to HDFS. Even if it's >

Re: [VOTE] Release Apache Hadoop 2.6.2

+1 binding, 1. Built the tar from the git tag checkout 2. Verified the release notes both downloaded and built 3. Installed single node cluster and ran some jobs successfully 4. Verified documents, Found "svn" link instead of git in the header of document. This could be corrected either in next

Re: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk

or capturing the issue and Uma for offering the help. > > --- > Zhe Zhang > > On Mon, Oct 5, 2015 at 12:19 PM, Gangumalla, Uma <uma.ganguma...@intel.com > > > wrote: > > > Vinay, > > > > > > I would merge them as part of HDFS-9182. > > &g

Re: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk

> Subject: RE: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk > > > > > > +1 (non-binding) > > > I have been involved in the development and code review on the feature > > > branch. It's a great feature and I think it's ready to merge it into > > trunk

[jira] [Created] (HDFS-9139) Enable parallel JUnit tests for HDFS Pre-commit

Vinayakumar B created HDFS-9139: --- Summary: Enable parallel JUnit tests for HDFS Pre-commit Key: HDFS-9139 URL: https://issues.apache.org/jira/browse/HDFS-9139 Project: Hadoop HDFS Issue Type

Re: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk

luster testing, and have executed most tests in the plan. The most > > >basic functionalities have been extensively tested and verified in > > >several real clusters with different hardware configurations; results > > >have been very stable. We have created follow-on tasks for mor

[jira] [Created] (HDFS-9049) Make Datanode Netty reverse proxy port to be configurable

Vinayakumar B created HDFS-9049: --- Summary: Make Datanode Netty reverse proxy port to be configurable Key: HDFS-9049 URL: https://issues.apache.org/jira/browse/HDFS-9049 Project: Hadoop HDFS

  1   2   3   >