Will have to get back to you on that, Ismael. This code is owned by
another team and is in a different code repository.
Chris
From: Ismael Juma
To: users@kafka.apache.org
Date: 06/08/2016 03:22 PM
Subject:Re: Invalid Version for API key
Great Chris. Out of curiosity
plied to me!
>
> Chris
>
>
>
>
> From: Ismael Juma
> To: users@kafka.apache.org
> Date: 06/08/2016 11:29 AM
> Subject:Re: Invalid Version for API key
> Sent by:isma...@gmail.com
>
>
>
> Hi Chris,
>
> The error includes the IP address of
Thanks, Ismael. We tracked it down to one of the 11 microservices running
on this system.
Thank you, all, who replied to me!
Chris
From: Ismael Juma
To: users@kafka.apache.org
Date: 06/08/2016 11:29 AM
Subject:Re: Invalid Version for API key
Sent by:isma
t;
> Thanks!
>
> Chris
>
>
>
>
>
> From: Grant Henke
> To: users@kafka.apache.org
> Date: 06/08/2016 10:58 AM
> Subject:Re: Invalid Version for API key
>
>
>
> ApiKey 2 is the Offsets request. There is only a version 0 of that
> protoc
uld resolve the issue.
Thanks!
Chris
From: Grant Henke
To: users@kafka.apache.org
Date: 06/08/2016 10:58 AM
Subject: Re: Invalid Version for API key
ApiKey 2 is the Offsets request. There is only a version 0 of that
protocol
since there has been no change in the proto
ApiKey 2 is the Offsets request. There is only a version 0 of that protocol
since there has been no change in the protocol version for LIST_OFFSETS
from 0.8 to 0.10. So there error that version 1 is invalid is correct.
What has changed in 0.10 is that the validation and errors of incorrect api
key
I believe the wire format has changed between 0.8 and 0.9. It might be
necessary to update your clients. I'd try that first before doing any further
debugging / tracing.
--
Best regards,
Rad
On Wed, Jun 8, 2016 at 4:40 PM +0200, "Chris Barlock"
wrote:
Anyone? Is there additiona
Anyone? Is there additional tracing that can be turned on to track down
the source of these exceptions?
Chris
From: Chris Barlock/Raleigh/IBM@IBMUS
To: users@kafka.apache.org
Date: 06/07/2016 12:45 PM
Subject:Invalid Version for API key
We are running some tests on upgradi
