*Hi Jitendra and all,Thanks for putting this together. I caught up on the
discussion on JIRA and document at HDFS-10419, and still have the same
concerns raised earlier
Charan Hebri created MAPREDUCE-7062:
---
Summary: MR job tags not compatible with YARN ATSv2 flow names,
flow run ids and flow versions
Key: MAPREDUCE-7062
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7062
Hi Konst and all,
Is there a list of 3.0 specific upgrade concerns that you could share? I
understand that a new major release comes with risk simply due to the
amount of code change, but we've done our best as a community to alleviate
these concerns through much improved integration testing and
Thanks Subru for initiating the thread about GPU support.
I think the path of taking 2.9 as a base for 2.10 and adding new resource
types into it is quite reasonable.
That way we can combine stabilization effort on 2.9 with GPUs.
Arun, upgrading Java is probably a separate topic.
We should
Hi Arun/Subru,
Bumping the minimum Java version is a major change, and incompatible for
users who are unable to upgrade their JVM version. We're beyond the EOL for
Java 7, but as we know from our experience with Java 6, there are plenty of
users who stick on old Java versions. Bumping the Java
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/705/
[Feb 26, 2018 4:28:04 PM] (kihwal) HDFS-12070. Failed block recovery leaves
files open indefinitely and at
[Feb 26, 2018 8:15:16 PM] (kkaranasos) YARN-7921. Transform a
PlacementConstraint to a string
