ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srimanth Gunturi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-6168) Error message about absent ATS after upgrade to 2.0.6 stack
Date Tue, 17 Jun 2014 20:11:02 GMT

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

Srimanth Gunturi updated AMBARI-6168:
-------------------------------------

    Attachment: AMBARI-6168.patch

Issue was that HDP 2.0.6 has YARN without ATS, and UI was not taking that into account.

> Error message about absent ATS after upgrade to 2.0.6 stack
> -----------------------------------------------------------
>
>                 Key: AMBARI-6168
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6168
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.6.1
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 1.6.1
>
>         Attachments: AMBARI-6168.patch, Selection_005.png
>
>
> Ambari 1.4.1 with HDP 2.0.6 Stack having YARN 2.1.
> When logging to the Ambari GUI, server error 500 occured:
> {code}
> Server Error
> 500 status code received on GET method for API: /api/v1/clusters/cl1/components/?ServiceComponentInfo/component_name=APP_TIMELINE_SERVER|ServiceComponentInfo/category=MASTER&fields=ServiceComponentInfo/Version,ServiceComponentInfo/StartTime,ServiceComponentInfo/HeapMemoryUsed,ServiceComponentInfo/HeapMemoryMax,ServiceComponentInfo/service_name,host_components/HostRoles/host_name,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/metrics/jvm/memHeapUsedM,host_components/metrics/jvm/HeapMemoryMax,host_components/metrics/jvm/HeapMemoryUsed,host_components/metrics/jvm/memHeapCommittedM,host_components/metrics/mapred/jobtracker/trackers_decommissioned,host_components/metrics/cpu/cpu_wio,host_components/metrics/rpc/RpcQueueTime_avg_time,host_components/metrics/dfs/FSNamesystem/*,host_components/metrics/dfs/namenode/Version,host_components/metrics/dfs/namenode/DecomNodes,host_components/metrics/dfs/namenode/TotalFiles,host_components/metrics/dfs/namenode/UpgradeFinalized,host_components/metrics/dfs/namenode/Safemode,host_components/metrics/runtime/StartTime,host_components/metrics/hbase/master/IsActiveMaster,ServiceComponentInfo/MasterStartTime,ServiceComponentInfo/MasterActiveTime,ServiceComponentInfo/AverageLoad,ServiceComponentInfo/Revision,ServiceComponentInfo/RegionsInTransition,host_components/metrics/yarn/Queue,ServiceComponentInfo/rm_metrics/cluster/activeNMcount,ServiceComponentInfo/rm_metrics/cluster/unhealthyNMcount,ServiceComponentInfo/rm_metrics/cluster/rebootedNMcount,ServiceComponentInfo/rm_metrics/cluster/decommissionedNMcount&minimal_response=true

> Error message: org.apache.ambari.server.controller.spi.SystemException: An internal system
exception occurred: Could not find service for component, componentName=APP_TIMELINE_SERVER,
clusterName=cl1, stackInfo=HDP-2.0.6
> {code}
> See also screenshot attached



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message