[HADOOP-18581] Handle Server KDC re-login when Server and Client run in same JVM.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.1
• Fix Version/s: 3.4.0
• Component/s: common
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: Surendra Singh Lilhore
• Reporter: Surendra Singh Lilhore
• Created: 20/Dec/22 10:01
• Updated: 27/Jan/24 08:53
• Resolved: 08/Jan/23 18:26

Description

Handle re-login in Server when client, server running in same JVM and client trying to re-login, but it fails.

For example, NameNode is server but in same JVM journal node client also running to push to edit logs. When JN client try to re-login and it fails, it will destroy server service ticket also and NameNode not able to server client request. We can see the below error logs in NameNode log file.

 

Auth failed for x.x.x.x:42199:null (GSS initiate failed) with true cause: (GSS initiate failed)
Auth failed for x.x.x.x:42199:null (GSS initiate failed) with true cause: (GSS initiate failed)
Auth failed for x.x.x.x:42199:null (GSS initiate failed) with true cause: (GSS initiate failed)

Same discussion happened in HADOOP-17996.

Issue Links

• is related to: HADOOP-17996 UserGroupInformation#unprotectedRelogin sets the last login time before logging in
• links to: GitHub Pull Request #5248