Hi all,

Pulsar has a backlog quota policy `producer_request_hold` which will hold
the message
publish request. It is very useful for some data sync scenarios. It looks
like the producer
waiting for the consumer to process the data.

But the new producer is not allowed to connect to the topic after reaching
the max backlog
limitation with producer_request_hold policy. The producer will get
`ProducerBlockedQuotaExceededError` error. This caused inconvenience to
users, they need
to have some retry to logic to try to create the producer again until the
consumer acked more
messages

IMO, we should allow the producer to connect the topic. To keep the
behavior consistent with
the producer is already connected.

WDYT?

Best Regards,
Penghui

Reply via email to