, NodeManager,
etc
- Verify rolling upgrade features from 2.7.4, include MR over distributed
cache, NM restart with work preserving, etc.
Now, we have:
8 binding +1s, from:
Eric Payne, Jason Lowe, Jian He, Wangda Tan, Rohith Sharma K S, Sunil G,
Naganarasimha Garla, Junping Du
5 non
Thanks Andrew for pushing new RC for 3.0.0. I was out last week, just get
chance to validate new RC now.
Basically, I found two critical issues with the same rolling upgrade scenario
as where HADOOP-15059 get found previously:
HDFS-12920, we changed value format for some hdfs configurations that
Junping Du created HDFS-12920:
-
Summary: HDFS default value change (with adding time unit) breaks
old version MR tarball work with new version (3.0) of hadoop
Key: HDFS-12920
URL: https://issues.apache.org/jira
your md5 checksum for given source tar ball?
Thanks,
Junping
From: Konstantin Shvachko
Sent: Saturday, December 9, 2017 11:06 AM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apach
necessary to extend the voting period for a
few more days. But please try as much as possible to verify our release bits.
Thanks!
Thanks,
Junping?
From: Eric Payne
Sent: Monday, December 11, 2017 1:51 PM
To: Junping Du; common-...@hadoop.apache.org; hdfs-dev
Hi all,
I've created the first release candidate (RC0) for Apache Hadoop 2.8.3.
This is our next maint release to follow up 2.8.2. It includes 79 important
fixes and improvements.
The RC artifacts are available at:
http://home.apache.org/~junping_du/hadoop-2.8.3-RC0
The RC tag
PM
To: Junping Du; Konstantin Shvachko
Cc: Wangda Tan; Andrew Wang; Zheng, Kai; common-...@hadoop.apache.org;
hdfs-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org;
yarn-...@hadoop.apache.org
Subject: Re: Apache Hadoop 2.8.3 Release Plan
Agree with Konstantin. This two issues has been opened
ations shouldn't
be recognized as "rolling". Do I miss anything?
Thanks,
Junping
From: Andrew Wang
Sent: Wednesday, November 15, 2017 10:34 AM
To: Junping Du
Cc: Wangda Tan; Steve Loughran; Vinod Kumar Vavilapalli; Kai Zheng; Arun
Suresh;
Just filed HADOOP-15059 to track this.
Thanks,
Junping
From: Junping Du
Sent: Tuesday, November 21, 2017 1:09 PM
To: Vinod Kumar Vavilapalli; Allen Wittenauer
Cc: common-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; hdfs
Another issue I just found is we have token format compatibility issue between
2.x and 3.0. I tried to run a simple MR job on 3.0 RC0 against with 2.9.0
tarball which is failed. This incompatibility change should also break other
applications which will break rolling upgrade.
I think it is anoth
ocker/critical fixes landing on branch-2.8.3. RC0 will
get cut-off shortly.
Thanks,
Junping
From: Wangda Tan
Sent: Tuesday, November 21, 2017 10:52 AM
To: Andrew Wang
Cc: Junping Du; Zheng, Kai; common-...@hadoop.apache.org;
hdfs-dev@hadoop.apache.org; mapr
Zheng, Kai
Cc: Junping Du; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: Apache Hadoop 2.8.3 Release Plan
I'm against including new features in maintenance releases, since they're meant
to be bug-fix
I did following verification work:
- build succeed from source
- verify signature
- deploy a pseudo cluster and run some simple MR jobs
- Check HDFS/YARN daemons' UI
- Verify commit history matching with JIRA's fix version (which will be
included in site document).
Most works fine, except I foun
Thanks Vinod to bring up this discussion, which is just in time.
I agree with most responses that option C is not a good choice as our community
bandwidth is precious and we should focus on very limited mainstream branches
to develop, test and deployment. Of course, we should still follow Apache
Hi,
We have several important fixes get landed on branch-2.8 and I would like
to cut off branch-2.8.3 now to start 2.8.3 release work.
So far, I don't see any pending blockers on 2.8.3, so my current plan is to
cut off 1st RC of 2.8.3 in next several days:
- For all coming com
Below is some findings from my recently run of JACC
(https://builds.apache.org/job/Hadoop-2.9-JACC/12/artifact/target/compat-check/report.html)
job against 2.9 and 2.8.2. I have discussed with Arun and Subru offline on
jdiff report who convinced me some of items are not a big concern. Just tried
Hi Subru and Arun,
Thanks for moving forward with 2.9 release. Is the first cut of 2.9
release supposed to be a stable version or just an alpha version? If it is
supposed to be a stable version, we should run jdiff test and check for API
compatibility before releasing out. Please let me kno
, NodeManager, etc.
Now, we have:
7 binding +1s, from:
John Zhuge, Jason Lowe, Chris Douglas, Wangda Tan, Ravi Prakash, Eric
Payne, Junping Du
10 non-binding +1s, from:
Hanisha Koneru, Wei Yan, Brahma Reddy Battula, Shane Kumpf, Ajay Kumar,
Bharat Viswanadham, Mukul Kumar Singh, Eric
annot tell which daemons/components of HDFS consumes unexpected high memory.
Don't sounds like a solid bug report to me.
Thanks,?
Junping
From: Sean Busbey
Sent: Tuesday, October 24, 2017 2:20 PM
To: Junping Du
Cc: Allen Wittenauer; Hadoop Common; Hdfs
Allen,
Do we have any solid evidence to show the HDFS unit tests going through
the roof are due to serious memory leak by HDFS? Normally, I don't expect
memory leak are identified in our UTs - mostly, it (test jvm gone) is just
because of test or deployment issues.
Unless there is con
, October 23, 2017 2:49 PM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC1)
My apologies, false alarm on the CHANGES.md and RELEASENOTES.md. I was in the
Hi folks,
I've created our new release candidate (RC1) for Apache Hadoop 2.8.2.
Apache Hadoop 2.8.2 is the first stable release of Hadoop 2.8 line and
will be the latest stable/production release for Apache Hadoop - it includes
315 new fixed issues since 2.8.1 and 69 fixes are marked a
s for vote once the build
process get finished. In the mean time, please hold on any commits to
branch-2.8.2 unless it really belongs to a blocker and please ping me ahead.
Thanks all for your patience!
Thanks,
Junping
From: Junping Du
Sent: F
is still open for blocker/critical issues
landing, but for major/minor/trivial issues, please commit to branch-2.8 and
marked the fixed version as 2.8.3.
Thanks all for heads up. Have a good weekend!
Thanks,
Junping
From: Junping Du
Sent: Tuesday
work out
a patch soon, I am open to accept it.
Thanks,
Junping
From: Junping Du
Sent: Monday, September 11, 2017 5:32 PM
To: Daniel Templeton; Chris Douglas
Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev;
mapreduce-...@hadoop.apache.org
nping
From: Daniel Templeton
Sent: Monday, September 11, 2017 4:45 PM
To: Chris Douglas; Junping Du
Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)
YARN-66
,
Junping
From: Chris Douglas
Sent: Monday, September 11, 2017 12:00 PM
To: Junping Du
Cc: Miklos Szegedi; Mingliang Liu; Hadoop Common; Hdfs-dev;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; junping_du
Subject: Re: [VOTE] Release Apache Hadoop
-...@hadoop.apache.org; junping_du; Junping Du
Subject: Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)
Hello Junping,
Thank you for working on this. Should not YARN-6622 be addressed first?
"Summary: Document Docker work as experimental".
Thank you,
Miklos
On Sun, Sep 10, 2017 at 6:39 PM, Min
Hi folks,
With fix of HADOOP-14842 get in, I've created our first release candidate
(RC0) for Apache Hadoop 2.8.2.
Apache Hadoop 2.8.2 is the first stable release of Hadoop 2.8 line and
will be the latest stable/production release for Apache Hadoop - it includes
305 new fixed issues s
hanks,
Junping
From: Junping Du
Sent: Friday, September 1, 2017 12:37 PM
To: larry mccay; Steve Loughran
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: Apache Hadoop
s the time to do it
>
>
> > On 1 Sep 2017, at 11:14, Junping Du wrote:
> >
> > HADOOP-14814 get committed and HADOOP-9747 get push out to 2.8.3, so we
> are clean on blocker/critical issues now.
> > I finish practice of going through JACC report and no more incompatible
&
JIRA before doing
any commits. branch-2.8 is still open for landing. Thanks for your cooperation!
Thanks,
Junping
From: Junping Du
Sent: Wednesday, August 30, 2017 12:35 AM
To: Brahma Reddy Battula; common-...@hadoop.apache.org;
hdfs-dev@hadoop.apach
ng to kick off RC0 around holiday
(this weekend).
Thanks,
Junping
From: Brahma Reddy Battula
Sent: Tuesday, August 29, 2017 8:42 AM
To: Junping Du; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.
From: Junping Du
Sent: Monday, July 24, 2017 1:41 PM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re:
I have done the change.
All committers,
2.8.2 release is supposed to be a stable/production releas
bug fixes/improvements, please commit to branch-2.8
(trunk/branch-2) only and mark JIRA fixed as 2.8.3. Thanks for your cooperation!
Thanks,
Junping
From: Junping Du
Sent: Monday, July 24, 2017 10:36 AM
To: Brahma Reddy Battula; Vinod Kumar Vavilapalli
Cc
Sent: Sunday, July 23, 2017 1:50 AM
To: Junping Du; Vinod Kumar Vavilapalli
Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Jason Lowe;
humbed...@apache.org
Subject: Re: Apache Hadoop 2.8.2 Release Plan
Just
.
I will also adjust fix version on all affected JIRA accordingly.
If you have any concerns on above operations, please raise it before the end of
this Sunday (7/23).
Thanks,
Junping
From: Junping Du
Sent: Friday, July 21, 2017 2:29 PM
To: Vinod Kumar
Make sense, just raise: https://issues.apache.org/jira/browse/INFRA-14669
Thanks,
Junping
From: Vinod Kumar Vavilapalli
Sent: Friday, July 21, 2017 12:31 PM
To: Junping Du
Cc: Kihwal Lee; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org
From: Jason Lowe
Sent: Friday, July 21, 2017 8:17 AM
To: Kihwal Lee; Junping Du; common-...@hadoop.apache.org;
hdfs-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org;
yarn-...@hadoop.apache.org
Subject: Re: Apache Hadoop 2.8.2 Release Plan
+1 to base the 2.8.2 release off
Hi all,
Per Vinod's previous email, we just announce Apache Hadoop 2.8.1 get
released today which is a special security release. Now, we should work towards
2.8.2 release which aim for production deployment. The focus obviously is to
fix blocker/critical issues [2], bug-fixes and *no* featu
Haohui,
I am waiting for a special security release on branch-2.8 get out to resume
the release work for production release of 2.8. You should be on security alias
and ask for update there.
Thanks,
Junping
From: Haohui Mai
Sent: Wednesday, July 12,
I just cut off branch-2.8.1 from branch-2.8 for 2.8.1 release. So from now, all
patch target for 2.8.1 need to be checked into branch-2.8.1 in addition to
branch-2.8.
Thanks,
Junping
From: Junping Du
Sent: Monday, April 03, 2017 1:41 PM
To: common
Thanks Sunil to bring it up. However, any reason not to go to latest version of
maven (3.3+)? Even version 3.1 is quite old - released 3+ years from now
(please refer: https://archive.apache.org/dist/maven/binaries/).
btw, I assume we only plan to change maven version on trunk given new YARN UI
Hi all,
We just released Apache Hadoop 2.8.0 recently [1] but it is not for
production yet due to some issues identified. Now, we should work towards 2.8.1
release which aim for production deployment. The focus obviously is to fix
blocker/critical issues [2], bug-fixes and *no* features / imp
are missing from mirror sites
which get reported in https://issues.apache.org/jira/browse/INFRA-13755. The
Apache infrastructure team is investigating right now. Will send release news
when issue get fixed. Stay tuned!
Thanks,
Junping
From: Junping Du
hanks,
Junping
From: Allen Wittenauer
Sent: Thursday, March 23, 2017 5:27 PM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Subject: Re: [RESULT] [VOTE] Release Apache Hadoop 2.8.0 (RC3)
Just a heads up.
some example MR jobs, like: PI, sleep, etc.
Now, we have:
7 binding +1s, from:
Wangda Tan, Jason Lowe, Akira Ajisaka, Ravi Prakash,
Karthik Kambatla, Jian He, Junping Du
18 non-binding +1s, from:
Miklos Szegedi, Eric Payne, Daniel Templeton, Mingliang Liu,
Sunil Govind, Marton
issues if founded - I will check if
another round of RC is needed based on your findings. Thanks!
Thanks,
Junping
From: Kuhu Shukla
Sent: Tuesday, March 21, 2017 3:17 PM
Cc: Junping Du; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.
: Monday, March 20, 2017 10:31 AM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.8.0 (RC3)
Yes, it only affects ADL. There is a workaround of adding these 2
From: John Zhuge
Sent: Monday, March 20, 2017 9:07 AM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.8.0 (RC3)
Discovered https
Hi all,
With fix of HDFS-11431 get in, I've created a new release candidate (RC3)
for Apache Hadoop 2.8.0.
This is the next minor release to follow up 2.7.0 which has been released
for more than 1 year. It comprises 2,900+ fixes, improvements, and new
features. Most of these commits a
: Thursday, March 16, 2017 7:27 AM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.8.0 (RC2)
> On 16 Mar 2017, at 00:25, Junping Du wrote:
>
> bq. From
tely when HDFS-11431 get fixed.
Thanks,
Junping
From: Andrew Wang
Sent: Wednesday, March 15, 2017 2:04 PM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Subject:
_
From: Andrew Wang
Sent: Tuesday, March 14, 2017 2:50 PM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 2.8.0 (RC2)
Hi Junping,
Noticed this p
Hi all,
With several important fixes get merged last week, I've created a new
release candidate (RC2) for Apache Hadoop 2.8.0.
This is the next minor release to follow up 2.7.0 which has been released
for more than 1 year. It comprises 2,919 fixes, improvements, and new features.
Most
Yes. I did maven deploy in root directory before close the staging repository.
If this is the only suspect, I can drop the repository and do mvn deploy again.
Thanks,
Junping
From: Andrew Wang
Sent: Friday, January 20, 2017 10:48 AM
To: Junping Du
Cc: common
he problem?
Thanks,
Junping
____
From: Junping Du
Sent: Thursday, January 19, 2017 6:46 PM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Cc: Varun Vasudev
Subject: Re: [Continued] [Rele
t anything to branch-2.8.0 at this moment. Thanks!
Cheers,
Junping
____
From: Junping Du
Sent: Wednesday, January 18, 2017 3:26 PM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
+1 on Sangjin's proposal -
"A minor release line is end-of-lifed 2 years after it is released or there
are 2 newer minor releases, whichever is sooner. The community reserves the
right to extend or shorten the life of a release line if there is a good
reason to do so."
I also noticed Karthik brin
f you have more
comments or suggestions.
Thanks,
Junping
From: Junping Du
Sent: Wednesday, January 04, 2017 1:41 AM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subjec
,
Junping
From: Junping Du
Sent: Wednesday, December 07, 2016 11:31 AM
To: Akira Ajisaka; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0
Thanks Ted. I noticed that Jenkins test for YARN is back to work now. Resolving
the infra ticket.
Thanks,
Junping
From: Ted Yu
Sent: Wednesday, December 21, 2016 12:25 PM
To: Junping Du
Cc: yarn-...@hadoop.apache.org; common-...@hadoop.apache.org;
hdfs-dev
Hi hadoop folks,
I noticed that our recent YARN jenkins tests are consistently failed
(https://builds.apache.org/job/PreCommit-YARN-Build) due to test environment
issues below.
I already filed blocker issue
https://issues.apache.org/jira/browse/INFRA-13141 to our INFRA team yesterday
bu
adoop/job/Hadoop-trunk-JACC/24/artifact/target/compat-check/report.html
Regards,
Akira
On 2016/12/02 2:08, Junping Du wrote:
> Thanks Andrew! That's also a nice suggestion. I already create a similar job:
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/ for 2.8
From: Andrew Wang
Sent: Wednesday, November 30, 2016 4:18 PM
To: Junping Du
Cc: Sangjin Lee; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod Vavilapalli;
Jian He; Wangda Tan; sj...@twitter.com
Subject: Re: [Continued] [Re
. Non-critical fixes can wait for
next one.
Any other comments and suggestions?
Thanks,
Junping
From: sjl...@gmail.com on behalf of Sangjin Lee
Sent: Wednesday, November 30, 2016 3:24 PM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev
Hi folks,
Per asked by Vinod offline, I would like to continue the effort to push
2.8 release out in next several weeks. The plan is as following:
- We only have 5 blockers and 3 critical issues
(https://s.apache.org/6kwx) so far, and most of them are in good progress now.
I put them a
+1 binding, based on:
- Download and build from source, check signatures
- Deploy a single node cluster and run some simple jobs, like sleep, PI, etc.
Thanks Sangjin and Chris for working on 2.6.5 release!
Thanks,
Junping
From: larry mccay
Sent: Saturd
Hi Andrew and all,
Thanks for the notice on the change. I still concern this rule change may
cause some confusion from conflicting against our previous rule - no need to
set trunk version if it is landing on 2.x branch. As we can see, there are 4
cases of version setting for JIRA landing on
Thanks Vinod for creating new RC for 2.7.3 release.
+1 (binding) based on following verifications:
- Download src and binary tar ball and verify signature (gpg --verify).
- Build from source Java 1.8.0_31-b13 on Mac native successfully.
- Build from source with Java 1.7.0_79-b15 on Ubuntu VM su
I think Allen's previous comments are very misleading.
In my understanding, only incompatible API (RPC, CLIs, WebService, etc.)
shouldn't land on branch-2, but other incompatible behaviors (logs, audit-log,
daemon's restart, etc.) should get flexible for landing. Otherwise, how could
52 issues
>From my quick understanding, HDFS-9395 is more like a bug fix and improvement
>for audit logging instead of incompatible changes. We mark incompatible
>probably because the audit log behavior could be corrected/updated in some
>exception cases. I think it still belongs to 2.7.3 scope.
Kuhu and
, Aug 11, 2016 at 12:50 PM, Allen Wittenauer <
> a...@effectivemachines.com
> > wrote:
>
> >
> > > On Aug 11, 2016, at 8:10 AM, Junping Du wrote:
> > >
> > > Allen, to be clear, I am not against any branch release effort here.
> > However,
> >
ake our release plan more
reasonable to the whole community. More thoughts?
Thanks,
Junping
From: Allen Wittenauer
Sent: Thursday, August 11, 2016 3:13 PM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@had
ris Trezzo
Sent: Wednesday, August 10, 2016 9:30 PM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Jason Lowe
Subject: Re: [Release thread] 2.6.5 release activities
Thanks Jason and Junping for the commen
Thanks Chris for bring up this discussion.
Before we going to detail discussion of releasing 2.6.5, I have a quick
question here: do we think it is necessary to continue to release branch-2.6,
like 2.6.5, etc after 2.7 is out for more than 1 year. Any reason to not
suggest users to upgrade to 2
I think that incompatible API between 3.0.0-alpha and 3.1.0-beta is something
less confusing than incompatible between 2.8/2.9 and 2.98.x alphas/2.99.x betas.
Why not just follow our previous practice in the beginning of branch-2? we can
have 3.0.0-alpha, 3.1.0-alpha/beta, but once when we are fi
Comparing with advantages, I believe the disadvantages of shipping any releases
directly from trunk are more obvious and significant:
- A lot of commits (incompatible, risky, uncompleted feature, etc.) have to
wait to commit to trunk or put into a separated branch that could delay feature
develo
cases, -1 without solid reason will frustrate people who
are doing contributions. I think we should restraint our -1 unless it is really
necessary.
Thanks,
Junping
From: Vinod Kumar Vavilapalli
Sent: Monday, June 06, 2016 9:36 PM
To: Andrew Wang
Cc: Junpi
monstrates he/she is more responsible, work hardly and
carefully and open communication with all community. Only through this, the
success of Hadoop in age of 3.0 are guranteed.
Thanks,
Junping
From: Aaron T. Myers
Sent: Monday, June 06, 2016 4:46 PM
To: Junping D
Hi Andrew,
I just noticed you revert 8 commits on trunk last Friday:
HADOOP-13226
HDFS-10430
HDFS-10431
HDFS-10390
HADOOP-13168
HDFS-10390
HADOOP-13168
HDFS-10346
HADOOP-12957
HDFS-10224
And I didn't see you have any comments on JIRA or email discussion before
you did this. I d
bq. We'll need to be strict after the switch: all patches to go into branch 2
will have to go through yetus as branch-2 patches, then cherry picked to trunk,
or a separate patch on the same JIRA done for the branch-2. Assuming yetus
still tests the branch-2 stuff on JDK7, that will check version
Thanks for bringing up this topic, Sean.
When I released our latest Hadoop release 2.6.4, the patch of HDFS-8791 haven't
been committed in so that's why we didn't discuss this earlier.
I remember in JIRA discussion, we treated this layout change as a Blocker bug
that fixing a significant perform
Shall we consolidate effort for 2.8.0 and 3.0.0? It doesn't sounds reasonable
to have two alpha releases to go in parallel. Is EC feature the main motivation
of releasing hadoop 3 here? If so, I don't understand why this feature cannot
land on 2.8.x or 2.9.x as an alpha feature.
If we release 3
lp to specify labels at submission time.
>
> Thanks and Regards
> Sunil
>
> On Wed, Feb 3, 2016 at 12:31 PM Junping Du wrote:
>
>> Hi community folks,
>>I've created a release candidate RC0 for Apache Hadoop 2.6.4 (the next
>> maintenance release to f
sed in all future
releases), and the concern Allen raised.
Best,
--Yongjun
On Wed, Feb 10, 2016 at 8:37 AM, Allen Wittenauer wrote:
>
> > On Feb 9, 2016, at 6:27 PM, Junping Du wrote:
> >
> > Thanks Yongjun for identifying and proposing this change to 2.6.4. I
> think
RCs.
Thanks Akira for +1 on this proposed additional release step. Once we have
an agreement on the details, we will update the wiki page accordingly.
Best,
--Yongjun
On Tue, Feb 2, 2016 at 11:01 PM, Junping Du wrote:
> Hi community folks,
>I've created a release candidate RC0 fo
Hi community folks,
I've created a release candidate RC0 for Apache Hadoop 2.6.4 (the next
maintenance release to follow up 2.6.3.) according to email thread of release
plan 2.6.4 [1]. Below is details of this release candidate:
The RC is available for validation at:
*http://people.apache.org
[
https://issues.apache.org/jira/browse/HDFS-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du resolved HDFS-4886.
--
Resolution: Duplicate
Assignee: (was: Junping Du)
There are already work in HDFS-9456 in
.
In the mean while, I’ll get go dust off 2.8.0 too ..
Thanks
+Vinod
> On Jan 6, 2016, at 3:59 PM, 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 loo
I give my binding +1 on 2.7.2-RC2 with following check:
- All new commits (155) since 2.7.1 are included in commit log and CHANGES.txt
which equally to JIRA
marked as fixed in 2.7.2.
- Signatures and message digests all are looks good, build get successfully
from the source tar ball with JDK
In addition, all new fixes backport from 2.6.3 doesn't listed in 2.7.2 entry of
CHANGES.txt but keep listed as 2.6.3. I think this is fine no matter we have
multiple entries to track the same commit or a single entry to track the
earliest commit. The only thing matter is the commits in release n
There are also several stale branches for YARN-2928 that we should consolidate:
remotes/origin/YARN-2928
remotes/origin/YARN-2928-new
remotes/origin/YARN-2928-old
remotes/origin/YARN-2928-old-2015-11-09
remotes/origin/YARN-2928-rebase
remotes/origin/feature-YARN-2928 (the latest one)
I
shape now.
Thanks,
Junping
From: Vinod Kumar Vavilapalli
Sent: Wednesday, January 13, 2016 11:15 PM
To: Junping Du
Cc: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE
sounds good to me.
>
> > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
> get out after 2.x.y release date"
>
> +1
>
> > I would prefer this rule only applies on critical/blocker fixes, but not
> applies on minor/trivial issues.
>
[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
rivial issues.
Just 2 cents.
Thanks,
Junping
From: Vinod Kumar Vavilapalli
Sent: Thursday, December 24, 2015 12:47 AM
To: Junping Du
Cc: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Subje
Checked 2.7.2-RC1 tag which match exactly with 2.7.2 branch.
Downloaded the release bit and deploy a single node cluster which works fine
with running some example jobs.
Built from src and check signatures, all looks good.
Checked release note which has 138 commits (HADOOP:22, HDFS:42, MAPREDUCE:1
Thanks Karthik to bring up the topic. Comparing with small enhancement on email
distribution for release/branch news, I think a more important thing is to make
our community (contributor & committer) to be more aware on ongoing
releases/branches.
I can see two improvements could be helpful here
>
> - 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,
1 - 100 of 170 matches
Mail list logo
