Hi Enrico, The current implementation of the transaction coordinator is run with the broker, but the transaction coordinator Is a separate module in Pulsar. This is also mentioned in PIP-31 https://github.com/apache/pulsar/wiki/PIP-31%3A-Transaction-Support
Thanks, Penghui On Apr 21, 2021, 7:24 PM +0800, Enrico Olivelli <eolive...@gmail.com>, wrote: > Hello, > Pulsar 2.8.0 is coming near to the release and we want transactions to > be "production ready". > > If I understand correctly now we start the Transaction Coordinator > service inside the Broker. > > Does it make sense to have the option to run the TC as a separate > service, as we do for the Functions Worker ? > > For instance in a big cluster, with many brokers, an user may like to > dedicate machines to the role of Transaction Coordinator and do not > serve all of the usual Broker activities. > > The same problem will also go into the Helm Chart, it would be better > to have the ability to configure the transaction related services with > specific options. > > What do you think ? > > > Enrico
