Replies: 2 comments 1 reply
-
If you're publishing to streams they would persist, however note a stream lives in one cluster only and can be mirrored to the other. For JetStream you need 3 clusters to keep things up during an outage. Best you give us some more information and check out these videos https://www.synadia.com/screencast |
Beta Was this translation helpful? Give feedback.
-
Thanks for quick answer. I subscribe into east cluster, publish into west cluster. While link is ok - all works.
Now subscriber is not available. Then I publish messages to west cluster again. After that I restore broken connection:
But subscriber has got no messages, but I expect it would. Below attached all configaration files: docker-compose.yml
golang client config.json
nats_conf/east_az1.conf
nats_conf/east_az2.conf
nats_conf/east_az3.conf
nats_conf/west_az1.conf
nats_conf/west_az2.conf
nats_conf/west_az31.conf
nats_conf/north_az1.conf
nats_conf/north_az2.conf
nats_conf/north_az3.conf
nats_conf/sys.conf
Thanks in advance |
Beta Was this translation helpful? Give feedback.
-
Hello,
We have 2 clusters, east_az1 (gw), east_az2, east_az3 and west_az1(gw), west_az2, west_az3
gateways east_az1 and west_az1 are linked together.
Jetstream enabled.
We subscribe to messages in east cluster, and publish messages to west cluster, and when east_az1 <-> west_az1 link got broken (temporary) the messages are lost.
How should we configure servers in order to found some kind of messages queue, to prevent messages lost ?
Can we do this by means of NATs or should we implement it in pub client only?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions