Hi Abhilash, I took a look at the issue you described. I don't think this is the right approach to solve the problem. Because the HTTP and HTTPS ports are only used for admin rest calls and topic lookups. You don't really need to advertise those addresses. When we introduced multiple advertised listeners, we already have that consideration in mind as we only need to advertise the addresses and ports used for binary protocols.
I think to solve the problem, we can just fix the name used in health check topics. E.g. switching from using HTTP port to Binary port. Thanks, Sijie On Sat, Dec 5, 2020 at 12:13 AM Abhilash Mandaliya < abhilashmandal...@gmail.com> wrote: > Replied on the doc :) > > On Fri, Dec 4, 2020 at 6:39 PM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > Hi, > > I left a few comments on the documenations. > > > > Thanks for your efforts, I hope we can get this new feature in soon > > > > Regards > > Enrico > > > > Il giorno gio 3 dic 2020 alle ore 16:39 Abhilash Mandaliya (via Google > > Docs) <abhilashmandal...@gmail.com> ha scritto: > > > >> I've shared an item with you: > >> > >> Apache Pulsar PIP - advertisedListener enhancement > >> > >> > https://docs.google.com/document/d/1YelHBuFAAYkmRNWzhVg4j39-VovGb9Ng2_Vg6zbCqGM/edit?usp=sharing&invite=CJTD-8sC&ts=5fc8a168 > >> > >> It's not an attachment -- it's stored online. To open this item, just > >> click > >> the link above. > >> > >> Let me know if you need an edit access of this doc > >> > > > > -- > Regards, > Abhilash Mandaliya >
