About Shelton

Shelton · ‎09-03-2018

@lam rab Did you do the post upgrade steps mentionned in Migrate Ambari Metrics Data that could be probably the cause. Never ignore researching before any upgrade so as not to miss some post-upgrade Tasks. Upgrades are NEVER all smooth otherwise no fun 🙂 Please accept the answer to close the thread.

Shelton · ‎09-01-2018

@lam rab Cleaning up the AMS data would remove all the historical AMS data available Step-by-step guide 1.Using Ambari a.Set AMS to maintenance b.Stop AMS from Ambari c.Identify the following from the AMS Configs screen i.'Metrics Service operation mode' (embedded or distributed) ii.hbase.rootdir iii.hbase.zookeeper.property.dataDir 2.AMS data would be stored in 'hbase.rootdir' identified above. Backup and remove the AMS data. a. If the Metrics Service operation mode i.is 'embedded', then the data is stored in OS files. Use regular OS commands to backup and remove the files in hbase.rootdir ii.is 'distributed', then the data is stored in HDFS. Use 'hdfs dfs ' commands to backup and remove the files in hbase.rootdir 3. Remove the AMS zookeeper data by backing up and removing the contents of 'hbase.tmp.dir'/zookeeper 4.Remove any Phoenix spool files from 'hbase.tmp.dir'/phoenix-spool folder 5.Restart AMS using Ambari HTH

Shelton · ‎08-31-2018

@Michael North The znode is created when you fire up zk it read and uploads the config of most of the components. I would think you need to revise your hive setup. Switch directory to /usr/hdp/current/zookeeper-client/ $ ./bin/zkCli.sh Could you check your ZK namespace under the hiveserver2 path you should have an entry like below [zk: localhost:2181(CONNECTED) o] ls /hiveserver2 [serverUri=nakuru.kenya.ke:10000;version=1.2.1000.2.6.2.0-205;sequence=0000000061] [zk: localhost:2181(CONNECTED) 1] Can you check if HS2 can reach 2181 port of ZK host which in your case is the same machine? Have you configured a metastore for your hive either MySQL, Postgres or otherwise? if not you need to do that See my attached screenshot When the HS2 is running and only then when you restart will zk pick the configuration and the znode as shown above HTH

Shelton · ‎08-29-2018

@Raffaele S That's the default behavior if you are using AD it appends the REALM to username.

Shelton · ‎08-29-2018

@Raffaele S To avoid unwanted groups and users loaded please see this HCC doc

Shelton · ‎08-28-2018

@CrazyMinion Can you setup the passwordless connection between Ambari-server and the other hosts in the cluster? To add on disable the firewall,ensure NTP is working after doing all these steps ,restart the cluster and then revert with the new error s if any HTH

Shelton · ‎08-27-2018

@Arjun Das What is the output of the command $ sudo hostname Check the hostname $ sudo nano /etc/hostname Edit hostname sudo nano /etc/hosts Make sure your hostname maps to the ip like 127.0.1.1 hostname alias If you have made changes in the previous steps then restart the server $ sudo shutdown -r now And again as reiterated by jay zipped the ambari log and share

Shelton · ‎08-27-2018

@Arjun Das Can you at least share 200 lines of the /var/log/ambari-server/ambari-server.log in your ambari.properties make sure the server.jdbc.hostname= [FQDN] matches your hostname -f output.

Shelton · ‎08-27-2018

@li Hao Great it worked for you... NOT really you can use any name you wish I just used it for convenience to enable identification between the component users/databases.

Shelton · ‎08-26-2018

@li Hao Can you try setting up a new database for Ranger? Here the assumption is the: Root password is test2345 Ranger user, database and password is ranger ################################################## # Create the ranger user and database schema. ################################################## mysql -u root -ptest2345 create user 'ranger'@'localhost' identified by 'ranger'; grant all privileges on *.* to 'ranger'@'%'; grant all privileges on *.* to 'ranger'@'localhost'; grant all privileges on *.* to 'ranger'@'fqdn'; grant all privileges on *.* to 'ranger'@'fqdn' identified by 'ranger' with grant option; grant all privileges on *.* to 'ranger'@'localhost' identified by 'ranger' with grant option; flush privileges; quit; Log on as user ranger ################################################## # As ranger user create the database ################################################## mysql -u ranger -pranger Create database ranger; quit; Now get back to the Ambari UI and retry installing Ranger all should be fine. Remember to drop that old database after successfully configuring ranger. HTH

Online	Offline
Last Visited	‎12-11-2025 11:50 PM

Member Since	‎01-19-2017 04:35 AM
Last Visited	‎12-11-2025 11:50 PM
Posts	3,679
Kudos received	627

Cloudera Community

Re: Apache nifi memory consumption in kubernetes

Re: Nifi toolkit command for GitLabFlowRegistry

Re: Not able to delete the NiFi existing flow usin...

Re: Securing Nifi with SSL and using OIDC provider...

Re: External zookeeper and nifi cluster connection...

Re: Ambari metric collecto down

Re: Ambari metric collecto down

Re: hiveserver2 not starting (Zookeeper not ready)

Re: NiFi Authorization with Ranger in Kerberized e...

Re: NiFi Authorization with Ranger in Kerberized e...

Re: Active Namenode is Down in Hadoop

Re: Hi i am getting the following errors while sta...

Re: Hi i am getting the following errors while sta...

Re: can't install ranger

Re: can't install ranger