Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7AD18181DB for ; Mon, 21 Dec 2015 23:53:48 +0000 (UTC) Received: (qmail 39119 invoked by uid 500); 21 Dec 2015 23:53:47 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 38551 invoked by uid 500); 21 Dec 2015 23:53:46 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 38477 invoked by uid 99); 21 Dec 2015 23:53:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Dec 2015 23:53:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A739B2C1F54 for ; Mon, 21 Dec 2015 23:53:46 +0000 (UTC) Date: Mon, 21 Dec 2015 23:53:46 +0000 (UTC) From: "Arpit Agarwal (JIRA)" To: common-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HADOOP-12664) UGI auto-renewer does not verify kinit availability during initialization MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Arpit Agarwal created HADOOP-12664: -------------------------------------- Summary: UGI auto-renewer does not verify kinit availability during initialization Key: HADOOP-12664 URL: https://issues.apache.org/jira/browse/HADOOP-12664 Project: Hadoop Common Issue Type: Improvement Reporter: Arpit Agarwal Priority: Minor UGI auto-renewer does not verify that {{hadoop.kerberos.kinit.command}} is in the path during initialization. If not available, the auto-renewal thread will hit an error during TGT renewal. We recently saw a case where it manifests as transient errors during client program execution which can be hard to track down without UGI logging. It seems like {{kinit}} availability should be verified during initialization to make the behavior more predictable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)