MySQL :: MySQL 8.0 Reference Manual

Search Results

Displaying 61 to 70 of 421 total results

25.5.4 ndb_mgmd — The NDB Cluster Management Server Daemon

https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-mgmd.html

--connect-retry-delay Command-Line Format --connect-retry-delay=# Removed 8.0.31 Type Integer Default Value 5 Minimum Value 0 Maximum Value 5 Number of seconds to wait between attempts to contact management server. Second, --initial forces the ...

25.5.29 ndb_top — View CPU usage information for NDB threads

https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-top.html

Each thread is represented by two rows in the output, the first showing system statistics, the second showing the measured statistics for the thread. The display updates once per second; to set a different delay interval, use --sleep-time (-s).

25.5.2 ndbinfo_select_all — Select From ndbinfo Tables

https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndbinfo-select-all.html

--connect-retry-delay Command-Line Format --connect-retry-delay=# Type Integer Default Value 5 Minimum Value 0 Maximum Value 5 Number of seconds to wait between attempts to contact management server. --delay=seconds Command-Line Format --delay=# ...

6.5.4 mysqldump — A Database Backup Program

https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html

If you do replay a further dump file on the target server that contains the same GTIDs (for example, another partial dump from the same origin server), any SET @@GLOBAL.gtid_purged statement in the second dump file fails. The mysqldump client ...

10.9.3 Optimizer Hints

https://dev.mysql.com/doc/refman/8.0/en/optimizer-hints.html

Conflicting hints: For a hint such as /*+ MRR(idx1) NO_MRR(idx1) */, MySQL uses the first hint and issues a warning about the second conflicting hint. Examples: /*+ JOIN_PREFIX(t1) JOIN_PREFIX(t2) */ The second JOIN_PREFIX hint is ignored with a ...

19.1.5.2 Provisioning a Multi-Source Replica for GTID-Based Replication

https://dev.mysql.com/doc/refman/8.0/en/replication-multi-source-provision-replica.html

In a multi-source replication topology, you must therefore remove the SET @@GLOBAL.gtid_purged statement from the dump output before replaying the dump files, because you cannot apply a second or subsequent dump file including this statement. If ...

19.1.6.1 Replication and Binary Logging Option and Variable Reference

https://dev.mysql.com/doc/refman/8.0/en/replication-options-reference.html

replica_checkpoint_period: Update progress status of multithreaded replica and flush relay log info to disk after this number of milliseconds. replica_net_timeout: Number of seconds to wait for more data from source/replica connection before ... The ...

19.2.3.2 Monitoring Replication Applier Worker Threads

https://dev.mysql.com/doc/refman/8.0/en/replication-threads-monitor-worker.html

The statistics are printed depending on the volume of events that the coordinator thread has assigned to applier worker threads, with a maximum frequency of once every 120 seconds. The message lists the following statistics for the relevant ... On a ...

7.6.4.2 Using the Rewriter Query Rewrite Plugin

https://dev.mysql.com/doc/refman/8.0/en/rewriter-query-rewrite-plugin-usage.html

The second statement illustrates that when the Rewriter plugin rewrites a statement, it produces a warning message. The second rule works only when appdb is the default database. To enable or disable the plugin, enable or disable the ...

7.1.10 Server Status Variables

https://dev.mysql.com/doc/refman/8.0/en/server-status-variables.html

Innodb_row_lock_time The total time spent in acquiring row locks for InnoDB tables, in milliseconds. Innodb_row_lock_time_avg The average time to acquire a row lock for InnoDB tables, in milliseconds. Innodb_row_lock_time_max The maximum time to ...

Displaying 61 to 70 of 421 total results