-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change default pulsar stanalone behavior #1152
Comments
We should make the Standalone service to behave like the Proxy. Currently, the Pulsar standalone service is a very regular Pulsar deployment, with 1 broker / 1 bookie / 1 ZK all running in the same JVM. The normal lookup and redirection for service discovery applies to standalone. If the "hostname" of the machine where the Standalone service is running is not set, or set to a name that is not in DNS or anyway reachable from other machines, the client will fail. The user can specify If we make the Standalone to force the "proxy" flag in the |
I wonder if an alternative fix would have been to force the proxy flag when no advertised address is configured. This would improve support for advanced configurations in standalone mode, and avoid treating standalone mode as a special case. |
That would pose a problem in a typical bare-metal deployment where the |
Good point. Here's another possibility, force the proxy flag when in standalone mode and the advertised address is pulsar/pulsar-broker/src/main/java/org/apache/pulsar/PulsarStandaloneStarter.java Lines 78 to 80 in 5ad4059
This would allow standalone mode to support advertised listeners when configured. At the moment, standalone is not really compatible with multiple listeners. I am working on a PR for that. |
Currently pulsar in standalone mode expects an advertised address to be passed to use localhost this is unnecessarily complicated , for cases such as docker images it's even more complicated in say osx environments where docker runs inside a linux vm.
Suggestion is to enable default pulsar proxy type configuration for standalone mode so it becomes easier to use.
The text was updated successfully, but these errors were encountered: