apache/pulsar

PoolMessage and DLQ can not work together

Open

#13,269 opened on Dec 13, 2021

View on GitHub
 (6 comments) (0 reactions) (1 assignee)Java (3,485 forks)batch import
Stalehelp wantedlifecycle/staletype/bug

Repository metrics

Stars
 (13,697 stars)
PR merge metrics
 (Avg merge 3d 10h) (146 merged PRs in 30d)

Description

Describe the bug PoolMessage and DLQ can not work together

To Reproduce Steps to reproduce the behavior:

  1. Enable poolMessages and DLQ in consumer side
  2. Call consumer.negativeAcknowledge(message) and then call message.release()
  3. The message did not resend to DLQ topic.

Expected behavior The message should be sent to DLQ topic.

Additional context The negative ack msgs will be sent to DLQ topic in a scheduler triggerRedelivery, when we enable poolMessages, message.release() will clear MessageImpl immediately, this will cause processPossibleToDLQ() fail to get message id and resend to DLQ.

Contributor guide

Research direction
Investigate the interaction between PoolMessage and DLQ in the consumer redelivery scheduler (triggerRedelivery). Focus on how message.release() clears MessageImpl and how processPossibleToDLQ() retrieves the message ID. Consider adding a delay or storing the message ID before release, or restructuring the negative ack logic.
Tech stack
java
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaApache Pulsar
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55