Pulsar client should be able to connect to brokers without DNS #3218
Comments
sijie
added
area/client
type/feature
|
A subtask for this would be to make it possible to use a list of brokers in the proxy client configuration to allow proxy use without dns |
…ice url and web url *Motivation* Sometimes people doesn't have DNS for brokers. It might be good for people to specify a list of brokers as bootstrap brokers. *Changes* This PR introduce `ServiceURI` and `ServiceNameResolver` for supporting specifying multiple hosts in pulsar service url and web url. Master Issue: apache#3218
|
@ivankelly added the subtasks. however I removed "metadata format" and "proxy". because there is nothing to do at these two parts. If the pulsar client supports a URI with multiple hosts, both metadata format and proxy will be working. However the current most tricky part is pulsar-admin. still figuring out how to do it in jersey client. |
…ice url and web url (#3249) *Motivation* Sometimes people doesn't have DNS for brokers. It might be good for people to specify a list of brokers as bootstrap brokers. *Changes* This PR introduce `ServiceURI` and `ServiceNameResolver` for supporting specifying multiple hosts in pulsar service url and web url. Master Issue: #3218
We should still test these, to ensure they do work. I would even stay we should only test these with multiple addresses, and not with single addresses, as single address is a special case of multiple. |
|
add a sub task issue for cpp client |
Fixes #177 Master Issue apache/pulsar#3218 ### Motivation add multiple hosts support to go client ### Modifications - add service uri & service name resolver - add service name resolver to lookup service & rpc client - add unit tests - add integration tests ### Verifying this change - [ ] Make sure that the change passes the CI checks.
|
go client now support multiple hosts (ref: apache/pulsar-client-go#484) |
|
@BewareMyPower @baodi @RobertIndie could you check whether client C++ and Python implement this functionality? |
|
The Python client support should be ready since the first 3.0.0 release or the 2.11.0 release. |
|
OK. Then I'm closing the related issues as completed... |
|
Closed as all subtasks done. |
Sometimes people doesn't have DNS for brokers. It might be good for people to specify a list of brokers as bootstrap brokers.
Since
ServiceUrlProviderwas introduced in #2543 , it should be trivial to add a service url provider implementation that randomly returns a chosen broker.The text was updated successfully, but these errors were encountered: