javax.security.sasl.SaslException: Failure to initialize security context [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos credentails)

[wangbin83-gmail-com]

Alluxio Version:
release-2.8.1

Describe the bug
Using HDFS as the alloxio UFS, HDFS enables secure mode, and the corresponding configuration and ticket credentials for KerberOS are correct. However, when starting alloxio, the job_ Worker startup failed, and the log shows that the ticket voucher cannot be found and the leader master cannot be connected. The error message is as follows:

Expected behavior
I hope that the cluster can be used normally after using kerberos authentication

Urgency
This issue has a significant impact, leading to project stagnation

[jasondrogba]

you can look at Connect to Secure HDFS.
You can put the contents of conf/alluxio-site.properties here, to make sure and check that there are no problems with your configuration.

[wangbin83-gmail-com]

alluxio-site.properties

[jasondrogba]

reference: connect to Secure HDFS

A known limitation is that the Kerberos TGT may expire after the max renewal lifetime. You can work around this by renewing the TGT periodically. Otherwise you may see No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt) when starting Alluxio services. Another option is to set alluxio.hadoop.security.kerberos.keytab.login.autorenewal=true so the TGT is automatically refreshed.

Maybe you can try this. but release-2.8.1 do not have alluxio.hadoop.kerberos.keytab.login.autorenewal.
you can use release-2.9.3.
alluxio.hadoop.kerberos.keytab.login.autorenewal is correct, hdfs doc has updated #18487