I see mention of symmetricDS allowing synchronisation one way, I'm just wondering if there is any example demonstrating what a proper single direction configuration should look like?
I have a setup configured where all the routes to the tables I'm synchonising are, to the best of my knowledge, are one way from the client to the server, yet the server node still seems to send routine notifications back to the clients connected to it.
Does one way configuration only refer to the tables you are trying to synchronise? or can you configure it so it's completely one way and the clients are only sending requests to the server and never get any notificaitons back from the server at all?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You should have a group link from server to client so that when you change configuration on the server, it syncs out to the clients. If you want to prevent the server from sending heartbeats to the client, you can set the following parameter for the server node:
start.heartbeat.job=false
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Forgive my newness to symmetricDS.
I see mention of symmetricDS allowing synchronisation one way, I'm just wondering if there is any example demonstrating what a proper single direction configuration should look like?
I have a setup configured where all the routes to the tables I'm synchonising are, to the best of my knowledge, are one way from the client to the server, yet the server node still seems to send routine notifications back to the clients connected to it.
Does one way configuration only refer to the tables you are trying to synchronise? or can you configure it so it's completely one way and the clients are only sending requests to the server and never get any notificaitons back from the server at all?
You should have a group link from server to client so that when you change configuration on the server, it syncs out to the clients. If you want to prevent the server from sending heartbeats to the client, you can set the following parameter for the server node:
start.heartbeat.job=false