Re: Hadoop BoF at ApacheCon NA'22

[俊平堵]

Sure. No problem. :)

Thanks,

Junping

Wei-Chiu Chuang  于2022年10月3日周一 00:51写道：

>
> Hi Junping yes it’s all settled. We’ll be meeting Monday 5:50pm central
> time which will be 6:50am Tuesday for you. Sorry the complete conference
> schedule is only available to participants at this time. It was taken down
> from the website.
>
> Hey so it’s really early for you. I’d suggest to move you to the back of
> the session if that’s okay for you.
>
> Zoom link:
> https://cloudera.zoom.us/j/94221207158
>
> Dial in: +1 877-853-5257
>
> The zoom link is available for any one to join remotely.
>
> 俊平堵 於 2022年10月2日 週日，上午7:23寫道：
>
>> Hi Uma and Wei-Chiu,
>>  Does this schedule update have settled down (from Tues. to Mon.)? If
>> so, would you provide a meeting link for me so that I can join remotely?
>> Thanks!
>>
>> Best,
>>
>> Junping
>>
>> Uma Maheswara Rao Gangumalla  于2022年9月27日周二
>> 02:00写道：
>>
>> > Guys, there is a schedule change for Hadoop BoaF due to the conflicts
>> with
>> > Lightning talks on Wednesday. It has been moved to Monday.
>> > Plan accordingly.
>> >
>> > Ozone BoAF will happen in Rhythms-I on Monday. Depending on the number
>> of
>> > people, we could combine as well.
>> >
>> > Regards,
>> > Uma
>> >
>> > On Sat, Sep 24, 2022 at 8:52 PM 俊平堵  wrote:
>> >
>> > > Yes. It should be a short talk and I can only present remotely for
>> this
>> > > time. That would be great if you help to coordinate. :)
>> > >
>> > > Thanks,
>> > >
>> > > Junping
>> > >
>> > > Wei-Chiu Chuang  于2022年9月24日周六 01:21写道：
>> > >
>> > >> That would be great! Will you be presenting in person or remote?
>> > >> If it's a short talk (15-20 minutes) we'll have enough time for 2-3
>> of
>> > >> these. If folks want to present remotely I can help coordinate that.
>> > >>
>> > >> Here I put up a short agenda for the BoF:
>> > >>
>> > >>
>> >
>> https://docs.google.com/document/d/1_ha1BFeEyIkAJtl5tJ8Z4Vf5Md_0rN23RCrXkyNCY1c/edit?usp=sharing
>> > >> Please add more details here.
>> > >>
>> > >>
>> > >> On Thu, Sep 22, 2022 at 10:27 PM 俊平堵  wrote:
>> > >>
>> > >> > Thanks Wei-Chiu. I am happy to share the status of Hadoop Meetups
>> in
>> > >> China
>> > >> > (2019-2022) if that is a suitable topic. :)
>> > >> >
>> > >> > Thanks,
>> > >> >
>> > >> > Junping
>> > >> >
>> > >> > Wei-Chiu Chuang  于2022年9月21日周三 02:31写道：
>> > >> >
>> > >> > > We've not had a physical event for a long long time and we're way
>> > >> overdue
>> > >> > > for one.
>> > >> > >
>> > >> > > I'm excited to announce we've reserved a room at the upcoming
>> > >> ApacheCon
>> > >> > for
>> > >> > > Birds-of-Feather on October 4th from 17:50-18:30 CDT in Rhythms
>> I. I
>> > >> was
>> > >> > > also told that participants can stay after that until the hotel
>> > >> > personnels
>> > >> > > throw us out.
>> > >> > >
>> > >> > > Feel free to pass along this information.
>> > >> > >
>> > >> > > On top of that, I was told that this year's ApacheCon is very
>> > popular
>> > >> > and a
>> > >> > > lot of good talk proposals were not selected. If folks are
>> > interested
>> > >> I'm
>> > >> > > happy to invite you to share online. A physical meetup in the Bay
>> > Area
>> > >> > > would also be a great idea, if we can find a sponsor.
>> > >> > >
>> > >> > > Thanks,
>> > >> > > Wei-Chiu
>> > >> > >
>> > >> >
>> > >>
>> > >
>> >
>>
>

Re: Hadoop BoF at ApacheCon NA'22

[俊平堵]

Hi Uma and Wei-Chiu,
 Does this schedule update have settled down (from Tues. to Mon.)? If
so, would you provide a meeting link for me so that I can join remotely?
Thanks!

Best,

Junping

Uma Maheswara Rao Gangumalla  于2022年9月27日周二 02:00写道：

> Guys, there is a schedule change for Hadoop BoaF due to the conflicts with
> Lightning talks on Wednesday. It has been moved to Monday.
> Plan accordingly.
>
> Ozone BoAF will happen in Rhythms-I on Monday. Depending on the number of
> people, we could combine as well.
>
> Regards,
> Uma
>
> On Sat, Sep 24, 2022 at 8:52 PM 俊平堵  wrote:
>
> > Yes. It should be a short talk and I can only present remotely for this
> > time. That would be great if you help to coordinate. :)
> >
> > Thanks,
> >
> > Junping
> >
> > Wei-Chiu Chuang  于2022年9月24日周六 01:21写道：
> >
> >> That would be great! Will you be presenting in person or remote?
> >> If it's a short talk (15-20 minutes) we'll have enough time for 2-3 of
> >> these. If folks want to present remotely I can help coordinate that.
> >>
> >> Here I put up a short agenda for the BoF:
> >>
> >>
> https://docs.google.com/document/d/1_ha1BFeEyIkAJtl5tJ8Z4Vf5Md_0rN23RCrXkyNCY1c/edit?usp=sharing
> >> Please add more details here.
> >>
> >>
> >> On Thu, Sep 22, 2022 at 10:27 PM 俊平堵  wrote:
> >>
> >> > Thanks Wei-Chiu. I am happy to share the status of Hadoop Meetups in
> >> China
> >> > (2019-2022) if that is a suitable topic. :)
> >> >
> >> > Thanks,
> >> >
> >> > Junping
> >> >
> >> > Wei-Chiu Chuang  于2022年9月21日周三 02:31写道：
> >> >
> >> > > We've not had a physical event for a long long time and we're way
> >> overdue
> >> > > for one.
> >> > >
> >> > > I'm excited to announce we've reserved a room at the upcoming
> >> ApacheCon
> >> > for
> >> > > Birds-of-Feather on October 4th from 17:50-18:30 CDT in Rhythms I. I
> >> was
> >> > > also told that participants can stay after that until the hotel
> >> > personnels
> >> > > throw us out.
> >> > >
> >> > > Feel free to pass along this information.
> >> > >
> >> > > On top of that, I was told that this year's ApacheCon is very
> popular
> >> > and a
> >> > > lot of good talk proposals were not selected. If folks are
> interested
> >> I'm
> >> > > happy to invite you to share online. A physical meetup in the Bay
> Area
> >> > > would also be a great idea, if we can find a sponsor.
> >> > >
> >> > > Thanks,
> >> > > Wei-Chiu
> >> > >
> >> >
> >>
> >
>

Re: Hadoop BoF at ApacheCon NA'22

[俊平堵]

Yes. It should be a short talk and I can only present remotely for this
time. That would be great if you help to coordinate. :)

Thanks,

Junping

Wei-Chiu Chuang  于2022年9月24日周六 01:21写道：

> That would be great! Will you be presenting in person or remote?
> If it's a short talk (15-20 minutes) we'll have enough time for 2-3 of
> these. If folks want to present remotely I can help coordinate that.
>
> Here I put up a short agenda for the BoF:
>
> https://docs.google.com/document/d/1_ha1BFeEyIkAJtl5tJ8Z4Vf5Md_0rN23RCrXkyNCY1c/edit?usp=sharing
> Please add more details here.
>
>
> On Thu, Sep 22, 2022 at 10:27 PM 俊平堵  wrote:
>
> > Thanks Wei-Chiu. I am happy to share the status of Hadoop Meetups in
> China
> > (2019-2022) if that is a suitable topic. :)
> >
> > Thanks,
> >
> > Junping
> >
> > Wei-Chiu Chuang  于2022年9月21日周三 02:31写道：
> >
> > > We've not had a physical event for a long long time and we're way
> overdue
> > > for one.
> > >
> > > I'm excited to announce we've reserved a room at the upcoming ApacheCon
> > for
> > > Birds-of-Feather on October 4th from 17:50-18:30 CDT in Rhythms I. I
> was
> > > also told that participants can stay after that until the hotel
> > personnels
> > > throw us out.
> > >
> > > Feel free to pass along this information.
> > >
> > > On top of that, I was told that this year's ApacheCon is very popular
> > and a
> > > lot of good talk proposals were not selected. If folks are interested
> I'm
> > > happy to invite you to share online. A physical meetup in the Bay Area
> > > would also be a great idea, if we can find a sponsor.
> > >
> > > Thanks,
> > > Wei-Chiu
> > >
> >
>

Re: Hadoop BoF at ApacheCon NA'22

[俊平堵]

Thanks Wei-Chiu. I am happy to share the status of Hadoop Meetups in China
(2019-2022) if that is a suitable topic. :)

Thanks,

Junping

Wei-Chiu Chuang  于2022年9月21日周三 02:31写道：

> We've not had a physical event for a long long time and we're way overdue
> for one.
>
> I'm excited to announce we've reserved a room at the upcoming ApacheCon for
> Birds-of-Feather on October 4th from 17:50-18:30 CDT in Rhythms I. I was
> also told that participants can stay after that until the hotel personnels
> throw us out.
>
> Feel free to pass along this information.
>
> On top of that, I was told that this year's ApacheCon is very popular and a
> lot of good talk proposals were not selected. If folks are interested I'm
> happy to invite you to share online. A physical meetup in the Bay Area
> would also be a great idea, if we can find a sponsor.
>
> Thanks,
> Wei-Chiu
>

Apache Hadoop Meetup 2022 @Shanghai for Proposal

[俊平堵]

Hello my friends in Hadoop community,

  I am very glad to share you that Apache Hadoop Meetup China 2022
will be held on Sept 24, 2022 in Shanghai. It is the forth time for meetup
in China since 2019 (
https://blogs.apache.org/hadoop/entry/hadoop-community-meetup-beijing-aug)
and there were tremendous wonderful time for passed meetups where we have
great sessions from Cloudera (with Hortonworks), Databricks, Huawei,
Tencent, Alibaba, Intel, ByteDance, Netease, XiaoMi, Didi, MeiTuan, JD,
etc. With over 1000+ in person and 2+ online attendees, it is already
the largest Hadoop party for local community.

   In this year, we will have a keynote forum and 4 break-out
forums including the Infra, AI & ML, Data Warehouse/Lake and Open Data,
based on Hadoop and other open source ecosystem in big data. With over 30
sessions in planning and calling for speakers, we sincerely invite you to
join us as the keynote or breakout session speaker to share your work or
insights around hadoop and big data ecosystem. Although attended in-person
is more prefered, joining remotely or preparing with a pre-recorded video
is also acceptable if you cannot make the attendance in person (20 minutes
for keynotes and 40 minutes for breakout session).

   If you are interested to give a presentation, please submit your
proposal (title + description + self introduction) to me and a local
organizer (hao.ch...@slidestalk.com). Also, free feel to contact us for any
questions or details as always.



Thanks,


Junping

Sep. Y2020 Hadoop Meetup in China

[俊平堵]

Hi,
Last year Aug, we had a very successful meetup in Beijing (
https://blogs.apache.org/hadoop) which help to promote hadoop user adoption
and development locally. This year, we would like to do it again in
Shanghai on 9/26.
 So if you have topic to share on hadoop development or some relevant
 interesting case. Please nominate it by replying this letter or contact me
directly. Slot is limited, first come first serve. Thanks!
  BTW, this meetup is plan to be offline. If many people want to share
but cannot come to Shanghai by then, we can plan something online later.

Thanks,

Junping

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

[俊平堵]

Hi Brahma,
 I think most of us in Hadoop community doesn't want to have biased on
ARM or any other platforms.
 The only thing I try to understand is how much complexity get involved
for our RM work. Does that potentially become a blocker for future
releases? And how we can get rid of this risk.
  If you can list the concrete work that RM need to do extra for ARM
release, that would help us to better understand.

Thanks,

Junping

Akira Ajisaka  于2020年3月13日周五 上午12:34写道：

> If you can provide ARM release for future releases, I'm fine with that.
>
> Thanks,
> Akira
>
> On Thu, Mar 12, 2020 at 9:41 PM Brahma Reddy Battula 
> wrote:
>
> > thanks Akira.
> >
> > Currently only problem is dedicated ARM for future RM.This i want to sort
> > out like below,if you've some other,please let me know.
> >
> > i) Single machine and share cred to future RM ( as we can delete keys
> once
> > release is over).
> > ii) Creating the jenkins project ( may be we need to discuss in the
> > board..)
> > iii) I can provide ARM release for future releases.
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Mar 12, 2020 at 5:14 PM Akira Ajisaka 
> wrote:
> >
> > > Hi Brahma,
> > >
> > > I think we cannot do any of your proposed actions.
> > >
> > >
> >
> http://www.apache.org/legal/release-policy.html#owned-controlled-hardware
> > > > Strictly speaking, releases must be verified on hardware owned and
> > > controlled by the committer. That means hardware the committer has
> > physical
> > > possession and control of and exclusively full administrative/superuser
> > > access to. That's because only such hardware is qualified to hold a PGP
> > > private key, and the release should be verified on the machine the
> > private
> > > key lives on or on a machine as trusted as that.
> > >
> > > https://www.apache.org/dev/release-distribution.html#sigs-and-sums
> > > > Private keys MUST NOT be stored on any ASF machine. Likewise,
> > signatures
> > > for releases MUST NOT be created on ASF machines.
> > >
> > > We need to have dedicated physical ARM machines for each release
> manager,
> > > and now it is not feasible.
> > > If you provide an unofficial ARM binary release in some repository,
> > that's
> > > okay.
> > >
> > > -Akira
> > >
> > > On Thu, Mar 12, 2020 at 7:57 PM Brahma Reddy Battula <
> bra...@apache.org>
> > > wrote:
> > >
> > >> Hello folks,
> > >>
> > >> As currently trunk will support ARM based compilation and qbt(1) is
> > >> running
> > >> from several months with quite stable, hence planning to propose ARM
> > >> binary
> > >> this time.
> > >>
> > >> ( Note : As we'll know voting will be based on the source,so this will
> > not
> > >> issue.)
> > >>
> > >> *Proposed Change:*
> > >> Currently in downloads we are keeping only x86 binary(2),Can we keep
> ARM
> > >> binary also.?
> > >>
> > >> *Actions:*
> > >> a) *Dedicated* *Machine*:
> > >>i) Dedicated ARM machine will be donated which I confirmed
> > >>ii) Or can use jenkins ARM machine itself which is currently
> used
> > >> for ARM
> > >> b) *Automate Release:* How about having one release project in
> > jenkins..?
> > >> So that future RM's just trigger the jenkin project.
> > >>
> > >> Please let me know your thoughts on this.
> > >>
> > >>
> > >> 1.
> > >>
> > >>
> >
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-qbt-linux-ARM-trunk/
> > >> 2.https://hadoop.apache.org/releases.html
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> --Brahma Reddy Battula
> > >>
> > >
> >
> > --
> >
> >
> >
> > --Brahma Reddy Battula
> >
>

Re: [Announcement] DiDi HDFS successfully upgraded from 2.7.2 to 3.2.0

[俊平堵]

That's Awesome! Great to see this great achievement and look forward to
more details/insights on lesson learned for the whole process.

Thanks,

Junping

Runlin zhang  于2019年12月9日周一 上午11:14写道：

> Hi Folks,
>
> This is Runlin Zhang from DiDi. I'm glad to announce that our HDFS has
> just been successfully upgraded from 2.7.2 to 3.2.0， Our cluster has nearly
> 10,000 nodes，Now the cluster services are stable and we are using new
> features, such as EC, that bring huge benefits！ Here I want to thank my
> colleagues for their efforts, Fei Hui, Hu Haiyang, Wang Hongbing, Zhu
> Linhai, Wu Tong; And thanks to the community.
>
> It is also highly recommended that you upgrade the version to 3.2.1, If
> you have any problems in the upgrade, you can also communicate and discuss
> with me.
>
>
> Thanks
> Runlin  Zhang
>

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

[俊平堵]

+1.

Thanks,

Junping

Elek, Marton  于2019年9月17日周二 下午5:48写道：

>
>
> 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
> be part of the source tree but with separated release cadence, mainly
> because it had the hadoop-trunk/SNAPSHOT as compile time dependency.
>
> During the last Ozone releases this dependency is removed to provide
> more stable releases. Instead of using the latest trunk/SNAPSHOT build
> from Hadoop, Ozone uses the latest stable Hadoop (3.2.0 as of now).
>
> As we have no more strict dependency between Hadoop trunk SNAPSHOT and
> Ozone trunk I propose to separate the two code base from each other with
> creating a new Hadoop git repository (apache/hadoop-ozone.git):
>
> With moving Ozone to a separated git repository:
>
>   * It would be easier to contribute and understand the build (as of now
> we always need `-f pom.ozone.xml` as a Maven parameter)
>   * It would be possible to adjust build process without breaking
> Hadoop/Ozone builds.
>   * It would be possible to use different Readme/.asf.yaml/github
> template for the Hadoop Ozone and core Hadoop. (For example the current
> github template [2] has a link to the contribution guideline [3]. Ozone
> has an extended version [4] from this guideline with additional
> information.)
>   * Testing would be more safe as it won't be possible to change core
> Hadoop and Hadoop Ozone in the same patch.
>   * It would be easier to cut branches for Hadoop releases (based on the
> original consensus, Ozone should be removed from all the release
> branches after creating relase branches from trunk)
>
>
> What do you think?
>
> Thanks,
> Marton
>
> [1]:
>
> https://lists.apache.org/thread.html/c85e5263dcc0ca1d13cbbe3bcfb53236784a39111b8c353f60582eb4@%3Chdfs-dev.hadoop.apache.org%3E
> [2]:
>
> https://github.com/apache/hadoop/blob/trunk/.github/pull_request_template.md
> [3]: https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
> [4]:
>
> https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute+to+Ozone
>
> -
> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
>
>

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

[俊平堵]

+1. Please 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 and completed all TODO parts.
>
>
> https://cwiki.apache.org/confluence/display/HADOOP/Submarine+Project+Spin-Off+to+TLP+Proposal
>
> If you have interests to learn more about this. Please review the proposal
> let me know if you have any questions/suggestions for the proposal. This
> will be sent to board post voting passed. (And please note that the
> previous voting thread [2] to move Submarine to a separate Github repo is a
> necessary effort to move Submarine to a separate Apache project but not
> sufficient 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/4a2210d567cbc05af92c12aa6283fd09b857ce209d537986ed800029@%3Cyarn-dev.hadoop.apache.org%3E
> [2]
>
> https://lists.apache.org/thread.html/6e94469ca105d5a15dc63903a541bd21c7ef70b8bcff475a16b5ed73@%3Cyarn-dev.hadoop.apache.org%3E
>

Re: Aug Hadoop Community Meetup in China

[俊平堵]

Hi all,
 Kindly remind that we will have Beijing meetup on 8/10 soon, and the
event will start since 10 am (CST time).
 The link has details on address:
https://docs.google.com/document/d/1wDfyuQv6PDeKZGVdYJw6IfXUa_MIzIstbb8iva6Zt-U/edit?usp=sharing

Thanks,

Junping

俊平堵  于2019年7月23日周二 下午5:07写道：

> Thanks for these positive feedbacks! The local community has voted the
> date and location to be 8/10, Beijing. So please book your time ahead if
> you have interest to join.
> I have gathered a few topics, and some candidate places for hosting this
> meetup. If you would like to propose more topics, please nominate it here
> or ping me before this weekend (7/28, CST time).
> Will update here when I have more to share. thx!
>
>
>
>
> [image: Screen Shot 2019-07-23 at 10.15.54.png]
>
> [image: Screen Shot 2019-07-23 at 10.16.06.png]
>
>
>
> Thanks,
>
> Junping
>
> 俊平堵  于2019年7月18日周四 下午3:28写道：
>
>> Hi, all!
>>
>> I am glad to let you know that we are organizing
>> Hadoop Contributors Meetup in China on Aug.
>>
>>
>> This could be the first time hadoop community meetup in China and many
>> attendees are expected to come from big data pioneers, such as: Cloudera,
>> Tencent, Alibaba, Xiaomi, Didi, JD, Meituan, Toutiao, Sina, etc.
>>
>>
>> We're still working out the details, such as dates, contents and
>> locations. Here is a quick survey: https://www.surveymonkey.com/r/Y99RT3W
>> where you can vote your prefer dates and locations if you would like to
>> attend - the survey will end in July. 21. 12PM China Standard Time, and
>> result will go public in next day.
>>
>>
>> Also, please feel free to reach out to me if you have a topic to propose
>> for the meetup.  Will send out an update later with more details when I get
>> more to share. Thanks!
>>
>>
>> Cheers,
>>
>>
>> Junping
>>
>

Re: [DISCUSS] EOL 2.8 or another 2.8.x release?

[俊平堵]

+1 for 1 more release in 2.8.x. However, it sounds too early to declare 2.8
is EoL. I would prefer to discuss this after seeing most people are
migrated to 2.9 or 3.x.

Thanks,

Junping

Akira Ajisaka  于2019年7月26日周五 下午12:03写道：

> I'm +1 for 1 more release in 2.8.x and declare that 2.8 is EoL.
>
> > would be even happier if we could move people to 2.9.x
> Agreed.
>
> -Akira
>
> On Thu, Jul 25, 2019 at 10:59 PM Steve Loughran
>  wrote:
> >
> > I'm in favour of 1 more release (it fixes the off-by 1 bug in
> > S3AInputStream HADOOP-16109), but would be even happier if we could move
> > people to 2.9.x
> >
> > maybe do a 2.9.x release and declare that 2.8 is EOL?
> >
> >
> > On Thu, Jul 25, 2019 at 2:08 PM Wei-Chiu Chuang 
> wrote:
> >
> > > My bad -- Didn't realize I was looking at the old Hadoop page.
> > > Here's the correct list of releases.
> > > https://hadoop.apache.org/releases.html
> > >
> > > On Thu, Jul 25, 2019 at 12:49 AM 张铎(Duo Zhang) 
> > > wrote:
> > >
> > > > IIRC we have a 2.8.5 release?
> > > >
> > > > On the download page:
> > > >
> > > > 2.8.5 2018 Sep 15
> > > >
> > > > Wei-Chiu Chuang  于2019年7月25日周四 上午9:39写道：
> > > >
> > > > > The last 2.8 release (2.8.4) was made in the last May, more than a
> year
> > > > > ago. https://hadoop.apache.org/old/releases.html
> > > > >
> > > > > How do folks feel about the fate of branch-2.8? During the last
> > > community
> > > > > meetup in June, it sounds like most users are still on 2.8 or even
> 2.7,
> > > > so
> > > > > I don't think we want to abandon 2.8 just yet.
> > > > >
> > > > > I would personally want to urge folks to move up to 3.x, so I can
> stop
> > > > > cherrypicking stuff all the way down into 2.8. But it's not up to
> me
> > > > along
> > > > > to decide :)
> > > > >
> > > > > How do people feel about having another 2.8 release or two? I am
> not
> > > > saying
> > > > > I want to drive it, but I want to raise the awareness that folks
> are
> > > > still
> > > > > on 2.8 and there's not been an update for over a year.
> > > > >
> > > > > Thoughts?
> > > > >
> > > >
> > >
>
> -
> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
>
>

Re: Any thoughts making Submarine a separate Apache project?

[俊平堵]

Thanks Vinod for these great suggestions. I agree most of your comments
above.
 "For the Apache Hadoop community, this will be treated simply as
code-change and so need a committer +1?". IIUC, this should be treated as
feature branch merge, so may be 3 committer +1 is needed here according to
https://hadoop.apache.org/bylaws.html?

bq. Can somebody who have cycles and been on the ASF lists for a while look
into the process here?
I can check with ASF members who has experience on this if no one haven't
yet.

Thanks,

Junping

Vinod Kumar Vavilapalli  于2019年7月29日周一 下午9:46写道：

> Looks like there's a meaningful push behind this.
>
> Given the desire is to fork off Apache Hadoop, you'd want to make sure
> this enthusiasm turns into building a real, independent but more
> importantly a sustainable community.
>
> Given that there were two official releases off the Apache Hadoop project,
> I doubt if you'd need to go through the incubator process. Instead you can
> directly propose a new TLP at ASF board. The last few times this happened
> was with ORC, and long before that with Hive, HBase etc. Can somebody who
> have cycles and been on the ASF lists for a while look into the process
> here?
>
> For the Apache Hadoop community, this will be treated simply as
> code-change and so need a committer +1? You can be more gently by formally
> doing a vote once a process doc 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 without any additional constraints.
>
> Thanks
> +Vinod
>
> > On Jul 25, 2019, at 1:31 PM, Wangda Tan  wrote:
> >
> > 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 bring this up.
> >>
> >> Our CNCF project's open source distributed KV storage system TiKV,
> >> Hadoop submarine's machine learning engine helps us to optimize data
> >> storage,
> >> helping us solve some problems in data hotspots and data shuffers.
> >>
> >> We are ready to improve the performance of TiDB in our open source
> >> distributed relational database TiDB and also using the hadoop submarine
> >> machine learning engine.
> >>
> >> I think if submarine can be independent, it will develop faster and
> better.
> >> Thanks to the hadoop community for developing submarine!
> >>
> >> Best Regards,
> >> neo
> >> www.pingcap.com / https://github.com/pingcap/tidb /
> >> https://github.com/tikv
> >>
> >> Xun Liu  于2019年7月22日周一 下午4:07写道：
> >>
> >>> @adam.antal
> >>>
> >>> The submarine development team has completed the following
> preparations:
> >>> 1. Established a temporary test repository on Github.
> >>> 2. Change the package name of hadoop submarine from
> org.hadoop.submarine
> >> to
> >>> org.submarine
> >>> 3. Combine the Linkedin/TonY code into the Hadoop submarine module;
> >>> 4. On the Github docked travis-ci system, all test cases have been
> >> tested;
> >>> 5. Several Hadoop submarine users completed the system test using the
> >> code
> >>> in this repository.
> >>>
> >>> 赵欣  于2019年7月22日周一 上午9:38写道：
> >>>
>  Hi
> 
>  I am a teacher at Southeast University (https://www.seu.edu.cn/). We
> >> are
>  a major in electrical engineering. Our teaching teams and students use
>  bigoop submarine for big data analysis and automation control of
> >>> electrical
>  equipment.
> 
>  Many thanks to the hadoop community for providing us with machine
> >>> learning
>  tools like submarine.
> 
>  I wish hadoop submarine is getting better and better.
> 
> 
>  ==
>  赵欣
>  东南大学电气工程学院
> 
>  -
> 
>  Zhao XIN
> 
>  School of Electrical Engineering
> 
>  ==
>  2019-07-18
> 
> 
>  *From:* Xun Liu 
>  *Date:* 2019-07-18 09:46
>  *To:* xinzhao 
>  *Subject:* Fwd: Re: Any thoughts making Submarine a separate Apache
>  project?
> 
> 
>  -- Forwarded message -
>  发件人： dashuiguailu...@gmail.com 
>  Date: 2019年7月17日周三 下午3:17
>  Subject: Re: Re: Any thoughts making Submarine a separate Apache
> >> project?
>  To: Szilard Nemeth , runlin zhang <
>  runlin...@gmail.com>
>  Cc: Xun Liu , common-dev <
> >>> common-...@hadoop.apache.org>,
>  yarn-dev , hdfs-dev <
>  hdfs-dev@hadoop.apache.org>, mapreduce-dev <
>  mapreduce-...@hadoop.apache.org>, submarine-dev <
>  submarine-...@hadoop.apache.org>
> 
> 
>  +1 ，Good idea, we are very much looking forward to 

Re: Hadoop Community Sync Up Schedule

[俊平堵]

Hi Folks,

 Kindly remind that we have YARN+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


Thanks,


Junping



Wangda Tan  于2019年6月28日周五 上午2:57写道：

> 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
>
> We gave it a try this week for YARN+MR and Submarine sync, feedbacks from
> participants seems pretty good, lots of new information shared during sync
> up, and companies are using/developing Hadoop can better know each other.
>
> Next week there're 4 community sync-ups (Two Submarine for different
> timezones, one YARN+MR, one storage), please join to whichever you're
> interested:
>
> [image: image.png]
>
> Zoom info and notes can be found in the Google calendar invitation.
>
> Thanks,
> Wangda
>

Re: Aug Hadoop Community Meetup in China

[俊平堵]

Thanks for these positive feedbacks! The local community has voted the date
and location to be 8/10, Beijing. So please book your time ahead if you
have interest to join.
I have gathered a few topics, and some candidate places for hosting this
meetup. If you would like to propose more topics, please nominate it here
or ping me before this weekend (7/28, CST time).
Will update here when I have more to share. thx!




[image: Screen Shot 2019-07-23 at 10.15.54.png]

[image: Screen Shot 2019-07-23 at 10.16.06.png]



Thanks,

Junping

俊平堵  于2019年7月18日周四 下午3:28写道：

> Hi, all!
>
> I am glad to let you know that we are organizing
> Hadoop Contributors Meetup in China on Aug.
>
>
> This could be the first time hadoop community meetup in China and many
> attendees are expected to come from big data pioneers, such as: Cloudera,
> Tencent, Alibaba, Xiaomi, Didi, JD, Meituan, Toutiao, Sina, etc.
>
>
> We're still working out the details, such as dates, contents and
> locations. Here is a quick survey: https://www.surveymonkey.com/r/Y99RT3W
> where you can vote your prefer dates and locations if you would like to
> attend - the survey will end in July. 21. 12PM China Standard Time, and
> result will go public in next day.
>
>
> Also, please feel free to reach out to me if you have a topic to propose
> for the meetup.  Will send out an update later with more details when I get
> more to share. Thanks!
>
>
> Cheers,
>
>
> Junping
>

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

[俊平堵]

Congrats Tao! Well deserve it!

Thanks,

Junping

Weiwei Yang  于2019年7月15日周一 下午5:54写道：

> Hi Dear Apache Hadoop Community
>
> It's my pleasure to announce that Tao Yang has been elected as an Apache
> Hadoop committer, this is to recognize his contributions to Apache Hadoop
> YARN project.
>
> Congratulations and welcome on board!
>
> Weiwei
> (On behalf of the Apache Hadoop PMC)
>

Aug Hadoop Community Meetup in China

[俊平堵]

Hi, all!

I am glad to let you know that we are organizing
Hadoop Contributors Meetup in China on Aug.


This could be the first time hadoop community meetup in China and many
attendees are expected to come from big data pioneers, such as: Cloudera,
Tencent, Alibaba, Xiaomi, Didi, JD, Meituan, Toutiao, Sina, etc.


We're still working out the details, such as dates, contents and locations.
Here is a quick survey: https://www.surveymonkey.com/r/Y99RT3W where you
can vote your prefer dates and locations if you would like to attend - the
survey will end in July. 21. 12PM China Standard Time, and result will go
public in next day.


Also, please feel free to reach out to me if you have a topic to propose
for the meetup.  Will send out an update later with more details when I get
more to share. Thanks!


Cheers,


Junping

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

[俊平堵]

Congrats, Eric!

Thanks,

Junping

Eric Payne  于2019年3月6日周三 上午1:20写道：

> It is my pleasure to announce that Eric Badger has accepted an invitation
> to become a Hadoop Core committer.
>
> Congratulations, Eric! This is well-deserved!
>
> -Eric Payne
>

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

[俊平堵]

Thanks Elek and Anu, it works now. I am sending letters to announce 2.8.5
get released.

Thanks,

Junping

Elek, Marton  于2018年9月23日周日 上午7:50写道：

> Yes. Currently you need to commit the generated site (source + rendered
> site, both are on the same branch).
>
> We can create a jenkins job to do the generation + commit automatically.
>
> I updated the wiki to make it more clean.
>
> Marton
>
> On 9/22/18 10:48 PM, Anu Engineer wrote:
> > I believe that you need to regenerate the site using ‘hugo’ command
> (hugo is a site builder). Then commit and push the generated files.
> >
> > Thanks
> > Anu
> >
> >
> > On 9/22/18, 9:56 AM, "俊平堵"  wrote:
> >
> >  Martin, thanks for your reply. It works now, but after git changes
> - I
> >  haven’t seen Apache Hadoop website get refreshed. It seems like to
> need
> >  some manually steps to refresh the website -if so, can you also
> update to
> >  the wiki?
> >
> >  Thanks,
> >
> >  Junping
> >
> >  Elek, Marton 于2018年9月20日 周四下午1:40写道：
> >
> >  > Please try
> >  >
> >  > git clone https://gitbox.apache.org/repos/asf/hadoop-site.git -b
> asf-site
> >  >
> >      > (It seems git tries to check out master instead of the branch).
> >  >
> >  > I updated the wiki, sorry for the inconvenience.
> >  >
> >  > Marton
> >  >
> >  > On 9/18/18 8:05 PM, 俊平堵 wrote:
> >  > > Hey Marton,
> >  > >   The new release web-site actually doesn't work for me.
> When I
> >  > > follow your steps in wiki, and hit the issue during git clone
> repository
> >  > > (writable) for hadoop-site as below:
> >  > >
> >  > > git clone https://gitbox.apache.org/repos/asf/hadoop-site.git
> >  > > Cloning into 'hadoop-site'...
> >  > > remote: Counting objects: 252414, done.
> >  > > remote: Compressing objects: 100% (29625/29625), done.
> >  > > remote: Total 252414 (delta 219617), reused 252211 (delta
> 219422)
> >  > > Receiving objects: 100% (252414/252414), 98.78 MiB | 3.32
> MiB/s, done.
> >  > > Resolving deltas: 100% (219617/219617), done.
> >  > > warning: remote HEAD refers to nonexistent ref, unable to
> checkout.
> >  > >
> >  > > Can you check above repository is correct for clone?
> >  > > I can clone readable repository (
> https://github.com/apache/hadoop-site)
> >  > > successfully though but cannot push back changes which is
> expected.
> >  > >
> >  > > Thanks,
> >  > >
> >  > > Junping
> >  > >
> >  > > Elek, Marton mailto:e...@apache.org
> >>于2018年9月17日
> >  > > 周一上午6:15写道：
> >  > >
> >  > > Hi Junping,
> >  > >
> >  > > Thank you to work on this release.
> >  > >
> >  > > This release is the first release after the hadoop site
> change, and I
> >  > > would like to be sure that everything works fine.
> >  > >
> >  > > Unfortunately I didn't get permission to edit the old wiki,
> but this
> >  > is
> >  > > definition of the site update on the new wiki:
> >  > >
> >  > >
> >  >
> https://cwiki.apache.org/confluence/display/HADOOP/How+to+generate+and+push+ASF+web+site+after+HADOOP-14163
> >  > >
> >  > > Please let me know if something is not working for you...
> >  > >
> >  > > Thanks,
> >  > > Marton
> >  > >
> >  > >
> >  > > On 09/10/2018 02:00 PM, 俊平堵 wrote:
> >  > >  > Hi all,
> >  > >  >
> >  > >  >   I've created the first release candidate (RC0) for
> Apache
> >  > >  > Hadoop 2.8.5. This is our next point release to follow
> up 2.8.4.
> >  > It
> >  > >  > includes 33 important fixes and improvements.
> >  > >  >
> >  > >  >
> >  > >  >  The RC artifacts are available at:
> >  > >  > http://home.apache.org/~junping_du/hadoop-2.8.5-RC0
> >  > >  >
> >  > >  >
> >  

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

[俊平堵]

Martin, thanks for your reply. It works now, but after git changes - I
haven’t seen Apache Hadoop website get refreshed. It seems like to need
some manually steps to refresh the website -if so, can you also update to
the wiki?

Thanks,

Junping

Elek, Marton 于2018年9月20日 周四下午1:40写道：

> Please try
>
> git clone https://gitbox.apache.org/repos/asf/hadoop-site.git -b asf-site
>
> (It seems git tries to check out master instead of the branch).
>
> I updated the wiki, sorry for the inconvenience.
>
> Marton
>
> On 9/18/18 8:05 PM, 俊平堵 wrote:
> > Hey Marton,
> >   The new release web-site actually doesn't work for me.  When I
> > follow your steps in wiki, and hit the issue during git clone repository
> > (writable) for hadoop-site as below:
> >
> > git clone https://gitbox.apache.org/repos/asf/hadoop-site.git
> > Cloning into 'hadoop-site'...
> > remote: Counting objects: 252414, done.
> > remote: Compressing objects: 100% (29625/29625), done.
> > remote: Total 252414 (delta 219617), reused 252211 (delta 219422)
> > Receiving objects: 100% (252414/252414), 98.78 MiB | 3.32 MiB/s, done.
> > Resolving deltas: 100% (219617/219617), done.
> > warning: remote HEAD refers to nonexistent ref, unable to checkout.
> >
> > Can you check above repository is correct for clone?
> > I can clone readable repository (https://github.com/apache/hadoop-site)
> > successfully though but cannot push back changes which is expected.
> >
> > Thanks,
> >
> > Junping
> >
> > Elek, Marton mailto:e...@apache.org>>于2018年9月17日
> > 周一上午6:15写道：
> >
> > Hi Junping,
> >
> > Thank you to work on this release.
> >
> > This release is the first release after the hadoop site change, and I
> > would like to be sure that everything works fine.
> >
> > Unfortunately I didn't get permission to edit the old wiki, but this
> is
> > definition of the site update on the new wiki:
> >
> >
> https://cwiki.apache.org/confluence/display/HADOOP/How+to+generate+and+push+ASF+web+site+after+HADOOP-14163
> >
> > Please let me know if something is not working for you...
> >
> > Thanks,
> > Marton
> >
> >
> > On 09/10/2018 02:00 PM, 俊平堵 wrote:
> >  > Hi all,
> >  >
> >  >   I've created the first release candidate (RC0) for Apache
> >  > Hadoop 2.8.5. This is our next point release to follow up 2.8.4.
> It
> >  > includes 33 important fixes and improvements.
> >  >
> >  >
> >  >  The RC artifacts are available at:
> >  > http://home.apache.org/~junping_du/hadoop-2.8.5-RC0
> >  >
> >  >
> >  >  The RC tag in git is: release-2.8.5-RC0
> >  >
> >  >
> >  >
> >  >  The maven artifacts are available via repository.apache.org
> > <http://repository.apache.org><
> >  > http://repository.apache.org> at:
> >  >
> >  >
> >
> https://repository.apache.org/content/repositories/orgapachehadoop-1140
> >  >
> >  >
> >  >  Please try the release and vote; the vote will run for the
> > usual 5 working
> >  > days, ending on 9/15/2018 PST time.
> >  >
> >  >
> >  > Thanks,
> >  >
> >  >
> >  > Junping
> >  >
> >
>

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

[俊平堵]

Hey Marton,
 The new release web-site actually doesn't work for me.  When I follow
your steps in wiki, and hit the issue during git clone repository
(writable) for hadoop-site as below:

git clone https://gitbox.apache.org/repos/asf/hadoop-site.git
Cloning into 'hadoop-site'...
remote: Counting objects: 252414, done.
remote: Compressing objects: 100% (29625/29625), done.
remote: Total 252414 (delta 219617), reused 252211 (delta 219422)
Receiving objects: 100% (252414/252414), 98.78 MiB | 3.32 MiB/s, done.
Resolving deltas: 100% (219617/219617), done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.

Can you check above repository is correct for clone?
I can clone readable repository (https://github.com/apache/hadoop-site)
successfully though but cannot push back changes which is expected.

Thanks,

Junping

Elek, Marton 于2018年9月17日 周一上午6:15写道：

> Hi Junping,
>
> Thank you to work on this release.
>
> This release is the first release after the hadoop site change, and I
> would like to be sure that everything works fine.
>
> Unfortunately I didn't get permission to edit the old wiki, but this is
> definition of the site update on the new wiki:
>
>
> https://cwiki.apache.org/confluence/display/HADOOP/How+to+generate+and+push+ASF+web+site+after+HADOOP-14163
>
> Please let me know if something is not working for you...
>
> Thanks,
> Marton
>
>
> On 09/10/2018 02:00 PM, 俊平堵 wrote:
> > Hi all,
> >
> >   I've created the first release candidate (RC0) for Apache
> > Hadoop 2.8.5. This is our next point release to follow up 2.8.4. It
> > includes 33 important fixes and improvements.
> >
> >
> >  The RC artifacts are available at:
> > http://home.apache.org/~junping_du/hadoop-2.8.5-RC0
> >
> >
> >  The RC tag in git is: release-2.8.5-RC0
> >
> >
> >
> >  The maven artifacts are available via repository.apache.org<
> > http://repository.apache.org> at:
> >
> > https://repository.apache.org/content/repositories/orgapachehadoop-1140
> >
> >
> >  Please try the release and vote; the vote will run for the usual 5
> working
> > days, ending on 9/15/2018 PST time.
> >
> >
> > Thanks,
> >
> >
> > Junping
> >
>

[VOTE] [RESULT] Release Apache Hadoop 2.8.5 (RC0)

[俊平堵]

Thanks all who helped to verify and vote!


I give my binding +1 to conclude the vote for 2.8.5 RC0:

- Built from source and verified signatures

- Deployed a small distributed cluster and run simple jobs

- Verified UI of daemons, such as: NN, RM, DN, NM, etc


Now, our RC0 for 2.8.5 got:


6 binding +1s, from:

 Jason Lowe, Eric Payne, Kihwal Lee, Brahma Reddy Battula, Yesha Vora,
Junping Du


4 non-binding +1s, from:

Gabor Bota, Eric Badger, Zsolt Venczel, Kitti Nánási


and no -1s.


So I am glad to announce that the vote for 2.8.5 RC0 passes.


Thanks everyone listed above who tried the release candidate and vote and
all who ever help with 2.8.5 release effort in all kinds of ways.

I'll push the release bits and send out an announcement for 2.8.5 soon.


Thanks,


Junping

Kitti Nánási  于2018年9月13日周四 上午8:34写道：

> Thanks for working on this Junping!
>
> +1 (non-binding)
>
> - checked out git tag release-2.8.5-RC0
> - built from source on Mac OS X 10.13.4, java version 8.0.172-zulu
> - deployed on a 3 node cluster
> - ran terasort, teragen, teravalidate with success
> - executed basic hdfs and dfsadmin commands
>
> Thanks,
> Kitti
>
>
> On Wed, Sep 12, 2018 at 2:37 PM, Yesha Vora  wrote:
>
>> +1 (binding)
>>
>> Tested the following:
>> - launch Pseudo-Distributed 1 node cluster
>> - Tested with word count / teragen / terasort / nnbench/ mrbench on yarn
>> - Validate yarn UI
>> - Test basic yarn cli operations such as -kill, -status, -appStates,
>> -appTypes
>>
>> --
>> Yesha Vora
>>
>>
>> 
>> From: 俊平堵 
>> Sent: Monday, September 10, 2018 5:00 AM
>> To: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org;
>> yarn-...@hadoop.apache.org
>> Cc: junpingdu(堵俊平)
>> Subject: [VOTE] Release Apache Hadoop 2.8.5 (RC0)
>>
>> Hi all,
>>
>>  I've created the first release candidate (RC0) for Apache
>> Hadoop 2.8.5. This is our next point release to follow up 2.8.4. It
>> includes 33 important fixes and improvements.
>>
>>
>> The RC artifacts are available at:
>> http://home.apache.org/~junping_du/hadoop-2.8.5-RC0
>>
>>
>> The RC tag in git is: release-2.8.5-RC0
>>
>>
>>
>> The maven artifacts are available via repository.apache.org<
>> http://repository.apache.org> at:
>>
>> https://repository.apache.org/content/repositories/orgapachehadoop-1140
>>
>>
>> Please try the release and vote; the vote will run for the usual 5
>> working
>> days, ending on 9/15/2018 PST time.
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> -
>> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
>> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
>>
>>
>

[VOTE] Release Apache Hadoop 2.8.5 (RC0)

[俊平堵]

Hi all,

 I've created the first release candidate (RC0) for Apache
Hadoop 2.8.5. This is our next point release to follow up 2.8.4. It
includes 33 important fixes and improvements.


The RC artifacts are available at:
http://home.apache.org/~junping_du/hadoop-2.8.5-RC0


The RC tag in git is: release-2.8.5-RC0



The maven artifacts are available via repository.apache.org<
http://repository.apache.org> at:

https://repository.apache.org/content/repositories/orgapachehadoop-1140


Please try the release and vote; the vote will run for the usual 5 working
days, ending on 9/15/2018 PST time.


Thanks,


Junping

Re: [DISCUSS] Alpha Release of Ozone

[俊平堵]

+1. Good to see the progress here and would like to try Ozone on real
cluster.

Thanks,

Junping

2018-08-07 1:34 GMT+08:00 Elek, Marton :

> Hi All,
>
> I would like to discuss creating an Alpha release for Ozone. The core
> functionality of Ozone is complete but there are two missing features;
> Security and HA, work on these features are progressing in Branches HDDS-4
> and HDDS-151. Right now, Ozone can handle millions of keys and has a Hadoop
> compatible file system, which allows applications like Hive, Spark, and
> YARN use Ozone.
>
> Having an Alpha release of Ozone will help in getting some early feedback
> (this release will be marked as an Alpha -- and not production ready).
>
> Going through a complete release cycle will help us flush out Ozone
> release process, update user documentation and nail down deployment models.
>
> Please share your thoughts on the Alpha release (over mail or in
> HDDS-214), as voted on by the community earlier, Ozone release will be
> independent of Hadoop releases.
>
> Thanks a lot,
> Marton Elek
>
>
>
>
> -
> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
>
>

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

[俊平堵]

Thanks all who helped to verify and vote!


I give my binding +1 to conclude the vote for 2.8.4 RC0:

- Built from source and verified signatures

- Deployed a small distributed cluster and run some simple job, like: pi,
sleep, terasort, etc.

- Verified UI of daemons, like: NameNode, DataNode, ResourceManager,
NodeManager, etc


Now, our RC0 for 2.8.4 got:


7 binding +1s, from:

 Sammi Chen, Mingliang Liu, Rohith Sharma K S, Sunil G, Wangda Tan,
Brahma Reddy Battula, Junping Du


4 non-binding +1s, from:

Ajay Kumar, Gabor Bota, Takanobu Asanuma, Zsolt Venczel


and no -1s.


So I am glad to announce that the vote for 2.8.4 RC0 passes.


Thanks everyone listed above who tried the release candidate and vote and
all who ever help with 2.8.4 release effort in all kinds of ways.

I'll push the release bits and send out an announcement for 2.8.4 soon.


Thanks,


Junping


2018-05-09 1:41 GMT+08:00 俊平堵 <junping...@apache.org>:

> Hi all,
>  I've created the first release candidate (RC0) for Apache Hadoop
> 2.8.4. This is our next maint release to follow up 2.8.3. It includes 77
> important fixes and improvements.
>
> The RC artifacts are available at: http://home.apache.org/~
> junping_du/hadoop-2.8.4-RC0
>
> The RC tag in git is: release-2.8.4-RC0
>
> The maven artifacts are available via repository.apache.org<http://
> repository.apache.org> at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1118
>
> Please try the release and vote; the vote will run for the usual 5
> working days, ending on 5/14/2018 PST time.
>
> Thanks,
>
> Junping
>

[VOTE] Release Apache Hadoop 2.8.4 (RC0)

[俊平堵]

Hi all,
 I've created the first release candidate (RC0) for Apache Hadoop
2.8.4. This is our next maint release to follow up 2.8.3. It includes 77
important fixes and improvements.

The RC artifacts are available at:
http://home.apache.org/~junping_du/hadoop-2.8.4-RC0

The RC tag in git is: release-2.8.4-RC0

The maven artifacts are available via repository.apache.org<
http://repository.apache.org> at:
https://repository.apache.org/content/repositories/orgapachehadoop-1118

Please try the release and vote; the vote will run for the usual 5
working days, ending on 5/14/2018 PST time.

Thanks,

Junping

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

[俊平堵]

Thanks Sammi for working on this!

+1 (binding), based on::
- built from source successfully
- verified signature is correct
- deployed a pseudo cluster and run some simple MR jobs (PI, sleep, etc.)
- checked HDFS/YARN daemons' UI are normal.

Thanks,

Junping
Chen, Sammi 于2018年4月19日 周四下午4:58写道：

> Hi all,
>
> This is the first dot release of Apache Hadoop 2.9 line since 2.9.0 was
> released on November 17, 2017.
>
> It includes 208 changes. Among them, 9 blockers, 15 critical issues and
> rest are normal bug fixes and feature improvements.
>
> Thanks to the many who contributed to the 2.9.1 development.
>
> The artifacts are available here:
> https://dist.apache.org/repos/dist/dev/hadoop/2.9.1-RC0/
>
> The RC tag in git is release-2.9.1-RC0. Last git commit SHA is
> e30710aea4e6e55e69372929106cf119af06fd0e.
>
> The maven artifacts are available at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1115/
>
> My public key is available from:
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>
> Please try the release and vote; the vote will run for the usual 5 days,
> ending on 4/25/2018 PST time.
>
> Also I would like thank Lei(Eddy) Xu and Chris Douglas for your help
> during the RC preparation.
>
> Bests,
> Sammi Chen
>

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

[俊平堵]

Thanks for reporting the issue, Rushabh! Actually, we found that these test
failures belong to test issues but not production issue, so not really a
solid blocker for release. Anyway, I will let RM of 2.9.1 to decide if to
cancel RC or not for this test issue.

Thanks,

Junping


Chen, Sammi 于2018年4月24日 周二下午7:50写道：

> Hi Rushabh,
>
> Thanks for reporting the issue.  I will upload a new RC candidate soon
> after the test failing issue is resolved.
>
>
> Bests,
> Sammi Chen
> From: Rushabh Shah [mailto:rusha...@oath.com]
> Sent: Friday, April 20, 2018 5:12 AM
> To: Chen, Sammi 
> Cc: Hadoop Common ; hdfs-dev <
> hdfs-dev@hadoop.apache.org>; mapreduce-...@hadoop.apache.org;
> yarn-...@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.9.1 (RC0)
>
> Hi Chen,
> I am so sorry to bring this up now but there are 16 tests failing in
> hadoop-distcp project.
> I have opened a ticket and cc'ed Junping since he is branch-2.8 committer
> but I missed to ping you.
>
> IMHO we should fix the unit tests before we release but I would leave upto
> other members to give their opinion.
>
>

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

[俊平堵]

Thanks Lei for the work!

+1 (binding), base on following verification work:
- built succeed from source
- verified signature
- deployed a pseudo cluster and run some simple MR jobs (PI, sleep,
terasort, etc.)
- checked HDFS/YARN daemons' UI
- Tried some rolling upgrade related features: MR over DistributedCache, NM
Restart with work preserving, etc.

Thanks,

Junping

2018-04-17 7:59 GMT+08:00 Lei Xu :

> Hi, All
>
> I've created release candidate RC-1 for Apache Hadoop 3.0.2, to
> address missing source jars in the maven repository in RC-0.
>
> Thanks Ajay Kumar for spotting the error.
>
> Please note: this is an amendment for Apache Hadoop 3.0.1 release to
> fix shaded jars in apache maven repository. The codebase of 3.0.2
> release is the same as 3.0.1.  New bug fixes will be included in
> Apache Hadoop 3.0.3 instead.
>
> The release page is:
> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.0+Release
>
> New RC is available at: http://home.apache.org/~lei/hadoop-3.0.2-RC1/
>
> The git tag is release-3.0.2-RC1, and the latest commit is
> 5c141f7c0f24c12cb8704a6ccc1ff8ec991f41ee, which is the same as RC-0.
>
> The maven artifacts are available at:
> https://repository.apache.org/content/repositories/orgapachehadoop-1102/
>
> Please try the release, especially, *verify the maven artifacts*, and vote.
>
> The vote will run 5 days, ending 4/21/2018.
>
> Here is my +1.
>
> Best,
>
> -
> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
>
>

[DISCUSS] Apache Hadoop 2.8.4 Release Plan

[俊平堵]

Hi my community friends,
With 3.0.1 and 3.1.0 release coming out successfully (thanks to the
great work from Eddy and Wangda), I am planning to do a maintenance release
for 2.8.4 in next few weeks. This release already includes 65 fixes - some
of them are outstanding issues. The reminding critial issues are listed in:
https://s.apache.org/SQce. I am going to move out some issues that had no
progress for a while and keep watching for the left, so please help me to
check non of them belongs to blockers. If there are any other outstanding
issues or work that you think it should be included in 2.8.4, please call
it out here. Thanks!

Thanks,

Junping

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

[俊平堵]

Thanks Wangda for the great work! Sorry for my late coming +1 (binding),
based on:

- Verified signatures

- Verified checksums for source and binary artifacts

- Built from source

- Deployed a single node cluster

- Verified web UIs, include Namenode, RM, etc.

* Tried shell commands of HDFS and YARN

* Ran sample MR jobs, include PI, Sleep, Terasort, etc.


Thanks,


Junping



Wangda Tan 于2018年3月30日 周五下午12:15写道：

> Hi folks,
>
> Thanks to the many who helped with this release since Dec 2017 [1]. We've
> created RC1 for Apache Hadoop 3.1.0. The artifacts are available here:
>
> http://people.apache.org/~wangda/hadoop-3.1.0-RC1
>
> The RC tag in git is release-3.1.0-RC1. Last git commit SHA is
> 16b70619a24cdcf5d3b0fcf4b58ca77238ccbe6d
>
> The maven artifacts are available via repository.apache.org at
> https://repository.apache.org/content/repositories/orgapachehadoop-1090/
> This vote will run 5 days, ending on Apr 3 at 11:59 pm Pacific.
>
> 3.1.0 contains 766 [2] fixed JIRA issues since 3.0.0. Notable additions
> include the first class GPU/FPGA support on YARN, Native services, Support
> rich placement constraints in YARN, S3-related enhancements, allow HDFS
> block replicas to be provided by an external storage system, etc.
>
> For 3.1.0 RC0 vote discussion, please see [3].
>
> We’d like to use this as a starting release for 3.1.x [1], depending on how
> it goes, get it stabilized and potentially use a 3.1.1 in several weeks as
> the stable release.
>
> We have done testing with a pseudo cluster:
> - Ran distributed job.
> - GPU scheduling/isolation.
> - Placement constraints (intra-application anti-affinity) by using
> distributed shell.
>
> My +1 to start.
>
> Best,
> Wangda/Vinod
>
> [1]
>
> https://lists.apache.org/thread.html/b3fb3b6da8b6357a68513a6dfd104bc9e19e559aedc5ebedb4ca08c8@%3Cyarn-dev.hadoop.apache.org%3E
> [2] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND fixVersion in (3.1.0)
> AND fixVersion not in (3.0.0, 3.0.0-beta1) AND status = Resolved ORDER BY
> fixVersion ASC
> [3]
>
> https://lists.apache.org/thread.html/b3a7dc075b7329fd660f65b48237d72d4061f26f83547e41d0983ea6@%3Cyarn-dev.hadoop.apache.org%3E
>

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

[俊平堵]

Hi Wanda,
 Thanks for the release effort on 3.1.0. Another reminder is I tried to
verify the signature of RC0 bits but found there is no known key get
uploaded to
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS. Would you
please upload it there then we can go ahead to verify the signature of
following RCs.Thanks!

Thanks,

Junping

Wangda Tan 于2018年3月30日 周五上午12:01写道：

> Thanks all for doing testing and reporting issues.
>
> YARN-8085 discovered by Weiwei/Tao is a blocker, we will roll an RC1 today.
>
> - Wangda
>
> On Thu, Mar 29, 2018 at 7:26 AM, Weiwei Yang 
> wrote:
>
> > Hi Wangda
> >
> > While testing the build, we found a bug https://issues.apache.org/
> > jira/browse/YARN-8085, it might cause NPE during RM fail-over. I think
> > that needs to be included in 3.1.0.
> >
> > We have run some other tests, and they look good so far. This includes
> > - Some basic teragen/terasort/DS jobs
> > - Various of metrics, UI displays, compatible tests
> > - Creating queues, different queue configurations
> > - Verified RM fail-over, app-recovery
> > - Enabled async scheduling
> > - Enabled placement constraints
> > - SLS tests
> >
> > Hope it helps.
> > Thanks
> >
> > --
> > Weiwei
> >
> > On 29 Mar 2018, 12:34 PM +0800, Ajay Kumar ,
> > wrote:
> >
> > +1 (non-binding)
> >
> > - verified binary checksum
> > - built from source and setup 4 node cluster
> > - run basic hdfs command
> > - run wordcount, pi & TestDFSIO (read/write)
> >
> > Ajay
> >
> > On 3/28/18, 5:45 PM, "Jonathan Hung"  wrote:
> >
> > Hi Wangda, thanks for handling this release.
> >
> > +1 (non-binding)
> >
> > - verified binary checksum
> > - launched single node RM
> > - verified refreshQueues functionality
> > - verified capacity scheduler conf mutation disabled in this case
> > - verified capacity scheduler conf mutation with leveldb storage
> > - verified refreshQueues mutation is disabled in this case
> >
> >
> > Jonathan Hung
> >
> > On Thu, Mar 22, 2018 at 9:10 AM, Wangda Tan  wrote:
> >
> > Thanks @Bharat for the quick check, the previously staged repository has
> > some issues. I re-deployed jars to nexus.
> >
> > Here's the new repo (1087)
> >
> > https://repository.apache.org/content/repositories/orgapachehadoop-1087/
> >
> > Other artifacts remain same, no additional code changes.
> >
> > On Wed, Mar 21, 2018 at 11:54 PM, Bharat Viswanadham <
> > bviswanad...@hortonworks.com> wrote:
> >
> > Hi Wangda,
> > Maven Artifact repositories is not having all Hadoop jars. (It is missing
> > many like hadoop-hdfs, hadoop-client etc.,)
> > https://repository.apache.org/content/repositories/orgapachehadoop-1086/
> >
> >
> > Thanks,
> > Bharat
> >
> >
> > On 3/21/18, 11:44 PM, "Wangda Tan"  wrote:
> >
> > Hi folks,
> >
> > Thanks to the many who helped with this release since Dec 2017 [1].
> > We've
> > created RC0 for Apache Hadoop 3.1.0. The artifacts are available
> >
> > here:
> >
> >
> > http://people.apache.org/~wangda/hadoop-3.1.0-RC0/
> >
> > The RC tag in git is release-3.1.0-RC0.
> >
> > The maven artifacts are available via repository.apache.org at
> > https://repository.apache.org/content/repositories/
> > orgapachehadoop-1086/
> >
> > This vote will run 7 days (5 weekdays), ending on Mar 28 at 11:59 pm
> > Pacific.
> >
> > 3.1.0 contains 727 [2] fixed JIRA issues since 3.0.0. Notable
> >
> > additions
> >
> > include the first class GPU/FPGA support on YARN, Native services,
> > Support
> > rich placement constraints in YARN, S3-related enhancements, allow
> >
> > HDFS
> >
> > block replicas to be provided by an external storage system, etc.
> >
> > We’d like to use this as a starting release for 3.1.x [1], depending
> > on how
> > it goes, get it stabilized and potentially use a 3.1.1 in several
> > weeks as
> > the stable release.
> >
> > We have done testing with a pseudo cluster and distributed shell job.
> > My +1
> > to start.
> >
> > Best,
> > Wangda/Vinod
> >
> > [1]
> > https://lists.apache.org/thread.html/b3fb3b6da8b6357a68513a6dfd104b
> > c9e19e559aedc5ebedb4ca08c8@%3Cyarn-dev.hadoop.apache.org%3E
> > [2] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND fixVersion in
> > (3.1.0)
> > AND fixVersion not in (3.0.0, 3.0.0-beta1) AND status = Resolved
> >
> > ORDER
> >
> > BY
> > fixVersion ASC
> >
> >
> >
> >
> >
> >
> > B�CB�
> > �[��X��ܚX�KK[XZ[���Y]�][��X��ܚX�PY
> ���\X�K�ܙ�B��܈Y][ۘ[��[X[��K[XZ[���Y]�Z[Y
> > ���\X�K�ܙ�B�
> >
> >
>

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

[俊平堵]

I think the proposal here is the right way to get consensus from each part
of community. +1 (binding)
Thanks Owen for driving this.


Thanks,

Junping

2018-03-21 2:20 GMT+08:00 Owen O'Malley :

> All,
>
> Following our discussions on the previous thread (Merging branch HDFS-7240
> to trunk), I'd like to propose the following:
>
> * HDSL become a subproject of Hadoop.
> * HDSL will release separately from Hadoop. Hadoop releases will not
> contain HDSL and vice versa.
> * HDSL will get its own jira instance so that the release tags stay
> separate.
> * On trunk (as opposed to release branches) HDSL will be a separate module
> in Hadoop's source tree. This will enable the HDSL to work on their trunk
> and the Hadoop trunk without making releases for every change.
> * Hadoop's trunk will only build HDSL if a non-default profile is enabled.
> * When Hadoop creates a release branch, the RM will delete the HDSL module
> from the branch.
> * HDSL will have their own Yetus checks and won't cause failures in the
> Hadoop patch check.
>
> I think this accomplishes most of the goals of encouraging HDSL development
> while minimizing the potential for disruption of HDFS development.
>
> The vote will run the standard 7 days and requires a lazy 2/3 vote. PMC
> votes are binding, but everyone is encouraged to vote.
>
> +1 (binding)
>
> .. Owen
>

[ANNOUNCE] Apache Hadoop 2.8.3 Release

[俊平堵]

Hi all,

I am pleased to announce that the Apache Hadoop community has voted to
release Apache Hadoop 2.8.3!

Apache Hadoop 2.8.3 is the next GA release of Apache Hadoop 2.8 line, which
include
79 fixes identified for previous Hadoop 2.8.2 releases:
 - For major changes included in Hadoop 2.8 line, please refer Hadoop 2.8.3
main page [1].
 - For more details about fixes in 2.8.3 release, please read the log of
CHANGES [2] and RELEASENOTES [3].

The release news is posted on the Hadoop website too, you can go to the
downloads section directly [4].

Thank you all for contributing to the Apache Hadoop!


Cheers,


Junping

[1] http://hadoop.apache.org/docs/r2.8.3/index.html

[2]
http://hadoop.apache.org/docs/r2.8.3/hadoop-project-dist/hadoop-common/release/2.8.3/CHANGES.2.8.3.html

[3]
http://hadoop.apache.org/docs/r2.8.3/hadoop-project-dist/hadoop-common/release/2.8.3/RELEASENOTES.2.8.3.html

[4] http://hadoop.apache.org/releases.html#Download

Re: Cutting branch-2.9

[俊平堵]

Hi Arun/Subru,
Thanks for updating on 2.9.0 release progress. A quick question here:
are we planning to release from branch-2.9 directly?
I doubt this as it seems against our current branch release practice (
https://wiki.apache.org/hadoop/HowToRelease#Branching). To get rid of any
confusion, I would suggest to cut-off branch-2.9.0 for 2.9.0 release work.
In the mean time, branch-2.9 should be reserved for next 2.9 point release
(2.9.1) and branch-2 should be reserved for next minor release (2.10.0 or
whatever name it is). Thoughts?

bq. @Junping, lets move the jdiff conversation to separate thread.
Sure. I will reply jdiff in separated thread.

Thanks,

Junping

2017-10-31 13:44 GMT-07:00 Arun Suresh :

> Hello folks
>
> We just cut branch-2.9 since all the critical/blocker issues are now
> resolved.
> We plan to perform some sanity checks for the rest of the week and cut
> branch-2.9.0 and push out an RC0 by the end of the week.
>
> Kindly refrain from committing to branch-2.9 without giving us a heads up.
>
> @Junping, lets move the jdiff conversation to separate thread.
>
> Cheers
> -Arun/Subru
>
> On Mon, Oct 30, 2017 at 12:39 PM, Subru Krishnan  wrote:
>
> > We want to give heads up that we are going to cut branch-2.9 tomorrow
> > morning.
> >
> > We are down to 3 blockers and they all are close to being committed
> > (thanks everyone):
> > https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.9+Release
> >
> > There are 4 other non-blocker JIRAs that are targeted for 2.9.0 which are
> > close to completion.
> >
> > Folks who are working/reviewing these, kindly prioritize accordingly so
> > that we can make the release on time.
> > https://issues.apache.org/jira/browse/YARN-7398?filter=12342468
> >
> > Thanks in advance!
> >
> > -Subru/Arun
> >
> >
> >
>

Re: [DISCUSS] Release numbering semantics with concurrent (>2) releases [Was Setting JIRA fix versions for 3.0.0 releases]

[俊平堵]

Thanks Vinod for bringing up this topic for discussion. I share the same
concern here from my previous experience and I doubt some simple rules
proposed below could make life easier.

> The question now is what we do for the 2.8.0 and 3.0.0-alpha1 fix
versions.
> Allen's historical perspective is that we've based each minor or major
> release off of the previous minor release. So, 2.8.0 would be based off of
> 2.7.0. Assuming 3.0.0-alpha1 happens before 2.8.0, 3.0.0-alpha1 would also
> be based off of 2.7.0. This also makes sense from a user POV; someone on a
> 2.6.x going to 3.0.0-alpha1 can look at the 2.7.0 and 3.0.0-alpha1 notes
to
> see what's changed.
This is not correct - not reflecting the past and not helpful for the
future. There is no benefit to claim 3.0.0-alpha1 is based on 2.7.0 over
2.7.3 (in case 2.8.0 is not there).
In the past, for example, when we cut off 2.7, we already have 2.6.0 and
2.6.1 get released, so 2.7.0 take all commits from 2.6.1 (not 2.6.0). In
future, assume when we start the release effor of 3.1.0 and we have 3.0.1,
3.0.2, etc., 3.0.x should be more stable than 3.0.0-alpha, so there is
unnecessary to do everything from scratch (3.0.0-alpha). So the rule here
should be: a new major or minor release should come from a release:
1. tag with stable
2. released latest
3. with maximum version number
If condition 2 and 3 get conflicts, we should give priority to 3. For
example, when 3.0.0-alpha1 is about to release, assume we have 2.8.0, 2.7.4
and 2.7.4 get released after 2.8.0, then we should claim 3.0.0-alpha is
based on 2.8.0 instead of 2.7.4.


> As an example, if a JIRA was committed to branch-2.6, branch-2.7,
branch-2,
> branch-3.0.0-alpha1, and trunk, it could have fix versions of 2.6.5,
2.7.3,
> 2.8.0, 3.0.0-alpha1. The first two fix versions come from application of
> rule 1, and the last two fix versions come from rule 2.
I don't think setting version tags to be more than 3 is a good practice.
The example above means we need to backport this patch to 5 branches which
make our committers' life really tough - it requires more effort of
committing a patch and also increases the risky of bugs that caused by
backport. Given realistic community review bandwidth (please check another
thread from Chris D.), I strongly suggest we keep active release train to
be less than 3, so we can have 2 stable release or 1 stable release + 1
alpha release in releasing.

BTW, I never see we have a clear definition for alpha release. It is
previously used as unstable in API definition (2.1-alpha, 2.2-alpha, etc.)
but sometimes means unstable in production quality (2.7.0). I think we
should clearly define it with major consensus so user won't
misunderstanding the risky here.
Also, if we treat our 3.0.0-alpha release work seriously, we should also
think about trunk's version number issue (bump up to 4.0.0-alpha?) or there
could be no room for 3.0 incompatible feature/bits soon.

Just 2 cents.

Thanks,

Junping

2016-07-27 15:34 GMT+01:00 Karthik Kambatla :

> Inline.
>
> > 1) Set the fix version for all a.b.c versions, where c > 0.
> > 2) For each major release line, set the lowest a.b.0 version.
> >
>
> Sounds reasonable.
>
>
> >
> > The -alphaX versions we're using leading up to 3.0.0 GA can be treated as
> > a.b.c versions, with alpha1 being the a.b.0 release.
> >
>
> Once 3.0.0 GA goes out, a user would want to see the diff from the latest
> 2.x.0 release (say 2.9.0).
>
> Are you suggesting 3.0.0 GA would have c = 5 (say) and hence rule 1 would
> apply, and it should show up in the release notes?
>
>
> >
> > As an example, if a JIRA was committed to branch-2.6, branch-2.7,
> branch-2,
> > branch-3.0.0-alpha1, and trunk, it could have fix versions of 2.6.5,
> 2.7.3,
> > 2.8.0, 3.0.0-alpha1. The first two fix versions come from application of
> > rule 1, and the last two fix versions come from rule 2.
> >
> > I'm very eager to move this discussion forward, so feel free to reach out
> > on or off list if I can help with anything.
> >
>
>
> I think it is good practice to set multiple fix versions. However, it might
> take the committers a little bit to learn.
>
> Since the plan is to cut 3.0.0 off trunk, can we just bulk edit to add the
> 3.0.0-alphaX version?
>
>
> >
> > Best,
> > Andrew
> >
>

Re: [DISCUSSION] Release Plan for Apache Hadoop 2.6.4

[俊平堵]

Thanks Akira and Eric for the feedback and help here. Our gap between
target commits (http://s.apache.org/JpE) and fixed commits (
http://s.apache.org/vJB) are much smaller now (from 37 to 15) for 2.6.4 in
passed week due to everyone's hard work.
I hope we can reduce the gap to be 0 in the coming week. In the mean while,
the branch out effort for 2.6.4 will wait for vote result of 2.7.2 for the
next step.

Cheers,

Junping

2016-01-08 7:55 GMT+00:00 Akira AJISAKA :

> +1 for releasing 2.6.4 after release 2.7.2.
> I'll work on the list [2].
>
> Thanks,
> Akira
>
>
> On 1/7/16 08:59, Junping Du wrote:
>
>> Hello folks,
>> Hope everyone had a wonderful holiday and good rest in passed
>> weeks. We just had a 2.6.3 release on Dec.17 and now it is a good time to
>> look forward to the next branch-2.6 maintenance release - 2.6.4 in the
>> beginning of new year. As usual, this release will be based on latest
>> release 2.6.3 but include a couple of critical/blocker bug fixes that
>> identified in community recently.
>>
>> Things Done/TODO:
>>
>>+ Schedule
>>  -- According to previous email discussion thread in community, we
>> are prefering fast-moving way (roughly as monthly) of releasing fixes on
>> branch-2.6. So I would expect this release could happen around end of Jan.
>> or early of Feb. dependens on if RC & VOTE process going on smoothly. Also,
>> it should be after release 2.7.2 to get rid of any possible disturb to that
>> release.
>>
>>+ Branch
>>  -- 2.6.4 will be based on branch-2.6, which has been open to 2.6.4
>> commits for a while. I plan to branch out branch-2.6.4 sometime next week
>> according to status of target/fixed fixes.
>>  -- Before 2.6.4 branch is cut off, new commits coming as fix to
>> 2.6.4 is good to commit/merge to trunk, branch-2 and branch-2.6.
>>
>>+ Patches
>>  -- In last couple of days, I went through all critial/blocker bug
>> fixes in the coming 2.7.2 release and ping authors/committers on JIRA to
>> ask for the same effort on branch-2.6.4. I could do more rounds of the same
>> practice in case I could miss something helpful. Also, a kindly reminder
>> from original author and committer is also appreciated.
>>  -- So far, 2.6.4 already has 18 fixes as list of [1] shows. However,
>> there are totally 55 fixes target for 2.6.4 for now [2], so there is still
>> a large gap and we need to work harder to resolve these tickets as many as
>> we can and push out some non-critical ones to meet our promise of date.
>>
>>+ Release
>>  -- Still too early to do anything directly related to RC. Will work
>> on resolve fixes in list of [2] first, and appreciate any help on this
>> effort.
>>
>> Any thoughts? Especially on schedule and list of patches that should be
>> included?
>>
>>
>> Cheers,
>>
>> Junping
>>
>> [1] Tickets fixed in 2.6.4:
>> http://s.apache.org/vJB
>>
>> [2] Tickets targets for 2.6.4:
>> http://s.apache.org/JpE
>>
>>
>> 
>> From: Junping Du
>> Sent: Thursday, December 17, 2015 1:36 PM
>> To: common-...@hadoop.apache.org; yarn-...@hadoop.apache.org
>> Cc: hdfs-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org;
>> junping...@apache.org
>> Subject: [RESULT] [VOTE] Release Apache Hadoop 2.6.3 RC0
>>
>> Hi all in community,
>>   I give my binding +1 to close the vote for 2.6.3 RC0. With 18 +1s
>> (10 binding), one +0 (non-binding) and no -1s, the vote passes.
>>
>> Thanks for everyone who tried the release candidate and voted. Thanks
>> Vinod, Sangjin and Steve to provide me advices on release process.
>>
>> I'll push the release bits and send out an announcement for 2.6.3 soon.
>>
>> Cheers,
>>
>> Junping
>> 
>> From: Xuan Gong 
>> Sent: Thursday, December 17, 2015 12:29 AM
>> To: common-...@hadoop.apache.org
>> Cc: hdfs-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org;
>> yarn-...@hadoop.apache.org; junping...@apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.6.3 RC0
>>
>> +1 (binding),
>>
>> Build and deploy the cluster from source code.
>> Ran a few example jobs and passed successfully.
>>
>> Xuan Gong
>>
>> On Dec 16, 2015, at 4:07 PM, Arpit Agarwal 
>>> wrote:
>>>
>>> +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:
>>>
>>>
 Hi all developers in hadoop community,
   I've created a release candidate RC0 for Apache Hadoop 2.6.3 (the
 next maintenance release to follow up 2.6.2.) according to email thread of
 release plan 2.6.3 [1]. Sorry for this RC coming a bit late as several
 blocker issues were getting committed until