You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2016/06/07 08:07:21 UTC

[jira] [Updated] (AMBARI-17082) Ambari server failed to start METRICS_COLLECTOR via BP

     [ https://issues.apache.org/jira/browse/AMBARI-17082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Sen updated AMBARI-17082:
--------------------------------
    Attachment: AMBARI-17082_1-trunk.patch

> Ambari server failed to start METRICS_COLLECTOR via BP
> ------------------------------------------------------
>
>                 Key: AMBARI-17082
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17082
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17082_1-trunk.patch
>
>
> If blueprint contains 2 AMS collectors, the start fails with 
> {code}
> 03 Jun 2016 04:18:49,545 ERROR [pool-16-thread-1] TopologyManager:782 - TopologyManager.ConfigureClusterTask: An exception occurred while attempting to process cluster configs and set on cluster:
> java.lang.IllegalArgumentException: Unable to update configuration property 'timeline.metrics.service.webapp.address' with topology information. Component 'METRICS_COLLECTOR' is mapped to an invalid number of hosts '2'.
>         at org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1350)
>         at org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$6.updateForClusterCreate(BlueprintConfigurationProcessor.java:2630)
>         at org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:271)
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:153)
>         at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:780)
>         at org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:754)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>         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)
> 03 Jun 2016 04:18:49,553  INFO [pool-3-thread-1] AsyncCallableService:111 - Exception during task execution:
> java.util.concurrent.ExecutionException: java.lang.Exception: java.lang.IllegalArgumentException: Unable to update configuration property 'timeline.metrics.service.webapp.address' with topology information. Component 'METRICS_COLLECTOR' is mapped to an invalid number of hosts '2'.
>         at java.util.concurrent.FutureTask.report(FutureTask.java:122)
>         at java.util.concurrent.FutureTask.get(FutureTask.java:202)
>         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:262)
>         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)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)