Support Questions

Find answers, ask questions, and share your expertise

Ambari UI is responding very Slow

avatar

Ambari UI is running slow. Currently, the cluster size is 6 nodes 

1 ACCEPTED SOLUTION

avatar
Master Mentor

@saivenkatg55 

Please don't forget to vote a helpful answer and accept the best answer.

If you found this answer addressed your initial question, please take a moment to login and click "accept" on the answer.

View solution in original post

11 REPLIES 11

avatar

Especially while clicking the services tab like hdfs config etc and it became normal after ambari server restart. Kindly help me to fix this issue.

avatar
Master Mentor

@saivenkatg55 

 

This is nor a silver bullet but worth trying,your ambari database could be overwhelmed scanning through old data to help you narrow down the problem please do the below steps

 

Stop the Ambari Server by using ambari-server stop.
# ambari-server stop

 

Run db-purge-history
Use the cotrrect data format for your server

# ambari-server db-purge-history --cluster-name [PROD] --from-date 2016-04-01

 

Start the Ambari Server: by using ambari-server start .
# ambari-server start

Ref: Tuning Ambari server performance

Please revert l

avatar

@Shelton which date we need to use in the from-date parameter?

avatar
Master Mentor

@saivenkatg55 

The example I gave purges history records created before  First of April 2016 for the cluster named [PROD].

 

You could safely delete data from last month   if you Cluster is named PROD

# ambari-server db-purge-history --cluster-name [PROD]  --from-date 2019-10-31

 

avatar
Expert Contributor

Can you also check heap size utilization for Ambari server. You might need to revisit Ambari server heap config if needed.

 

Check this link for details - https://docs.cloudera.com/HDPDocuments/Ambari-2.7.4.0/administering-ambari/content/amb_adjust_ambari...

 

avatar
Master Mentor

@saivenkatg55 

Any updates your feedback will be appreciated.

avatar

@Shelton I could see some improvement on the UI, after clearing the DB old logs 

avatar
Master Mentor

@saivenkatg55 

Great, can you gauge the improvement in percentage?   Can you back up your ambari.properties and make the below changes to further enhance the Ambari performance I usually script that as a post-install step.

Can you then take time and Accept the solution and close the thread so other members can reference it should they encounter a simpler situation.

 

Purging in the Ambari database from time to time should be an Admin maintenance task 

 

Backup the ambari server properties file

# cp /etc/ambari-server/conf/ambari.properties  /etc/ambari-server/conf/ambari.properties.ORIG

 

Change the timeout of the ambari server


# echo 'server.startup.web.timeout=120' >> /etc/ambari-server/conf/ambari.properties
# echo 'server.jdbc.connection-pool.acquisition-size=5' >> /etc/ambari-server/conf/ambari.properties
# echo 'server.jdbc.connection-pool.max-age=0' >> /etc/ambari-server/conf/ambari.properties
# echo 'server.jdbc.connection-pool.max-idle-time=14400' >> /etc/ambari-server/conf/ambari.properties
# echo 'server.jdbc.connection-pool.max-idle-time-excess=0' >> /etc/ambari-server/conf/ambari.properties
# echo 'server.jdbc.connection-pool.idle-test-interval=7200' >> /etc/ambari-server/conf/ambari.properties

 

Hope that helps

 

Happy hadooping

 

avatar

Sure @Shelton