PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-basics.html
NDB Cluster tables are normally stored completely in memory rather than on disk (this is why we refer to NDB Cluster as an in-memory database). This NDB Cluster Connector includes ClusterJ, a high-level database API similar to object-relational ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-importing-data.html
If a data import operation does not complete successfully, for whatever reason, you should be prepared to perform any necessary cleanup including possibly one or more DROP TABLE statements, DROP DATABASE statements, or both. Failing to do so may ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-information-schema-tables.html
Additional statistical and other data about NDB Cluster transactions, operations, threads, blocks, and other aspects of performance can be obtained from the tables in the ndbinfo database. For information about these tables, see Section 21.6.15, ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-install-configuration.html
Since the "world" database takes up # only about 500KB, this should be more than enough for # this example NDB Cluster setup. In this section, we discuss manual configuration of an installed NDB Cluster by creating and editing configuration files.
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-limitations-exclusive-to-cluster.html
The following are limitations specific to the NDB storage engine: Machine architecture. All machines used in the cluster must have the same architecture. That is, all machines hosting nodes must be either big-endian or little-endian, and you cannot ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-mgm-client-commands.html
ENTER SINGLE USER MODE node_id Enters single user mode, whereby only the MySQL server identified by the node ID node_id is permitted to access the database. EXIT SINGLE USER MODE Exits single user mode, enabling all SQL nodes (that is, all running ... In addition to the central configuration file, a cluster may also be controlled through a command-line interface available through the management client ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-locks-per-fragment.html
fq_name is a fully qualified database object name in database/schema/name format, such as test/def/t1 or sys/def/10/b$unique. The locks_per_fragment table provides information about counts of lock claim requests, and the outcomes of these requests ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-memory-per-fragment.html
memory_per_fragment Table: Notes memory_per_fragment Table: Examples The memory_per_fragment table provides information about the usage of memory by individual fragments. See the Notes later in this section to see how you can use this to find out ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-nodes.html
This table contains information on the status of data nodes. For each data node that is running in the cluster, a corresponding row in this table provides the node's node ID, status, and uptime. For nodes that are starting, it also shows the ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-option-tables.html
ndbinfo_offline: Put ndbinfo database into offline mode, in which no rows are returned from tables or views. The following list includes command-line options, system variables, and status variables applicable within mysqld when it is running as an ...