ProducerBlockedQuotaExceededError: Cannot create producer on topic with backlog quota exceeded #18189
-
How can I avoid it? I tried to adjust the Backlog parameter in the StreamNative Tenants / Namespaces Tab. But it didn't work. What do I need to do if I encounter this next time? This morning I had a workaround to delete the old topic and create a new one. |
Beta Was this translation helpful? Give feedback.
Answered by
michaeljmarshall
Oct 28, 2022
Replies: 1 comment
-
@Icemap - the proper way to change the backlog is by using the admin http endpoints. You can do this with the pulsar admin cli tool. Here are example commands: bin/pulsar-admin namespaces set-backlog-quota
The following options are required: [-l | --limit], [-p | --policy]
Set a backlog quota policy for a namespace
Usage: set-backlog-quota [options] tenant/namespace
Options:
* -l, --limit
Size limit (eg: 10M, 16G)
-lt, --limitTime
Time limit in second (or minutes, hours, days, weeks eg: 100m, 3h, 2d,
5w), non-positive number for disabling time limit.
* -p, --policy
Retention policy to enforce when the limit is reached. Valid options
are: [producer_request_hold, producer_exception,
consumer_backlog_eviction]
-t, --type
Backlog quota type to set. Valid options are: destination_storage and
message_age. destination_storage limits backlog by size (in bytes).
message_age limits backlog by time, that is, message timestamp (broker
or publish timestamp). You can set size or time to control the backlog,
or combine them together to control the backlog.
Default: destination_storage bin/pulsar-admin namespaces remove-backlog-quota --help
Remove a backlog quota policy from a namespace
Usage: remove-backlog-quota [options] tenant/namespace
Options:
-t, --type
Backlog quota type to remove. Valid options are: destination_storage,
message_age
Default: destination_storage |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
michaeljmarshall
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@Icemap - the proper way to change the backlog is by using the admin http endpoints. You can do this with the pulsar admin cli tool. Here are example commands: