Skip to content

AxonOps — AI-Native Control Plane for Open Source Data Platforms

Kafka Share-Group Failures

Share groups use record acquisition locks and acknowledgement state. Consumer-group offset assumptions do not map directly to them.

Terminal window
kafka-share-groups.sh --bootstrap-server kafka:9092 \
--describe --group work-queue --state
kafka-share-groups.sh --bootstrap-server kafka:9092 \
--describe --group work-queue --members --verbose
kafka-share-groups.sh --bootstrap-server kafka:9092 \
--describe --group work-queue --offsets

Capture member IDs, assigned topics, delivery-attempt counts, acknowledgement type/errors, acquisition-lock expiry/renewal, archived records, coordinator broker, client/server versions, and group configuration.

Error or symptomInvestigate
SHARE_SESSION_NOT_FOUNDSession eviction, connection churn, coordinator movement
INVALID_SHARE_SESSION_EPOCHStale concurrent requests or client/session lifecycle
SHARE_SESSION_LIMIT_REACHEDAbandoned sessions, churn, concurrency, broker capacity
FENCED_STATE_EPOCHStale coordinator state or admin operation
Lock expires repeatedlyProcessing exceeds lock duration or renewal fails
Records redeliverRelease, failed ack, lock expiry, member failure
Records archive unexpectedlyReject action or delivery-attempt limit
  • Restore stable client connections and coordinator health.
  • Let the supported client rebuild a lost or stale session.
  • Fix processing time or use supported lock renewal instead of extending every timeout blindly.
  • Correct acknowledgement logic and observe results per partition.
  • Reset offsets only while the share group is inactive, using --dry-run before --execute.

Broker-managed share-group DLQs require Kafka 4.4 and share.version=2. Verify group errors.deadletterqueue.* settings, DLQ topic configuration, broker authorization, write/error metrics, and whether the record was actually archived.

Members and sessions remain stable, acquisition locks complete or renew as designed, acknowledgement errors stop, delivery attempts behave within policy, and archived records reach the configured DLQ when eligible.

Monitor share-session count/limits, lock expiry, acknowledgement error rate, delivery attempts, archive/DLQ rate, coordinator errors, and client churn. Load-test processing duration against lock policy.