Search Results
                    
                    
            https://dev.mysql.com/doc/refman/8.4/en/replication-bugs.html
                                 When you have determined that there is no user error involved, and replication still either does not work at all or is unstable, it is time to send us a bug report. If you have a “phantom” problem (one that you cannot duplicate at will), use ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/replication-features-timeout.html
                                If a transaction has a non-temporary error that prevents it from succeeding, it is not retried. The default setting for replica_transaction_retries is 10, meaning that a failing transaction with an apparently temporary error is retried 10 times ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html
                                No error is raised, and no statement in the transaction is executed. If the server runs out of GTIDs, it takes the action specified by binlog_error_action. An error message is returned to the client that requested the rotation, and a warning is ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks.html
                                The account can also be safely used by an administrator to apply or reapply transactions from mysqlbinlog output, for example to recover from a replication error on the channel. If an unexpected operation is attempted for which you did not grant the ... By default, MySQL replication (including Group Replication) does not carry out privilege checks when transactions that were already accepted by another server are applied on a replica or group ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/replication-sbr-rbr.html
                                If there is an error in evaluation on the replica, particularly when executing complex statements, statement-based replication may slowly increase the margin of error across the affected rows over time. For most users, the mixed replication format ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/replication-semisync-installation.html
                                For example: mysql> SELECT PLUGIN_NAME, PLUGIN_STATUS FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME LIKE '%semi%'; +----------------------+---------------+ | PLUGIN_NAME | PLUGIN_STATUS | +----------------------+---------------+ | ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/replication-setup-replicas.html
                                If an event runs on the new replica that has already run on the source, the duplicated operation causes an error. Error messages are issued to the replica's error log if it is not able to replicate for any reason. Before you proceed, ensure that you ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/reusing-ssl-sessions.html
                                Regardless of the cause, an error is returned by default if you specify --ssl-session-data but the session cannot be reused. For example: mysqlshow -u admin -p --ssl-session-data=~/private-dir/session.txt Enter password: ***** ERROR: ... MySQL ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/roles.html
                                If mandatory_roles is assigned a role at runtime that has the SYSTEM_USER privilege, an error occurs and the mandatory_roles value remains unchanged. When the server attempts role activation for a user, it does not treat the nonexistent role as ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/savepoint.html
                                If the ROLLBACK TO SAVEPOINT statement returns the following error, it means that no savepoint with the specified name exists: ERROR 1305 (42000): SAVEPOINT identifier does not exist The RELEASE SAVEPOINT statement removes the named savepoint from ... SAVEPOINT identifier ROLLBACK [WORK] TO [SAVEPOINT] identifier RELEASE SAVEPOINT identifier InnoDB supports the SQL statements SAVEPOINT, ROLLBACK TO SAVEPOINT, RELEASE SAVEPOINT and the optional WORK keyword for ...