java.net.NoRouteToHostException is considered a failure that can be recovered from in any deployment with floating IP addresses. This was essentially the sole form of failover in Hadoop pre NN-HA (HADOOP-6667 added the check). I think we ought to revisit that decision ... View more

I've just commented on the JIRA. I think you could try configuring hive to not use the timeline service —I've done that on other applications <property> <name>yarn.timeline-service.enabled</name> <value>false</value> </property> ... View more

Arvind, you may be using a combination of Hadoop & JDK that doesn't support keytab renewal. The later versions of Hadoop 2.6 (that's apache 2.6.2+ and HDP 2.2 maintenance releases) should work. ... View more

1. The clickalbe link is: apache-spark-1-6-technical-preview-with-hdp-2-3 2, @vshukla: is there a tarball somewhere too? That's useful client-side ... View more

Hmm, that's my code at fault there. What it's saying is that the history server can't find the class org.apache.spark.deploy.history.yarn.server.YarnHistoryProvider, which is what it is configured to use for histories. The workaround is to switch to the classic filesystem history provider, which you can do spark.history.provider org.apache.spark.deploy.history.FsHistoryProvider Deleting the line entirely should force the history server to revert to this. I'd also look at deleting the line spark.yarn.services org.apache.spark.deploy.yarn.history.YarnHistoryService If the timeline server integration is not on the classpath, the publisher is unlikely to be there too. If that doesn't solve it, comment on this issue and I'll see what else we can do. ... View more