[AMBARI-18545] Kerberos server actions should not timeout in minutes as specified in configuration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.2
• Fix Version/s: 2.5.0
• Component/s: ambari-server
• Labels: kerberos
• Assignee: Robert Levas
• Reporter: Robert Levas
• Created: 06/Oct/16 13:29
• Updated: 10/Oct/16 17:40
• Resolved: 10/Oct/16 15:17

Description

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

if  server.task.timeout < X 
  timeout = X;
else 
  timeout =  server.task.timeout

Where X is set to something like 10 hours. 

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.

Issue Links

• links to: ReviewBoard