Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-semisync.html
Semisynchronous replication between a source and its replicas operates as follows: A replica indicates whether it is semisynchronous-capable when it connects to the source. If semisynchronous replication is enabled on the source side and there is at ... In addition to the built-in asynchronous replication, MySQL 8.4 supports an interface to semisynchronous replication that is implemented by ...
https://dev.mysql.com/doc/refman/8.4/en/stop-group-replication.html
To be completely safe, ensure that your applications can no longer connect to the instance before issuing this statement to avoid any chance of stale reads. The group_replication_components_stop_timeout system variable specifies the time for which ...This statement requires the GROUP_REPLICATION_ADMIN privilege (or the deprecated SUPER ...
https://dev.mysql.com/doc/relnotes/mysql-cluster/8.4/en/news-8-4-4.html
Handling of DBTC and API state alignment errors has been improved by this set of fixes, as well as scan protocol timeout handling in DBSPJ; now, when such misalignments in state are detected, the involved API nodes are disconnected rather than the ...(Bug #37331118) NDB Replication: When a MySQL server performing binary logging connects to an NDB Cluster, it checks for existing binary logs; if it finds any, it writes an Incident event to a log file of its own so that any downstream replicas can detect the potential for lost ...
https://dev.mysql.com/doc/internals/en/debug-sync-further-reading.html
See also worklog entry WL#4259 - Debug Sync Facility Reference manual 5.1 2.3.2 Typical configure Options (--enable-debug-sync) 5.1.2 Command Options (--debug-sync-timeout) 5.1.4 System Variables (debug_sync) Test framework manual 4.14 Thread ...
https://dev.mysql.com/doc/internals/en/semi-sync-replication.html
The clients COMMIT (or in auto-commit mode the current statement) waits until _one_ slave acknowledged that it received (not neccesarilly executed) the transaction or a timeout is reached. In MySQL 5.5 replication can optionally be made ...
https://dev.mysql.com/doc/refman/8.4/en/check-table.html
To avoid timeouts, the semaphore wait threshold (600 seconds) is extended by 2 hours (7200 seconds) for CHECK TABLE operations. To avoid the possibility of a semaphore wait timeout entirely, run CHECK TABLE QUICK instead of CHECK TABLE. option: { ...
https://dev.mysql.com/doc/refman/8.4/en/clone-plugin-failure-handling.html
If the cloning operation is unable to obtain a DDL lock within the time limit specified by the clone_ddl_timeout variable, an error is reported. If a network error occurs during a cloning operation, the operation resumes if the error is resolved ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-configuring-consistency-guarantees.html
Transactions whose consistency level is not EVENTUAL hold execution until a timeout, configured by wait_timeout value is reached, which defaults to 8 hours. A transaction cannot be on-hold forever, and if the time held exceeds wait_timeout it ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure-rejoin.html
The group_replication_autorejoin_tries system variable makes a member that has been expelled or reached its unreachable majority timeout try to rejoin the group automatically. With auto-rejoin, when the member's expulsion or unreachable majority ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-transaction-inconsistencies.html
After this timeout, the coordinator gives up and aborts the transaction. After this timeout, it aborts the transaction, so it may be left half-completed. The global setting for the system variable rpl_stop_replica_timeout is unrelated to the process ... Inconsistencies in the sequence of transactions that have been executed from the relay log can occur depending on your replication ...