That trace is buried in request handling code. Are you sure you don’t have a consumer or producer running somewhere with a newer version of Kafka?
If you get the startup succeeded message and then get that error later, I would iftop the box and male sure there isn’t anything surprising trying to talk to my Kafka instance (developer’s machine, etc). Barring that I’d audit all the deployed applications to make sure they picked up their new configs. If none of that bears fruit, I’d try upgrading to a newer version in the 0.10 series? Someone else may have better suggestions. On Mon, Nov 6, 2017 at 3:13 AM Madhukar Bharti <bhartimadhu...@gmail.com> wrote: > Hi Matt, > > We are getting below exception while updating with old Kafka > build(0.10.0.1) > > kafka.network.InvalidRequestException: Error getting request for apiKey: 6 > and apiVersion: 3 > at > kafka.network.RequestChannel$Request.liftedTree2$1(RequestChannel.scala:95) > at kafka.network.RequestChannel$Request.<init>(RequestChannel.scala:87) > at > > kafka.network.Processor$$anonfun$processCompletedReceives$1.apply(SocketServer.scala:488) > at > > kafka.network.Processor$$anonfun$processCompletedReceives$1.apply(SocketServer.scala:483) > at scala.collection.Iterator$class.foreach(Iterator.scala:893) > at scala.collection.AbstractIterator.foreach(Iterator.scala:1336) > at scala.collection.IterableLike$class.foreach(IterableLike.scala:72) > at scala.collection.AbstractIterable.foreach(Iterable.scala:54) > at kafka.network.Processor.processCompletedReceives(SocketServer.scala:483) > at kafka.network.Processor.run(SocketServer.scala:413) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IllegalArgumentException: Invalid version for API key > 6: 3 > > > Above log is keep on printing. > > Regards, > Madhukar > > > > > On Mon, Nov 6, 2017 at 2:05 AM, Matt Farmer <m...@frmr.me> wrote: > > > If you could provide more details about the kind of issues you saw when > you > > downgraded (e.g. error logs, behavior, etc) it might help folks help you. > > At the moment, I wouldn't know where to begin with the issue you've > > described as there's not a ton of detail about what, exactly, went wrong. > > > > On Sun, Nov 5, 2017 at 12:57 PM Madhukar Bharti < > bhartimadhu...@gmail.com> > > wrote: > > > > > Hi all, > > > > > > Recently we have upgraded our cluster from 0.10.0.1 to 0.11.0.1. After > > few > > > hours of upgrade we faced issue of too many closed_wait connection. > > Latter > > > got to know that this is a bug and got fixed in 1.0.0. > > > > > > As of now we can’t take this as there is still possible known bugs are > > > there, we need to test it well putting in production. > > > > > > Can you please help us how to downgrade from 0.11.0.1 to 0.10.0.1.? As > of > > > now we have message format as 0.10.0.1 in 0.11.0.1 brokers. All clients > > are > > > also on 0.10.0.1. > > > > > > I tried like below, > > > > > > Set inter broker protocol version to 0.10.0.1. > > > Restart brokers one by one. > > > Re-install with Kafka 0.10.0.1. > > > > > > But it dint worked properly for all partitions. > > > > > > > > > Regards, > > > Madhukar > > > > > > > > > -- > > > Thanks and Regards, > > > Madhukar Bharti > > > Mob: 7845755539 > > > > > > > > > -- > Thanks and Regards, > Madhukar Bharti > Mob: 7845755539 >
