[Bug] Cannot use non-default value for pulsar.service url
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Version
Pulsar 3.1
Tested in both MacOS and Docker-compose
### Minimal reproduce step
Follow the steps in
https://pulsar.apache.org/docs/3.1.x/io-cdc-debezium/#configuration-2
but change pulsar.service.url to something else, e.g. `pulsar://pulsar-server:6650` for docker-compose
### What did you expect to see?
Its is always "pulsar://localhost:6650" no matter what I change the config to…
I can see logs:
2023-09-28T16:31:36,502-0700 [pulsar-client-io-1-3] INFO org.apache.pulsar.client.impl.ConsumerStatsRecorderImpl - Pulsar client config: {"serviceUrl":"pulsar://localhost:6650","authPluginClassName":null,"authParams":null,"authParamMap":null,"operationTimeoutMs":30000,"lookupTimeoutMs":30000,"statsIntervalSeconds":60,"numIoThreads":8,"numListenerThreads":8,"
and
2023-09-28 16:33:46 2023-09-28T23:33:46,136+0000 [pulsar-client-io-1-2] WARN org.apache.pulsar.client.impl.ConnectionPool - Failed to open connection to localhost/:6650 : io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:6650
I need to change the url to something else so that I can work in docker-compose or production.
Thanks!
### What did you see instead?
I had to use `network_mode: host` for now as workaround in https://github.com/xdblab/xdb/pull/25
### Anything else?
_No response_
### Are you willing to submit a PR?
- [X] I'm willing to submit a PR!
Contributor guide
Research direction
Start with the Pulsar 3.1.x Debezium connector configuration at the linked documentation and reproduce the issue in Docker Compose using a non-default pulsar.service.url. Trace the configuration value against the client logs; done means the client connects to the configured URL instead of always using pulsar://localhost:6650.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100