@Shelton Glad that you reproduce this problem. I have ten brokers and every broker is configured with their respective IP addresses but I am afraid I cannot provide screenshot for some reasons. I have a workaround for this problem. In my own opinion, the reason of this problem is that Ambari cannot recognize IP and port bindings correctly. So to solve this is to avoiding the challenge for it. Here is my configuration now:   listeners=SASL_PLAINTEXT://0.0.0.0:9092,EXTERNAL://0.0.0.0:19092 advertised.listeners=SASL_PLAINTEXT://192.168.1.1:9092,EXTERNAL://88.88.88.88:19092 The other configurations stay unchanged. Notice that I change `listeners` so that even Ambari  cannot recognize the right IP and port binding, both ports are now available on all interfaces so there are no false alerts now. Thanks you so much for helping me on this problem and apologize for this late response. ... View more

@neha_t_jain  Great I have seen a similar question of a member asking HDP compatibility with Java 12 it's unfortunate the open sourceness of Java is gone and some companies will have to pay to use it. HDP being a packaged software need rigorous unitary tests for all the components which as you know are many so the certification of  a new version of Java will take a while which in one way is good because it gives software testers time to uncover memory leaks etc. Having said that if my response answered you then take some time to mark it as a solution so other members can easily resolve similar queries and avoid creating new threads  ... View more

@m4x1m1li4n  To validate the zookeeper ports can you run the snippets and share the output, it seems CDH uses the port 4181 for its zookeeper I am from the HDP world!   Using port 2181 echo "stat" | nc server.example.org 2181 | grep Mode $ telnet slave3.sysdatadigital.it 2181 Using port 4181 echo "stat" | nc slave3.sysdatadigital.it 4181 | grep Mode $ telnet slave3.sysdatadigital.it 4181   Disable the firewall in the VPC which is a subnet doesn't  disable the firewall on the host please validate that all the hosts  have the firewall disable  Assuming you are on Centos/RHEL 7 and share the output readapt if your OS is different # systemctl status firewalld   From your CM can you share the zookeeper screenshot ... View more

Thanks adding my IP works. ... View more

@mike_bronson7  Yes, it's possible to deploy HDF using Ambari blueprints.  If you compared an HDP and HDF blueprint you will notice a difference in the components section only. Deploy HDF 1 using a blueprint Deploy HDF 2 using a blueprint Deploy HDF 3 using a blueprint  Above are some links that show the possibility      ... View more

@MIkeL  The best technical reference before you embark on deploying your cluster is to check the compatibility of the different moving parts of HDP/Cloudera binaries against an operating system of your choice, the first source of truth is please filter all the possible valid options using   supportmatrix cloudera/hortonworks tool Hortonworks and Cloudera do run exhaustive tests on a particular Operating system before certifying it as production-ready and from the about  RHEL/Centos 7.7 are not yet certified so I highly doubt whether  RHEL/Centos 8  is certified that explains the Python errors you are encountering. HTH ... View more

@Anuj  Here is the official steps from the Ambari.org read through and follow the steps  look at my steps for checking the zookeeper entries  Step-by-step guide  Using Ambari Set AMS to maintenance Stop AMS from Ambari Identify the following from the AMS Configs screen 'Metrics Service operation mode' (embedded or distributed) hbase.rootdir  hbase.zookeeper.property.dataDir AMS data would be stored in 'hbase.rootdir' identified above. Backup and remove the AMS data. If the Metrics Service operation mode is 'embedded', then the data is stored in OS files. Use regular OS commands to backup and remove the files in hbase.rootdir is 'distributed', then the data is stored in HDFS. Use 'hdfs dfs' commands to backup and remove the files in hbase.rootdir Remove the AMS zookeeper data by backing up and removing the contents of 'hbase.tmp.dir'/zookeeper Remove any Phoenix spool files from 'hbase.tmp.dir'/phoenix-spool folder Restart AMS using Ambari I take the above a step further by locating  the zookeeper executable usually in /usr/hdp/{hdp_version}/zookeeper/bin/ Log into zookeeper [zookeeper@osaka bin]$ ./zkCli.sh List the root leaf structure you should see ambari-metrics-cluster should look like below [zk: localhost:2181(CONNECTED) 0] ls / [cluster, registry, controller, brokers, storm, zookeeper, infra-solr, hbase-unsecure, admin, isr_change_notification, log_dir_event_notificat ion, controller_epoch, hiveserver2, hiveserver2-leader, rmstore, atsv2-hbase-unsecure, consumers, ambari-metrics-cluster, latest_producer_id_b lock, config] Now check the entries under ambari-metrics-cluster, you should find something like below ls /ambari-metrics-cluster/INSTANCES/ FQDN_12001 Delete the entry that corresponds to your cluster [zk: localhost:2181(CONNECTED) 25] rmr /ambari-metrics-cluster/INSTANCES/FQDN_12001 Restart the AM this should recreate a new entry in zookeeper ... View more