- I've created YARN-9855 and uploaded patches to fix YARN-6616 in
branch-2.8 and branch-2.7.
- For YARN-6050, not sure either. Robert/Wangda, can you comment on
YARN-6050 compatibility?
- For YARN-7813, not sure why moving from 2.8.4/5 -> 2.8.6 would be
incompatible with this strategy? It should
* For YARN-6616, for branch-2.8 and below, it was only committed to
2.7.8/2.8.6 which have not been released (as I understand). Perhaps we can
revert YARN-6616 from branch-2.7 and branch-2.8.
- This seems reasonable. Since we haven't released anything, it should be
no issue to change the
Sorry, let me edit my first point. We can just create addendums for YARN-6616
in branch-2.7 and branch-2.8 to edit the submitTime field to the correct id 28.
We don’t need to revert YARN-6616 from these branches completely.
Jonathan
From: Jonathan Hung
Sent:
Hi Eric, thanks for the investigation.
- For YARN-6616, for branch-2.8 and below, it was only committed to
2.7.8/2.8.6 which have not been released (as I understand). Perhaps we can
revert YARN-6616 from branch-2.7 and branch-2.8.
- For YARN-6050, there's a bit here:
Hi devs and users,
Tomorrow (sorry for the short notice) we will do a presentation at Strata
Data Conf @ NY for a Community update of Hadoop 3.x. I'm thinking to create
a slide about existing production deployment on Hadoop 3.x. Basically, I
want to put a logo wall with a list of big names so we
We (Verizon Media) are currently moving towards upgrading our clusters from
our internal fork of branch-2.8 to an internal fork of branch-2. During
this process, we have found multiple incompatible changes in protobufs
between branch-2.8 and branch-2. These incompatibilities were all
introduced
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,
