Files
seaweedfs/weed
chrislu 0cdcb88081 feat: Identify root cause - data loss during buffer flush
Phase 6: Root Cause Discovered - NOT Disk Read Bug

After comprehensive debugging with server-side logging:

What We Found:
  ✅ Disk read works correctly (reads what exists on disk)
  ✅ Cache works correctly (caches what was read)
  ✅ Extraction works correctly (returns what's cached)
  ❌ DATA IS MISSING from both disk and memory!

The Evidence:
  Request offset: 1764
  Disk has: 1000-1763 (764 messages)
  Memory starts at: 1800
  Gap: 1764-1799 (36 messages) ← LOST!

Root Cause:
  Buffer flush logic creates GAPS in offset sequence
  Messages are lost when flushing from memory to disk
  bufferStartOffset jumps (1763 → 1800) instead of incrementing

Changes:
  - log_read_stateless.go: Simplified cache extraction to return empty for gaps
  - Removed complex invalidation/retry (data genuinely doesn't exist)

Test Results:
  Original: 87.9% delivery
  Cache invalidation attempt: 73.3% (cache thrashing)
  Gap handling: 82.1% (confirms data is missing)

Next: Fix buffer flush logic in log_buffer.go to prevent offset gaps
2025-10-17 12:42:43 -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