Setting/Reverting replication trigger behaviors from a command line

In the 2023.03 release of Mongoose, we introduced new functionality that changed some skip-replication trigger behavior and Data Lake replication behavior. You can revert to the pre-2023.03 behavior using a Command Line Interface (CLI).

Previous to these changes, there were two issues in this area:

  • Some applications were purposefully setting skip-replication triggers for performance reasons in a way that left Data Lake data incorrect.
  • The second involved situations in which 'Site A' would replicate to Data Lake, and 'Site B' would also replicate to Data Lake. In this scenario, data that was replicated transactionally from Site A to Site B was not then being replicated from Site B to Data Lake.

To address these situations, we introduced new replication trigger generation code such that:

  • Data being replicated to Data Lake now ignores any skip-replication triggers.
  • Data is replicated to Data Lake from both Site A and Site B.

This new behavior is now the default behavior.

Reverting the behavior

If you prefer to return to the original behavior, you can revert to it by using a CLI to set the disabledlignoreskip switch value to 1. This can be done by means of this command in a CLI: 
ConfigManager -U:APP -name:appName -mode:edit -disabledlignoreskip:1

where appName is the name of your Mongoose-based application.

Note: To reinstate the new (default) behavior, set this value to 0 (zero).
Related topics