I’m wanting to get some thoughts on the architecture side of how we could increase the availability of Pulsar for producers. We’re running into an interesting problem with some of our teams where Pulsar is occasionally not available when they attempt to produce a message. There have been discussions about using an event-sourcing pattern with an external data store that’s periodically checked (like a queue), but even with the most available data storage technologies, there’s still sort of a chicken vs egg problem of “What happens if that data store is not available either?”I’m wondering if there’s something we could do in the Pulsar client to handle Pulsar availability issues. If multiple cluster endpoints are passed to the serviceUrl parameter when constructing the Pulsar Client, if one cluster is not available, will the client automatically try one of the other endpoints? If not, what are some ways we could address this problem without making the implementation overly complex on the producer-side? -- Devin G. Bost Senior Data Engineer [signature_1883684011]
________________________________ CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you.
