[
https://issues.apache.org/jira/browse/METRON-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289572#comment-16289572
]
ASF GitHub Bot commented on METRON-1349:
----------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/metron/pull/866#discussion_r156725657
--- Diff: metron-deployment/roles/ambari_config/tasks/main.yml ---
@@ -26,16 +26,15 @@
retries: 5
delay: 10
-- name : check if ambari-server is up on {{ ambari_host }}:{{ambari_port}}
+- name : Wait for Ambari to start; http://{{ ambari_host }}:{{ ambari_port
}}
wait_for :
host: "{{ ambari_host }}"
port: "{{ ambari_port }}"
- delay: 120
- timeout: 300
+ timeout: 600
--- End diff --
There is no need to always wait 2 minutes for Ambari to be ready. Most
often it is already up and kicking by the time we get here. Rather than have a
forced delay, I just added the delay duration to the overall timeout parameter
in case there is a delay in getting Ambari going.
> Full Dev Builds Metron Twice
> ----------------------------
>
> Key: METRON-1349
> URL: https://issues.apache.org/jira/browse/METRON-1349
> Project: Metron
> Issue Type: Bug
> Reporter: Nick Allen
> Assignee: Nick Allen
>
> When deploying Metron in Full Dev, the "Build Metron" step gets run twice.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
