Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space ML1 and version 9.1

...

where N is the number of statements to skip. The Slave skips the specified number of statements and attempts to execute the following statements. If the statement after N+1 fails for any reason, the Slave remains in the same state as before the SKIP command was issued. For example, if there are three consecutive failing queries in a row, SKIP 1 or SKIP 2 has no effect on the Slave position, but SKIP 3 enables replication to resume.

Anchor
Specifying_Ignored_and_Included_Databases
Specifying_Ignored_and_Included_Databases
Specifying Ignored and Included Databases

The ClustrixDB replication Slave supports the following modes:

...

Note
  • These "ignore" and "include" directives affect named Slave instances globally.
  • Only the current database of a statement determines whether it is executed or skipped as part of this policy.
  • Rows in which the allow column matches the policy variable are treated as if they are not present (that is, according to the policy).
  • Stop the Slave manually before changing policies. This configuration is read when the Slave starts (and periodically when its buffer fills).

Anchor
Controlling_Slave_Behavior_on_Errors
Controlling_Slave_Behavior_on_Errors
Controlling Slave Behavior on Errors

ClustrixDB offers two ways to control slave behavior on errors:

...