ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration
Date Mon, 10 Oct 2016 15:18:20 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Levas updated AMBARI-18545:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk
{noformat}
commit 0a61db5666f3ee8b82cdab0d50a1c8450b177ae7
Author: Robert Levas <rlevas@hortonworks.com>
Date:   Mon Oct 10 11:16:01 2016 -0400
{noformat}

Committed to branch-2.5
{noformat}
commit 367c2c95b260fc41fc6708549efe9cbcb0b3bd95
Author: Robert Levas <rlevas@hortonworks.com>
Date:   Mon Oct 10 11:17:07 2016 -0400
{noformat}


> 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.4_02.patch,
AMBARI-18545_branch-2.5_01.patch, AMBARI-18545_branch-2.5_02.patch, AMBARI-18545_trunk_01.patch,
AMBARI-18545_trunk_02.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)

Mime
View raw message