poorbarcode commented on issue #19187: URL: https://github.com/apache/pulsar/issues/19187#issuecomment-1379929522
Hi @eolivelli > If there is a problem we should spend time on investigating the problem and not in adding this kind of tools. You are right. When a user encounters a problem, it often takes a while actually to solve the root cause. It is important to provide a tool to recover services quickly, and cmd 'unload topic' is often used to solve problems temporarily. But now a topic can be used by multiple teams, such as Business-team A to produce messages, Business-team B and C to consume messages (each using a different subscription name), and Data-team D to read messages using reader api (using a random subscription name). When there is a consumption problem in subscription B, if we do unload the topic, this will affect teams A, B, C, D, and when we provide a new API to reset subscribers, the impact can be controlled only to affect team B. So I think a new API is necessary。 Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
