You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/09/29 14:37:02 UTC

[jira] [Commented] (AMBARI-22092) Blueprint Created Cluster Is Throwing Constant Exceptions

    [ https://issues.apache.org/jira/browse/AMBARI-22092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185920#comment-16185920 ] 

Hadoop QA commented on AMBARI-22092:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12889699/AMBARI-22092_branch-2.6.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12384//console

This message is automatically generated.

> 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
>
>         Attachments: AMBARI-22092_branch-2.6.patch, AMBARI-22092.patch
>
>
> 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)