Hi dev,When subscribe to multi-partitioned topic and set user-defined
partitioned retry and dlq topic in deadLetterPolicy,the producer instances are
multipled by partitions, In order to reduce the resource usage at both client
and server side, I start discussing PIP-308
Congrats!
Best,
lifepuzzlefun
On 2023/07/23 04:13:35 Haiting Jiang wrote:
> Congrats!
>
> Best,
> Haiting
>
> On Sun, Jul 23, 2023 at 9:38 AM houxiaoyu wrote:
> >
> > Congrats, Tison!
> >
> > Best,
> > Xiaoyu Hou
> >
> > D
InfoCompressionThresholdInBytes
>managedCursorInfoCompressionThresholdInBytes
>
>And it is better to add a link to the data structure to help
>reviewers to understand the proposal.
>
>Regards,
>Penghui
>
>On Sun, May 28, 2023 at 5:53 AM lifepuzzlefun wrote:
>
>> agree. update the pip with more ba
d be grateful if you can expand the PIP, so the reader will have
> answers to those questions when reading it.
>
>
> On Thu, May 11, 2023 at 7:28 PM Enrico Olivelli wrote:
>
> > Makes sense to me.
> > Thanks for your contribution
> >
> > Enrico
> >
> >
help much when the data is lower than 16KB.
>
> Thanks,
> Penghui
sorry, i will start the vote after the pip thoroughly discussed next time.
> Hello lifepuzzlefun,
> thanks for your proposal
> I believe that it is too early to start a VOTE as the discussion has
> not happened yet.
Hello Pulsar community,
This thread is to start a PIP-270 Add config to set metadata size threshold for
compression
Discussion thread:
https://lists.apache.org/thread/6930c74m31rflrql9y3dpjmm0sbccqkb Issue:
https://github.com/apache/pulsar/issues/20307
Voting will be open for at least 48
Dear Pulsar community,
I create a pip aim to add configuration on size based metadata compresssion.
https://github.com/apache/pulsar/issues/20307
We welcome your feedback and suggestions on this proposal.
yes, my issue is the big pojo.
> Oh, I figured out the reason finally. It's caused by the lombok. After
> I changed all getters and setters with the trivial getters and
> setters, the completion time was reduced from 15 seconds to 2 seconds.
>
> Thanks,
> Yunze
Seems Yunze has solved the
+1 (non-binding)
hope to see this feature！
current file is 3470 line with all pulsar configuration.
it is slow in my local ide.
59 config in loadbalancer.
17 config in metric.
64 config in policies.
41 config for bk client.
50 for managed ledger.
100+ for all other server cofig.
if split by category maybe more clear
class
Totally agree. I have seen some patches with little change worth to do, but
stopped making progress, only being told an pip is needed.
I think if we have one fast-path for notice small changes like metrics or
configuration.
some pip to add configuration is also simple enough. like just add an
I think this feature is very helpful on heavy traffic topic which have
continuous stable load on each partition.
Is there a way we can set some kind of namespace policy to set the plugin
PartitionAssigner. Hope this can be set on namespace level,
if this can be achieved, it is more adoptable
I'm interest on the implementation details.
1. where is the partition to bundle mapping stored？when upgrade origin logic to
the new round robin logic. how the current code distinguish partition assigned
by origin logic and the new created topic assign by round robin logic.
2. can you explain
Hi, pulsar community. I'm insterest in this topic and want to join the
discussion : - )
I test to create one partitioned topic with 1024 partitions in a namespace with
256 bundle.
the distribution for this topic is post below.
key is the total assigned partition number to the bundle.
value
14 matches
Mail list logo
