[
https://issues.apache.org/jira/browse/AMBARI-18545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552390#comment-15552390
]
Hadoop QA commented on AMBARI-18545:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831971/AMBARI-18545_trunk_02.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8822//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8822//console
This message is automatically generated.
> 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)
