Hi Aaron Nice explanation. If Solace is having two server in LB mode with mutiple brokers ...each broker having standalone datastore and client published the messages .. Does the data distributed across the brokers like offset segmented in kafka or sit in one datastore ?
Just a follow-up here, I never saw this message! From how I understand your question: yes, if you have a pair of Solace brokers configured in a High-Availability redundant pair, then their message store and state and everything is shared between them and kept in-sync; so if one broker fails, the other can take over, and the publishing application API will automatically reconnect to the other broker and continue. Note that message loss/reordering will not happen if using Guaranteed messaging, our persistent messaging QoS.
![Intro to Docker [with Java Examples]](http://i.ytimg.com/vi/FzwIs2jMESM/mqdefault.jpg)
Hi Aaron, this is very informative! Looking forward to more of these tutorials...
Hi Aaron
Nice explanation. If Solace is having two server in LB mode with mutiple brokers ...each broker having standalone datastore and client published the messages .. Does the data distributed across the brokers like offset segmented in kafka or sit in one datastore ?
Hey mamatha! Have you tried to look for your answer on our Solace Community on solace.community?
Just a follow-up here, I never saw this message! From how I understand your question: yes, if you have a pair of Solace brokers configured in a High-Availability redundant pair, then their message store and state and everything is shared between them and kept in-sync; so if one broker fails, the other can take over, and the publishing application API will automatically reconnect to the other broker and continue. Note that message loss/reordering will not happen if using Guaranteed messaging, our persistent messaging QoS.
How to print only that hello world from payload specifically??