Hi, Yubiao
I agree with this idea because some users care about the production rate. They
don't want to unload the whole topic to fix the subscription problem.
I've got some questions:
1. How do you handle the race condition when you are trying to unload the
subscription, and the new consumer
Thanks YuBiao Feng:
> We sometimes try to unload the topic to resolve some consumption-stop
> issues. But the unloading topic will also impact the producer side.
This is indeed an interesting thing. In the current production operation
and maintenance, unload is a very frequently used operation. A
Greetings,
I was informed to ask this here but was unclear yet if this should be a PIP
or not. Please advise if I should follow a different process. Thanks in
advance.
The motivation is as follows: today we have KeyShared subscriptions in
which the consumers are rapidly autoscaling up and down
Hi community
Now that site [admin-rest-api](https://pulsar.apache.org/admin-rest-api) is
automatically generated through swagger, each API in the site has its link
that we can walk through, the generated rule of API-link is `
https://pulsar.apache.org/admin-rest-api/#operation/{operationId}`, we c
Hi community
I am starting a DISCUSS for PIP-240: A new API to unload subscriptions.
PIP issue: https://github.com/apache/pulsar/issues/19187
### Motivation
We sometimes try to unload the topic to resolve some consumption-stop
issues. But the unloading topic will also impact the producer side.
