01-04-2017 11:54 AM - edited 01-04-2017 12:36 PM
i experienced this issue also. removing open jdk resolved it.
it appears open jdk add two extra columns to the output of the alternatives call. i belive it is setting the --family when it installs the alternative.
/usr/lib/jvm/java-1.8.0-openjdk-220.127.116.11-2.b15.el7_3.x86_64/jre/bin/java - family java-1.8.0-openjdk.x86_64 priority 1800111
01-04-2017 12:50 PM
Indeed, you are correct about the columns.
Please see my recent posts in the following thread for some more information:
I outlined a proposed fix (expiremental) if you really need the JDK. Cloudera engineering is reviewing to decide on how we will address it in future releases.
01-08-2017 09:29 PM
I had the same issue. After went through the alternative list, I found there are three more openjdk items, which are jre_openjdk, jre_1.8.0 and jre_1.8.0_openjdk. After I removed these three items, CM started distributing task.
08-18-2017 02:57 AM
Is the issue fixed in a recent cloudera manager releases?
We are running 5.8.3 and we are experiencing the issue not for a jdk but for a custom alternatives.
I'm asking because is simplier for us to just upgrade the cloudera manager than fixing the alternatives name...