CODEWITHSUNDEEP
symmetricds
Cody Schilke
Cody Schilke

Reputation: 21

SymetricDS Multi-NodeGroup Replication

In SymmetricDS we've been replicating successfully from master to children and children to master for years. We're now needing to replicate from master to master (mirror) where the latter master is a mirrored reporting database. Keep in mind that some tables between the master/child relationship are asynchronous. When we build out the SymmetricDS configurations for the master we see a successful initial load. We also see successful replication between master --> mirror. What we cannot resolve is the replication between child --> master --> mirror. Any changes occurring on a child, as usual, replicates to the master, but nothing moves to the mirror. If a change happens directly on the master, the mirror is updated. We need both.

Upvotes: 1

Views: 200

Answers (2)

Cody Schilke
Cody Schilke

Reputation: 21

I believe I've found a work-around. In sym_data the node_id is recorded to prevent looping. This value represents a child node. The mirror master has no contact or relationship with a child node, so when the master trigger fires, it records the child node and so the master mirror ignores it. If I modify the triggers to hard code the master node in the result instead of the child node the master mirror then processes the result. Again, I believe there is a limitation in SymmetricDS with regards to the sym_node table as it should not require a node_group_id (a node should be allowed to join many node_groups).

Upvotes: 0

Boris Pavlović
Boris Pavlović

Reputation: 64640

Configure sync on incoming batch as explained in the chapter on bi-directional synchronization https://www.jumpmind.com/downloads/symmetricds/doc/3.10/html/user-guide.html#_bi_directional_synchronization

Upvotes: 0

Related Questions