Kafka Consumer Group Rebalance Storm Triggering Lambda Restarts

warning

reliabilityUpdated Feb 9, 2026

Frequent Kafka consumer group rebalances (detected via kafka_consumergroup_members changes) can trigger Lambda function restarts (fullRestarts metric), causing processing interruptions, increased cold starts (InitDuration), and temporary offset lag spikes as Lambda event source mappings rejoin the consumer group.

Sources

Types of metrics for Lambda functions - AWS Lambdadocs.aws.amazon.com

How to Implement CockroachDB Changefeed for Real-Time CDC on Kubernetesoneuptime.com

Metrics and dimensions in Managed Service for Apache Flink - Managed Service for Apache Flinkdocs.aws.amazon.com

Technologies:

Apache KafkaThe root cause of this issue originates in Apache Kafka

kafka.consumer.delayed_requests

kafka.consumer.max_lag

How to detect:

Track Lambda fullRestarts and downtime metrics spiking in correlation with kafka_consumergroup_members changes or kafka.consumer.delayed_requests increases. Monitor InitDuration spikes following fullRestarts indicating cold start penalties after rebalance.

Recommended action:

Increase Kafka consumer group session.timeout.ms and heartbeat.interval.ms to reduce rebalance sensitivity. Use Lambda provisioned concurrency to minimize cold start impact after rebalances. Review Kafka broker logs for rebalance triggers. If using Lambda provisioned mode, ensure stable MinimumPollers configuration to reduce poller churn.