Environment
Self-hosted Sentry via sentry-kubernetes/charts v31.5.0, application image 26.5.0 (also reproduced on 26.2.1).
- Redis backend: Dragonfly (Redis-compatible), not stock Redis
- Connection:
externalRedis in Helm values — redis://dragonfly:6379/1 with password
- Consumer:
sentry run consumer process-spans (processSpans deployment)
Related closed issue: #80440 (Dragonfly Lua randomseed — different failure mode).
Steps to Reproduce
- Deploy Sentry with
externalRedis pointing at Dragonfly.
- Send performance/span data so the
ingest-spans Kafka topic receives messages (or let backlog exist from SDK traffic).
- Observe
process-spans consumer pod logs.
Expected Result
process-spans runs continuously, commits Kafka offsets, and performance traces appear in the UI.
Actual Result
Consumer crashes on every batch that hits span buffer metrics handling:
File "/usr/src/sentry/src/sentry/spans/buffer.py", line 473, in process_spans
if evalsha_latency_ms > longest_evalsha_data[0]:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'bytes' and 'float'
- Pod enters CrashLoopBackOff;
ingest-spans offset does not advance.
- Errors/issues pipeline is unaffected (separate consumers).
- Stock Redis: we have not verified on Redis 7 yet; Dragonfly returns Lua numeric fields as bytes while Sentry expects a numeric type for
evalsha_latency_ms.
Product Area
Performance Monitoring / ingest (process-spans consumer, spans buffer)
Version
26.5.0 (26.2.1 identical failure at buffer.py line 354)
Suggested fix
Coerce evalsha_latency_ms (and similar EVALSHA return fields) to float when isinstance(value, bytes) before comparison, or document Dragonfly as unsupported for the spans buffer until Redis semantics match.
Environment
Self-hosted Sentry via sentry-kubernetes/charts v31.5.0, application image 26.5.0 (also reproduced on 26.2.1).
externalRedisin Helm values —redis://dragonfly:6379/1with passwordsentry run consumer process-spans(processSpansdeployment)Related closed issue: #80440 (Dragonfly Lua
randomseed— different failure mode).Steps to Reproduce
externalRedispointing at Dragonfly.ingest-spansKafka topic receives messages (or let backlog exist from SDK traffic).process-spansconsumer pod logs.Expected Result
process-spansruns continuously, commits Kafka offsets, and performance traces appear in the UI.Actual Result
Consumer crashes on every batch that hits span buffer metrics handling:
ingest-spansoffset does not advance.evalsha_latency_ms.Product Area
Performance Monitoring / ingest (process-spans consumer, spans buffer)
Version
26.5.0 (26.2.1 identical failure at
buffer.pyline 354)Suggested fix
Coerce
evalsha_latency_ms(and similar EVALSHA return fields) tofloatwhenisinstance(value, bytes)before comparison, or document Dragonfly as unsupported for the spans buffer until Redis semantics match.