ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doroszlai, Attila (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions
Date Fri, 29 Sep 2017 10:55:00 GMT
Doroszlai, Attila created AMBARI-22092:
------------------------------------------

             Summary: Blueprint Created Cluster Is Throwing Constant Exceptions
                 Key: AMBARI-22092
                 URL: https://issues.apache.org/jira/browse/AMBARI-22092
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.2.0
            Reporter: Doroszlai, Attila
            Assignee: Doroszlai, Attila
             Fix For: 2.6.0


During the creation of a cluster, Ambari server is spitting out the following exception every
second until all host groups have the required number of hosts.

{code}
2017-09-26 11:08:56,221 INFO  [pool-4-thread-1] (AsyncCallableService.java:115) taskCompleted()
- 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:106)
	at org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:77)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: TopologyManager.ConfigureClusterTask - prerequisites
for config request processing not yet  satisfied
	at org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:64)
	at org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
	at org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:1)
	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)
{code}

Logging in {{ConfigureClusterTask}} and {{AsyncCallableService}} should be refined and clarified.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message