Search



Search Results
Displaying 4081 to 4090 of 4186 total results
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-restore-cluster.html
Stop the cluster using stop cluster, then restart it using start cluster with the --initial option, which causes the data node file systems to be cleared. Following this, you can restore the cluster from the desired backup using restore cluster.
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-start-cluster.html
--initial option The --initial option (short form: -i) causes the following to happen: All cluster data node are started as if start process --initial had been used on them, which means that all data nodes wipe their data and start with clean data ...See Section 5.4.1, “The create cluster Command”, and Section 4.5, “Importing MySQL NDB Clusters into MySQL Cluster Manager”, for more ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-start-process.html
When the --initial option (short form: -i) is used, the following happens: For a data node, MySQL Cluster Manager starts it with the --initial option, causing the data node to rebuild its file system. start process {[--initial|-i] nodespec | ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-stop-agents.html
Note When IPv6-enabled Windows systems are used as MySQL NDB Cluster hosts under MySQL Cluster Manager, you must reference these hosts using IPv4 addresses. stop agents [[--hosts=host_list] site_name] This command stops one or more MySQL Cluster ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-upgrade-cluster.html
It finishes an upgrade by performing a rolling restart for the cluster, in which data nodes are restarted with the --initial option to have their data file systems rebuilt. upgrade cluster {--package=|-P }package_name [{--nodeid|-n }node_id_list] ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-using-backup-restore-requirements.html
At least one data node in each node group must be running, and there must be sufficient disk space on the node file systems. This section provides information about basic requirements for performing backup and restore operations using MySQL Cluster ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-using-import-cluster-example.html
As discussed previously (see Section 4.5.1, “Importing a Cluster Into MySQL Cluster Manager: Basic Procedure”), importing a standalone or “wild” cluster that was not created with MySQL Cluster Manager into the manager requires the ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-what-is-new.html
MySQL Cluster Manager 8.4 is recommended for use on production systems. MySQL Cluster Manager 8.4 marks the start of a new series of LTS (Long Term Support) releases. The 8.4.X LTS releases will focus on security and bug fixes while the next ...
https://dev.mysql.com/doc/refman/9.7/en/alter-logfile-group.html
(Bug #13116514, Bug #16104705, Bug #62858) On 32-bit systems, the maximum supported value for INITIAL_SIZE is 4294967296 (4 GB). ALTER LOGFILE GROUP logfile_group ADD UNDOFILE 'file_name' [INITIAL_SIZE [=] size] [WAIT] ENGINE [=] engine_name This ...
https://dev.mysql.com/doc/refman/9.7/en/alter-table-problems.html
This is done because InnoDB and these operating systems cannot drop a table that is in use. If you get a duplicate-key error when using ALTER TABLE to change the character set or collation of a character column, the cause is either that the new ...
Displaying 4081 to 4090 of 4186 total results