Re: [DISCUSS] PIP-222: Add CommandPartitionedTopicMetadata metrics

2022-11-10 Thread Jiuming Tao
iven the way the code is structured >>> today. The metric name you gave is generic enough so this can be refactored >>> as I said but in the future. >>> >>> 2. We provide some means for the operator to discover the issue, but >>> definitely not easy means. Also, we're not really solving any user >>> experience. In theory, we can say: >>> * There should be a reasonable delay between requests for this metadata, >>> why not enforce it? Perhaps apply a rate limit to this command which seems >>> reasonable by default >>> * The client can utilize the bi-directional nature of Pulsar Protocol and >>> get notified when partitions change (subscribe) therefore limiting the need >>> to pull based on frequency. >>> >>> Thanks, >>> >>> Asaf >>> >>> >>> >>> On Thu, Nov 3, 2022 at 12:19 PM Jiuming Tao >>> wrote: >>> >>>> Hi pulsar community, >>>> >>>> I’ve opened a PIP to discuss: PIP-222: Add CommandPartitionedTopicMetadata >>>> metrics >>>> >>>> The PIP link: https://github.com/apache/pulsar/issues/18319 < >>>> https://github.com/apache/pulsar/issues/18319> >>>> >>>> Thanks, >>>> Tao Jiuming >>

Re: [DISCUSS] PIP-222: Add CommandPartitionedTopicMetadata metrics

2022-11-10 Thread Enrico Olivelli
me means for the operator to discover the issue, but > > definitely not easy means. Also, we're not really solving any user > > experience. In theory, we can say: > > * There should be a reasonable delay between requests for this metadata, > > why not enforce it? Perhaps app

Re: [DISCUSS] PIP-222: Add CommandPartitionedTopicMetadata metrics

2022-11-10 Thread Jiuming Tao
command which seems > reasonable by default > * The client can utilize the bi-directional nature of Pulsar Protocol and > get notified when partitions change (subscribe) therefore limiting the need > to pull based on frequency. > > Thanks, > > Asaf > > > > O

Re: [DISCUSS] PIP-222: Add CommandPartitionedTopicMetadata metrics

2022-11-08 Thread Asaf Mesika
this command which seems reasonable by default * The client can utilize the bi-directional nature of Pulsar Protocol and get notified when partitions change (subscribe) therefore limiting the need to pull based on frequency. Thanks, Asaf On Thu, Nov 3, 2022 at 12:19 PM Jiuming Tao wrote: >

[DISCUSS] PIP-222: Add CommandPartitionedTopicMetadata metrics

2022-11-03 Thread Jiuming Tao
Hi pulsar community, I’ve opened a PIP to discuss: PIP-222: Add CommandPartitionedTopicMetadata metrics The PIP link: https://github.com/apache/pulsar/issues/18319 <https://github.com/apache/pulsar/issues/18319> Thanks, Tao Jiuming