SASL authentication not complete

[yaoxiaowei0909]

使用sql任务执行 建表时报错，点击“重跑失败任务”后成功。
错误信息如下：
[ERROR] 2023-04-08 00:00:02.882 +0800 - execute sql error: org.apache.thrift.transport.TTransportException: SASL authentication not complete
[ERROR] 2023-04-08 00:00:02.882 +0800 - sql task error
java.sql.SQLException: org.apache.thrift.transport.TTransportException: SASL authentication not complete
at org.apache.hive.jdbc.HiveStatement.closeClientOperation(HiveStatement.java:211)
at org.apache.hive.jdbc.HiveStatement.close(HiveStatement.java:228)
at com.zaxxer.hikari.pool.ProxyStatement.close(ProxyStatement.java:75)
at org.apache.dolphinscheduler.plugin.task.sql.SqlTask.executeUpdate(SqlTask.java:332)
at org.apache.dolphinscheduler.plugin.task.sql.SqlTask.executeFuncAndSql(SqlTask.java:202)
at org.apache.dolphinscheduler.plugin.task.sql.SqlTask.handle(SqlTask.java:158)
at org.apache.dolphinscheduler.server.worker.runner.TaskExecuteThread.run(TaskExecuteThread.java:208)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125)
at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57)
at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
Caused by: org.apache.thrift.transport.TTransportException: SASL authentication not complete
at org.apache.thrift.transport.TSaslTransport.write(TSaslTransport.java:474)
at org.apache.thrift.transport.TSaslClientTransport.write(TSaslClientTransport.java:37)
at org.apache.thrift.protocol.TBinaryProtocol.writeI32(TBinaryProtocol.java:178)
at org.apache.thrift.protocol.TBinaryProtocol.writeMessageBegin(TBinaryProtocol.java:106)
at org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:70)
at org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:62)
at org.apache.hive.service.rpc.thrift.TCLIService$Client.send_CloseOperation(TCLIService.java:507)
at org.apache.hive.service.rpc.thrift.TCLIService$Client.CloseOperation(TCLIService.java:499)
at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hive.jdbc.HiveConnection$SynchronizedHandler.invoke(HiveConnection.java:1426)
at com.sun.proxy.$Proxy178.CloseOperation(Unknown Source)
at org.apache.hive.jdbc.HiveStatement.closeClientOperation(HiveStatement.java:205)
... 13 common frames omitted

[Cocytus316]

me too,my hive scheduling also reports this error from time to time.The critical recovery failure succeeded again.
Have you solved it yet?

[Cocytus316]

hi,guy.After various attempts, I suspect the datasource cache expiration mechanism is to blame.

In the common.properties configuration file, kerberos.expire.time=2. In theory, it should expire only if not updated or used for 2 hours.
This cache should have been added for Kerberos, but currently, it seems that even the active connections are being forcibly removed from the cache. Since my cluster does not use Kerberos authentication, I changed kerberos.expire.time to a very large number, such as 80000. Currently, Hive tasks seem to be running normally.

[jack-wqing]

better way: expireAfterWrite -> expireAfterAccess