[ https://issues.apache.org/jira/browse/AMBARI-20289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Yang updated AMBARI-20289: ------------------------------- Summary: Optional host_group can interfere with blueprint deployment (was: Optional host_group can interfere with actual deployment) > Optional host_group can interfere with blueprint deployment > ----------------------------------------------------------- > > Key: AMBARI-20289 > URL: https://issues.apache.org/jira/browse/AMBARI-20289 > Project: Ambari > Issue Type: Improvement > Affects Versions: 2.4.2 > Reporter: Eric Yang > > User defines a blueprint that contains 4 host groups. Edge group, management > group 1 and 2, and worker group. For management group 1, include a single > knox server. In edge group, also define Knox server. When edge group > includes one or more hosts, they will be used for Knox Server HA. Without > edge group, management group 1 will be used as a single Knox server. > When edge group does not contain any host, Ambari throws a weird exception: > {code} > 26 Feb 2017 19:14:55,108 WARN [pool-16-thread-1] > BlueprintConfigurationProcessor:1403 - The property > 'dfs.namenode.secondary.http-address' is associated with the component > 'SECONDARY_NAMENODE' which isn't mapped to any host group. This may affect > configuration topology resolution. > 26 Feb 2017 19:14:55,129 INFO [pool-3-thread-1] AsyncCallableService:111 - > Exception during task execution: > java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: > TopologyManager.ConfigureClusterTask - prerequisites for config request > processing not yet satisfied > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at > org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:103) > at > org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:74) > at > org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:37) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IllegalArgumentException: > TopologyManager.ConfigureClusterTask - prerequisites for config request > processing not yet satisfied > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:908) > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:889) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > ... 3 more > {code} > HDFS does not get formatted. There is a 30 minutes delay between submit > cluster construction REST request, and Ambari start to install the cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)