@Michael Bronson Ambari API dos not have a support to return boolean true or false as result for the asked question. The nearest information that you can get from ambari API is as below and then you will need to have small client side logic to calculate the boolean 1. Ambari API to return list of all components in the cluster that are down http://localhost:8080/api/v1/clusters/c4/components?(ServiceComponentInfo/init_count!=0|ServiceComponentInfo/install_failed_count!=0|ServiceComponentInfo/installed_count!=0)&ServiceComponentInfo/category!=CLIENT&minimal_response=true The response to above APIs will look like as below and implies that some instances of DataNode and NodeManager are down. We can ofcourse also know which one specifically are down but it seems as per the question that it is not of interest. {items: [ { ServiceComponentInfo: { component_name: "DATANODE" } }, { ServiceComponentInfo: { component_name: "NODEMANAGER" } } ]} 2. Ambari API to return list of all components of a specific service (HDFS in below example) that are down http://localhost:8080/api/v1/clusters/c4/components?(ServiceComponentInfo/init_count!=0|ServiceComponentInfo/install_failed_count!=0|ServiceComponentInfo/installed_count!=0)&ServiceComponentInfo/category!=CLIENT&ServiceComponentInfo/service_name=HDFS&minimal_response=true Note: Replace localhost with ambari server host name ... View more

@Joshua Connelly Thanks for reporting this issue. From the description, this issue looks to be an ambari bug. can you please create Apache Ambari Jira for this ? Let us know on this thread when you create bug. We will look into it and address it in the next ambari release. Also you mentioned in your description that this issue was noticed on HDP-2.6.2.14 and the tag to this question is of ambari-2.2.0 But ambari-2.2.0 does not support HDP-2.6.2.14. can you please verify these version related information for both HDP and Ambari ? For now, to get around this issue, you will need to edit a file on ambari-server host at location /var/lib/ambari-server/resources/stacks/HDP/2.0.6/services/stack_advisor.py. Comment out config items for now in this file at code link Ambari will then not recommend any changes to these configs whenever you attempt to change any other configs on your cluster ... View more

Thanks for the information @Amine ZITOUNI I was able to confirm that this is an existing issue in ambari since version 2.2.2 When Namenode HA is enabled and the default port for namenode is changed, quicklinks does not reflect the changed port Please report this as ambari bug at https://issues.apache.org/jira/projects/AMBARI and inform us on this thread. We will look to address this issue in upcoming version of ambari ... View more

@Amine ZITOUNI can you please let us know the release version of Apache Ambari that you are using ? ... View more

@Shishir Saxena As per your description, This looks to me most likely case of some JavaScript error in ambari-web (bug). if you can let us know what version of ambari you are using and the JS error trace that you are hitting, it will help us debug further in the issue and verify if it's a known issue or not. you can fetch JS error by using google chrome and executing same steps. Before you click next, please open developers tool of chrome and look for console tab. you can also filter the level to Error, so other info level information is not dumped and you are only presented with JS errors. Also clicking on that error should navigate to the code that is throwing that error. ... View more

@suresh krish Ambari APIs responses only in Json format. if you need an xml file for a specific service of a specific HDP stack by which you can get service's version then it would be metainfo.xml file for that service. you can fetch such service's metainfo.xml from ambari-server host at location /var/lib/ambari-server/resources/stacks/HDP/$StackVersion/services/$serviceName/metainfo.xml Please substitute $StackVersion and $serviceName with actual desired values. For example: /var/lib/ambari-server/resources/stacks/HDP/2.6/services/HDFS/metainfo.xml The same can be browsed on github at link ... View more

@William Brooks In the widget context, only service page widgets are persisted in ambari db, their definition is REST API driven and So it allows to add user defined widgets. It has "Create Widget" wizard that allows user to do so. Dashboard page widgets and host page widgets and their definition is still completely coded in ambari-web JS code. so to add any new widget as of now, new widget definition code needs to be added in ambari-web JS code. Pointers to the host page widget definition code: https://github.com/apache/ambari/tree/trunk/ambari-web/app/views/main/host/metrics ... View more

@David Pocivalnik It is ok to have service that only has slave. Flume service is a working example for that: https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/metainfo.xml There seems to be something else in the custom service that you defined which might be causing this issue. Does the new custom service has any configurations ? can you also post zip file for the custom hbase service that you are introducing ? ... View more

@David Pocivalnik every time recommendation API call is made, new entry for logs is made at path "/var/run/ambari-server/stack-recommendations/" on ambari-server host. there will be several and if you are not certain about the last entry then please move all historical existing entries to different location and then again go through add service wizard to produce a repro. Entry will have stackadvisor.err and stackadvisor.out files. Please refer them for further debugging the issue. If it's not clear from logs, please compress the directory and post it on this thread, So that we can get more information for debugging purpose. ... View more

@Yurii Tymchii In addition to what @rnettleton suggested, please also share detailed error that will be logged when the API call resulting in 500 server error is made. ambari-server log is located at /var/log/ambari-server/ambari-server.log location on the host. This will help us to understand the cause of the failure. ... View more

@Ben Weintraub I assume that your question is in context of ui driven service deployment (ambari-web installer or add service wizard). There is no such property in released versions of ambari that will make HDFS/SECONDARY_NAMENODE the default node for custom service will be installed on. Although as I said in my previous comment that service developer can always add python code to achieve such requirements in custom service's service advisor. Also in the ambari trunk some work has already been done to achieve similar requirement in decalarative manner rather than writing python code. This has been done via AMBARI-19685. It's associated reviewboard (link) has the images of how ui will react when host scope dependency is added for some component. Although this is not exactly what you are looking for, it will help your use-case. If MY_SERVICE/MY_COMPONENT is not hosted on HDFS/SECONDARY_NAMENODE then user will be prompted with the error message before they move forward. This is a validation and I understand that you are more looking for default recommendation, so that by default MY_SERVICE/MY_COMPONENT is hosted on HDFS/SECONDARY_NAMENODE when user lands on "Assign Masters" page for the first time and if user overrides the default presented layout, then in that case AMBARI-19685 validation work should show the message for component level dependency violation. Please report your requirement as a task at apache ambari Jira and let us know over here. I will follow up on the reported jira and try to add this functionality as part of being developed Ambari-3.0.0 release. ... View more

@Ben Weintraub Adding host scope dependency at component level will make sure that the dependent component is co-hosted with the needed one. This is done by default in blueprint based deployment. Post ambari-2.5.0 release (trunk of ambari), work has been done to make sure that UI deployments also forces users to co-host required components as marked in the stack. Although user can choose to deploy MY_SERVICE/MY_COMPONENT on some additional hosts as well in either blueprint or ui based deployment which will be permitted. If you strictly want to restrict user to have MY_SERVICE/MY_COMPONENT only on HDFS/SECONDARY_NAMENODE than you can add that logic as python code in service advisor of the custom service. HAWQ service had some specific requirements for which they added the logic in it's service advisor. you can refer it as an example: https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/service_advisor.py#L100-L121 ... View more

@Neil Watson API /api/v1/clusters/dev15/configurations?type=hive-site will give you all versions of hive-site. ambari-web UI does not show versions of particular config type (Example hive-site, core-site) in any of its user interface. ambari-web shows config versions for a service (Example: hive, hdfs, etc) on service config page and dashboard config history page. config versions for a service gets incremented everytime when a config related to service is changed. Thus if hive-site has 13 versions and service config versions for hive has 17 versions, it means that there were 4 times hive service config changes that did not involved any changes in hive-site. changes could have been in other sites related to hive like hive-env, webhcat-site, hive-log4j, etc if you want to see from REST API v17 config version for hive service, you can use following API that ambari-web uses: http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/configurations/service_config_versions?service_name=HIVE&service_config_version=17 ... View more

@sakshi chourasiaFollowing python files are used while collecting system related information on the host by ambari: https://github.com/apache/ambari/blob/trunk/ambari-agent/src/main/python/ambari_agent/HostInfo.py https://github.com/apache/ambari/blob/trunk/ambari-agent/src/main/python/ambari_agent/Facter.py When ambari-agent resgisters with ambari-server, json blob reported by ambari-agent look like following: {'hardwareProfile': {'kernel': 'Linux', 'domain': 'twcable.com', 'physicalprocessorcount': 24, 'kernelrelease': '2.6.32-431.el6.x86_64', 'uptime_days': '253', 'memorytotal': 132119088, 'swapfree': '15.99 GB', 'memorysize': 132119088, 'osfamily': 'redhat', 'swapsize': '16.00 GB', 'processorcount': 24, 'netmask': '255.255.255.0', 'timezone': 'EST', 'hardwareisa': 'x86_64', 'memoryfree': 125668248, 'operatingsystem': 'redhat', 'kernelmajversion': '2.6', 'kernelversion': '2.6.32', 'macaddress': 'A0:D3:C1:FB:61:E5', 'operatingsystemrelease': '6.5', 'ipaddress': '10.64.193.239', 'hostname': 'hdpdedge02', 'uptime_hours': '6089', 'fqdn': 'hdpdedge02.twcable.com', 'id': 'root', 'architecture': 'x86_64', 'selinux': False, 'mounts': [{'available': '4253556', 'used': '7502756', 'percent': '64%', 'device': '/dev/mapper/vg_root-lv_root', 'mountpoint': '/', 'type': 'ext4', 'size': '12385456'}, {'available': '66059396', 'used': '148', 'percent': '1%', 'device': 'tmpfs', 'mountpoint': '/dev/shm', 'type': 'tmpfs', 'size': '66059544'}, {'available': '414292', 'used': '75536', 'percent': '16%', 'device': '/dev/sda1', 'mountpoint': '/boot', 'type': 'ext3', 'size': '516040'}, {'available': '6606020', 'used': '1231504', 'percent': '16%', 'device': '/dev/mapper/vg_root-lv_export', 'mountpoint': '/export', 'type': 'ext4', 'size': '8256952'}, {'available': '7871164', 'used': '3885148', 'percent': '34%', 'device': '/dev/mapper/vg_root-lv_opt', 'mountpoint': '/opt', 'type': 'ext4', 'size': '12385456'}, {'available': '2877288', 'used': '1041448', 'percent': '27%', 'device': '/dev/mapper/vg_root-lv_tmp', 'mountpoint': '/tmp', 'type': 'ext4', 'size': '4128448'}, {'available': '7428368', 'used': '409156', 'percent': '6%', 'device': '/dev/mapper/vg_root-lv_var', 'mountpoint': '/var', 'type': 'ext4', 'size': '8256952'}, {'available': '3214473752', 'used': '397069656', 'percent': '11%', 'device': '/dev/mapper/vg_workspace-lv_workspace', 'mountpoint': '/product/ssrt_workspace', 'type': 'ext4', 'size': '3804817056'}, {'available': '97777324', 'used': '192116', 'percent': '1%', 'device': '/dev/mapper/vg_root-lv_hdptmp', 'mountpoint': '/hdptmp', 'type': 'ext4', 'size': '103212320'}, {'available': '10201972', 'used': '4493436', 'percent': '31%', 'device': '/dev/mapper/vg_root-lv_usrhdp', 'mountpoint': '/usr/hdp', 'type': 'ext4', 'size': '15481840'}, {'available': '28894904', 'used': '495940', 'percent': '2%', 'device': '/dev/mapper/vg_root-lv_varlog', 'mountpoint': '/var/log', 'type': 'ext4', 'size': '30963708'}, {'available': '95557412', 'used': '2412028', 'percent': '3%', 'device': '/dev/mapper/vg_root-lv_product', 'mountpoint': '/product/software', 'type': 'ext4', 'size': '103212320'}, {'available': '314251264', 'used': '321536', 'percent': '1%', 'device': 'ncemcorpcifs03.itss.twcable.com:/ifs/data/hdpdedge_app_code', 'mountpoint': '/product/app_code', 'type': 'nfs', 'size': '314572800'}, {'available': '2867454464', 'used': '1212764672', 'percent': '30%', 'device': 'ncemcorpcifs03.itss.twcable.com:/ifs/data/hdpdedge_app_data', 'mountpoint': '/product/app_data', 'type': 'nfs', 'size': '4080219136'}], 'hardwaremodel': 'x86_64', 'uptime_seconds': '21920401', 'interfaces': 'bond0,bond1,eth0,eth1,eth2,eth3,eth5,lo'}, 'currentPingPort': 8670, 'prefix': '/var/lib/ambari-agent/data', 'agentVersion': '2.2.1.0', 'agentEnv': {'transparentHugePage': 'never', 'hostHealth': {'agentTimeStampAtReporting': 1457381979545, 'activeJavaProcs': [{'command': '/opt/tidal/jre1.6.0_29/bin/java -cp /opt/tidal/Agent/lib/agutil.jar:/opt/tidal/Agent/lib/TAgent.jar -Xms16m -Xmx48m JAgent agent=agent_hdpdedge02 port=7105 logdays=7 OSLnk.InActTimeout=600 path=/opt/tidal/Agent bin=/opt/tidal/Agent/lib/LINUX stdout=n jobstoptree=y jobkilltree=y agplatform=LINUX calccpuload=y encryptonly=n sslvldcrt=y sslvldhst= sslvldhstpw= sshvldhst= jobexec64=n multftpstd=y', 'pid': 45319, 'hadoop': False, 'user': 'twcsched'}, {'command': '/usr/jdk64/jdk1.7.0_67/bin/java -Xmx1024m -Dhdp.version=2.2.6.0-2800 -Djava.net.preferIPv4Stack=true -Dhdp.version=2.2.6.0-2800 -Dhadoop.log.dir=/var/log/hadoop/eimetlusr -Dhadoop.log.file=hadoop.log -Dhadoop.home.dir=/usr/hdp/2.2.6.0-2800/hadoop -Dhadoop.id.str=eimetlusr -Dhadoop.root.logger=INFO,console -Djava.library.path=:/usr/hdp/2.2.6.0-2800/hadoop/lib/native/Linux-amd64-64:/usr/hdp/2.2.6.0-2800/hadoop/lib/native -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true -Xmx1024m -XX:MaxPermSize=512m -Dhadoop.security.logger=INFO,NullAppender org.apache.sqoop.Sqoop import --direct --connect jdbc:netezza://10.136.199.55:5480/data_fm --username ********** --password ********** --table MIGRATION_FACT --split-by CUST_ACCT_KEY -m 10 --target-dir /apps/hive/warehouse/lab_test/MIGRATION_FACT --input-fields-terminated-by \xed', 'pid': 48256, 'hadoop': True, 'user': 'eimetlusr'}], 'liveServices': [{'status': 'Healthy', 'name': 'ntpd', 'desc': ''}]}, 'reverseLookup': True, 'alternatives': [], 'umask': '18', 'firewallName': 'iptables', 'stackFoldersAndFiles': [{'type': 'directory', 'name': '/etc/hadoop'}, {'type': 'directory', 'name': '/etc/hive'}, {'type': 'directory', 'name': '/etc/oozie'}, {'type': 'directory', 'name': '/etc/sqoop'}, {'type': 'directory', 'name': '/etc/zookeeper'}, {'type': 'directory', 'name': '/etc/storm'}, {'type': 'directory', 'name': '/etc/hive-hcatalog'}, {'type': 'directory', 'name': '/etc/tez'}, {'type': 'directory', 'name': '/etc/falcon'}, {'type': 'directory', 'name': '/etc/hive-webhcat'}, {'type': 'directory', 'name': '/etc/slider'}, {'type': 'directory', 'name': '/etc/storm-slider-client'}, {'type': 'directory', 'name': '/etc/spark'}, {'type': 'directory', 'name': '/etc/pig'}, {'type': 'directory', 'name': '/etc/ambari-metrics-monitor'}, {'type': 'directory', 'name': '/var/run/hadoop'}, {'type': 'directory', 'name': '/var/run/hive'}, {'type': 'directory', 'name': '/var/run/oozie'}, {'type': 'directory', 'name': '/var/run/zookeeper'}, {'type': 'directory', 'name': '/var/run/storm'}, {'type': 'directory', 'name': '/var/run/falcon'}, {'type': 'directory', 'name': '/var/run/webhcat'}, {'type': 'directory', 'name': '/var/run/hadoop-yarn'}, {'type': 'directory', 'name': '/var/run/hadoop-mapreduce'}, {'type': 'directory', 'name': '/var/run/spark'}, {'type': 'directory', 'name': '/var/run/ambari-metrics-monitor'}, {'type': 'directory', 'name': '/var/log/hadoop'}, {'type': 'directory', 'name': '/var/log/hive'}, {'type': 'directory', 'name': '/var/log/oozie'}, {'type': 'directory', 'name': '/var/log/sqoop'}, {'type': 'directory', 'name': '/var/log/zookeeper'}, {'type': 'directory', 'name': '/var/log/storm'}, {'type': 'directory', 'name': '/var/log/falcon'}, {'type': 'directory', 'name': '/var/log/hadoop-yarn'}, {'type': 'directory', 'name': '/var/log/hadoop-mapreduce'}, {'type': 'directory', 'name': '/var/log/spark'}, {'type': 'directory', 'name': '/var/log/ambari-metrics-monitor'}, {'type': 'directory', 'name': '/usr/lib/hadoop'}, {'type': 'directory', 'name': '/usr/lib/flume'}, {'type': 'directory', 'name': '/usr/lib/storm'}, {'type': 'directory', 'name': '/var/lib/hive'}, {'type': 'directory', 'name': '/var/lib/oozie'}, {'type': 'directory', 'name': '/var/lib/hadoop-hdfs'}, {'type': 'directory', 'name': '/var/lib/hadoop-yarn'}, {'type': 'directory', 'name': '/var/lib/hadoop-mapreduce'}, {'type': 'directory', 'name': '/var/lib/spark'}], 'existingUsers': [{'status': 'Available', 'name': 'hive', 'homeDir': '/home/hive'}, {'status': 'Available', 'name': 'oozie', 'homeDir': '/home/oozie'}, {'status': 'Available', 'name': 'ambari-qa', 'homeDir': '/home/ambari-qa'}, {'status': 'Available', 'name': 'flume', 'homeDir': '/home/flume'}, {'status': 'Available', 'name': 'hdfs', 'homeDir': '/home/hdfs'}, {'status': 'Available', 'name': 'knox', 'homeDir': '/home/knox'}, {'status': 'Available', 'name': 'storm', 'homeDir': '/home/storm'}, {'status': 'Available', 'name': 'spark', 'homeDir': '/home/spark'}, {'status': 'Available', 'name': 'mapred', 'homeDir': '/home/mapred'}, {'status': 'Available', 'name': 'tez', 'homeDir': '/home/tez'}, {'status': 'Available', 'name': 'zookeeper', 'homeDir': '/home/zookeeper'}, {'status': 'Available', 'name': 'kafka', 'homeDir': '/home/kafka'}, {'status': 'Available', 'name': 'falcon', 'homeDir': '/home/falcon'}, {'status': 'Available', 'name': 'sqoop', 'homeDir': '/home/sqoop'}, {'status': 'Available', 'name': 'yarn', 'homeDir': '/home/yarn'}, {'status': 'Available', 'name': 'hcat', 'homeDir': '/home/hcat'}, {'status': 'Available', 'name': 'ams', 'homeDir': '/home/ams'}, {'status': 'Available', 'name': 'ranger', 'homeDir': '/home/ranger'}], 'firewallRunning': False}, 'timestamp': 1457381979468, 'hostname': 'hdpdedge02.twcable.com', 'responseId': -1, 'publicHostname': 'c6401.ambari.apache.org'} some of these host related information is also exposed by ambri-server RESTful API via host resource endpoint: http://localhost:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org Above API will return c6401.ambari.apache.org host information like disk info, memory, os family, etc ... View more

@rama the above error snippet suggests that there might be permission issue with the public ssh key that you upload on this page of the wizard. Usually in my dev environment I give 600 permission to the ssh key and login in user is the owner of the key -rw------- 1 Jaimin staff 1.6K Mar 12 2015 /Users/Jaimin/insecure_private_key ... View more