range quarantined after max reclaims [SQL0027]

Edit this page

code SQL0027 · log event at warn — degraded but self-healing, or a durable data consequence; an operator should learn of it eventually

the log line

· Report this thread

SQL0027 Log event at warn

As it arrives in your log — example values stand where yours will:

level=WARN msg="range quarantined after max reclaims" code=SQL0027 schema=sqlstreams stream_id=1 group_id=7 low=4100 high=4200

A range was reclaimed MaxRangeReclaims times without committing, so it is treated as poison: its messages are written into the exception window as 'ready' rows instead of being handed out again. Inspect those exceptions for the input that keeps crashing the consumer.

brandon Site Admin

Posts: 677

Helpful info.

the exceptions the quarantine wrote

SELECT
	message_id,
	status,
	attempts,
	can_run_after,
	last_error
FROM {schema}.exception_queue_{stream_id}
WHERE consumer_group_id = {group_id}
	AND message_id BETWEEN {low} AND {high}
ORDER BY message_id;

the messages in the range, to find what kills a consumer

SELECT
	id,
	routing_key,
	payload
FROM {schema}.message_log_{stream_id}
WHERE id BETWEEN {low} AND {high}
ORDER BY id;