@LeeFan    Usually ambari makes use of the following script to run the alert check for the ats-hbase service.   /var/lib/ambari-server/resources/stacks/HDP/3.0/services/YARN/package/alerts/alert_ats_hbase.py (on Ambari Server) /var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/alerts/alert_ats_hbase.py (On Agent hosts)   Above script relies on the following command to fetch the status.   # su - yarn-ats -c "/usr/hdp/current/hadoop-yarn-client/bin/yarn app -status ats-hbase"     However, in your attached screenshot where we see the alert .. shows the alert was executed 13 hours old alert. It might not be the current status of your ats-hbase.    So can you please try to disable the alert and then enable it after 10 seconds to see if the old alert clears. Ambari UI --> Alerts (from left bottom panel) --> filter (icon) --> "Alert Definition Name" as "ATSv2 HBase Application"          (click on Disable alertand then after 10 seconds to clear the old alert and then enable it back)   ... View more

@girish_khole  It will be highly impossible to tell exactly what all changes are needed in your application when Kafka version changes from 1.0 to 2.0 (similarly Storm version changes from 1.1.0 to 1.2.0). As we do not know which kind of APIs your application is using.   Kafka version changes are from 1.0 to 2.0 which is kind of version upgrade and with any such version upgrade it is possible that there may be few methods removed which were declared as deprecated earlier... or some methods signatures might have changes.. Similarly some new classes and methods are introduced.   So better to go step by step try upgrading the pom.xml dependencies inside your JBoss deployed application and then check if it works ... if you see any NoSuchMethodError/ ClasssNotFountError/ ..etc then accordingly you will need to fix it by referring to the new APIs available as part of the upgraded components. If your question is answered then, Please make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@rvillanueva  HDF and HDP versions can be different in a cluster. They need not to  be exactly same. For example please refer to the https://supportmatrix.hortonworks.com/ Click on "HDP 3.1"  (or click on desired HDF version like HDF 3.4.1.1) and then you will find the compatibility matrix with Ambari + HDF versions. ... View more

@maxolasersquad  One very basic test we can do to verify if the "ambari-server setup" was performed or not is to look for JDBC settings. For example when we simply install ambari server binary on a host then the ambari.properties file will not have any JDBC configs so the output for the following will be empty. Example: (no output on a server where ambari-server setup was not executed) # grep 'jdbc' /etc/ambari-server/conf/ambari.properties However, on a server where setup was executed you will see atleast some jdbc settings as following: # grep 'jdbc' /etc/ambari-server/conf/ambari.properties custom.mysql.jdbc.name=mysql-connector-java.jar custom.oracle.jdbc.name=ojdbc8.jar previous.custom.mysql.jdbc.name=mysql-jdbc-driver.jar server.jdbc.connection-pool=internal server.jdbc.database=postgres server.jdbc.database_name=ambari server.jdbc.postgres.schema=ambari server.jdbc.user.name=ambari server.jdbc.user.passwd=${alias=ambari.db.password} .   ... View more

@Manoj690   Regarding  "how to kill the process" ? 1. Please find the PID of the process which is using port 53. # netstat -tnlpa | grep 53 2. Kill that PID using the following command: # kill -9 $PID You can find the value of $PID form point 1 command.     If your question is answered then, Please make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.  ... View more