You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
When the queue is full or the solace queue is configured incomming, the kafka connect sink always sends messages, these messages are unfortunately lost (I use the solace topic to publish "sol.topics")
it's not very resilient
Do you have a solution to offer me so as not to lose messages please?
The text was updated successfully, but these errors were encountered:
The solution would be to use queues instead of topics. A PubSub+ queue guarantees order of delivery, provides High Availability and Disaster Recovery (depending on the setup of the PubSub+ brokers) and provides an acknowledgment to the connector when the event is stored in all HA and DR members and flushed to disk.
Hello,
When the queue is full or the solace queue is configured incomming, the kafka connect sink always sends messages, these messages are unfortunately lost (I use the solace topic to publish "sol.topics")
it's not very resilient
Do you have a solution to offer me so as not to lose messages please?
The text was updated successfully, but these errors were encountered: