[ https://issues.apache.org/jira/browse/AMBARI-18545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Levas updated AMBARI-18545: ---------------------------------- Attachment: AMBARI-18545_trunk_01.patch AMBARI-18545_branch-2.5_01.patch AMBARI-18545_branch-2.4_01.patch > Kerberos server actions should not timeout in minutes as specified in > configuration > ----------------------------------------------------------------------------------- > > Key: AMBARI-18545 > URL: https://issues.apache.org/jira/browse/AMBARI-18545 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.2.2 > Reporter: Robert Levas > Assignee: Robert Levas > Labels: kerberos > Fix For: 2.5.0 > > Attachments: AMBARI-18545_branch-2.4_01.patch, > AMBARI-18545_branch-2.5_01.patch, AMBARI-18545_trunk_01.patch > > > Kerberos related server-side actions should not time out in minutes as > specified in configuration. Some Kerberos-related task can potentially take > a much longer time based on number of hosts and components installed in the > cluster. > The {{Create Principals}} and {{Create Keytab Files}} stages need to be set > to a rather large timeout value such that > {noformat} > if server.task.timeout < X > timeout = X; > else > timeout = server.task.timeout > Where X is set to something like 10 hours. > {noformat} > 10 hours seems to be a reasonable timeout value since it is not possible to > specified an unlimited amount of time give Ambari's current task processing > infrastructure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)