Thanks that worked out.   Regards. ... View more

@nlewis135031    We remove livy.spark.master in zeppelin-0.7. Because we suggest user to use livy 0.3 in zeppelin-0.7. And livy 0.3 don't allow to specify livy.spark.master by default, it enforce yarn-cluster mode refer here. As you aware always to have yarn-cluster mode is better after all using the cluster resource is wise. yarn-cluster mode --> you can't directly mention yarn-cluster as master option ( in HDP 2.6.x i guess - i tested in HDP 2.6.3) instead you can use the workaround below to use the yarn cluster mode. this option is available from 0.8.0 jira. master yarn spark.submit.deployMode cluster   Hope this helps! ... View more

As the description mentions that nothing from /var/lib/ambari-server/resources is populated in agent cache, I see a behavior where custom dashboard files which are placed at /var/lib/ambari-server/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/ are also not available in /var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/. How to make this work? ... View more

@GerardReverte  thanks fort the inputs, yes as of now it's best to go for " Dedicated Instance with dedicated storage and configuration:" or "Dedicated Instance:" mentioned in the article for extensive or heavy production use. Thanks for sharing your experience, much appreciated. ... View more