The Next Generation of the Consumer Rebalance Protocol should be configureable

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
kafka, kubernetes, rust
Domain
distributed-systems, infrastructure

Research direction

Read KIP-848 first, then trace how this operator exposes Kafka broker and client configuration. Identify the configuration point for the consumer rebalance protocol and define completion as allowing users to choose the protocol behavior instead of enforcing it by default.

Written by the indexing model from the issue text.

Description

KIP-848: The Next Generation of the Consumer Rebalance Protocol is enforced by default at the broker side and clients are expected to adapt.

We should still leave this configureable.

Dominant language
Rust
Stars
28
Forks
8
Avg merge
2d 12h
Merged PRs (30d)
9

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.

More from stackabletech/kafka-operator

All issues in stackabletech/kafka-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.