Adding also users@ +1 for me. Discovery service has never been useful AFAICT.
On Thu, Sep 16, 2021 at 9:42 AM Michael Marshall <mikemars...@gmail.com> wrote: > Hi Pulsar Community, > > What is the status of the Pulsar Discovery Service? It seems to me that > this service is no longer needed and could possibly be removed. I don't > have historical context though, and I'm not sure if anyone is using it, so > I am sending this question to the mailing list. > > In the module's README, it lists the primary function of the Pulsar > Discovery Service as follows: > > > It keeps list of active available brokers and redirects all incoming > requests to one of > > the broker in round-robin manner. > > Based on talking with Matteo in today's community meeting, this > functionality (or something similar to it) was historically useful in on > premise installations. Those use cases are likely no longer required, given > that Load Balancers and DNS can solve this network routing problem. > > I ask because the Pulsar Discovery Service's authentication implementation > is a bit behind. It does not use the AuthenticationState interface for > authenticating connections, which means that it only supports a subset of > the Pulsar authentication features. For example, the AuthenticationState > interface is required for supporting SASL and for reauthenticating > connections once a JSON Web Token has expired. It seems to me that we > should either update the Discovery Service's authentication implementation, > or we should remove the module altogether. > > If there is consensus that we can remove it, I am happy to remove the > module, its associated documentation from the website, and any references > to it in start-up scripts. It is not referenced in the Helm Chart, so the > helm chart will not need to be updated. > > Thanks, > Michael > -- -- Matteo Merli <matteo.me...@gmail.com>
