Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-08-03 Thread Enrico Olivelli
I support this proposal. I can't understand if this is still a VOTE thread. If it is a VOTE thread then this is my +1 (binding) Sorry for late reply Enrico Il Gio 3 Ago 2023, 21:43 Rajan Dhabalia ha scritto: > Hi Penghui. > > I think I tried to answer most of the questions and have enough use

Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-08-03 Thread Rajan Dhabalia
Hi Penghui. I think I tried to answer most of the questions and have enough usecases for this PIP as you also mentioned in your last email. Users can use this feature for any additional reasons like security, or convenience depending on their usecases. I think I have also answered all the concerns

Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-08-03 Thread Asaf Mesika
So, I'm trying to summarize the motivation you have for this feature and what we know about it, so we can proceed with discussion. I think Pulsar users should be happy with using Pulsar and not hit a "wall", on the other hand, there are cons to adding it: * Exposing more to the API, adding more sur

Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-08-02 Thread Rajan Dhabalia
>> If so, I think it could be a good reason for introducing binary protocol support here. For the security sensitive users like financial application. Usually they will try to reduce the dependencies (less dependencies, less CVEs and the exposed service endpoints. For example, the flink connector a

Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-06-26 Thread PengHui Li
Hi Rajan, Thanks for the explanation > This feature helps them to avoid multiple different extra efforts If I understand correctly. You want to say users don't want to add the pulsar-admin dependency or the the cluster don't want to expose the REST API to external (not the cluster admin or tenan

Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-06-26 Thread Rajan Dhabalia
> I do not deny that binary protocol has performance advantages. But maybe the bottleneck is not the protocol level for now. Well, sure. We had serious issue with performance in past over http but this feature we would mainly like to introduce it now for the applications to enhance api user access

Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-06-24 Thread PengHui Li
> >> Main reasons are performance (you will see improvement due to http overhead compare to tcp, limited threads on http-server side and definitely performance compare to netty-tcp vs http-jetty server), user feasibility (same reason why we have producer/consumer stats using binary protocol where u

Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-06-21 Thread Rajan Dhabalia
Please find the response inline. On Wed, Jun 21, 2023 at 5:53 PM PengHui Li wrote: > > However, stats retrieval over HTTP API doesn’t work well in use cases > when users would like to access this API at a higher scale when a large > number of application nodes would like to use it over HTTP whic

Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-06-21 Thread PengHui Li
> However, stats retrieval over HTTP API doesn’t work well in use cases when users would like to access this API at a higher scale when a large number of application nodes would like to use it over HTTP which could overload brokers and sometimes makes broker irresponsive and impact admin API perfor

[VOTE] PIP-268: Add support of topic stats/stats-internal using

2023-06-20 Thread Rajan Dhabalia
Hi, I would like to start VOTE for : https://github.com/apache/pulsar/issues/20265 Thanks, Rajan