No committed transactions are lost.

The slave automatically identifies that the master is unreachable and performs any required actions so that applications can start using the slave as the new master.

As soon as the incident happens, application can read data from the slave and rely on it to return a full and current set of data.

Reads from the slave can return outdated data until the value of the rpi_semi_sync_master_timeout variable is reached.

Reads from the slave can return outdated data for some time, until it applies all transactions from its relay log.

A small amount of committed transactions may be lost in case they were committed just before the disk failure.

It defines all innodb tablespace options relative to a starting parent directory.

It is not necessary because innodb_data_home_dir is already defined.

It allows scanning of other locations to discover more innodb tablespaces.

It moves all innodb tablespaces to the /innodb_extras directory to enable a new

innodb_data_home_dir to be defined.

It adds more temporary workspace in addition to the innodb_tmpdir location.

recording the order in which queries are issued

audit of all queries

point-in-time recovery

replication

logging the duration and locks for all queries

TCP

SOCKET

PIPE

DIRECT

IPv6

FILE

IPv4

The mysqlcheck --check --all-databases command takes table write locks while performing a series of checks.

The mysqlcheck --optimize --all-databases command reclaims free space from table files.

The mysqlcheck --repair --all-databases command can repair an InnoDB corrupted table.

The mysqlcheck command can be renamed mysqlrepair so that it repairs tables by default.

The mysqlcheck --analyze --all-databases command performs a series of checks to spot eventual table corruptions.

They are converted to a highly compressible binary format.

The data format is identical to how MySQL stores the data on disk.

They are required to obtain FIPS security compliance.

The resulting files are easily human readable.

They are faster than logical backups because the process is a simple file or file system copy.

The user is logged in with --user=accounting as an option.

The user is authenticated as the anonymous proxy user ‘’@’%’.

The user is authorized as the accounting@localhost user.

The user is authorized as the rsmith@localhost user.

The user failed to define a username and the connecting username defaulted to ‘’@’%’.

It is the time between the I/O thread receiving details of the master ' s last transaction and the time it was applied by the SQL thread.

It is the time between the most recent transaction written to the relay logs and the time it was committed on the master.

It is the time between the I/O thread receiving details of the master’s last transaction and the time it was written to the relay log on the slave.

It is the time between the most recent transaction applied by a SQL thread and the time it was committed on the master.

The instance deployed on host2 is elected as the new primary instance.

The instance deployed on host3 is expelled from the cluster and must be rejoined using cluster.addInstance ( ' host3:3377 ' )

The instance deployed on host3 will automatically rejoin the cluster when connectivity is re-established.

Failure of the instance deployed on host1 provokes an outage.

The issuing command cluster.switchToMuitiPrimaryMode() will fail to enable multi-primary mode.

The primary instance can be specified by using the command cluster.setPrimaryInstance( < host > : < port > ).

It creates a logical backup of all MySQL user accounts.

It creates a logical backup of all metadata, but contains no table data.

It returns an error because the mysqldump command should have been used.

It creates a logical backup of only the users database.