Delegation Token can be issued only with kerberos or web authenticati

houwenqiang7 2023-11-08 17:36:13

hadoop中hive、hdfs都开启了kerberos认证,使用hive on spark,通过thrift连接hive,可以进行建表、insert values,select操作,。但是创建一个外部表,外部表数据路径在hdfs上,从外部表向hive表插入时,出现Delegation Token can be issued only with kerberos or web authentication错误。

2023-11-08 02:57:11.469 [140233487042304] ExecSQLOnEngineJob::Execute - failed: Error while processing statement: FAILED: Execution Error, return code 3 from org.apache.hadoop.hive.ql.exec.spark.SparkTask. org.apache.hadoop.ipc.RemoteException(java.io.IOException): Delegation Token can be issued only with kerberos or web authentication
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getDelegationToken(FSNamesystem.java:6612)
        at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getDelegationToken(NameNodeRpcServer.java:564)
        at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getDelegationToken(ClientNamenodeProtocolServerSideTranslatorPB.java:1000)
        at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
        at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
        at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
        at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2217)
        at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2213)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:422)
        at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1746)
        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2213)

        at org.apache.hadoop.ipc.Client.call(Client.java:1476)
        at org.apache.hadoop.ipc.Client.call(Client.java:1413)
        at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
        at com.sun.proxy.$Proxy10.getDelegationToken(Unknown Source)
        at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getDelegationToken(ClientNamenodeProtocolTranslatorPB.java:938)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:191)
        at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
        at com.sun.proxy.$Proxy11.getDelegationToken(Unknown Source)
        at org.apache.hadoop.hdfs.DFSClient.getDelegationToken(DFSClient.java:1030)
        at org.apache.hadoop.hdfs.DistributedFileSystem.getDelegationToken(DistributedFileSystem.java:1543)
        at org.apache.hadoop.fs.FileSystem.collectDelegationTokens(FileSystem.java:532)
        at org.apache.hadoop.fs.FileSystem.addDelegationTokens(FileSystem.java:510)
        at org.apache.hadoop.hdfs.DistributedFileSystem.addDelegationTokens(DistributedFileSystem.java:2228)
        at org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:121)
        at org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:100)
        at org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodes(TokenCache.java:80)
        at org.apache.hadoop.mapreduce.lib.input.FileInputFormat.listStatus(FileInputFormat.java:243)
        at org.apache.hadoop.hive.shims.Hadoop23Shims$1.listStatus(Hadoop23Shims.java:131)
        at org.apache.hadoop.mapreduce.lib.input.CombineFileInputFormat.getSplits(CombineFileInputFormat.java:217)
        at org.apache.hadoop.mapred.lib.CombineFileInputFormat.getSplits(CombineFileInputFormat.java:76)
        at org.apache.hadoop.hive.shims.HadoopShimsSecure$CombineFileInputFormatShim.getSplits(HadoopShimsSecure.java:321)
        at org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.getCombineSplits(CombineHiveInputFormat.java:427)
        at org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.getSplits(CombineHiveInputFormat.java:547)
        at org.apache.spark.rdd.HadoopRDD.getPartitions(HadoopRDD.scala:194)
        at org.apache.spark.rdd.RDD

anonfun$partitions$2.apply(RDD.scala:252)atorg.apache.spark.rdd.RDD�������$����������$2.�����(���.�����:252)�����.����ℎ�.�����.���.���

anonfun$partitions$2.apply(RDD.scala:250)
        at scala.Option.getOrElse(Option.scala:121)
        at org.apache.spark.rdd.RDD.partitions(RDD.scala:250)
        at org.apache.spark.rdd.MapPartitionsRDD.getPartitions(MapPartitionsRDD.scala:35)
        at org.apache.spark.rdd.RDD

anonfun$partitions$2.apply(RDD.scala:252)atorg.apache.spark.rdd.RDD�������$����������$2.�����(���.�����:252)�����.����ℎ�.�����.���.���

anonfun$partitions$2.apply(RDD.scala:250)
        at scala.Option.getOrElse(Option.scala:121)
        at org.apache.spark.rdd.RDD.partitions(RDD.scala:250)
        at org.apache.spark.rdd.AsyncRDDActions

anonfun$foreachAsync$1.apply(AsyncRDDActions.scala:127)atorg.apache.spark.rdd.AsyncRDDActions�������$������ℎ�����$1.�����(���������������.�����:127)�����.����ℎ�.�����.���.���������������

anonfun$foreachAsync$1.apply(AsyncRDDActions.scala:125)
        at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
        at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:112)
        at org.apache.spark.rdd.RDD.withScope(RDD.scala:362)
        at org.apache.spark.rdd.AsyncRDDActions.foreachAsync(AsyncRDDActions.scala:125)
        at org.apache.spark.api.java.JavaRDDLike$class.foreachAsync(JavaRDDLike.scala:732)
        at org.apache.spark.api.java.AbstractJavaRDDLike.foreachAsync(JavaRDDLike.scala:45)
        at org.apache.hadoop.hive.ql.exec.spark.RemoteHiveSparkClient$JobStatusJob.call(RemoteHiveSparkClient.java:351)
        at org.apache.hive.spark.client.RemoteDriver$JobWrapper.call(RemoteDriver.java:358)
        at org.apache.hive.spark.client.RemoteDriver$JobWrapper.call(RemoteDriver.java:323)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
 

...全文
889 回复 打赏 收藏 转发到动态 举报
写回复
用AI写文章
回复
切换为时间正序
请发表友善的回复…
发表回复
内容概要:本文深入剖析了ext4文件系统的设计理念与核心技术,揭示其作为“老将”在Linux和Android生态中持久不衰的原因。ext4继承自为机械硬盘优化的ext2/ext3家族,采用块组、位图、inode表等结构保障磁头寻道效率,并通过稀疏超级块、flex_bg等机制优化布局。其核心创新包括引入extents替代传统多级间接指针,大幅提升大文件寻址效率;支持延迟分配以降低碎片率;启用64bit模式突破容量限制。日志系统jbd2提供三种写入模式(journal/ordered/writeback),在安全性与性能间灵活权衡,确保崩溃后快速恢复。此外,ext4配备fallocate、hole punch、e4defrag等现代工具,支持稀疏文件、在线扩容与碎片整理,并通过metadata_csum增强元数据完整性检测。在Android系统中,ext4虽非userdata主文件系统,却广泛用于metadata、misc、persist等“小而关键”的分区,凭借高可靠性与成熟修复工具成为系统稳定性的基石。最后,文章通过f2fs、ext4、EROFS三者在设计初衷、写入方式、压缩能力等方面的七维对照,阐明“没有银弹”的选型心法:不同介质与负载需匹配最适合的文件系统。; 适合人群:具备一定操作系统基础知识的开发者、存储系统工程师、Android系统研发人员及对文件系统原理感兴趣的技术爱好者。; 使用场景及目标:①理解ext4为何能在闪存时代仍被广泛用于关键小分区;②掌握extents、jbd2日志、延迟分配等核心技术原理;③对比f2fs、ext4、EROFS在不同应用场景下的优劣,指导实际选型决策。; 阅读建议:此资源兼具技术深度与历史视角,建议结合姊妹篇①(Android存储架构)与②(f2fs闪存优化)对照阅读,以构建完整的文件系统认知体系。对于关键章节如日志机制与三系统对照表,建议反复研读并结合内核文档与实际命令(如tune2fs、e2fsck)进行实践验证。

20,843

社区成员

发帖
与我相关
我的任务
社区描述
Hadoop生态大数据交流社区,致力于有Hadoop,hive,Spark,Hbase,Flink,ClickHouse,Kafka,数据仓库,大数据集群运维技术分享和交流等。致力于收集优质的博客
社区管理员
  • 分布式计算/Hadoop社区
  • 涤生大数据
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧