search

hortonworks / ansible-hortonworks

Ansible playbooks for deploying Hortonworks Data Platform and DataFlow using Ambari Blueprints
Apache License 2.0
248 stars 253 forks source link

Issue when running apply_blueprint.sh #158

Closed thepg closed 5 years ago

thepg commented 5 years ago

Hello I'm working with the static installation with 3 machines (1 Master 1 Slave 1 Kdc) created with DigitalOcean (with 16GB Ram ..) all the steps ( Prepare the nodes: prepare_nodes.sh Install Ambari: install_ambari.sh ** Configure Ambari: configure_ambari.sh ) work fine but when i run "apply_blueprint.sh" failed at the task :

TASK [ambari-blueprint : Wait for the cluster to be built] *** FAILED - RETRYING: Wait for the cluster to be built (360 retries left). FAILED - RETRYING: Wait for the cluster to be built (359 retries left). FAILED - RETRYING: Wait for the cluster to be built (358 retries left). FAILED - RETRYING: Wait for the cluster to be built (357 retries left). FAILED - RETRYING: Wait for the cluster to be built (356 retries left). FAILED - RETRYING: Wait for the cluster to be built (355 retries left). FAILED - RETRYING: Wait for the cluster to be built (354 retries left). FAILED - RETRYING: Wait for the cluster to be built (353 retries left). FAILED - RETRYING: Wait for the cluster to be built (352 retries left). FAILED - RETRYING: Wait for the cluster to be built (351 retries left). ...

alexandruanghel commented 5 years ago

Hi @thepg This is normal as the FAILED is followed by a RETRYING. If you see the entire playbook fail and ansible giving out and error then that's a concern but not the RETRYING one above.

This happens because at this stage of the build, Ambari itself starts installing and building the cluster, and Ansible waits on Ambari to finish building the cluster. The message from Ansible, I agree it's not really great and can be confusing, but I didn't find a more friendly way of changing the message for this task.

abh23 commented 5 years ago

Hey @thepg, It doesn't seem to be an error. This logic here is to check if the cluster has formed or not. Ansible calls an API to check the cluster status and since cluster is getting deployed(component installation and services start), it fails but retries again after a delay specified in the apply_blueprint's ansible playbook.

Just login into your ambari portal http://:8080 and see the progress in the operation at the top bar.

Depending on the number of components you are trying to install, it can take 20+ minutes to complete this process. Try that and let us know how it went.