Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mount the Kerberized HDFS using the Hadoop 3.2 can't autorenew Kerberos TGT #18611

Open
xiaozhch5 opened this issue May 16, 2024 · 0 comments
Open
Labels
type-bug This issue is about a bug

Comments

@xiaozhch5
Copy link

Alluxio Version:
2.9.1
2.9.3

Describe the bug
I downloaded the official Alluxio tar package and repackaged it into an Alluxio image to run Alluxio on Kubernetes.

When I mount the Kerberized HDFS using the Hadoop 3.2 client (alluxio-underfs-hadoop-3.2-2.9.3.jar) and set alluxio.hadoop.kerberos.keytab.login.autorenewal=true, Alluxio still throws the error: "No valid credentials provided (Mechanism level: Failed to find any Kerberos TGT)." after the Kerberos TGT expire.

image

I found that the autorenewal function in Hadoop was introduced in version 3.3.0. Therefore, we need to upgrade the Hadoop version to at least 3.3.0 to ensure that the autorenewal function works properly.

To Reproduce
Mount the Kerberized HDFS with hadoop 3.2
Expected behavior

Alluxio should autorenew the Kerberos TGT.

Urgency
Describe the impact and urgency of the bug.

Are you planning to fix it
Please indicate if you are already working on a PR.

Additional context
Add any other context about the problem here.

@xiaozhch5 xiaozhch5 added the type-bug This issue is about a bug label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug This issue is about a bug
Projects
None yet
Development

No branches or pull requests

1 participant