Vinod,
Thanks for offering the help.
Yeah. I haven't finished the remaining steps. Due to the permission issue,
I cannot push the artifacts to the hadoop dist repo for now.
And Sunil is helping on this.
I'll ping you if any other issue. Thanks.
BR,
Zhankun
Vinod Kumar Vavilapalli 于2019年10月13日
Zhankun et.al,
Did we close down the rest of the release process for 3.1.3?
I don't yet see this on the site, so asking.
If it's not done yet and you are running into issues, please let me know
and I can help with the corresponding release management tasks.
Thanks
+Vinod
On Tue, Sep 24, 2019
Hi,
Thank you all who spent time to verify and vote 3.1.3 release!
I‘m pleased to announce that the vote for 3.1.3 RC0 passed! I'll push the
release bits and send out an announcement for 3.1.3 soon.
Summary of votes for Hadoop-3.1.3-RC0:
4 binding +1s, from Rohith Sharma K S, Sunil Govindan,
+1 (binding)
Thanks Zhankun for all of your hard work on this release.
I downloaded and built the source and ran it on an insecure multi-node pseudo
cluster.
I performed various YARN manual tests, including creating custom resources,
creating queue submission ACLs, and queue refreshes.
+1 (binding)
- Downloaded source, setup a single node cluster
- Verified basic HDFS operations, put/get/cat etc
- Verified basic YARN restful apis, cluster/nodes/scheduler, all seem good
- Run several distributed shell job
Thanks
Weiwei
On Sep 19, 2019, 4:28 PM +0800, Sunil Govindan , wrote:
>
+1 (binding)
Thanks Zhankun for putting up the release. Thanks for leading this.
- verified signature
- ran a local cluster from tar ball
- ran some MR jobs
- perform CLI ops, and looks good
- UI seems fine
Thanks
Sunil
On Thu, Sep 12, 2019 at 1:34 PM Zhankun Tang wrote:
> Hi folks,
>
>
Hi Masatake,
My bad. I read it wrong. Yeah. You're right. The HDFS-14759 can be
backported to both Branch-3.2 and 3.1.
Let's see if there's any other blocker/critical issue come up, otherwise,
personally I don't prefer to run another RC1 and vote for this minor change.
BR,
Zhankun
On Wed, 18
Hi Zhankun,
> 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?
I tried to cherry-picking the HDFS-14759 on my side.
Since there was no conflict, I
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
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
+1 (binding)
- verified sha512 for all the artifacts
- built from source and installed pseudo cluster. Run sample MR jobs and
distributed shell.
-Rohith Sharma K S
11 matches
Mail list logo
