linkedin / linkedin/Burrow

Warning Messages: failed to decode

Open
#587 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
4k
Forks
818
Avg merge
1h 14m
Merged PRs (30d)
1

Description

Hi i'm using the latest version of Burrow with a Kafka Cluster V2.3.1.
It is working well but I get those Warning messages:

{"level":"warn","ts":1575366398.2769194,"msg":"failed to decode","type":"module","coordinator":"consumer","class":"kafka","name":"kafkaconsumer","offset_topic":"smf","offset_partition":0,"offset_offset":2338203,"reason":"key version","version":27493}

I think there is something wrong with the key version (see attached picture). Maybe it can't decode it because Kafka version 2.3.1 is not supported. Am I right?

Thank you!

![image](https://user-images.githubusercontent.com/58469498/70047333-26fd5300-15c8-11ea-9ed8-45ce61d28270.png)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the "failed to decode" warning with Kafka 2.3.1 and the reported consumer offset metadata. Trace the consumer decoding path for the reported key version and compare the observed behavior with supported Kafka record formats. Done means identifying whether the warning is expected or fixing decoding so the warning no longer occurs, with a regression test if the project has one.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kafka
Domain
stream-processing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.