Part of #3560. ## Summary Decide and document how the Kafka gateway stores consumer group offsets for Phase 2. ## Motivation Open question from https://github.com/apache/iggy/discussions/3253#discussioncomment-17181030: | Option | Description | |--------|-------------| | **A (recommended)** | Iggy-backed `__consumer_offsets` internal topic | | **B** | SQLite file on bridge host | | **C** | In-memory only (resets on restart) | Phase 2 is blocked until this decision is recorded. ## Depends on - #3539 — Phase 1 complete (or near-complete) ## Deliverables - [ ] ADR or design comment on #3253 with chosen option - [ ] Data model: key = `(group, topic, partition)` → committed offset - [ ] Durability, backup, multi-bridge-instance behavior documented - [ ] Partition assignment strategy decision: range / round-robin / sticky vs Iggy balanced ## Acceptance criteria - [ ] Maintainers sign off on Option A/B/C - [x] Phase 2 implementation issues unblocked
Activity
[-]design(gateways): Consumer offset persistence strategy for Kafka gateway Phase 2[/-][+]Kafka gateway: Design Consumer offset persistence strategy for Kafka gateway Phase 2[/+]numinnex commentedon Sep 24, 2026
I am picking this one up