PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/group-replication-system-variables.html
This safeguard is particularly important when the server is configured to start Group Replication on server boot (group_replication_start_on_boot=ON), but it is also useful when Group Replication is started manually using a START GROUP_REPLICATION ... This section lists the system variables that are specific to the Group Replication ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-operations.html
Since it is rare to re-create a clustered index or re-define primary keys on large tables, or to encounter a system crash during this operation, this manual does not provide information on recovering from this scenario. Online support details, ...
https://dev.mysql.com/doc/refman/5.7/en/linux-installation-rpm.html
Be aware that they may differ from those built by Oracle in features, capabilities, and conventions (including communication setup), and that the installation instructions in this manual do not necessarily apply to them. This is because conflicts ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbd-definition.html
The only mandatory parameter is HostName; this must be defined in the local [ndbd] section. Information about configuration parameters specific to NDB Cluster Disk Data tables can be found later in this section (see Disk Data Configuration ... The ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-privilege-distribution.html
This support is not enabled by default; you should follow the procedure outlined in this section in order to do so. The first step in enabling distributed privileges is to load this script into a MySQL Server that functions as an SQL node (which we ... NDB Cluster supports distribution of MySQL users and privileges across all SQL nodes in an NDB ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html
ndb_restore cannot be used to re-create the table with a different definition from the original; this means that you must either create the table manually, or alter the columns which you wish to promote using ALTER TABLE after restoring the table ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication-issues.html
This message is available in the output of SHOW SLAVE STATUS, and indicates that the SQL thread has stopped due to an incident registered in the replication stream, and that manual intervention is required. This must be done manually, or possibly by ... This section discusses known problems or issues when using replication with NDB ...A loss of connection can occur either between the source cluster SQL node and the replica ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication-schema.html
This is true regardless of whether the replica is a single server or a cluster. This keeps the source mysqld process updated to changes performed by the NDB storage engine. This table can be updated by the user to perform filtering by database or ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-upgrade.html
If the table cannot be repaired, see Section 2.10.12, “Rebuilding or Repairing Tables or Indexes” for manual table repair strategies. InnoDB tablespace encryption requires that the keyring plugin to be used be loaded prior to InnoDB ... Each ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-errors.html
This includes the case that a statement produces an error on the source or the replica, but not both. To address the issue, connect to the replica manually and determine the cause of the problem. For example, if the replication SQL thread records a ... If a statement produces the same error (identical error code) on both the source and the replica, the error is logged, but replication ...