Re: Debugging invalid_request response from a .10.2 server for list offset api using librdkafka client
I understand that it won't support it, my only concern is about the error code. Locally with these settings I get a message formatted error, 43 . Which makes sense. In one particular cluster we see an invalid request 42 instead of unsupported format 43. What are the implications of changing the broker protocol version to 10.2, for the topics that were created before this change? My assumption is that they will return 43 for list offset request version 1+ and all other requests would work. Is that correct? Also, can the message format be changed for a topic from 0.8.1 to 0.10.2? If not, what is the recommended way to upgrade old topics. On Sep 27, 2017 11:15 AM, "Hans Jespersen" wrote: > The 0.8.1 protocol does not support target timestamps so it makes sense > that you would get an invalid request error if the client is sending a > Version 1 or Version 2 Offsets Request. The only Offset Request that a > 0.8.1 broker knows how to handle is a Version 0 Offsets Request. > > From https://kafka.apache.org/protocol > INVALID_REQUEST 42 False This most likely occurs because of a request being > malformed by the client library or the message was sent to an incompatible > broker. See the broker logs for more details. > > For more info on the 0.11 Kafka protocol and ListOffset Requests see > > https://cwiki.apache.org/confluence/display/KAFKA/A+ > Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol- > OffsetAPI(AKAListOffset) > > -hans > > /** > * Hans Jespersen, Principal Systems Engineer, Confluent Inc. > * h...@confluent.io (650)924-2670 > */ > > On Wed, Sep 27, 2017 at 10:20 AM, Vignesh wrote: > > > Correction in above mail, we get 42 - INVALID_REQUEST, not 43. > > Few other data points > > > > Server has following configs set > > > > inter.broker.protocol.version=0.8.1 > > > > log.message.format.version=0.8.1 > > > > > > > > My understanding is that we should get unsupported message format with > > above configurations, why do we get invalid_request? > > > > > > Thanks, > > > > Vignesh. > > > > > > > > > > On Wed, Sep 27, 2017 at 9:51 AM, Vignesh wrote: > > > > > Hi, > > > > > > We are using LibrdKafka library version .11.0 and calling List Offset > API > > > with a timestamp on a 0.10.2 kafka server installed in a windows > machine. > > > > > > This request returns an error code, 43 - INVALID_REQUEST. > > > > > > We have other local installations of Kafka version 0.10.2 (also on > > > Windows) and are able to use the library successfully. > > > > > > Are there any settings on this specific server that is causing this > > error? > > > Which logs can we enable and look at to get additional details about > what > > > is wrong with the request? > > > > > > Thanks, > > > Vignesh. > > > > > >
Re: Debugging invalid_request response from a .10.2 server for list offset api using librdkafka client
The 0.8.1 protocol does not support target timestamps so it makes sense that you would get an invalid request error if the client is sending a Version 1 or Version 2 Offsets Request. The only Offset Request that a 0.8.1 broker knows how to handle is a Version 0 Offsets Request. >From https://kafka.apache.org/protocol INVALID_REQUEST 42 False This most likely occurs because of a request being malformed by the client library or the message was sent to an incompatible broker. See the broker logs for more details. For more info on the 0.11 Kafka protocol and ListOffset Requests see https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-OffsetAPI(AKAListOffset) -hans /** * Hans Jespersen, Principal Systems Engineer, Confluent Inc. * h...@confluent.io (650)924-2670 */ On Wed, Sep 27, 2017 at 10:20 AM, Vignesh wrote: > Correction in above mail, we get 42 - INVALID_REQUEST, not 43. > Few other data points > > Server has following configs set > > inter.broker.protocol.version=0.8.1 > > log.message.format.version=0.8.1 > > > > My understanding is that we should get unsupported message format with > above configurations, why do we get invalid_request? > > > Thanks, > > Vignesh. > > > > > On Wed, Sep 27, 2017 at 9:51 AM, Vignesh wrote: > > > Hi, > > > > We are using LibrdKafka library version .11.0 and calling List Offset API > > with a timestamp on a 0.10.2 kafka server installed in a windows machine. > > > > This request returns an error code, 43 - INVALID_REQUEST. > > > > We have other local installations of Kafka version 0.10.2 (also on > > Windows) and are able to use the library successfully. > > > > Are there any settings on this specific server that is causing this > error? > > Which logs can we enable and look at to get additional details about what > > is wrong with the request? > > > > Thanks, > > Vignesh. > > >
Re: Debugging invalid_request response from a .10.2 server for list offset api using librdkafka client
Correction in above mail, we get 42 - INVALID_REQUEST, not 43. Few other data points Server has following configs set inter.broker.protocol.version=0.8.1 log.message.format.version=0.8.1 My understanding is that we should get unsupported message format with above configurations, why do we get invalid_request? Thanks, Vignesh. On Wed, Sep 27, 2017 at 9:51 AM, Vignesh wrote: > Hi, > > We are using LibrdKafka library version .11.0 and calling List Offset API > with a timestamp on a 0.10.2 kafka server installed in a windows machine. > > This request returns an error code, 43 - INVALID_REQUEST. > > We have other local installations of Kafka version 0.10.2 (also on > Windows) and are able to use the library successfully. > > Are there any settings on this specific server that is causing this error? > Which logs can we enable and look at to get additional details about what > is wrong with the request? > > Thanks, > Vignesh. >
Debugging invalid_request response from a .10.2 server for list offset api using librdkafka client
Hi, We are using LibrdKafka library version .11.0 and calling List Offset API with a timestamp on a 0.10.2 kafka server installed in a windows machine. This request returns an error code, 43 - INVALID_REQUEST. We have other local installations of Kafka version 0.10.2 (also on Windows) and are able to use the library successfully. Are there any settings on this specific server that is causing this error? Which logs can we enable and look at to get additional details about what is wrong with the request? Thanks, Vignesh.