Unable to spin up cluster using ambari blue print

pbasgod — Sun, 13 May 2018 06:18:18 GMT

blueprint.txtTrying to spin up a cluster without Hive component using ambari-server blue print.

Services fail to start with error

```12 May 2018 22:33:21,952 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert oozie_server_status for an invalid cluster named test 12 May 2018 22:33:21,952 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert yarn_resourcemanager_webui for an invalid cluster named test 12 May 2018 22:33:21,952 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert datanode_heap_usage for an invalid cluster named test 12 May 2018 22:33:21,952 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert infra_solr for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert hive_webhcat_server_status for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert nodemanager_health_summary for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert datanode_webui for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert yarn_app_timeline_server_webui for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert mapreduce_history_server_webui for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert namenode_last_checkpoint for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert datanode_health_summary for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert zeppelin_server_status for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert ambari_agent_disk_usage for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert ams_metrics_monitor_process for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert metadata_server_webui for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-1] AlertReceivedListener:480 - Unable to process alert namenode_directory_status for an invalid cluster named test 12 May 2018 22:33:21,951 ERROR [alert-event-bus-2] AlertReceivedListener:480 - Unable to process alert mapreduce_history_server_process for an invalid cluster named test 12 May 2018 22:33:21,953 ERROR [alert-event-bus-2] AlertReceivedListener:480 - Unable to process alert storm_webui for an invalid cluster named test```

ambari-version:2.6.1

Attached blue print

Thanks in advance

Re: Unable to spin up cluster using ambari blue print

Shelton — Sun, 13 May 2018 16:03:43 GMT

@prarthana basgod

Where is it picking this from "invalid cluster named test"

if you won't install hive why not remove this component which is dependent of hive?

webhcat_server

Re: Unable to spin up cluster using ambari blue print

pbasgod — Mon, 14 May 2018 23:45:55 GMT

that worked. thanks for the help

question Re: Unable to spin up cluster using ambari blue print in Archives of Support Questions (Read Only)

Unable to spin up cluster using ambari blue print

Re: Unable to spin up cluster using ambari blue print

Re: Unable to spin up cluster using ambari blue print