Burrow consume error.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
We using burrow to monitor consumer lag. We have two cluster
1. Number of topics: 108
2. Number of topics: 21
Burrow is working fine in the case of #2 while in the case of #1 cluster it has started giving *consume error* error intermittently. Can someone help us?
{"level":"warn","ts":1602512182.2992618,"msg":"failed to decode","type":"module","coordinator":"consumer","class":"kafka","name":"local","offset_topic":"__consumer_offsets","offset_partition":13,"offset_offset":437696989,"message_type":"metadata","group":"xyz","reason":"value version","version":3}
{"level":"error","ts":1602512183.8760965,"msg":"consume error","type":"module","coordinator":"consumer","class":"kafka","name":"local","topic":"__consumer_offsets","partition":34,"error":"kafka server: Unexpected (unknown?) server error."}
{"level":"error","ts":1602512185.8804855,"msg":"consume error","type":"module","coordinator":"consumer","class":"kafka","name":"local","topic":"__consumer_offsets","partition":34,"error":"kafka server: Unexpected (unknown?) server error."}
{"level":"error","ts":1602512187.883883,"msg":"consume error","type":"module","coordinator":"consumer","class":"kafka","name":"local","topic":"__consumer_offsets","partition":34,"error":"kafka server: Unexpected (unknown?) server error."}
{"level":"error","ts":1602512189.903179,"msg":"consume error","type":"module","coordinator":"consumer","class":"kafka","name":"local","topic":"__consumer_offsets","partition":34,"error":"kafka server: Unexpected (unknown?) server error."}
{"level":"error","ts":1602512191.9411907,"msg":"consume error","type":"module","coordinator":"consumer","class":"kafka","name":"local","topic":"__consumer_offsets","partition":34,"error":"kafka server: Unexpected (unknown?) server error."}
{"level":"warn","ts":1602512193.27345,"msg":"failed to decode","type":"module","coordinator":"consumer","class":"kafka","name":"local","offset_topic":"__consumer_offsets","offset_partition":10,"offset_offset":358919584,"message_type":"metadata","group":"abc","reason":"value version","version":3}
{"level":"error","ts":1602512193.944589,"msg":"consume error","type":"module","coordinator":"consumer","class":"kafka","name":"local","topic":"__consumer_offsets","partition":34,"error":"kafka server: Unexpected (unknown?) server error."}
{"level":"error","ts":1602512195.9564376,"msg":"consume error","type":"module","coordinator":"consumer","class":"kafka","name":"local","topic":"__consumer_offsets","partition":34,"error":"kafka server: Unexpected (unknown?) server error."}
{"level":"error","ts":1602512197.9608557,"msg":"consume error","type":"module","coordinator":"consumer","class":"kafka","name":"local","topic":"__consumer_offsets","partition":34,"error":"kafka server: Unexpected (unknown?) server error."}
{"level":"warn","ts":1602512199.9541771,"msg":"failed to decode","type":"module","coordinator":"consumer","class":"kafka","name":"local","offset_topic":"__consumer_offsets","offset_partition":15,"offset_offset":439570387,"message_type":"metadata","group":"fgsdf","reason":"value version","version":3}
{"level":"error","ts":1602512199.987991,"msg":"consume error","type":"module","coordinator":"consumer","class":"kafka","name":"local","topic":"__consumer_offsets","partition":34,"error":"kafka server: Unexpected (unknown?) server error."}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Burrow logs, especially the failed decode messages for __consumer_offsets and the repeated consume errors on partition 34. Investigate why the larger cluster produces these errors intermittently compared with the smaller cluster; done means identifying a reproducible cause and documenting or correcting the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100