Files
seaweedfs/weed
chrislu 65415e515f mq(kafka): 🎯 BREAKTHROUGH - Fix deterministic member ID generation
 MAJOR SUCCESS - Member ID Consistency Fixed!

🔧 TECHNICAL FIXES:
- Deterministic member ID using SHA256 hash of client info 
- Member reuse logic: check existing members by clientKey 
- Consistent member ID across JoinGroup calls 
- No more timestamp-based random member IDs 

📊 EVIDENCE OF SUCCESS:
- First call: 'generated new member ID ...4b60f587'
- Second call: 'reusing existing member ID ...4b60f587'
- Same member consistently elected as leader 
- kafka-go no longer disconnects after JoinGroup 

🎯 ROOT CAUSE RESOLUTION:
The issue was GenerateMemberID() using time.Now().UnixNano()
which created different member IDs on each call. kafka-go
expects consistent member IDs to progress from JoinGroup → SyncGroup.

🚀 BREAKTHROUGH IMPACT:
kafka-go now progresses past JoinGroup and attempts to fetch
messages, indicating the consumer group workflow is working!

NEXT: kafka-go is now failing on Fetch API - this represents
major progress from JoinGroup issues to actual data fetching.

Test result: 'Failed to consume message 0: fetching message: context deadline exceeded'
This means kafka-go successfully completed the consumer group
coordination and is now trying to read actual messages
2025-09-10 19:01:19 -07:00
..
2025-08-09 21:47:29 -07:00
2025-07-19 23:56:17 -07:00
2025-08-30 11:15:48 -07:00
2025-08-31 23:31:28 -07:00
2025-08-22 01:15:42 -07:00
2025-09-10 11:04:42 -07:00
2025-08-30 11:15:48 -07:00
2024-06-25 09:18:11 -07:00
2025-08-30 11:15:48 -07:00
2024-02-14 08:26:38 -08:00
2025-07-19 21:43:34 -07:00
2025-03-17 23:13:27 -07:00