Community Articles
Find and share helpful community-sourced technical articles
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
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.

agent.task.timeout=3600 
server.task.timeout=3600

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

618 Views
0 Kudos
Comments
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.

Contributor

it needs to be updated in ambari.properties file

Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
1 of 1
Last update:
‎09-13-2018 11:26 PM
Updated by:
 
Contributors
Top Kudoed Authors