Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 17774200BAD for ; Mon, 10 Oct 2016 17:18:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1650B160AE1; Mon, 10 Oct 2016 15:18:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 624EF160ACA for ; Mon, 10 Oct 2016 17:18:21 +0200 (CEST) Received: (qmail 84336 invoked by uid 500); 10 Oct 2016 15:18:20 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 84322 invoked by uid 99); 10 Oct 2016 15:18:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Oct 2016 15:18:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 6D40B2C0059 for ; Mon, 10 Oct 2016 15:18:20 +0000 (UTC) Date: Mon, 10 Oct 2016 15:18:20 +0000 (UTC) From: "Robert Levas (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 10 Oct 2016 15:18:22 -0000 [ 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 Date: Mon Oct 10 11:16:01 2016 -0400 {noformat} Committed to branch-2.5 {noformat} commit 367c2c95b260fc41fc6708549efe9cbcb0b3bd95 Author: Robert Levas 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)