If you have a topic that has high fanout of subscriptions, the current
workaround is to increase the number of partitions. So partitions can be
spreading across brokers. So you have more bandwidth to support fanout
subscriptions.
Bypass brokers to read directly from bookies is also another approac
I'm curious what the current work around is: 1) a partitioned topic to help
spread the load or 2) reading directly from the bookie?
Best.
On Thu, May 21, 2020, 2:29 PM Joe F wrote:
> Very useful feature.
>
> I would like the proposers to think just beyond scaling consumers. If done
> right, th
Very useful feature.
I would like the proposers to think just beyond scaling consumers. If done
right, this has the potential to open up a lot of use cases in ML, where
you need to reprocess old/archived data. Being able to spin up a read-only
broker, ( dedicated brokers that read from tiered s
👍
Best Regards.
Jia Zhai
Beijing, China
Mobile: +86 15810491983
On Fri, May 8, 2020 at 4:29 AM Sijie Guo wrote:
> Dezhi, thank you for sharing the proposal!
>
> It is great to see Tencent started contributing this great feature back to
> Pulsar! This feature will unlock a lot of new capa
Dezhi, thank you for sharing the proposal!
It is great to see Tencent started contributing this great feature back to
Pulsar! This feature will unlock a lot of new capabilities of Pulsar.
I have moved the proposal to
https://github.com/apache/pulsar/wiki/PIP-63:-Readonly-Topic-Ownership-Support
