Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Dead Letter Policy in Consumer configuration doesn't account for chunking or batching configuration. #20934

Closed
2 tasks done
jackson-chris opened this issue Aug 4, 2023 · 0 comments · Fixed by #21048 · May be fixed by rindavis/pulsar#1
Closed
2 tasks done
Assignees
Labels
type/bug The PR fixed a bug or issue reported a bug

Comments

@jackson-chris
Copy link

Search before asking

  • I searched in the issues and found nothing similar.

Version

2.11.1

Minimal reproduce step

  • Produce a message to a topic that exceeds the maxMessageSize default value of 5MB.
  • Create a consumer that consumes from that topic. This consumer should be configured with a deadLetterPolicy that includes retry letter and dead letter topics.
  • Simulate a failure in the consumer code by forcing a call to reconsumeLater

What did you expect to see?

I would expect that a message will be produced to the retry letter topic that was configured in the deadLetterPolicy for that consumer.

What did you see instead?

The following error is observed:

org.apache.pulsar.client.api.PulsarClientException$InvalidMessageException: The producer mdl-pulsar-0-12 of the topic persistent://metadatalake/metadatalake/part-rlt-v1 sends a  message with 7094331 bytes that exceeds 5242880 bytes

Anything else?

The root cause is expected to be that the consumer implementation with respect to creating the producers for whatever is provided in deadLetterPolicy does not have any configuration parameters regarding if batching or chunking should be enabled. Problematic code:

Are you willing to submit a PR?

  • I'm willing to submit a PR!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment