You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/09/16 01:06:36 UTC

[GitHub] [pulsar] EronWright edited a comment on issue #12040: [PIP 95] Smart Listener Selection with Multiple Bind Addresses

EronWright edited a comment on issue #12040:
URL: https://github.com/apache/pulsar/issues/12040#issuecomment-920486231


   @wangjialing218 thanks for sharing, I believe our efforts are complimentary.  It would be reasonable to use the new `bindAddresses` property to define KOP ports; each protocol handler would filter on the scheme component.  For example, the Pulsar broker service would act on the bindings for `pulsar` and `pulsar+ssl`.
   
   Please take a look at the linked PR.  My expectation is that the KOP handler obtain its server ports using:
   ```
   List<BindAddress> bindAddresses = BindAddressValidator.validateBindAddresses(serviceConfig,
                   Arrays.asList("kafka", "kafka+ssl"));
   ```


-- 
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-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org