lhotari commented on issue #25083: URL: https://github.com/apache/pulsar/issues/25083#issuecomment-3664383815
> Some more questions: > > 1. Should we limit the client-side total retrieved analyze-backlog count by adding a new parameter? It could be a client-side request param, or a server-side param, protecting server from overload. Yes. The parameter would be completely on the client side and not passed to the server. One of the reasons for performing the client-side looping is that there are reasonable sizes of tasks that are sent to the server. It's possible that the client request times out or fails and that's why the logic should also be idempotent so that the client can retry the request. > 3. You mentioned `pulsar-admin` command progress reporting. What about `TopicsImpl` implementation? Should we also add a new method and use loop to get and aggregate data. If doing so, executing this method may take a lot of time to get the final result. Yes, it might take a lot of time to get the final result. The default value for the max limits could be similar to the ones on the server side. The progress reporting could be handled using some callback interface. In the command implementation, it could print out to stderr so that the final result could be in json in stdout. -- 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]
