Skip to content

ref(consumers): Remove the unused dlq-consumer (EAP-944) - #8690

Draft
ElioDiNino wants to merge 1 commit into
masterfrom
eliodinino/eap-944-remove-dlq-consumer
Draft

ElioDiNino wants to merge 1 commit into
masterfrom
eliodinino/eap-944-remove-dlq-consumer

Conversation

@ElioDiNino

@ElioDiNino ElioDiNino commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

Removes the dlq-consumer CLI command and the code that only it used. It replayed a storage's DLQ when Snuba admin wrote an instruction to the dlq Redis cluster. That admin tool was removed in #8200, so nothing can start a replay anymore, and Datadog shows no usage in its retention window.

  • Delete snuba/cli/dlq_consumer.py and snuba/consumers/dlq.py (instructions, Redis helpers, ExitAfterNMessages) and their tests.
  • ConsumerBuilder: drop build_dlq_strategy_factory and build_dlq_consumer.
  • KafkaConsumerStrategyFactory: drop max_messages_to_process, which only the DLQ consumer passed.
  • Drop the dlq Redis cluster (RedisClientKey.DLQ, REDIS_CLUSTERS["dlq"]).
  • deploy-py.sh: stop targeting the dlq-consumer container.

The eap-items-dlq-replay-consumer and the regular DLQ policy on consumers are unaffected.

Ticket: EAP-944

The dlq-consumer replayed a storage's DLQ when Snuba admin wrote an
instruction to the dlq Redis cluster. That admin tool was removed in
#8200, so nothing can start a replay, and Datadog has no
snuba.dlq_consumer metrics in its 15-month retention window.

Remove the CLI command, the instruction helpers, the DLQ builder methods,
the max_messages_to_process option only it used, the dlq Redis client
and its deploy container.
@linear-code

linear-code Bot commented Nov 10, 2026

Copy link
Copy Markdown

EAP-944

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant