Files
seaweedfs/weed
chrislu 8969b45092 fix: Don't report long-poll duration as throttle time
PROBLEM:
Consumer test (make consumer-test) shows Sarama being heavily throttled:
  - Every Fetch response includes throttle_time = 100-112ms
  - Sarama interprets this as 'broker is throttling me'
  - Client backs off aggressively
  - Consumer throughput drops to nearly zero

ROOT CAUSE:
In the long-poll logic, when MaxWaitTime is reached with no data available,
the code sets throttleTimeMs = elapsed_time. If MaxWaitTime=100ms, the client
gets throttleTime=100ms in response, which it interprets as rate limiting.

This is WRONG: Kafka's throttle_time is for quota/rate-limiting enforcement,
NOT for reflecting long-poll duration. Clients use it to back off when
broker is overloaded.

FIX:
- When long-poll times out with no data, set throttleTimeMs = 0
- Only use throttle_time for actual quota enforcement
- Long-poll duration is expected and should NOT trigger client backoff

BEFORE:
- Sarama throttled 100-112ms per fetch
- Consumer throughput near zero
- Test times out (never completes)

AFTER:
- No throttle signals
- Consumer can fetch continuously
- Test completes normally
2025-10-16 22:37:11 -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