Support Questions
Find answers, ask questions, and share your expertise

Ambari performance issue

Solved Go to solution
Highlighted

Ambari performance issue

Rising Star

Need help in troubleshooting the performance issue. Every little things on Ambari, starting from logging in to Navigating , to make configuration changes is extremely slow and sometime it also times out. NameNode/Ambari-server has 32GB and other node in the cluster are 16GB and 8 GB and have no load. What may be causing this behaviour..

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Ambari performance issue

Super Mentor

@Prakash Punj

You can refer to the following article which explains some very common areas to look for when we see the Slowness on Ambari: https://community.hortonworks.com/articles/131670/ambari-server-performance-tuning-troubleshooting-c...

.

If your Ambari Cluster is bit old then it is highly possible that the DB size has grown a bit, So many times "db-cleanup" helps to improve the performance much.

From Ambari 2.5.2 Onwards: From Ambari 2.5.2 onwards the name of this operation will be changed to "db-purge-history" and apart from the Alert related tables it should also consider of other tables lie host_role_command and execution_commands and if there is any other tables as well.

# ambari-server db-purge-history --cluster-name Prod --from-date 2017-08-01

See: https://docs.hortonworks.com/HDPDocuments/Ambari-2.5.2.0/bk_ambari-administration/content/purging-am...

.

View solution in original post

2 REPLIES 2
Highlighted

Re: Ambari performance issue

Super Mentor

@Prakash Punj

You can refer to the following article which explains some very common areas to look for when we see the Slowness on Ambari: https://community.hortonworks.com/articles/131670/ambari-server-performance-tuning-troubleshooting-c...

.

If your Ambari Cluster is bit old then it is highly possible that the DB size has grown a bit, So many times "db-cleanup" helps to improve the performance much.

From Ambari 2.5.2 Onwards: From Ambari 2.5.2 onwards the name of this operation will be changed to "db-purge-history" and apart from the Alert related tables it should also consider of other tables lie host_role_command and execution_commands and if there is any other tables as well.

# ambari-server db-purge-history --cluster-name Prod --from-date 2017-08-01

See: https://docs.hortonworks.com/HDPDocuments/Ambari-2.5.2.0/bk_ambari-administration/content/purging-am...

.

View solution in original post

Highlighted

Re: Ambari performance issue

Rising Star

thanks @Jay SenSharma. I just find out about this article. Will go through...

Don't have an account?