MySQL Cluster

InnoDB Table Maintenance If a table check indicates problems, restore the table to a consistent state by dumping it with mysqldump, dropping it, and re-creating it from the dump file. In the event of a crash of the MySQL server or the host on which it runs, some InnoDB tables might be in an inconsistent state. InnoDB performs auto-recovery as part of its startup sequence. Use CHECK TABLE or a client program to find inconsistencies, incompatibilities, and other problems. Restore a table by … [Read more...] about MySQL Table Maintenance – InnoDB, MyISAM, MEMORY, ARCHIVE

mysqlcheck Client Program In some cases, mysqlcheck is more convenient than issuing SQL statements directly. For example, if you provide it with a database name as its argument, mysqlcheck determines what tables the database contains and issues statements to process them all. You do not need to provide explicit table names as arguments. Also, because mysqlcheck is a command-line program, you can easily use it in operating system jobs that perform scheduled maintenance. mysqlcheck is a … [Read more...] about Understanding mysqlcheck and myisamchk utilities

Table maintenance operations are useful for identifying and correcting database problems such as the following: – Tables that become damaged as a result of a server crash. – Slow query processing on tables. Many tools are available for performing table maintenance: MySQL Workbench MySQL Enterprise Monitor SQL (DML) maintenance statements Utilities: mysqlcheck and myisamchk Server auto-recovery SQL for Table Maintenance Operations There are multiple SQL statements for performing … [Read more...] about Beginners Guide to Implementing Table Maintenance in MySQL

Question: How to list tables inside tablespaces in a MuSQL cluster? The following query meets the aim of the question, lists the database, table name and the corresponding tablespace: SELECT DISTINCT t.table_schema, t.table_name, p.tablespace_name FROM partitions p JOIN TABLES t ON (t.table_schema=p.table_schema and t.table_name = p.table_name) WHERE t.engine='ndbcluster' and tablespace_name IS NOT NULL … [Read more...] about How to List Tables Per Tablespace In MySQL Cluster

Note: In MySQL Server 8.0.X you must use the exact same patch release of MEB as the Server, eg MySQL Server 8.0.13 requires the use of MEB 8.0.13. The Basics For *nix OSes, the document uses a shell expansion for simple naming of folders with "todays" date+time, eg shell:~ # d="$(date '+%d%b_%H%M')" shell:~ # echo $d 13Nov_1338 It is, of course, possible to adjust this as any existing naming conventions dictate. Simple high level backup / restore commands: creates an image backup ( … [Read more...] about Backup and Restore Of Group Replication Node ( MySQL 8.0 )

The Problem A replication slave cannot continue replicating from its Master. One such example is that after being stopped for a long ( or longer than anticipated ) timeframe, the BINARY LOGS required on the Master have been purged. [ERROR] [MY-013114] [Repl] Slave I/O for channel 'group_replication_recovery': Got fatal error 1236 from master when reading data from binary log: 'Cannot replicate because the master purged required binary logs. Replicate the missing transactions from elsewhere, or … [Read more...] about MySQL Server 8.0 – How to create a REPLICATION SLAVE using MEB

Each online MySQL Cluster backup receives a unique identification number. This is to ensure that there is a history of activities in the backup directory. However, this can causes problems. For example, if a system restarts, this ID counter is reset and starts again at number 1, causing problems if you didn't move earlier backups. This post will discuss how to generate unique backup ids. The best method is after each online backup operation to move the created backup directory to another … [Read more...] about How to Generate Unique IDs For MysQL Cluster Backups

A rolling restart is required when you need to restart all of the nodes in a cluster for some change to take effect. Rather than bringing down the entire cluster, you can restart each single node one by one, in order to allow the cluster to continue serving requests during the changes. Most operations can be done using this technique, such as changing config.ini settings (ie. DataMemory, MaxNoOfConcurrentTransactions, etc.). However, there is a main instance when you can not use this process … [Read more...] about How to Perform a Rolling Restart of MySQL NDB Cluster

There are three types of nodes that you might want to add to an existing MySQL Cluster: mysqld (API) nodes, management server nodes, and data nodes. Adding a new mysqld (API) node In order to add a new mysqld node, you simply need to add the new [mysqld] section to the config.ini and then perform a rolling upgrade. After you have done this, then you can start up the new mysqld node and it will have all of the cluster data available. To do this, following you would follow these steps: Edit … [Read more...] about How to Add New Nodes To an Existing MySQL Cluster Setup