Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

best practice for time out values in ambari.properties

best practice for time out values in ambari.properties


hi all


in ambari.properties we have the timeout values

since some times we failed on time out issue

I was thinking how to fit the timeout values to the best prectice


grep time /etc/ambari-server/conf/ambari.properties
agent.package.install.task.timeout=1800
agent.task.timeout=900
recommendations.artifacts.lifetime=1w
server.http.session.inactive_timeout=1800
server.task.timeout=1200
user.inactivity.timeout.default=0
user.inactivity.timeout.role.readonly.default=0
views.ambari.request.connect.timeout.millis=30000
views.ambari.request.read.timeout.millis=45000
views.request.connect.timeout.millis=5000
views.request.read.timeout.millis=10000


what is the best practice for time out values?

or what is the max values that will damage the cluster functionality?

can we achieve this ?



example of timeout problems that we get sometimes , when starting services after new scratch cluster installation

110137-capture.png



Michael-Bronson
Don't have an account?
Coming from Hortonworks? Activate your account here