Community Articles

Find and share helpful community-sourced technical articles.
Labels (1)

When Ambari executes tasks like START/STOP/RESTART/... , it timeouts after waiting 20mins ( 1200 seconds).

For example Namenode START command waits for 20mins and then mark the service is Failed/Timeout - in larger clusters NameNodes takes much longer time - How to tell Ambari to wait for much longer?

Add below 2 configs and re-start the service - this change increases the timeout value to 1Hour.


Note: This change may not take affect during the Upgrade If it is already scheduled.

0 Kudos
Expert Contributor

Super helpful to know it can be done, but is this the ambari-server conf file you edit or the ambari-agent file? I assume it's ambari-server but it would be nice to have that as a clear call out in the article.


it needs to be updated in file

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.
Version history
Last update:
‎09-13-2018 11:26 PM
Updated by:
Top Kudoed Authors