FATAL [Kafka Server 0], Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
kafka.common.KafkaException: DelegationToken not a valid resourceType name. The valid names are Topic,Group,Cluster,TransactionalId
at kafka.security.auth.ResourceType$$anonfun$fromString$1.apply(ResourceType.scala:56)
at kafka.security.auth.ResourceType$$anonfun$fromString$1.apply(ResourceType.scala:56)
at scala.Option.getOrElse(Option.scala:121)
at kafka.security.auth.ResourceType$.fromString(ResourceType.scala:56)
at kafka.security.auth.SimpleAclAuthorizer$$anonfun$loadCache$1$$anonfun$apply$mcV$sp$1.apply(SimpleAclAuthorizer.scala:234)
at kafka.security.auth.SimpleAclAuthorizer$$anonfun$loadCache$1$$anonfun$apply$mcV$sp$1.apply(SimpleAclAuthorizer.scala:233)
at scala.collection.Iterator$class.foreach(Iterator.scala:891)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1334)
at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
at kafka.security.auth.SimpleAclAuthorizer$$anonfun$loadCache$1.apply$mcV$sp(SimpleAclAuthorizer.scala:233)
at kafka.security.auth.SimpleAclAuthorizer$$anonfun$loadCache$1.apply(SimpleAclAuthorizer.scala:231)
at kafka.security.auth.SimpleAclAuthorizer$$anonfun$loadCache$1.apply(SimpleAclAuthorizer.scala:231)
at kafka.utils.CoreUtils$.inLock(CoreUtils.scala:213)
at kafka.utils.CoreUtils$.inWriteLock(CoreUtils.scala:221)
at kafka.security.auth.SimpleAclAuthorizer.loadCache(SimpleAclAuthorizer.scala:231)
at kafka.security.auth.SimpleAclAuthorizer.configure(SimpleAclAuthorizer.scala:115)
at kafka.server.KafkaServer$$anonfun$startup$4.apply(KafkaServer.scala:247)
at kafka.server.KafkaServer$$anonfun$startup$4.apply(KafkaServer.scala:245)
at scala.Option.map(Option.scala:146)
at kafka.server.KafkaServer.startup(KafkaServer.scala:245)
at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:38)
at kafka.Kafka$.main(Kafka.scala:65)
at kafka.Kafka.main(Kafka.scala)
昵称
0 声望
这家伙太懒,什么都没留下
sparing-Kafka 是在集群内部环境嘛? 在哪里? 为什么删除/kafka-acl/BelegationToken就恢复了,原理什么的可以简单说明一下吗?(或者给一个参考博客)
spring-kafka这kafka的访问客户端jar包,与srping的项目集成在一想,这个问题是 kafka的客户端jar与kafka服务端的版本不一致产生。为什么要删除/kafka-acl/DelegationToken,是因为这个路径是错误的客户端创建的,所以要删除
哦哦,了解蟹蟹。
因为使用java客户端 spring-kafka是 2.12的版本,服务器broker是 2.11 的版本,进行操作broker时 , 在 zookeeper中创建 /kafka-acl/DelegationToken 节点,导致服务启不来,解决办法是 java客户制成与 broker版本一致 , 删除 zk 中的 /kafka-acl/DelegationToken , 就可以正常启动,谢谢各位关注!
这个东西的路径在哪?
在zookeeper中,使用 zkClient.sh -server localhost 登陆到zk中, broker 的版本是 0.11的
上面 zkClient.sh更正为 zkCli.sh
你的答案