Although I agree with this direction, having the config in the lookup requests, I have the following questions.
1. Given that the current pulsar assigns topics to brokers at the bundle level, what happens with a topic lookup with rack info(rack A) for the bundle that's already assigned to a different rack(rack B)? 2. Given that the latest load shedders(TransferShedder and AvgShedder) determine the destination brokers from the leader, how would the leader make sure to unload bundles(topics) to the brokers in the same rack? Thanks, Heesung On Fri, Jul 26, 2024 at 8:29 AM Heesung Sohn <hees...@apache.org> wrote: > > +1 (not binding) > > Heesung > > On Thu, Jul 25, 2024 at 7:52 PM Jie crossover <crossover...@gmail.com> wrote: > > > > +1 > > I left some comments in the PR. > > -- > > Best Regards！ > > crossoverJie > > > > > > Zike Yang <z...@apache.org> 于2024年7月25日周四 11:15写道： > > > > > Hi, all, > > > > > > I proposed a new proposal to add client properties support for the > > > lookup: https://github.com/apache/pulsar/pull/23075 > > > > > > PTAL and share your thoughts. Thanks! > > > > > > BR, > > > Zike Yang > > >
