| Option | --auto-enable | |
| Aliases | --repl-auto-enable | |
| Config File Options | auto-enable, repl-auto-enable | |
| Description | Auto-enable services after start-up | |
| Value Type | boolean | |
| Valid Values | false | |
| true | ||
--auto-recovery-delay-interval
| Option | --auto-recovery-delay-interval | |
| Aliases | --repl-auto-recovery-delay-interval | |
| Config File Options | auto-recovery-delay-interval, repl-auto-recovery-delay-interval | |
| Description | Delay (in seconds) between going OFFLINE and attempting to go ONLINE | |
| Value Type | numeric | |
| Default | 5 | |
The delay between the replicator identifying that autorecovery is needed, and autorecovery being attempted. For busy MySQL installations, larger numbers may be needed to allow time for MySQL servers to restart or recover from their failure.
| Option | --auto-recovery-max-attempts | |
| Aliases | --repl-auto-recovery-max-attempts | |
| Config File Options | auto-recovery-max-attempts, repl-auto-recovery-max-attempts | |
| Description | Maximum number of attempts at automatic recovery | |
| Value Type | numeric | |
| Default | 0 | |
Specifies the number of attempts the replicator will make to go
back online. When the number of attempts has been reached, the
replicator will remain in the
OFFLINE state.
Autorecovery is not enabled until the value of this parameter is
set to a non-zero value. The state of autorecovery can be
determined using the autoRecoveryEnabled
status parameter. The number of attempts made to autorecover can
be tracked using the autoRecoveryTotal
status parameter.
--auto-recovery-reset-interval
| Option | --auto-recovery-reset-interval | |
| Aliases | --repl-auto-recovery-reset-interval | |
| Config File Options | auto-recovery-reset-interval, repl-auto-recovery-reset-interval | |
| Description | Delay (in seconds) before autorecovery is deemed to have succeeded | |
| Value Type | numeric | |
| Default | 5 | |
The time in ONLINE state
that indicates to the replicator that the autorecovery procedure
has succeeded. For servers with very large transactions, this
value should be increased to allow the transaction to be
successfully applied.