Does it look like a new message router for the case that the message is without the partition key? The only difference is the router is based on the backlog.
Thanks, Penghui On Fri, Aug 26, 2022 at 10:15 AM Haiting Jiang <jianghait...@gmail.com> wrote: > Hi Mingyu, > > About the use case of this feature, I have some concerns. > > Changing the message routing strategy in the producer may cause a message > ordering issue. > But if you don't have message ordering requirements, you can use SHARE > subscription mode, > and we can increase the consumer number of one partition to increase the > consumption rate. > > > Thanks, > Haiting > > On Thu, Aug 25, 2022 at 1:35 PM Gavin Gao <zhangmin...@apache.org> wrote: > > > Where we store the metadata? > > I suggest we use the system topic to store the metadata instead of zk > > > > On 2022/08/25 02:36:56 baomingyu_5 wrote: > > > Hi all, > > > > > > In the exclusive consumption mode of exclusive, failover, reader, etc. > > if a large number of messages accumulate due to limited consumption > > capacity or consumption logic problems, expanding partitions or modifying > > consumption logic cannot reduce the consumption of new messages in time. > > Influence, a certain proportion of newly added messages will still be > > produced in the accumulated paritition, and new messages cannot be > quickly > > consumed by restarted consumers or new consumers. In this way, the time > > affected by the accumulation factor may very long. > > > > > > In order to reduce the impact on the business, through the control of > > read and write permissions, configure some partitions as read-only, so > that > > newly produced messages can be sent to the partitions with less > > accumulation or newly expanded, reducing the impact on the business > caused > > by the accumulation of messages. Reduce the overall time-consuming of > > production--consumption. > > >
