You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sebastian Toader (JIRA)" <ji...@apache.org> on 2016/05/05 14:04:12 UTC
[jira] [Updated] (AMBARI-16270) Blueprint processor should create
ConfigGroup even with only one host registered
[ https://issues.apache.org/jira/browse/AMBARI-16270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Toader updated AMBARI-16270:
--------------------------------------
Attachment: AMBARI-16270.trunk.v1.patch
AMBARI-16270.branch-2.2.2.v1.patch
> Blueprint processor should create ConfigGroup even with only one host registered
> --------------------------------------------------------------------------------
>
> Key: AMBARI-16270
> URL: https://issues.apache.org/jira/browse/AMBARI-16270
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Sebastian Toader
> Assignee: Sebastian Toader
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16270.branch-2.2.2.v1.patch, AMBARI-16270.trunk.v1.patch
>
>
> When creating a cluster using Blueprints that has configuration properties defined at host group level Ambari should create a config group for those configuration properties when the first host is assigned to the host group.
> In case the host group expects multiple host the config group creation fails with the error below if among those host there are hosts which were not assigned to the cluster yet.
> {noformat}
> 4 May 2016 17:33:14,782 INFO [qtp-ambari-agent-93] HeartBeatHandler:469 - Recovery configuration set to RecoveryConfig{, type=AUTO_START, maxCount=6, windowInMinutes=60, retryGap=5, maxLifetimeCount=1024, disabledComponents=, enabledComponents=METRICS_COLLECTOR}
> 04 May 2016 17:33:14,818 ERROR [pool-3-thread-1] AbstractResourceProvider:280 - Caught AmbariException when creating a resource
> org.apache.ambari.server.HostNotFoundException: Host not found, hostname=perf-c-11.c.pramod-thangali.internal
> at org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:370)
> at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.createConfigGroups(ConfigGroupResourceProvider.java:501)
> at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.access$200(ConfigGroupResourceProvider.java:65)
> at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$3.invoke(ConfigGroupResourceProvider.java:256)
> at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$3.invoke(ConfigGroupResourceProvider.java:253)
> at org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:450)
> at org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:273)
> at org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.createResources(ConfigGroupResourceProvider.java:252)
> at org.apache.ambari.server.topology.AmbariContext.createConfigGroupsAndRegisterHost(AmbariContext.java:621)
> at org.apache.ambari.server.topology.AmbariContext.registerHostWithConfigGroup(AmbariContext.java:323)
> at org.apache.ambari.server.topology.HostRequest$RegisterWithConfigGroupTask.run(HostRequest.java:469)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The config group should be created with the available hosts and updated with additional hosts as new hosts are assigned to the cluster and host group.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)