The new release of SymmetricDS 3.3 will help you:
Change how synchronization is performed for a select group of nodes before rolling out the change across all nodes. While each node's group assignment determines how it will sync with other nodes, it can also be added to a small subgroup called a grouplet. A grouplet lets you add to or subtract from an existing configuration and specify which nodes will participate. Once configured, it's easy to add more nodes to the grouplet to activate the new configuration for more nodes.
A new configuration table makes it easy for one node to request a table reload from another node. When a remote node is undergoing a software upgrade, it can request that the server send it a new dataset for tables. The reload can be modified to remove and populate specific rows instead of the entire subset defined in configuration. The system records when the reload completes successfully.
An improved conflict management now records the conflict identifier and the current data from the database on an incoming batch in error. When a remote node sends data to load that has already changed, a conflict detector puts the batch in error. Now the user can see which conflict detector was used, the old and new data at the time of change, and the current data from the database.
The user interface was enhanced with icons and tooltips that indicate when a trigger is setup properly or missing a router link. The user can quickly see when there is a configuration error. Better default values have been set to avoid or report on common mistakes, such as sending data for tables that don't exist and specifying catalog or schema when it should be left blank. Log messages were improved and more logging was added to help in some problem areas such as node registration.