linkedin / linkedin/Burrow

Consumer status/lag showing NOTFOUND

Open
#323 9 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Using the api `/v3/kafka/CLUSTER/consumer` I am able to get a list of consumers, however when I try to pass any of those into either `/v3/kafka/CLUSTER/consumer/ENTITY_FROM_CALL/status` or `/v3/kafka/CLUSTER/consumer/ENTITY_FROM_CALL/lag` it returns cluster or consumer group not found. I am able to get a list of topics as well and then see the offset of that particular topic.

I am running on kafka 0.10.0.0, here is the config I am using.

```
[general]
pidfile="burrow.pid"
stdout-logfile="burrow.out"

[logging]
filename="logs/burrow.log"
level="info"
maxsize=100
maxbackups=30
maxage=10
use-localtime=false
use-compression=true

[zookeeper]
servers=[ "dv-kafka-01:2181", "dv-kafka-02:2181", "dv-kafka-03:2181" ]
timeout=6
root-path="/burrow_v1"

[client-profile.dv_kafka]
client-id="burrow-lagchecker"
kafka-version="0.10.0.0"

[cluster.dv_kafka]
class-name="kafka"
servers=[ "dv-kafka-01:9092", "dv-kafka-02:9092", "dv-kafka-03:9092", "dv-kafka-04:9092", "dv-kafka-05:9092", "dv-kafka-06:9092", "dv-kafka-07:9092", "dv-kafka-08:9092", "dv-kafka-09:9092", "dv-kafka-10:9092" ]
client-profile="dv_kafka"
topic-refresh=120
offset-refresh=30

[consumer.dv_kafka]
class-name="kafka"
cluster="dv_kafka"
servers=[ "dv-kafka-01:9092", "dv-kafka-02:9092", "dv-kafka-03:9092", "dv-kafka-04:9092", "dv-kafka-05:9092", "dv-kafka-06:9092", "dv-kafka-07:9092", "dv-kafka-08:9092", "dv-kafka-09:9092", "dv-kafka-10:9092" ]
client-profile="dv_kafka"
group-blacklist="^(console-consumer-|python-kafka-consumer-|quick-).*$"
group-whitelist=""
offset-topic="__consumer_offsets"

[httpserver.default]
address=":8081"
```

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 `/v3/kafka/CLUSTER/consumer`, `/status`, and `/lag` requests with the supplied Kafka 0.10.0.0 configuration, then trace how the consumer list is mapped to status and lag lookups. Done means consumers returned by the list endpoint no longer produce cluster or consumer-group-not-found responses for the other endpoints.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.