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 <aajis...@apache.org> 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 <gabor.b...@cloudera.com > .invalid> > wrote: > > > 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 > > https://repository.apache.org/content/repositories/orgapachehadoop-1267/ > > > > You can find my public key at: > > https://dist.apache.org/repos/dist/release/hadoop/common/KEYS > > and http://keys.gnupg.net/pks/lookup?op=get&search=0xB86249D83539B38C > > > > Please try the release and vote. The vote will run for 5 weekdays, > > until June 30. 2020. 23:00 CET. > > > > Thanks, > > Gabor > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org > > For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org > > > > >
