Search Results
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-delete-package.html
If you attempt to use the unregistered package in a create cluster command, the command fails, as shown here: mcm> create cluster --package=mypackage > --processhosts=ndb_mgmd@tonfisk,ndbd@grindval,ndbd@flundra,mysqld@tonfisk mycluster; ERROR 4001 ... delete package [{--hosts=|-h }host_list] package_name host_list: host[,host[,...]] This command is used to unregister a ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-eventual-consistency.html
While an agent might be lagging behind, the guaranteed eventual consistency means that, unless prevented by a network error or some other issues, any lagging agent will eventually catch up with the other agents, and all agents will eventually get a ... MySQL Cluster Manager guarantees eventual consistency among agents, meaning that: Any message communicated among agents is either delivered or not delivered to ALL agents (instead of delivered to some and missed by ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-get.html
get [--include-defaults|-d] [--all] [filter_specification_list] cluster_name filter_specification_list: filter_specification[,filter_specification][,...] filter_specification: [attribute_name][:process_specification][+process_specification]] ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-import-cluster.html
It is recommended that you use the two options separately: perform the checks with the --dryrun option only, and once the only errors observed are with the angel processes, run import cluster again with the --remove-angel option only to complete the ... import cluster [--dryrun|-y] [--remove-angel] cluster_name This command imports a MySQL NDB Cluster created independently of MySQL Cluster Manager into a cluster named cluster_name that has been created in MySQL Cluster ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-issues-mysql-server.html
For example, the command set loose-skip-innodb:mysqld=true mycluster; fails with the error No such config variable loose-skip-innodb for process mysqld. The limitations described in this section relate to functionality in the MySQL Server that is ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-start-process.html
You cannot use this command to start a mysqld process in a stopped or unavailable cluster—trying to do so will cause an error. start process {[--initial|-i] nodespec | --added} cluster_name nodespec: {nodetype | process_id_list} process_id_list: ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-stop-cluster.html
See Section 5.4.1, “The create cluster Command”, and Section 4.5, “Importing MySQL NDB Clusters into MySQL Cluster Manager”, for more information.
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-using-backup-restore-simple.html
To create a backup, use the backup cluster command with the name of the cluster as an argument, similar to what is shown here: mcm> backup cluster mycluster; +-------------------------------+ | Command result | +-------------------------------+ | ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-using-import-cluster-create-configure.html
Once this is done, we modify the target cluster's configuration until it matches that of the wild cluster that we want to import. At a later point in the example, we also show how to test the configuration in a dry run before attempting to perform ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-using-import-cluster-verify-pid-files.html
You must verify that each process in the wild cluster has a valid PID file. For purposes of this discussion, a valid PID file has the following characteristics: The file name is in the format of ndb_node_id.pid, where node_id is the node ID used ...