lsm/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2025-11-09 04:46:46 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Added bounds checking after calculating startIdx.

Browse Source 
Problem: Race condition in cache lookup logic:
Thread A reads cache metadata (17+ records, endOffset = 32)
Thread B modifies/truncates the cache to 17 records
Thread A calculates startIdx = 19 based on old metadata
Slice operation consumedRecords[19:17] panics
This commit is contained in:
chrislu
2025-10-13 21:19:38 -07:00
parent f15eaaf8b9
commit ffc45a538d
1 changed files with 13 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
weed/mq/kafka/integration/broker_client_subscribe.go
View File

@@ -271,6 +271,12 @@ func (bc *BrokerClient) ReadRecordsFromOffset(ctx context.Context, session *Brok
if requestedOffset >= cacheStartOffset && requestedOffset <= cacheEndOffset { if requestedOffset >= cacheStartOffset && requestedOffset <= cacheEndOffset {
// Found in cache // Found in cache
startIdx := int(requestedOffset - cacheStartOffset) startIdx := int(requestedOffset - cacheStartOffset)
// CRITICAL: Bounds check to prevent race condition where cache is modified between checks
if startIdx < 0 || startIdx >= len(session.consumedRecords) {
glog.V(2).Infof("[FETCH] Cache index out of bounds (race condition): startIdx=%d, cache size=%d, falling through to normal read",
startIdx, len(session.consumedRecords))
// Cache was modified, fall through to normal read path
} else {
endIdx := startIdx + maxRecords endIdx := startIdx + maxRecords
if endIdx > len(session.consumedRecords) { if endIdx > len(session.consumedRecords) {
endIdx = len(session.consumedRecords) endIdx = len(session.consumedRecords)
@@ -280,6 +286,7 @@ func (bc *BrokerClient) ReadRecordsFromOffset(ctx context.Context, session *Brok
return session.consumedRecords[startIdx:endIdx], nil return session.consumedRecords[startIdx:endIdx], nil
} }
} }
}
// CRITICAL FIX for Schema Registry: Keep subscriber alive across multiple fetch requests // CRITICAL FIX for Schema Registry: Keep subscriber alive across multiple fetch requests
// Schema Registry expects to make multiple poll() calls on the same consumer connection // Schema Registry expects to make multiple poll() calls on the same consumer connection