kafka.admin.AdminOperationException

tip

Verify on the createTopic command if you've set the right replication factor for the amount of brokers you have. Check as well if all your brokers are correctly setup and that they're alive when you create the topic.

tip

If you're having problems using kafka in cluster, refer to this guide: https://goo.gl/tgWDjS

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

  • GitHub comment 200#142925291
    via GitHub by kjetilhp
    ,
  • GitHub comment 17#166511969
    via GitHub by ewencp
    ,
  • [ut]KafkaStreamProducerSpec fail
    via GitHub by clockfly
    ,
  • GitHub comment 17#195530179
    via GitHub by krishna81m
    ,
    • kafka.admin.AdminOperationException: replication factor: 3 larger than available brokers: 1 at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:70) at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:171) at kafka.server.KafkaApis$$anonfun$19.apply(KafkaApis.scala:513) at kafka.server.KafkaApis$$anonfun$19.apply(KafkaApis.scala:503) at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244) at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244) at scala.collection.immutable.Set$Set1.foreach(Set.scala:74) at scala.collection.TraversableLike$class.map(TraversableLike.scala:244) at scala.collection.AbstractSet.scala$collection$SetLike$$super$map(Set.scala:47) at scala.collection.SetLike$class.map(SetLike.scala:93) at scala.collection.AbstractSet.map(Set.scala:47) at kafka.server.KafkaApis.getTopicMetadata(KafkaApis.scala:503) at kafka.server.KafkaApis.handleTopicMetadataRequest(KafkaApis.scala:542) at kafka.server.KafkaApis.handle(KafkaApis.scala:62) at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:59) at java.lang.Thread.run(Thread.java:745)

    Users with the same issue

    Unknown visitor1 times, last one,
    roioteromorales
    1 times, last one,
    Unknown visitor1 times, last one,