You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Surendra Singh Lilhore (Jira)" <ji...@apache.org> on 2022/12/20 10:04:00 UTC
[jira] [Updated] (HADOOP-18581) Handle Server KDC re-login when Server and Client run in same JVM.
[ https://issues.apache.org/jira/browse/HADOOP-18581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Surendra Singh Lilhore updated HADOOP-18581:
--------------------------------------------
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.
{noformat}
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){noformat}
Same discussion happened in HADOOP-17996.
was:
Handle re-login in Server when client and 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.
{noformat}
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){noformat}
Same discussion happened in HADOOP-17996.
> Handle Server KDC re-login when Server and Client run in same JVM.
> ------------------------------------------------------------------
>
> Key: HADOOP-18581
> URL: https://issues.apache.org/jira/browse/HADOOP-18581
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
> Priority: Major
>
> 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.
>
> {noformat}
> 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){noformat}
> Same discussion happened in HADOOP-17996.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org