Hi Masatake,

Thanks for helping to verify!
I checked that branch-3.2 has the HDFS-14759 committed already.
Release-3.2.1-RC0 should have no such issue.

For branch-3.1, cherry-pick the same commit has conflicts. I'm confirming
if we can fix it or there's a feasible plan to backport the whole
Hadoop-15226 (which targeting branch-3.2) to branch-3.1.

Can you please help to provide a branch-3.1 patch for HDFS-14759? Or we can
move it to the next release of branch-3.1 since the noisy info is not a
blocker issue to me. Does that make sense?


BR,
Zhankun

On Wed, 18 Sep 2019 at 14:23, Masatake Iwasaki <iwasak...@oss.nttdata.co.jp>
wrote:

> Thanks for putting this up, Zhankun Tang.
>
> While I was testing the RC0 wich CLI,
> noisy INFO message was emitted on every data transfer operation.::
>
>    2019-09-17 16:00:42,942 INFO sasl.SaslDataTransferClient: SASL
> encryption trust check: localHostTrusted = false, remoteHostTrusted = false
>
> The issue was fixed by HDFS-14759.
> I think the fix should be backported if we cut RC1.
>
> Since the fix version of HDFS-14759 is 3.3.0, CR0 of 3.2.1 could have
> same issue.
>
> Regards,
> Masatake Iwasaki
>
> On 9/12/19 17:04, Zhankun Tang wrote:
> > Hi folks,
> >
> > Thanks to everyone's help on this release. Special thanks to Rohith,
> > Wei-Chiu, Akira, Sunil, Wangda!
> >
> > I have created a release candidate (RC0) for Apache Hadoop 3.1.3.
> >
> > The RC release artifacts are available at:
> > http://home.apache.org/~ztang/hadoop-3.1.3-RC0/
> >
> > The maven artifacts are staged at:
> > https://repository.apache.org/content/repositories/orgapachehadoop-1228/
> >
> > The RC tag in git is here:
> > https://github.com/apache/hadoop/tree/release-3.1.3-RC0
> >
> > And my public key is at:
> > https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> >
> > *This vote will run for 7 days, ending on Sept.19th at 11:59 pm PST.*
> >
> > For the testing, I have run several Spark and distributed shell jobs in
> my
> > pseudo cluster.
> >
> > My +1 (non-binding) to start.
> >
> > BR,
> > Zhankun
> >
> > On Wed, 4 Sep 2019 at 15:56, zhankun tang <tangzhan...@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> Thanks for everyone helping in resolving all the blockers targeting
> Hadoop
> >> 3.1.3[1]. We've cleaned all the blockers and moved out non-blockers
> issues
> >> to 3.1.4.
> >>
> >> I'll cut the branch today and call a release vote soon. Thanks!
> >>
> >>
> >> [1]. https://s.apache.org/5hj5i
> >>
> >> BR,
> >> Zhankun
> >>
> >>
> >> On Wed, 21 Aug 2019 at 12:38, Zhankun Tang <zt...@apache.org> wrote:
> >>
> >>> Hi folks,
> >>>
> >>> We have Apache Hadoop 3.1.2 released on Feb 2019.
> >>>
> >>> It's been more than 6 months passed and there're
> >>>
> >>> 246 fixes[1]. 2 blocker and 4 critical Issues [2]
> >>>
> >>> (As Wei-Chiu Chuang mentioned, HDFS-13596 will be another blocker)
> >>>
> >>>
> >>> I propose my plan to do a maintenance release of 3.1.3 in the next few
> >>> (one or two) weeks.
> >>>
> >>> Hadoop 3.1.3 release plan:
> >>>
> >>> Code Freezing Date: *25th August 2019 PDT*
> >>>
> >>> Release Date: *31th August 2019 PDT*
> >>>
> >>>
> >>> Please feel free to share your insights on this. Thanks!
> >>>
> >>>
> >>> [1] https://s.apache.org/zw8l5
> >>>
> >>> [2] https://s.apache.org/fjol5
> >>>
> >>>
> >>> BR,
> >>>
> >>> Zhankun
> >>>
>
>

Reply via email to