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 c
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 discuss
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 ver
Hello folks
We also think this bridging release opens up an opportunity to bump the
java version in branch-2 to java 8.
Would really love to hear thoughts on that.
Cheers
-Arun/Subru
On Mon, Feb 26, 2018 at 5:18 PM, Jonathan Hung wrote:
> Hi Subru,
>
> Thanks for starting the discussion.
>
>
Hi Subru,
Thanks for starting the discussion.
We (LinkedIn) have an immediate need for resource types and native GPU
support. Given we are running 2.7 on our main clusters, we decided to avoid
deploying hadoop 3.x on our machine learning clusters (and having to
support two very different hadoop v
Folks,
We (i.e. Microsoft) have started stabilization of 2.9 for our production
deployment. During planning, we realized that we need to backport 3.x
features to support GPUs (and more resource types like network IO) natively
as part of the upgrade. We'd like to share that work with the community.
