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 <vignesh.v...@gmail.com> 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 <vignesh.v...@gmail.com> 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. > > >
