Kinesis Consumer Stuck in Infinite Loop During Shard Discovery

[Envoy49]

Description

The Kinesis consumer (harlow/kinesis-consumer) is exhibiting a recursive loop behavior in shard discovery and iterator retrieval. The application repeatedly attempts to get shard iterators and scan shards, suggesting either a deadlock in shard management or an issue with stream state handling.

Environment Details

• Package: github.com/harlow/[email protected]
• Runtime: Go
• Infrastructure: AWS ECS

Stack Trace Analysis

The application shows a recursive pattern in goroutine 19, with multiple identical sequences:

Primary Call Path:

1. (*AllGroup).findNewShards.func1
   - Location: allgroup.go:139
   - Created by: (*AllGroup).findNewShards at allgroup.go:132

2. (*Consumer).getShardIterator
   - Location: consumer.go:294
   - Called within scan operations

3. (*Consumer).ScanShard
   - Location: consumer.go:171
   - Part of the main processing loop

4. (*Consumer).Scan.func2
   - Location: consumer.go:136
   - Handling individual shard scanning