BewareMyPower commented on code in PR #23075: URL: https://github.com/apache/pulsar/pull/23075#discussion_r1690756510
########## pip/pip-368.md: ########## @@ -0,0 +1,148 @@ +# PIP-368: Support client properties for the lookup + +# Background knowledge + +## How Pulsar Lookup Works + +Before producing or consuming messages, a Pulsar client must first find the broker responsible for the topic. This +happens through the lookup service. The client sends a `CommandLookupTopic` request with the topic name to the lookup +service, which then returns the responsible broker. The client then interacts with this broker to produce or consume +messages. + +On the broker side, users can customize lookup logic by setting a custom load manager in the `loadManagerClassName` +configuration. + +# Motivation + +Currently, the lookup process uses only the topic name as its parameter. However, to enhance this process, it's +beneficial for clients to provide additional information. This could be done by introducing the `properties` field in +the client configuration. The client can then send these properties to the broker during the lookup process. + +Here is a scenario for using the client properties for the lookup: +Assuming there are two brokers that broker-0 configures the "rack" property with "A" and broker-1 configures the "rack" +property with "B". By using the lookup properties, clients can supply rack information during the lookup, enabling the Review Comment: Even if a broker configures the "rack" property, there is no way to let a broker know another broker's "rack" property. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
