Re: [VOTE] Moving Ozone to a separated Apache project

+1, Thanks, Wangda Tan On Tue, Sep 29, 2020 at 10:10 AM Aravindan Vijayan wrote: > +1, thank you Marton. > > On Tue, Sep 29, 2020 at 9:17 AM Bharat Viswanadham > wrote: > > > +1 > > Thank You @Elek, Marton for driving this. > > > > > > Thanks

Re: [ANNOUNCE] New Apache Hadoop Committer - He Xiaoqiao

Congrats! Best, Wangda Tan On Thu, Jun 11, 2020 at 5:55 PM Tao Yang wrote: > Congratulations Xiaoqiao! > > Best, > Tao > > > -- > 发件人：Weiwei Yang > 发送时间：2020年6月12日(星期五) 02:24 > 收件人：Sree Vaddi

Re: [DISCUSS] making Ozone a separate Apache project

+1, Thanks, Wangda On Thu, May 14, 2020 at 7:01 AM Tsuyoshi Ozawa wrote: > +1 > > Thanks > - Tsuyoshi > > On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan < > rakeshr.oz...@gmail.com> > wrote: > > > +1 > > > > Thanks, > > Rakesh > > > > On Wed, May 13, 2020 at 1:23 PM Elek, Marton wrote: >

Re: [VOTE] EOL Hadoop branch-2.8

+1 On Mon, Mar 2, 2020 at 8:50 PM Akira Ajisaka wrote: > +1 > > -Akira > > On Tue, Mar 3, 2020 at 4:55 AM Ayush Saxena wrote: > > > +1 for marking 2.8 EOL > > > > -Ayush > > > > > On 03-Mar-2020, at 12:18 AM, Wei-Chiu Chuang > wrote: > > > > > > I am sorry I forgot to start a VOTE thread. >

Re: [DISCUSS] Hadoop 2019 Release Planning

on can be used to get the explicit version you want.) > > > > > > On Tue, Jan 7, 2020 at 2:18 AM Akira Ajisaka > > wrote: > > > > > > > > I am interested on 3.3 release ..will act as RM .will update the > > wiki > > > as > > > > we

Re: [DISCUSS] Hadoop 2019 Release Planning

help from folks >> > > especially Sunil. :D >> > > And this time I would like to help to release the 3.1.4. Thanks! >> > > >> > > BR, >> > > Zhankun >> > > >> > > Hui Fei 于2019年8月16日 周五下午7:19写道： >> >

Re: [DISCUSS] Making 2.10 the last minor 2.x release

+1, thanks Jonathan for bringing this up! On Fri, Nov 15, 2019 at 11:41 AM epa...@apache.org wrote: > Thanks Jonathan for opening the discussion. > > I am not in favor of this proposal. 2.10 was very recently released, and > moving to 2.10 will take some time for the community. It seems

Re: [DISCUSS] Remove Ozone and Submarine from Hadoop repo

+1, we should do that earlier than later. It is a code change that I think we don't need to wait for 7 days vote. On Thu, Oct 24, 2019 at 4:18 PM Anu Engineer wrote: > +1 for Ozone. We are in our own repo now. It would be good to remove this > code from Hadoop, otherwise it will confuse new

Re: [Discuss] Hadoop-Ozone repository mailing list configurations

We're going to fix the Submarine email list issues once spin-off works start On Wed, Oct 23, 2019 at 2:39 PM Matt Foley wrote: > Definitely yes on ‘ozone-issues’. Whether we want to keep ozone-dev and > hdfs-dev together or separate, I’m neutral. > Thanks, > —Matt > > On Oct 23, 2019, at 2:11

[NEED HELP] Hadoop 3.x Production Deployment Can be Publicly Talk About?

). If you could include a short summary (which can be publicly shared) of the use cases that will be very helpful. If the number of companies responded is too low, I may skip putting a logo wall. Hope to get your feedbacks soon. Thanks, Wangda Tan

Re: [NOTICE] Building trunk needs protoc 3.7.1

Hi Vinay, Thanks for the clarification. Do you have a timeline about all you described works w.r.t. the compatibility will be completed? I'm asking this is because we need to release 3.3.0 earlier if possible since there're 1k+ of patches in 3.3.0 already, we should get it out earlier. If the

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 wrote: > Hi All, > > A very long pending task, protobuf upgrade is happening

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

+1 (binding). >From my experiences of Submarine project, I think moving to a separate repo helps. - Wangda On Tue, Sep 17, 2019 at 11:41 AM Subru Krishnan wrote: > +1 (binding). > > IIUC, there will not be an Ozone module in trunk anymore as that was my > only concern from the original

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

Thanks everyone for voting, support, and suggestions! Best, Wangda On Sun, Sep 8, 2019 at 10:57 PM Sree Vaddi wrote: > Congratulations, Wangda. Thank you. > > Let's work towards it's better adoption. > > > Thank you. > /Sree > > > > > On Sunday, September

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

Thanks everybody for voting! Let me conclude the voting thread: We got 16 binding +1s from PMCs. And 29 +1s from Committers/Contributors. With no veto. The vote now passed, we will work with the Apache community to get new project created and continue the spin-off process. Best, Wangda Tan

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

ase include me also. >> >> Thanks, >> >> Junping >> >> Wangda Tan 于2019年9月1日周日 下午1:19写道： >> >> > Hi all, >> > >> > As we discussed in the previous thread [1], >> > >> > I just moved the spin-off proposal to CWIKI

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

wish to contribute and will help in same. please let me know if you DON'T want to add to the committer list. Best, Wangda Tan On Fri, Sep 6, 2019 at 3:54 PM Wei-Chiu Chuang wrote: > +1 > I've involved myself in Submarine dev and I'd like to be included in the > future. > > Thanks

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

a TLP > > 2. direct TLP > > > Thank you. > /Sree > > > > > On Saturday, August 31, 2019, 10:19:06 PM PDT, Wangda Tan < > wheele...@gmail.com> wrote: > > > Hi all, > > As we discussed in the previous thread [1], > > I just moved the spin-off pro

[VOTE] Moving Submarine to a separate Apache project proposal

so I sent two separate voting thread.) Please let me know if I missed anyone in the proposal, and reply if you'd like to be included in the project. This voting runs for 7 days and will be concluded at Sep 7th, 11 PM PDT. Thanks, Wangda Tan [1] https://lists.apache.org/thread.html

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

Got some trouble in creating git repo using Apache self-service. Created https://issues.apache.org/jira/browse/INFRA-18964 Thanks, Wangda On Thu, Aug 29, 2019 at 11:52 PM Wangda Tan wrote: > Thanks everyone for voting. > > We got 12 binding +1s from committers. The vote passed. >

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

t; > > 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 discuss

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

I just put it to CWIKI: https://cwiki.apache.org/confluence/display/HADOOP/EOL+%28End-of-life%29+Release+Branches Any thoughts? If no I will go ahead to send it to user/dev/general email lists. (Should we send it to general?) On Wed, Aug 28, 2019 at 5:03 PM Wangda Tan wrote: > Hi fo

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

28, 2019 at 2:45 AM Konstantin Shvachko wrote: > +1 for the proposal. > > I thought we already EOL-ed 2.6 though some time ago. > > Thanks, > --Konstantin > > On Tue, Aug 20, 2019 at 8:03 PM Wangda Tan wrote: > > > Hi all, > > > > This is a vote

Re: Any thoughts making Submarine a separate Apache project?

next? Could you help to send this to the ASF board? Thanks, Wangda Tan On Tue, Aug 13, 2019 at 4:36 PM Wangda Tan wrote: > Hi folks, > > I just drafted a proposal which is targetted to send to PMC list and board > for thoughts. Thanks Xun Liu for providing thoughts about future

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

Contributors who have permissions to push to Hadoop Git repository will have permissions to push to the new Submarine repository. This voting thread will run for 7 days and will end at Aug 30th. Please let me know if you have any questions. Thanks, Wangda Tan

Re: Hadoop Community Sync Up Schedule

kly (every 2 weeks). Sometimes this gives us 3 > sync-ups in one month, which I think is fine. > -Eric Payne > > On Wednesday, August 21, 2019, 5:01:52 AM CDT, Wangda Tan < > wheele...@gmail.com <mailto:wheele...@gmail.com>> wrote: > > > > For folks in other

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

Hi Steve, The proposal is to EOL for the following branches: [2.0.x - 2.7.x] [3.0.x] 2.8.x, 2.9.x, 2.10.x (not released yet), 3.1.x (and later) are not EOL. Thoughts? On Sat, Aug 24, 2019 at 1:40 AM Steve Loughran wrote: > > > On Wed, Aug 21, 2019 at 4:03 AM Wangda Tan wrote: &g

Re: Hadoop Community Sync Up Schedule

s gives us 3 > sync-ups in one month, which I think is fine. > -Eric Payne > > On Wednesday, August 21, 2019, 5:01:52 AM CDT, Wangda Tan < > wheele...@gmail.com <mailto:wheele...@gmail.com>> wrote: > > > > For folks in other US time zones: how about 11am PDT

Re: Thoughts about moving submarine to a separate git repo?

new repo for more cleaner code base and remove > additional dependencies, jenkins etc. > One major point from my end is that the commits to new repo ideally should > happen from committers or branch committers. > > As hadoop community, we could help in this case. @Wangda Tan >

Re: Hadoop Community Sync Up Schedule

do “second Wednesday > of the month”. > > But I’ll schedule them one-by-one if I have to, I just wanted clarity. :-) > > Thanks, > —Matt > > > On Aug 19, 2019, at 8:31 PM, Wangda Tan wrote: > > Hi folks, > > We have run community sync up for 1.5 months. I s

Re: Thoughts about moving submarine to a separate git repo?

Hi Xun, Thanks for starting this thread. I'm glad to see the existing momentum made by Submarine community, and I like the proposal to make it be a separate Git repo. Some suggestions: 1) For options mentioned by Sunil: I think it's better to be a separate Git repo instead of a branch. To me,

[VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

Hi all, This is a vote thread to mark any versions smaller than 2.7 (inclusive), and 3.0 EOL. This is based on discussions of [1] This discussion runs for 7 days and will conclude on Aug 28 Wed. Please feel free to share your thoughts. Thanks, Wangda [1]

Re: Make EOL branches to public?

gt; > +1 > > I feel like one year of inactivity is a good sign that the community is > not > > interested in the branch any more. > > > > On Fri, Aug 16, 2019 at 3:14 AM Wangda Tan wrote: > > > > > Hi folks, > > > > > > Want to hea

Re: Hadoop Community Sync Up Schedule

N+MR APAC sync today, and you are > welcome to join: > > > Time and Date：07/25 1:00 pm (CST Time) > > Zoom link：Zoom | https://cloudera.zoom.us/j/880548968 > > Summary： > > https://docs.google.com/document/d/1GY55sXrekVd-aDyRY7uzaX0hMDPyh3T-AL1kUY2TI5M > > > Than

Make EOL branches to public?

Hi folks, Want to hear your thoughts about what we should do to make some branches EOL. We discussed a couple of times before in dev lists and PMC list. However, we couldn't get a formal process of EOL. According to the discussion. It is hard to decide it based on time like "After 1st release,

Re: [DISCUSS] Hadoop 2019 Release Planning

> > -Rohith Sharma K S > > On Sat, 10 Aug 2019 at 08:29, Wangda Tan wrote: > > > Hi all, > > > > Hope this email finds you well > > > > I want to hear your thoughts about what should be the release plan for > > 2019. > > > > In 2018, w

Re: Any thoughts making Submarine a separate Apache project?

c is written down. >> >> Back to the sustainable community point, as part of drafting this >> proposal, you'd definitely want to make sure all of the Apache Hadoop >> PMC/Committers can exercise their will to join this new project as >> PMC/Committers respectively w

[DISCUSS] Hadoop 2019 Release Planning

add your thoughts. Volunteers welcome! If you have interests to run a release as Release Manager (or co-Resource Manager), please respond to this email thread so we can coordinate. Thanks, Wangda Tan [1] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution = Fixed AND fixVersion = 3.1.3 [2

Re: Any thoughts making Submarine a separate Apache project?

re all of the Apache Hadoop > PMC/Committers can exercise their will to join this new project as > PMC/Committers respectively without any additional constraints. > > Thanks > +Vinod > > > On Jul 25, 2019, at 1:31 PM, Wangda Tan wrote: > > > > Thanks everybod

Re: Any thoughts making Submarine a separate Apache project?

Thanks everybody for sharing your thoughts. I saw positive feedbacks from 20+ contributors! So I think we should move it forward, any suggestions about what we should do? Best, Wangda On Mon, Jul 22, 2019 at 5:36 PM neo wrote: > +1, This is neo from TiDB & TiKV community. > Thanks Xun for

Re: [ANNOUNCE] New Apache Hadoop Committer - Tao Yang

Congrats! Best, Wangda On Tue, Jul 16, 2019 at 10:37 AM 杨弢(杨弢) wrote: > Thanks everyone. > I'm so honored to be an Apache Hadoop Committer, I will keep working on > this great project and contribute more. Thanks. > > Best Regards, > Tao Yang > > >

Hadoop Community Sync Up Schedule

Hi folks, Here's the Hadoop Community Sync Up proposal/schedule: https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit#heading=h.xh4zfwj8ppmn And here's calendar file: https://calendar.google.com/calendar/ical/hadoop.community.sync.up%40gmail.com/public/basic.ics

Re: Agenda & More Information about Hadoop Community Meetup @ Palo Alto, June 26

://cloudera.zoom.us/j/606607666 Please let me know if you have any questions. If you haven't RSVP yet, please go ahead and RSVP so we can better prepare food, seat, etc. Thanks, Wangda On Wed, Jun 19, 2019 at 4:49 PM Wangda Tan wrote: > Hi All, > > I want to let you know that we have confi

Agenda & More Information about Hadoop Community Meetup @ Palo Alto, June 26

YARN. Any improvements to this scheduler can benefit both Kubernetes and YARN community.Speaker: Wangda Tan (Cloudera)PM:12:00 - 12:55 Lunch Break (Provided by Cloudera)1:00 - 1:25---Talk: Yarn Efficiency at UberAbstract: We will present the work do

Re: [DISCUSS] A unified and open Hadoop community sync up schedule?

it on the third Wednesday. > > On Tue, Jun 18, 2019 at 5:29 PM Wangda Tan wrote: > > > Hi Folks, > > > > I just updated doc: > > > > > https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# > > with > > di

Re: [DISCUSS] A unified and open Hadoop community sync up schedule?

to give it a try from next week, any suggestions? Thanks, Wangda On Fri, Jun 14, 2019 at 4:02 PM Wangda Tan wrote: > And please let me know if you can help with coordinate logistics stuff, > cross-checking, etc. Let's spend some time next week to get it finalized. > > Thanks, > Wa

Re: [DISCUSS] A unified and open Hadoop community sync up schedule?

And please let me know if you can help with coordinate logistics stuff, cross-checking, etc. Let's spend some time next week to get it finalized. Thanks, Wangda On Fri, Jun 14, 2019 at 4:00 PM Wangda Tan wrote: > Hi Folks, > > Yufei: Agree with all your opinions. > > Anu: i

Re: [DISCUSS] A unified and open Hadoop community sync up schedule?

;waiting for review for ever, which turns away new contributors. >>- 30m per session sounds a little bit short, we can try it out and see >>if extension is needed. >> >> Best, >> >> Yufei >> >> `This is not a contribution` >>

[DISCUSS] A unified and open Hadoop community sync up schedule?

stions to the time, frequency and themes and feel free to share your thoughts if we should do sync ups for other topics which are not covered by the proposal. Link to the Proposal Google doc <https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit#> Thanks, Wangda Tan

Re: [ANNOUNCE] Eric Badger is now a committer!

Congratulations, Eric. Welcome aboard! Best, Wangda On Tue, Mar 5, 2019 at 2:26 PM Sree V wrote: > Congratulations, Eric. > > > > Thank you./Sree > > > > On Tuesday, March 5, 2019, 12:50:20 PM PST, Ayush Saxena < > ayush...@gmail.com> wrote: > > Congratulations Eric!!! > > -Ayush > > >

Re: [VOTE] Propose to start new Hadoop sub project "submarine"

narasimha Garla < > naganarasimha...@apache.org> wrote: > >> +1 >> >> On Sat, 2 Feb 2019, 09:51 Rohith Sharma K S > wrote: >> >> > +1 >> > >> > On Sat, Feb 2, 2019, 3:54 AM Wangda Tan wrote: >> > >> > > Hi all, >

[ANNOUNCE] Apache Hadoop 3.1.2 release

, tmarquardt, trjianjianjiao, uranus, varun_saxena, vinayrpet, vrushalic, wilfreds, write2kish...@gmail.com, wujinhu, xiaochen, xiaoheipangzi, xkrogen, yangjiandan, yeshavora, yiran, yoelee, yuzhih...@gmail.com, zichensun, zvenczel Wangda Tan and Sunil Govind [1] JIRA query: project in (YARN, HADOOP

Re: [VOTE] Moving branch-2 precommit/nightly test builds to java 8

+1, make sense to me. On Tue, Feb 5, 2019 at 3:29 PM Konstantin Shvachko wrote: > +1 Makes sense to me. > > Thanks, > --Konst > > On Mon, Feb 4, 2019 at 6:14 PM Jonathan Hung wrote: > > > Hello, > > > > Starting a vote based on the discuss thread [1] for moving branch-2 > > precommit/nightly

Re: [VOTE] Release Apache Hadoop 3.1.2 - RC1

sum > and signature look good. > > Billie > > On Tue, 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 > > release. > > > > Also updated checksu

[VOTE] Propose to start new Hadoop sub project "submarine"

Hi all, According to positive feedbacks from the thread [1] This is vote thread to start a new subproject named "hadoop-submarine" which follows the release process already established for ozone. The vote runs for usual 7 days, which ends at Feb 8th 5 PM PDT. Thanks, Wangda Tan

Re: [DISCUSS] Making submarine to different release model like Ozone

ithdraw my veto and let > Submarine set its own course. > > > > Good luck Wangda. > > > > Regards, > > Eric > > > > *From: *Wangda Tan > *Date: *Friday, February 1, 2019 at 10:52 AM > *To: *Eric Yang > *Cc: *Weiwei Yang , Xun Liu , > Ha

Re: [DISCUSS] Making submarine to different release model like Ozone

artment (http://www.youdao.com) requires voice > recognition, > > 6) Massive Open Online Courses (https://open.163.com/) requires > multilingual translation and so on. > > > > If Submarine can be released independently like Ozone, it will help > us quickly get the l

[DISCUSS] Making submarine to different release model like Ozone

Strata Data Conf NY <https://conferences.oreilly.com/strata/strata-ny-2018/public/schedule/detail/68289> Thoughts? Thanks, Wangda Tan

Re: [VOTE] Release Apache Hadoop 3.1.2 - RC0

Hi Rohith, Thanks for reporting and fixing this issue, let’s redo the issue and will send another vote shortly. Best, Wangda On Sun, Jan 27, 2019 at 10:03 PM Rohith Sharma K S < rohithsharm...@apache.org> wrote: > @Wangda Tan I have pushed the changes to branch-3.1 > and

[VOTE] Release Apache Hadoop 3.1.2 - RC0

tains 325 [1] fixed JIRA issues since 3.1.1. I have done testing with a pseudo cluster and distributed shell job. My +1 to start. Best, Wangda Tan and Sunil Govind [1] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND fixVersion in (3.1.2) ORDER BY priority DESC

Re: [Urgent] Question about Nexus repo and Hadoop release

d-7] - > org.sonatype.nexus.configuration.ModelUtils - Saving model > /x1/nexus-work/conf/staging.xml > 2019-01-22 05:41:22 INFO [pool-1-thread-7] - > org.sonatype.nexus.configuration.ModelUtils - Saving model > /x1/nexus-work/conf/staging.xml > 2019-01-22 05:41:22 WARN [pool-1-thre

Re: [Urgent] Question about Nexus repo and Hadoop release

> -Chris > > > > On Jan 21, 2019, at 2:39 PM, Brian Fox wrote: > > > > They keys file is irrelevant to Nexus. The only thing that matters is > it’s in the mit pgp key ring. > > > > --Brian (mobile) > > > > > > On Jan 21, 2019, at 3:34 PM, W

Re: [Urgent] Question about Nexus repo and Hadoop release

I just checked on KEYS file, it doesn't show sig part. I updated KEYS file on Apache https://dist.apache.org/repos/dist/release/hadoop/common/KEYS and made it be ultimately trusted. pub rsa4096 2018-03-20 [SC] 4C899853CDDA4E40C60212B5B3FA653D57300D45 uid [ultimate] Wangda tan

Re: [NOTICE] branch-3.1.2 created for 3.1.2 release

) 9 AM PDT. Thank, Wangda On Mon, Jan 7, 2019 at 10:13 AM Wangda Tan wrote: > Hi devs, > > I just created branch-3.1.2 for 3.1.2 release and pushed to remote. > branch-3.1 is still open for new commits required for next 3.1.x release > (which will be 3.1.3). In the meantim

Re: [Urgent] Question about Nexus repo and Hadoop release

Hi David, Thanks for helping check this, I can see signatures on my key: pub 4096R/57300D45 <http://pool.sks-keyservers.net:11371/key/0xB3FA653D57300D45> 2018-03-20 Fingerprint=4C89 9853 CDDA 4E40 C602 12B5 B3FA 653D 5730 0D45 uid Wangda tan sig sig3 57300D45 <http:/

Re: [Urgent] Question about Nexus repo and Hadoop release

wrote: > Can you share the link to your key? > > -Brian > > On Jan 20, 2019, at 11:21 PM, Wangda Tan wrote: > > Still couldn't figure out without locating the log on the Nexus machine. > With help from several committers and PMCs, we didn't see anything wrong > with my si

Re: [Urgent] Question about Nexus repo and Hadoop release

repo. Thanks, Wangda On Thu, Jan 17, 2019 at 11:18 AM Wangda Tan wrote: > Spent several more hours trying to figure out the issue, still no luck. > > I just filed https://issues.sonatype.org/browse/OSSRH-45646, really > appreciate if anybody could add some suggestions. > >

Re: [Urgent] Question about Nexus repo and Hadoop release

Spent several more hours trying to figure out the issue, still no luck. I just filed https://issues.sonatype.org/browse/OSSRH-45646, really appreciate if anybody could add some suggestions. Thanks, Wangda On Tue, Jan 15, 2019 at 9:48 AM Wangda Tan wrote: > It seems the problem still exi

Re: [VOTE] Release Apache Hadoop 3.2.0 - RC1

rce. > https://repository.apache.org/content/repositories/orgapachehadoop-1186/ > > Please help to cross check the same. > > Thanks & Regards > Sunil > > On Tue, Jan 15, 2019 at 10:05 AM Wangda Tan wrote: > >> +1 (Binding). >> >> Deployed a local cluster fro

Re: [Urgent] Question about Nexus repo and Hadoop release

ase. So it should be synced between the key >> servers. >> >> But it seems that the INFRA solved the problem with shuffling the key >> server order (or it was an intermittent issue): see INFRA-17649 >> >> Seems to be working now... >> >> Marto

Re: [VOTE] Release Apache Hadoop 3.2.0 - RC1

+1 (Binding). Deployed a local cluster from binary, and ran some sample sanity jobs. Thanks Sunil for driving the release. Best, Wangda On Mon, Jan 14, 2019 at 11:26 AM Virajith Jalaparti wrote: > Thanks Sunil and others who have worked on the making this release happen! > > +1

Re: [Urgent] Question about Nexus repo and Hadoop release

>> >> https://issues.apache.org/jira/browse/INFRA-17649 >> >> Marton >> >> >> [1]: >> >> https://repository.apache.org/service/local/repositories/orgapachehadoop-1183/content/org/apache/hadoop/hadoop-mapreduce-client-jobclient/3.1.2/had

Re: [Urgent] Question about Nexus repo and Hadoop release

Uploaded sample file and signature. On Sat, Jan 12, 2019 at 9:18 PM Wangda Tan wrote: > Actually, among the hundreds of failed messages, the "No public key" > issues still occurred several times: > > failureMessage No public key: Key with id: (b3fa653d57300d45) was no

Re: [Urgent] Question about Nexus repo and Hadoop release

our public key and try the operation again. Once the close operation returned, I will upload sample files which may help troubleshoot the issue. Thanks, On Sat, Jan 12, 2019 at 9:04 PM Wangda Tan wrote: > Thanks David for the quick response! > > I just retried, now the "No p

Re: [Urgent] Question about Nexus repo and Hadoop release

uce-client-jobclient/3.1.2/hadoop-mapreduce-client-jobclient-3.1.2.pom', check the logs. Still exists and repeated hundreds of times. Do you know how to access the logs mentioned by above log? Best, Wangda On Sat, Jan 12, 2019 at 8:37 PM David Nalley wrote: > On Sat, Jan 12, 2019 at 9:09 PM Wang

[Urgent] Question about Nexus repo and Hadoop release

: key B3FA653D57300D45: "Wangda tan " not changed gpg: Total number processed: 1 gpg: unchanged: 1 gpg --keyserver pool.sks-keyservers.net --recv-keys B3FA653D57300D45 gpg: WARNING: unsafe permissions on homedir '/Users/wtan/.gnupg' gpg: key B3FA653D57300D45: 1 signature not c

[NOTICE] branch-3.1.2 created for 3.1.2 release

Hi devs, I just created branch-3.1.2 for 3.1.2 release and pushed to remote. branch-3.1 is still open for new commits required for next 3.1.x release (which will be 3.1.3). In the meantime, branch-3.1.2 is closed for new commits unless further noticed. I'm working on RC0 of 3.1.2 release now.

Re: Apache Hadoop 3.1.2 release plan

h Affects Version 3.1.2 and only one of them > as blocker. > > Why not just release now as soon as there are no blockers? > > Thanks > +Vinod > > > On Oct 24, 2018, at 4:36 PM, Wangda Tan wrote: > > > > Hi, All > > > > We have released Apache Had

Re: Apache Hadoop 3.1.2 release plan

Hi Steve, Is there any other JIRAs need to be released 3.1.2? I want to get 3.1.2 release starts earlier if possible. Thanks, Wangda On Wed, Nov 21, 2018 at 5:31 PM Wangda Tan wrote: > Hi Steve, > > It gonna be really good if you could get the patch committed during US > Thanksgi

Re: Apache Hadoop 3.1.2 release plan

Hi Steve, It gonna be really good if you could get the patch committed during US Thanksgiving holiday so I can start releasing starting next week. Thanks, Wangda On Mon, Nov 19, 2018 at 10:21 AM Wangda Tan wrote: > Hi Steve, > > It's helpful if you could share any timeline a

Re: New committer: Botong Huang

Congrats! Best, Wangda On Wed, Nov 21, 2018 at 4:23 PM Srinivas Reddy wrote: > Congratulations Botong !!! > > - > Srinivas > > - Typed on tiny keys. pls ignore typos.{mobile app} > > On Thu 22 Nov, 2018, 03:27 Chang Qiang Cao > > Congrats Botong! > > > > On Wed, Nov 21, 2018 at 2:15 PM Subru

Re: Apache Hadoop 3.1.2 release plan

tories, and the > high-performance one doesn't. > > https://issues.apache.org/jira/browse/HADOOP-15932 > > The patch doesn't delete the new code, just takes it out of the execution > path > > > > > On 16 Nov 2018, at 18:14, Wangda Tan wrote: > > > > Ju

Re: Apache Hadoop 3.1.2 release plan

RAs is already quite a bunch! > > I only see 7 JIRAs marked with Affects Version 3.1.2 and only one of them > as blocker. > > Why not just release now as soon as there are no blockers? > > Thanks > +Vinod > > > On Oct 24, 2018, at 4:36 PM, Wangda Tan wrote: >

Apache Hadoop 3.1.2 release plan

to cut branch-3.1 on Nov 15 and vote for RC on the same day. Please feel free to share your insights. Thanks, Wangda Tan [1] project in (YARN, "Hadoop HDFS", "Hadoop Common", "Hadoop Map/Reduce") AND fixVersion = 3.1.2

Re: Hadoop 3.1.2 release timing

Hi Jonathan, Sorry for my late response, I'm currently starting the discussion for 3.1.2 release, I want to get it done by Nov. If you want to upgrade to 3.1.x shortly. Please go with 3.1.1 and then upgrade to 3.1.2 given it has chances that release will be delayed of random issues and blockers.

Re: [IMPORTANT] Apache JIRA doesn't properly show sub-tickets from parent

Just checked the JIRA again, now the issue has gone. I think it might be caused by some intermittent JIRA system issue. Thanks, Wangda On Mon, Oct 1, 2018 at 10:52 AM Wangda Tan wrote: > Hi all devs, > > Today I found many subtickets doesn't show properly under parent. > > Fo

[IMPORTANT] Apache JIRA doesn't properly show sub-tickets from parent

Hi all devs, Today I found many subtickets doesn't show properly under parent. For example, YARN-6875 is the parent of YARN-7072. But from YARN-6875's sub ticket, YARN-7072 isn't shown here. I found many sub-tickets are gone from parent JIRA, such as YARN-6223 (there were ~20+ sub tickets),

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

+1, thanks for working on this, Marton! Best, Wangda On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal wrote: > +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.

[ANNOUNCE] Apache Hadoop 3.1.1 release

Tao Jie, Tao Yang, Ted Yu, Thomas Graves, Thomas Marquardt, Todd Lipcon, Vinod Kumar Vavilapalli, Wangda Tan, Wei Yan, Wei-Chiu Chuang, Weiwei Yang, Wilfred Spiegelenburg, Xiao Chen, Xiao Liang, Xintong Song, Xuan Gong, Yang Wang, Yesha Vora, Yiqun Lin, Yiran Wu, Yongjun Zhang, Yuanbo Liu, Zian

Re: [VOTE] Release Apache Hadoop 3.1.1 - RC0

eue balancing feature is enabled. This does not seem to be >> > specific to this release. >> > - The preemption-to-balance-queue-after-satisfied.enabled property seems >> > to always be enabled, but again, that is not specific to this release. >> > >> >

Re: [VOTE] Release Apache Hadoop 3.1.1 - RC0

c sanity check on NN UI > > Issue found > * In "Browse the file system" under "Utilities" tab in NN UI, "Head the > file" and "Tail the file" are not working. > > -Nanda > > On 8/3/18, 12:14 AM, "Wangda Tan" wrote: >

[VOTE] Release Apache Hadoop 3.1.1 - RC0

and distributed shell job. My +1 to start. Best, Wangda Tan [1] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND fixVersion in (3.1.1) ORDER BY priority DESC

Re: Apache Hadoop 3.1.1 release plan

Hi all, I'm working on RC for 3.1.1 now, if you have any commits to 3.1.x line, please commit them to branch-3.1. If it is a blocker for 3.1.1, please let me know so we can decide if we want to roll another RC or not. Thanks, Wangda On Thu, Jul 19, 2018 at 2:47 PM Wangda Tan wrote: > Hi

[jira] [Reopened] (HADOOP-15637) LocalFs#listLocatedStatus does not filter out hidden .crc files

[ https://issues.apache.org/jira/browse/HADOOP-15637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan reopened HADOOP-15637: - [~xkrogen], [~vagarychen], could u help to check the comments from [~bibinchundatt] below

Re: Apache Hadoop 3.1.1 release plan

ed so users could start to explore this feature. Otherwise the > functionality is pretty limited. It has been Patch Available for a while, I > just promoted it targeting to 3.1.1. Hope that makes sense. > > Thanks! > > -- > Weiwei > > On 11 May 2018, 9:02 AM +0800, Wan

Re: Hadoop 3.2 Release Plan proposal

Thanks Sunil for volunteering to be RM of 3.2 release, +1 for that. To concerns from Steve, It is a good idea to keep the door open to get important changes / features in before cutoff. I would prefer to keep the proposed release date to make sure things can happen earlier instead of last minute

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

+1 On Thu, Jul 5, 2018 at 2:37 PM Subru Krishnan wrote: > Folks, > > There was a merge commit accidentally pushed to trunk, you can find the > details in the mail thread [1]. > > I have raised an INFRA ticket [2] to reset/force push to clean up trunk. > > Can we have a quick vote for INFRA

Re: Merge branch commit in trunk by mistake

Adding back hdfs/common/mr-dev again to cc list. Here's the last merge revert commit: https://github.com/apache/hadoop/commit/39ad98903a5f042573b97a2e5438bc57af7cc7a1 On Thu, Jul 5, 2018 at 2:17 PM Wangda Tan wrote: > It looks like the latest revert is not correct, many of commits

Re: Merge branch commit in trunk by mistake

> > that said, I'm -1 (non-binding). force pushes are extremely > > > disruptive. there's no way to know who's updated their local git repo > > > to include these changes in the last few hours. if a merge commit is > > > so disruptive that we need to subject fol

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

+1 (binding) - Build from source. - Ran sanity jobs successfully. Thanks, Wangda On Mon, May 14, 2018 at 5:44 AM, Sunil G wrote: > +1 (binding) > > 1. Build package from src > 2. Ran few MR jobs and verified checked App Priority cases > 3. Node Label basic functions are ok.

  1   2   3   >