You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
use_tls and pulsar+ssl:// client behavior can differ #269
While running Pulsar cluster proxies behind an AWS Load Balancer I ran into issues with TLS connections to the proxies using example code from this repository. Running the examples/consumer.py code with the client url set to an LB hostname and use_tls=True results in connection failures, whereas simply specifying pulsar+ssl:// the consumer works as expected. After checking docs it seems the use_tls argument is deprecated, but I would still expect the behavior between use_tls and pulsar+ssl:// to be the same. I can provide details on the load balancer configuration if needed.
@mattsre The use_tls is indeed deprecated setting.
In early client version, it was actually requiring to use both pulsar+ssl as well as use_tls. Later on, the flag was made redundant by inferring directly, though it was not removed to avoid compatibility issues.
Activity
merlimat commentedon Oct 11, 2025
@mattsre The
use_tlsis indeed deprecated setting.In early client version, it was actually requiring to use both
pulsar+sslas well asuse_tls. Later on, the flag was made redundant by inferring directly, though it was not removed to avoid compatibility issues.