Correction: I meant "withdraw this vote now for RC1" and "create an RC2".
Ayush, I'll add it if it applies without conflict.
Regards,
Gabor
On Wed, Jun 24, 2020 at 1:01 PM Ayush Saxena wrote:
>
> Hi Gabor,
> As you are going ahead with another RC,
> Please include : HDFS-15323 as well if
Hi Gabor,
As you are going ahead with another RC,
Please include : HDFS-15323 as well if possible.
https://issues.apache.org/jira/browse/HDFS-15323
Remember tagging you there but at that time RC0 was up, try if that could
make into the release as well.
Thanx!!!
-Ayush
On Wed, 24 Jun 2020 at
Thanks for looking into this Akira, Kihwal!
I noted that it is a hard to create situation described in HDFS-14941.
The issue created by HDFS-14941 would be even harder to fix in
HDFS-15421, test it, prove that it's stable, etc..
That's why I will do a revert of HDFS-14941 and create an RC3.
*
Gabor,
If you want to release asap, you can simply revert HDFS-14941 in the
release branch for now. It is causing the issue and was committed after
3.1.3. This causes failure of the automated upgrade process and namenode
memory leak.
Kihwal
On Tue, Jun 23, 2020 at 8:47 AM Akira Ajisaka wrote:
Hi Gabor,
Thank you for your work!
Kihwal reported IBR leak in standby NameNode:
https://issues.apache.org/jira/browse/HDFS-15421.
I think this is a blocker and this affects 3.1.4-RC1. Would you check this?
Best regards,
Akira
On Mon, Jun 22, 2020 at 10:26 PM Gabor Bota
wrote:
> Hi folks,
>
Hi folks,
I have put together a release candidate (RC1) for Hadoop 3.1.4.
The RC is available at: http://people.apache.org/~gabota/hadoop-3.1.4-RC1/
The RC tag in git is here:
https://github.com/apache/hadoop/releases/tag/release-3.1.4-RC1
The maven artifacts are staged at
