redpanda-data / redpanda-data/console

Add Support for KIP-848 - The Next Generation of the Consumer Rebalance Protocol

Open
#1,815 5 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backend bug
Dominant language
TypeScript
Stars
4.3k
Forks
432
Avg merge
3d 6h
Merged PRs (30d)
40

Description

Hi Redpanda Console Team.
My company is currently in the process of migrating our Kafka clusters to KRaft. With KRaft clusters comes support for various new features in Kafka, one of them being KIP-848 - The Next Generation of the Consumer Rebalance Protocol.

We have been using Redpanda Console UI for our Kafka clusters, and have tried using this new protocol on a consumer group in the newest Redpanda Console UI version, but the UI shows the cosumer group to be in a DEAD state.

If this is a feature that currently exists, but has been missed by us, we would really appreciate if you could point out the config that we may have missed. Otherwise, if this feature is still not supported we would really appreciate if this could be added to the list of features to implement.

Thanks In advance for your help.

Environment Reference,

  • Kafka version - 3.9.0
  • Redpanda Console Version - v3.1.0

Contributor guide

Open the contributing guide

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 reading KIP-848 and reproducing the consumer-group display with Kafka 3.9.0 and Redpanda Console v3.1.0. Trace the consumer-group UI behavior that reports the group as DEAD, then determine the protocol state information it receives. Done means KIP-848 consumer groups are recognized and shown with the correct state in the UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
kafka, react, typescript
Domain
distributed-systems, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.