Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
0004254: Multi-master configuration with 3 nodes doesn't work (see note
added to issue)
  • Loading branch information
Philip Marzullo committed Nov 18, 2020
1 parent ed6bf6d commit b1e9a1f
Showing 1 changed file with 7 additions and 4 deletions.
Expand Up @@ -477,10 +477,13 @@ protected Trigger buildTriggerForSymmetricTable(String tableName) {
boolean syncChanges = !TableConstants.getTablesThatDoNotSync(tablePrefix).contains(
tableName)
&& parameterService.is(ParameterConstants.AUTO_SYNC_CONFIGURATION);
boolean syncOnIncoming = !configurationService.isMasterToMaster() && (parameterService.is(
ParameterConstants.AUTO_SYNC_CONFIGURATION_ON_INCOMING, true)
|| tableName.equals(TableConstants.getTableName(tablePrefix,
TableConstants.SYM_TABLE_RELOAD_REQUEST)));
// sync on incoming for symmetric tables are blocked from being synchronized to other nodes when
// master to master is set up. We need to allow sync on incoming at the registration server so that
// tables like sym_node and sym_node_security are delivered to other nodes in the master to master
// and the other nodes will then be able to synchronize with non-registration nodes.
boolean syncOnIncoming = (!configurationService.isMasterToMaster() || nodeService.isRegistrationServer())
&& (parameterService.is(ParameterConstants.AUTO_SYNC_CONFIGURATION_ON_INCOMING, true)
|| tableName.equals(TableConstants.getTableName(tablePrefix,TableConstants.SYM_TABLE_RELOAD_REQUEST)));
Trigger trigger = new Trigger();
trigger.setUseHandleKeyUpdates(false);
trigger.setTriggerId(tableName);
Expand Down

0 comments on commit b1e9a1f

Please sign in to comment.