You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Jim Brennan (Jira)" <ji...@apache.org> on 2020/11/03 15:29:00 UTC

[jira] [Created] (HADOOP-17342) Creating a token identifier should not do kerberos name resolution

Jim Brennan created HADOOP-17342:
------------------------------------

             Summary: Creating a token identifier should not do kerberos name resolution
                 Key: HADOOP-17342
                 URL: https://issues.apache.org/jira/browse/HADOOP-17342
             Project: Hadoop Common
          Issue Type: Improvement
          Components: common
    Affects Versions: 2.10.1, 3.4.0
            Reporter: Jim Brennan


This problem was found and fixed internally for us by [~daryn].

Creating a token identifier tries to do auth_to_local short username translation. The authentication process creates a blank token identifier for deserializing the wire format. Attempting to resolve an empty username is useless work.

Discovered the issue during fair call queue backoff testing. The readers are unnecessary slowed down by this bug.





--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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