Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 6 Jun 2017 19:41:18 +0000 (UTC)
From: "Yongjun Zhang (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.13077779.1496778027000.9730.1496778078108@Atlassian.JIRA>
In-Reply-To: <JIRA.13077779.1496778027000@Atlassian.JIRA>
References: <JIRA.13077779.1496778027000@Atlassian.JIRA> <JIRA.13077779.1496778027164@jira-lw-us.apache.org>
Subject: [jira] [Created] (HDFS-11938) Logs for KMS delegation token
 lifecycle
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Jun 2017 19:41:23 -0000

Yongjun Zhang created HDFS-11938:
------------------------------------

             Summary: Logs for KMS delegation token lifecycle
                 Key: HDFS-11938
                 URL: https://issues.apache.org/jira/browse/HDFS-11938
             Project: Hadoop HDFS
          Issue Type: Improvement
            Reporter: Yongjun Zhang


We run into quite some customer cases about authentication failures related to KMS delegation token. It would be nice to see a log for each stage of the token:
1. creation
2. renewal
3. removal upon cancel
4. remove upon expiration
So that when we correlate the logs for the same DT, we can have a good picture about what's going on, and what could have caused the authentication failure.

The same is applicable to other delegation tokens.

NOTE: When log info about delagation token, we don't want leak user's secret info.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org