Files
seaweedfs/weed
chrislu 0529a2af28 debug: Add consumer coordination logging to pinpoint consumer init issue
Added logging for consumer group coordination API keys (9,11,12,14) to identify
where consumer gets stuck during initialization.

KEY FINDING: Consumer is NOT stuck in group coordination!
Instead, consumer is stuck in seek/metadata discovery phase.

Evidence from test logs:
- Metadata (apiKey=3): 2,137 requests 
- ApiVersions (apiKey=18): 22 requests 
- ListOffsets (apiKey=2): 6 requests  (but not completing!)
- JoinGroup (apiKey=11): 0 requests 
- SyncGroup (apiKey=14): 0 requests 
- Fetch (apiKey=1): 0 requests 

Consumer is stuck trying to execute seekToBeginning():
1. Consumer.assign() succeeds
2. Consumer.seekToBeginning() called
3. Consumer sends ListOffsets request (succeeds)
4. Stuck waiting for metadata or broker connection
5. Consumer.poll() never called
6. Initialization never completes

Root cause likely in:
- ListOffsets (apiKey=2) response format or content
- Metadata response broker assignment
- Partition leader discovery

This is separate from the context timeout bug (Bug #1).
Both must be fixed for Schema Registry to work.
2025-10-16 15:34:49 -07:00
..
2025-10-13 18:05:17 -07:00
2025-10-14 13:04:33 -07:00
2025-10-13 18:05:17 -07:00
2025-10-13 18:05:17 -07:00
2025-10-15 22:56:47 -07:00
2025-10-13 18:05:17 -07:00
2025-08-31 23:31:28 -07:00
2025-08-22 01:15:42 -07:00
2025-10-15 16:08:21 -07:00
2025-10-13 18:05:17 -07:00
2024-06-25 09:18:11 -07:00
2025-10-13 18:05:17 -07:00
2025-08-30 11:15:48 -07:00
2025-10-13 18:05:17 -07:00
2024-02-14 08:26:38 -08:00
2025-10-13 18:05:17 -07:00
2025-10-13 18:05:17 -07:00
2025-10-13 18:05:17 -07:00
2025-10-13 18:05:17 -07:00
2025-07-19 21:43:34 -07:00
2025-03-17 23:13:27 -07:00