Re: [VOTE] Hadoop-1.1.0 release candidate 5

+1 (non-binding) Downloaded and installed from tar file and ran dfsio read/write tests on a single-node cluster. Tests ran successfully. Thanks, Arpit On Fri, Oct 5, 2012 at 2:31 PM, Matt Foley wrote: > Here at long last is a votable release candidate for Hadoop 1.1.0. > Please download and te

Re: [Vote] Merge branch-trunk-win to trunk

gt; > >>For details of the testing done, please see the thread - > >>http://bit.ly/WpavJ4. Merge patch for this is available on HADOOP-8562< > >>https://issues.apache.org/jira/browse/HADOOP-8562>. > >> > >>This was a large undertaking that involved

Re: Buiding Hadoop code from source

Vikas, are you trying to build trunk? You will need Maven 3.0. I recommend checking out the source tree and reading BUILDING.txt which has detailed instructions, including how to build jar packages. --Arpit On Fri, Mar 1, 2013 at 9:49 AM, Vikas Jadhav wrote: > thank you all > Working on ubuntu

Re: Heads up - 2.0.5-beta

On Thu, Apr 25, 2013 at 6:36 PM, Suresh Srinivas wrote: > Thanks for starting this discussion. I volunteer to do a final review of > protocol changes, so we can avoid incompatible changes to API and wire > protocol post 2.0.5 in Common and HDFS. > > We have been working really hard on the followi

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

+1 (non-binding) On Wed, May 22, 2013 at 10:04 AM, Roman Shaposhnik wrote: > +1 (non-binding) > > On Wed, May 22, 2013 at 10:00 AM, Chris Nauroth > wrote: > > +1 (non-binding) > > > > Chris Nauroth > > Hortonworks > > http://hortonworks.com/ > > > > > > > > On Wed, May 22, 2013 at 7:58 AM, Tom

Re: Error in protobuf definitions

Ralph, could you please file a Jira? We'll fix it. -Arpit On Wed, May 29, 2013 at 9:39 AM, Ralph Castain wrote: > Hi folks > > On line 228 of > hadoop-hdfs-project/hadoop-hdfs/src/main/proto/NamenodeProtocol.proto, > someone named a function using a reserved name: > > /** >* Request to re

Re: [DISCUSS] which release lines should we still consider actively maintained?

+1 to EOL 3.1.x at least. > On May 23, 2021, at 9:51 PM, Wei-Chiu Chuang > wrote: > > Sean, > > For reasons I don't understand, I never received emails from your new > address in the mailing list. Only Akira's response. > > I was just able to start a thread like this. > > I am +1 to EOL 3.1

Re: [DISCUSS] Migrate hadoop from log4j1 to log4j2

Hi Duo, Thank you for starting this discussion. Log4j1.2 bridge seems like a practical short-term solution. However the bridge will silently affect applications that add appenders or filters. NameNode audit logger and metrics come to mind. There may be others. Thanks, Arpit > On Jan 20, 2022

Re: Github integration for Hadoop

+1, thanks for proposing it. On 10/29/15, 10:47 AM, "Owen O'Malley" wrote: >All, > For code & patch review, many of the newer projects are using the Github >pull request integration. You can read about it here: > >https://blogs.apache.org/infra/entry/improved_integration_between_apache_and

Re: Github integration for Hadoop

On 10/29/15, 3:48 PM, "Andrew Wang" wrote: > If we pushed for it, I think it could happen. Gerrit support is a complete unknown. The community response to date supports Github integration. Github will appeal to new contributors as their Github profiles will reflect their work. I'd be interes

Re: Github integration for Hadoop

On 10/29/15, 5:14 PM, "Andrew Wang" wrote: >On Thu, Oct 29, 2015 at 4:58 PM, Arpit Agarwal >wrote: > >> On 10/29/15, 3:48 PM, "Andrew Wang" wrote: >> >> >> > If we pushed for it, I think it could happen. >> >> Gerrit suppo

Re: [VOTE] Release Apache Hadoop 2.6.3 RC0

+1 (binding) - Verified signatures for source and binary distributions - Built jars from source with java 1.7.0_79 - Deployed single-node pseudo-cluster - Ran example map reduce jobs - Ran hdfs admin commands, verified NN web UI shows expected usages On 12/11/15, 4:16 PM, "Junping Du" wrote:

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

Thanks for putting together this release Vinod. +1 (binding) - Verified signatures - Started pseudo-cluster with binary distribution, verified git commit ID - Built sources, deployed pseudo-cluster and ran example map reduce jobs, DistributedShell, HDFS commands. PS: Extra file hadoop-2.7.2

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

+1 (binding) - verified signatures - Installed pseudo-cluster from binary distribution and ran example MapReduce jobs - Built from sources and reran tests on pseudo-cluster On 1/14/16, 8:57 PM, "Vinod Kumar Vavilapalli" wrote: >Hi all, > >I've created an updated release candidate RC2 for Ap

'Target Version' field missing in Jira

Is it just me or has the Target Version/s field gone missing from Apache Hadoop Jira? I don't recall any recent discussion about it.

Re: [VOTE] Release Apache Hadoop 2.1.0-beta

Hi Arun, Would it make sense to generate Windows binaries since this is the first 2.0 release with Windows support? I am happy to help out with that. FWIW I generated a Windows tarball from the source, brought up a pseudo-distributed cluster, ran some smoke tests and it is looking good! Thanks,

Re: help needed to test a patch for Java7 on OSX

Patch built fine for me on Windows Server 2008 + JDK7. On Wed, Sep 11, 2013 at 1:51 AM, Steve Loughran wrote: > There's now a patch (and instructions of a manual stage) to get hadoop to > build on java7 on OSX > > before I commit it, I need to make sure it doesn't break on any other > platforms.

Re: Need help for building haddop source on windows 7

Hi Ranjan, I just noticed this thread. Please use 'trunk' or 'branch-2' to build Hadoop 2.0 on Windows. Instructions are in BUILDING.txt. Let us know if you get stuck on any step. Arpit On Tue, Sep 10, 2013 at 8:23 AM, Vinayakumar B wrote: > Hi.. > As Kai told you can build trunk or branch 2.1

Re: windows support in trunk?

Andrey, thanks for testing your patch on Windows. cygwin is no longer required. Instead, please install the free Windows SDK and build from an SDK command prompt. This is documented in BUILDING.txt. Please feel free to email the dev list if you get stuck at any step. On Tue, Sep 24, 2013 at 10:3

Re: windows support in trunk?

nd managed to do step #1. Then I succeed with > steps 2-4 and started all daemons using *cmd scripts. The only issue I have > is with the jobhistory daemon, as there's no mr-jobhistory-daemon.cmd > script. Is there an alternative way to start it? > > > > On Wed, Sep 25, 2013

Re: [VOTE] Release Apache Hadoop 2.2.0

+1 (non-binding) - Verified md5/SHA checksums - Installed binary distribution on Centos 6.4 - Ran a few MapReduce jobs on a single-node cluster - Copied files to/from the cluster using HDFS commands No issues encountered. On Mon, Oct 7, 2013 at 12:00 AM, Arun C Murthy wrote: > Folks, > > I've

Re: Need help for building haddop source on windows7

Ranjan, it looks like the release version in a pom.xml was edited. You might want to try again with a clean source tree. On Sun, Oct 27, 2013 at 9:07 PM, Ranjan Dutta wrote: > Hi, > > I was trying to build the latest Hadoop code taken from trunk in Windows 7 > and end up with following build err

Re: Need help for building haddop source on windows7

en using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please re > d the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyRes > lutionException &g

[VOTE] Merge HDFS-2832 Heterogeneous Storage Phase 1 to trunk

Hello all, I would like to call a vote to merge phase 1 of the Heterogeneous Storage feature into trunk. *Scope of the changes:* The changes allow exposing the DataNode as a collection of storages and set the foundation for subsequent work to present Heterogeneous Storages to applications. This a

Re: [VOTE] Merge HDFS-2832 Heterogeneous Storage Phase 1 to trunk

o get clarification on. > > Thanks, > Andrew > > > On Wed, Dec 4, 2013 at 7:21 AM, Sirianni, Eric >wrote: > > > +1 > > > > My team has been developing and testing against the HDFS-2832 branch for > > the past month. It has proven to be quite stable. &

Re: [VOTE] Merge HDFS-2832 Heterogeneous Storage Phase 1 to trunk

: > Thanks for clarifying that Arpit. I'm a +0.9 since I haven't reviewed > enough to +1, but everything thus far looks great. > > Andrew > > > On Fri, Dec 6, 2013 at 5:35 PM, Chen He wrote: > > > +1 nice feature for HDFS > > > > > > On Fri, Dec

Re: Improved HDFS Web UI

Hi Robert, My fault, the target version should have been 2.3. I am not sure if branch-2.3 is still taking improvements. If yes I will merge this to branch-2.3 and set the fix version to be 2.3, else the fix version will be 2.4. Arpit On Fri, Dec 20, 2013 at 1:11 PM, Robert Rati wrote: > Did

Re: Next releases

We plan to merge HDFS-2832 to branch-2 next week for inclusion in 2.4. On Fri, Dec 6, 2013 at 1:53 PM, Arun C Murthy wrote: > Thanks Suresh & Colin. > > Please update the Roadmap wiki with your proposals. > > As always, we will try our best to get these in - but we can collectively > decide to

Re: Edit permissions for my Hadoop wiki account

Could some kind admin do the same for my account too? My Hadoop wiki username is ArpitAgarwal Thanks! On Fri, Jan 3, 2014 at 4:54 PM, Andrew Wang wrote: > Hi all, > > Could someone give my wiki account edit permissions? Username is > "AndrewWang". > > Thanks, > Andrew > -- CONFIDENTIALITY NO

Re: Edit permissions for my Hadoop wiki account

Thanks Eli. On Fri, Jan 3, 2014 at 5:01 PM, Eli Collins wrote: > Added you both. > > On Fri, Jan 3, 2014 at 4:58 PM, Arpit Agarwal > wrote: > > Could some kind admin do the same for my account too? > > > > My Hadoop wiki username is ArpitAgarwal > > > &g

Re: Next releases

This merge to branch-2 is complete. The changes have been merged to branch-2 and target version set to 2.4.0 (r1556076). On Fri, Jan 3, 2014 at 4:13 PM, Arpit Agarwal wrote: > We plan to merge HDFS-2832 to branch-2 next week for inclusion in 2.4. > > > > On Fri, Dec 6, 2013 at

Re: Maintaining documentations

I will review HADOOP-10086this week unless another committer gets to it first. Akira, could you please resend a list of your patches that need reviewing if you have it handy. Thanks for your efforts to clean up the documentation. Unfortunately

Re: Maintaining documentations

>> documentation >> > fixes, so thanks for bringing these to our attention. >> >> I will do what I can do to improve this. Such as helping review process. >> >> >> Regards, >> Masatake Iwasaki >> >> >> (2014/01/22 3:22), Arpit Agarwa

Re: Maintaining documentations

ot ready. I need to add the new metrics for the latest trunk. > I'll create a new patch in this week. > > In addition, could you please review HADOOP-9830? > This issue is to fix a typo at the top page and I think it's easy to > review. > > Akira > > > (20

Re: Re-swizzle 2.3

IMO HADOOP-10273 (Fix 'mvn site') should be included in 2.3. I will merge it to branch-2.3 tomorrow PST if no one disagrees. On Tue, Feb 4, 2014 at 5:03 PM, Alejandro Abdelnur wrote: > IMO YARN-1577 is a blocker, it is breaking unmanaged AMs in a very odd ways > (to the point it seems un-determ

Re: Re-swizzle 2.3

Merged HADOOP-10273 to branch-2.3 as r1565456. On Wed, Feb 5, 2014 at 4:49 PM, Arpit Agarwal wrote: > IMO HADOOP-10273 (Fix 'mvn site') should be included in 2.3. > > I will merge it to branch-2.3 tomorrow PST if no one disagrees. > > > On Tue, Feb 4, 2014 at 5:03

Re: Wiki Editing

+common-dev, bcc user Hi Steve, *I'm wondering if someone wouldn't mind adding my user to the list so I can > add my (small) contribution to the project.* > A wiki admin should be able to do this for you (a few of them are on this mailing list). Feel free to send a reminder to the list if no o

Re: Best Linux version for hadoop development

Can you please file a Jira and post the logs/stack traces? I cannot repro any of those test failures on either trunk or branch-2.4 (on Centos 6.5). Don't have an Ubuntu installation to verify. Thanks, Arpit On Fri, Jun 13, 2014 at 4:04 AM, Malcolm wrote: > Running tests on hadoop 2.4, both nat

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

+1 Arpit On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy wrote: > Folks, > > As discussed, I'd like to call a vote on changing our by-laws to change > release votes from 7 days to 5. > > I've attached the change to by-laws I'm proposing. > > Please vote, the vote will the usual period of 7 da

Re: 'current' document links to 2.3.0

On a related note, https://hadoop.apache.org/docs/stable/ still points to 2.2.0. Since 2.4.x is the current stable series, I updated stable to point to 2.4.1. On Mon, Jul 14, 2014 at 12:13 AM, Akira AJISAKA wrote: > Thanks Andrew! > > > > One thing we can do though is have proper notes for 2.5

TestIPC failures in Jenkins

Can someone with administrator access to the Jenkins VMs please take a look at the /etc/hosts configuration? TestIPC often fails in Jenkins runs due to a timeout in InetAddress.getLocalHost. Most likely a missing entry in /etc/hosts for the system hostname. e.g. https://builds.apache.org/job/PreC

Re: Hadoop Code of Incompatible Changes

I cleared out the wiki page and left a forwarding link to the site docs. >From a quick scan all the content is included in the site docs. On Tue, Jul 29, 2014 at 2:14 PM, Sandy Ryza wrote: > Eli pointed out to me that this is the up-to-date compatibility guide: > > http://hadoop.apache.org/docs

Re: [DISCUSS] Migrate from svn to git for source control?

+1 to voting on specific workflow(s). On Tue, Aug 5, 2014 at 5:49 PM, Karthik Kambatla wrote: > If we are to start a vote thread, will people prefer a vote thread that > includes potential workflows as well? > > > On Tue, Aug 5, 2014 at 5:40 PM, Karthik Kambatla > wrote: > > > Thanks for your

Re: [DISCUSS] Migrate from svn to git for source control?

Abdelnur wrote: > I would say we can first move to git and keep the very same workflow we > have today, then we can evolve it. > > > On Tue, Aug 5, 2014 at 6:46 PM, Arpit Agarwal > wrote: > > > +1 to voting on specific workflow(s). > > > > > > On

Re: [VOTE] Migration from subversion to git for version control

+1 binding. On Tue, Aug 12, 2014 at 6:08 AM, Thomas Graves < tgra...@yahoo-inc.com.invalid> wrote: > +1 (binding). > > > Tom > > > On Friday, August 8, 2014 9:57 PM, Karthik Kambatla > wrote: > > > > I have put together this proposal based on recent discussion on this topic. > > Please vote on

[DISCUSS] Switch to log4j 2

I don't recall whether this was discussed before. I often find our INFO logging to be too sparse for useful diagnosis. A high performance logging framework will encourage us to log more. Specifically, Asynchronous Loggers look interesting. https://logging.apache.org/log4j/2.x/manual/async.html#Per

Re: [DISCUSS] Switch to log4j 2

The block state change logs are indeed too noisy at INFO and I've not found them useful when troubleshooting. Just filed HDFS-6860 to fix that. This is orthogal to SLF4J migration however moving to SLF4J would help ease the transition to Log4j 2. Thanks for the pointer to HDFS-5421 Aaron, looking

Re: Updates on migration to git

I cloned the new repo, built trunk and branch-2, verified all the branches are present. Also checked a few branches and the recent commit history matches our existing repo. Everything looks good so far. On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla wrote: > The git repository is now ready f

Re: migrating private branches to the new git repo

Allen, I think the correct field you are looking for is 'Target Version'. If a fix is committed to both branch-2 and trunk, the fix version must include both 2.x.0 and 3.0.0. However the target version would be 2.x.0 as that is the earliest release that includes the fix. On Wed, Sep 3, 2014 at 12

Re: migrating private branches to the new git repo

doesn't appear to have any documentation around it. (I think it's > confusing because branch-0.22 was *not* considered a mainline branch even > though it appears to be by first glance.) > > That said, I just yanked all the fix versions that were both 3.0 and 2.6 > and marked

Re: migrating private branches to the new git repo

ot;. :D > > > On Sep 3, 2014, at 1:07 PM, Arpit Agarwal > wrote: > > > Thanks, good to know. > > > > So in the spirit of simplification can we just eliminate the 'Target > > Version' field from Jira? > > > > > > On Wed, Sep 3, 2014 a

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

That makes sense for Beta users but most of our users will be upgrading from a previous GA release and the changelog will mislead them. The webpage does not mention this is a delta from the beta release. From: Andrew Wang Date: Friday, December 15, 2017 at 10:36 AM To: Arpit Agarwal Cc

Re: Access to wiki

Granted Ajay write access to the confluence wiki. On 1/9/18, 10:38 AM, "Steve Loughran" wrote: Is this for the confluence wiki at https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Home On 4 Jan 2018, at 20:25, Ajay Kumar mailto:ajay.ku...@hortonworks.com>> wrote

Re: Apache Hadoop 3.0.1 Release plan

Hi Aaron/Lei, Do you plan to roll an RC with an uncommitted fix? That isn't the right approach. This issue has good visibility and enough discussion. If there is a binding veto in effect then the change must be abandoned. Else you should be able to proceed with committing. However, 3.0.0 must

Re: About reset branch-3.1 to trunk before release.

Thanks Wangda. On 3/19/18, 11:38 AM, "Wangda Tan" wrote: Done JIRA fix version update: Moved all JIRAs with fixVersion = 3.2.0 to 3.1.0 except following few fixes (which committed after 49c747ab187d0650143205ba57ca19607ec4c6bd) YARN-8002. Support NOT_SELF and ALL

Re: [VOTE] Release Apache Hadoop 3.1.0 (RC1)

Thanks for putting together this RC, Wangda. The guidance from Apache is to omit MD5s, specifically: > SHOULD NOT supply a MD5 checksum file (because MD5 is too broken). https://www.apache.org/dev/release-distribution#sigs-and-sums On Apr 2, 2018, at 7:03 AM, Wangda Tan mailto:wheele...@gma

Re: [VOTE] Release Apache Hadoop 3.0.1 (RC1)

Hi Lei, It looks like the release artefacts have dummy shaded jars. E.g. Repository Path: /org/apache/hadoop/hadoop-client-runtime/3.0.1/hadoop-client-runtime-3.0.1.jar Uploaded by: lei Size: 44.47 KB Uploaded Date:Fri Mar 16 2018 15:50:42 GMT-0700 (PDT) Last Modified:F

Re: [VOTE] Release Apache Hadoop 3.1.0 (RC1)

, 2018 at 9:25 PM To: Arpit Agarwal Cc: Gera Shegalov , Sunil G , "yarn-...@hadoop.apache.org" , Hdfs-dev , Hadoop Common , "mapreduce-...@hadoop.apache.org" , Vinod Kumar Vavilapalli Subject: Re: [VOTE] Release Apache Hadoop 3.1.0 (RC1) As pointed by Arpit, the previo

Re: HADOOP-15124 review

Hi Igor, it is perfectly fine to request a code review on the dev mailing list. From: Igor Dvorzhak Date: Tuesday, June 26, 2018 at 9:27 PM To: Cc: , Subject: Re: HADOOP-15124 review Hi Yiqun, Thank you for the explanation. I didn't know that this is not appropriate and will not do so in fu

Re: [DISCUSS]Merge ContainerIO branch (HDDS-48) in to trunk

t week we will clean up the unused classes, fix old integration tests and continue testing the changes. Thanks to Hanisha Koneru, Arpit Agarwal, Anu Engineer, Jitendra Pandey, Xiaoyu Yao, Ajay Kumar, Mukul Kumar Singh, Marton Elek and Shashikant Banerjee for their contributions in des

Re: [VOTE] reset/force push to clean up inadvertent merge commit pushed to trunk

-1 for the force push. Nothing is broken in trunk. The history looks ugly for two commits and we can live with it. The revert restored the branch to Giovanni's intent. i.e. only YARN-8435 is applied. Verified there is no delta between hashes 0d9804d and 39ad989 (HEAD). 39ad989 2018-07-05 aengin

Re: [VOTE] reset/force push to clean up inadvertent merge commit pushed to trunk

afaict YARN-8435 is still in trunk. YARN-7556 and YARN-7451 are not. From: Giovanni Matteo Fumarola Date: Friday, July 6, 2018 at 10:59 AM To: Vinod Kumar Vavilapalli Cc: Anu Engineer , Arpit Agarwal , "su...@apache.org" , "yarn-...@hadoop.apache.org" , "h

Re: [VOTE] reset/force push to clean up inadvertent merge commit pushed to trunk

s original. I can do this if there are no objection. - Sunil On Fri, Jul 6, 2018 at 11:10 AM Arpit Agarwal wrote: > afaict YARN-8435 is still in trunk. YARN-7556 and YARN-7451 are not. > > > From: Giovanni Matteo Fumarola > Date: F

Re: [VOTE] reset/force push to clean up inadvertent merge commit pushed to trunk

Things are good. > > I can push this now which will restore trunk to its original. > I can do this if there are no objection. > > - Sunil > > On Fri, Jul 6, 2018 at 11:10 AM Arpit Agarwal > wrote: > > afaict YARN-8435 is s

Re: [VOTE] Merge ContainerIO branch (HDDS-48) in to trunk

Late +1 for the merge. Thanks for driving this improvement Hanisha and Bharat. On 6/29/18, 3:10 PM, "Bharat Viswanadham" wrote: Hi All, Given the positive response to the discussion thread [1], here is the formal vote thread to merge HDDS-48 in to trunk. Summary of code

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

+1 Thanks for initiating this Marton. On 8/31/18, 1:07 AM, "Elek, Marton" wrote: Bumping this thread at last time. I have the following proposal: 1. I will request a new git repository hadoop-site.git and import the new site to there (which has exactly the same cont

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

Requested a new git repo for the site: https://gitbox.apache.org/repos/asf/hadoop-site.git On 9/4/18, 1:33 PM, "Mingliang Liu" wrote: It might be late but I'm +1 on the new site and transition proposal. Thanks Marton. On Fri, Aug 31, 2018 at 1:07 AM Elek, Marton wrote:

Re: [VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)

Thanks for putting together this release Marton. +1 (binding) - Verified signatures and checksums - LICENSE and NOTICE files exist in source and binary tarballs - Built from source code - Deployed to three node cluster - Tried out Ozone shell commands via 'ozone sh' - Tried out OzoneF

Jenkins build machines are down

A number of the Jenkins build machines appear to be down with different error messages. https://builds.apache.org/label/Hadoop/ Does anyone know what is the process to restore them? I assume INFRA cannot help as they don’t own these machines.

Re: Jenkins build machines are down

e and will be back when complete. Thank You @Marton Elek for providing this information. Thanks, Bharat On 10/31/18, 11:58 AM, "Arpit Agarwal" wrote: A number of the Jenkins build machines appear to be down with different error messages.

Re: [VOTE] Release Apache Hadoop Ozone 0.3.0-alpha (RC1)

+1 binding. - Verified signatures - Verified checksums - Checked LICENSE/NOTICE files - Built from source - Deployed to three node cluster and ran smoke tests. Thanks Marton for putting up the RC. On 2018/11/14, 9:14 AM, "Elek, Marton" wrote: Hi all, I've created the s

Re: [VOTE] - HDDS-4 Branch merge

+1 It's great to see Ozone security being merged. On 2019/01/11, 7:40 AM, "Anu Engineer" wrote: Since I have not heard any concerns, I will start a VOTE thread now. This vote will run for 7 days and will end on Jan/18/2019 @ 8:00 AM PST. I will start with my vote, +1 (Binding

Re: proposed new repository for hadoop/ozone docker images (+update on docker works)

I’ve requested a new repo hadoop-docker-ozone.git in gitbox. > On Jan 22, 2019, at 4:59 AM, Elek, Marton wrote: > > > > TLDR; > > I proposed to create a separated git repository for ozone docker images > in HDDS-851 (hadoop-docker-ozone.git) > > If there is no objections in the next 3 days

Re: [VOTE] Release Apache Hadoop 3.1.2 - RC1

+1 (binding) - Verified signatures - Verified checksums - Built from source - Verified Maven artifacts on staging repo - Deployed 3 node cluster - Tried out HDFS commands, MapReduce jobs. Confirmed the issues Billie pointed out. Not sure if you need to spin up a new RC or you can update the tarb

Re: [VOTE] Release Apache Hadoop 3.1.2 - RC1

+1 binding for updated source package. - Rechecked signatures and checksums - Source matches release git tag - Built from source > On Feb 5, 2019, at 10:50 AM, Sunil G wrote: > > Thanks Billie for pointing out. > I have updated source by removing patchprocess and extra line create > rele

Re: [DISCUSS] Docker build process

Hi Eric, > Dockerfile is most likely to change to apply the security fix. I am not sure this is always. Marton’s point about revising docker images independent of Hadoop versions is valid. > When maven release is automated through Jenkins, this is a breeze > of clicking a button. Jenkins eve

Re: VOTE: Hadoop Ozone 0.4.0-alpha RC1

Thanks Ajay for putting together this RC. Unfortunately HDDS-1425 looks like a blocker. We should make the docker experience smooth for anyone trying out 0.4.0. I’ve just committed Marton’s patch for HDDS-1425 this morning. Let’s roll a new RC.

Re: VOTE: Hadoop Ozone 0.4.0-alpha RC2

Thanks for building this RC Ajay. +1 binding. - verified signatures and checksums - built from source - deployed to 3 node cluster, tried out basic operations - ran smoke tests - ran unit tests - LICENSE/NOTICE files look ok There is an extra file in the source root named JenkinsFile. > On A

Re: [VOTE] Unprotect HDFS-13891 (HDFS RBF Branch)

The request is specific to HDFS-13891, correct? We should not allow force push on trunk. > On May 14, 2019, at 8:07 AM, Anu Engineer > wrote: > > Is it possible to unprotect the branches and not the trunk? Generally, a > force push to trunk indicates a mistake and we have had that in the past

Re: [DISCUSS] Merge HDFS-13891(RBF) to trunk

I scanned the merge payload for changes to non-RBF code. The changes are minimal, which is good. The only commit that I didn’t understand was: https://issues.apache.org/jira/browse/HDFS-14268 The jira description doesn’t make it clear why ECBlo

Re: [DISCUSS] Merge HDFS-13891(RBF) to trunk

Utility method which is moved to > hadoop-hdfs-client module. Ideally it could have been seperate jira. But this > changes will not induce any issues, will take necessary action for this. > > On Mon, Jun 10, 2019 at 8:40 PM Arpit Agarwal <mailto:aagar...@cloudera.com>> wrote:

Re: [VOTE] Move Submarine source code, documentation, etc. to a separate Apache Git repo

+1 > On Aug 23, 2019, at 7:05 PM, Wangda Tan wrote: > > Hi devs, > > This is a voting thread to move Submarine source code, documentation from > Hadoop repo to a separate Apache Git repo. Which is based on discussions of > https://lists.apache.org/thread.html/e49d60b2e0e021206e22bb2d430f4310019

Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree

+1 > On Sep 17, 2019, at 2:49 AM, Elek, Marton wrote: > > > > TLDR; I propose to move Ozone related code out from Hadoop trunk and store it > in a separated *Hadoop* git repository apache/hadoop-ozone.git > > > > > When Ozone was adopted as a new Hadoop subproject it was proposed[1] to b

Re: [VOTE] create ozone-dev and ozone-issues mailing lists

+1 > On Oct 27, 2019, at 1:25 AM, Elek, Marton wrote: > > > As discussed earlier in the thread of "Hadoop-Ozone repository mailing list > configurations" [1] I suggested to solve the current misconfiguration problem > with creating separated mailing lists (dev/issues) for Hadoop Ozone. > > I

Re: [VOTE] create ozone-dev and ozone-issues mailing lists

Thanks for kicking this off Marton. Submitted INFRA requests to create the following. The lists should be live soon. - ozone-dev@h.a.o - ozone-issues@h.a.o - ozone-commits@h.a.o > On Oct 31, 2019, at 3:32 AM, Elek, Marton wrote: > > > Thanks for all the votes and fee

Re: [DISCUSS] Ozone 0.4.2 release

+1 > On Dec 6, 2019, at 5:25 PM, Dinesh Chitlangia wrote: > > All, > Since the Apache Hadoop Ozone 0.4.1 release, we have had significant > bug fixes towards performance & stability. > > With that in mind, 0.4.2 release would be good to consolidate all those fixes. > > Pls share your thought

Re: Needs support to add more entropy to improve cryptographic randomness on Linux VMs

Thanks for flagging this Ahmed. urandom is a perfectly acceptable option. I am not sure who maintains the pre-commit machines these days. > On Jan 14, 2020, at 10:42 AM, Ahmed Hussein wrote: > > Hi, > > I was investigating a JUnit test > (MAPREDUCE-7079:TestMRIntermediateDataEncryption > is

Re: [DISCUSS] Feature branch for HDFS-14978 In-place Erasure Coding Conversion

+1 > On Jan 23, 2020, at 2:51 PM, Jitendra Pandey wrote: > > +1 for the feature branch. > > On Thu, Jan 23, 2020 at 1:34 PM Wei-Chiu Chuang > wrote: > Hi we are working on a feature to improve Erasure Coding, and I would like > to seek your opinion on creating a feature branch for it. (HDFS

Re: [VOTE] Apache Hadoop Ozone 0.5.0-beta RC0

Hi Dinesh, Thanks for spinning up this RC! Looks like we still had ~15 issues that were tagged as Blockers for 0.5.0 in jira. I’ve moved out most of them, however the remaining 4 look like must fixes. https://issues.apache.org/jira/issues/?jql=project%20%3D%20%22HDDS%22%20and%20%22Target%20Vers

Re: [VOTE] Apache Hadoop Ozone 0.5.0-beta RC1

+1 (binding) Verified mds, sha512 Verified signatures Built from source Deployed to 3 node cluster Tried a few ozone shell and filesystem commands Ran freon load generator Thanks Dinesh for putting the RC1 together. > On Mar 6, 2020, at 4:46 PM, Dinesh Chitlangia wrote: > > Hi Folks, > > We

Re: [VOTE] Apache Hadoop Ozone 0.5.0-beta RC1

* Compiled sources >> * Ran ozone smoke test against both binary and locally compiled versions >> >> Thanks Dinesh for RC1. >> >> -Attila >> >> On Sun, Mar 8, 2020 at 2:34 AM Arpit Agarwal >> wrote: >>> >>> +1 (binding) >&g

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

Can ARM binaries be provided after the fact? We cannot increase the RM’s burden by asking them to generate an extra set of binaries. > On Mar 17, 2020, at 10:23 AM, Brahma Reddy Battula wrote: > > + Dev mailing list. > > -- Forwarded message - > From: Brahma Reddy Battula > D

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

16797 > > On Tue, Mar 17, 2020 at 10:59 PM Arpit Agarwal > wrote: > >> Can ARM binaries be provided after the fact? We cannot increase the RM’s >> burden by asking them to generate an extra set of binaries. >> >> >>> On Mar 17, 2020, at 10:23 AM, Br

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

ote: > > Sure, we can't make mandatory while voting and we can upload to downloads > once release vote is passed. > > On Tue, 17 Mar 2020 at 11:24 PM, Arpit Agarwal > wrote: > >>> Sorry,didn't get you...do you mean, once release voting is >>> processed

Re: [VOTE] Apache Hadoop Ozone 0.5.0-beta RC2

+1 binding. - Verified hashes and signatures - Built from source - Deployed to 5 node cluster - Tried ozone shell and filesystem operations - Ran freon stress test for a while with write validation I couldn’t find the RC2 tag in the gitbox repo, although i

Hadoop 3.1.2 missing from download site?

The Hadoop 3.1.2 download links seem to be broken on https://hadoop.apache.org/releases.html Was it removed on purpose? - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common

Re: [VOTE] Release cadence and EOL

The ASF release policy says releases may not be vetoed [1] so the EOL policy sounds unenforceable. Not sure a release cadence is enforceable either since Release Managers are volunteers. 1. https://www.apache.org/dev/release.html#approving-a-release On 1/18/17, 7:06 PM, "Junping Du" wrote:

Re: Access to Confluence Wiki

Can you please grant me write access too? Thanks. On 10/30/17, 11:01 PM, "Akira Ajisaka" wrote: Done. Welcome! -Akira On 2017/10/28 3:26, Hanisha Koneru wrote: > Hi, > > Can I please get access to the Confluence Hadoop Wiki. My confluence id is “hanishakoner

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

Hi Andrew, Thank you for your hard work in getting us to this step. This is our first major GA release in many years. I feel a 5-day vote window ending over the weekend before thanksgiving may not provide sufficient time to evaluate this RC especially for downstream components. Would you plea

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

Best, Andrew On Fri, Nov 17, 2017 at 1:27 PM, Arpit Agarwal wrote: > Hi Andrew, > > Thank you for your hard work in getting us to this step. This is our first > major GA release in many years. > > I feel a 5-day vote wind

  1   2   3   >