MySQL NDB Cluster 7.6: Fast Import with ndb_import (no replies)
↧
↧
SQL Node failed to start (no replies)
I'm trying to install SQL cluster. When I deploy the configuration, my management and data nodes start fine, but my SQL will not start.
The error say, Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
I tried first running SQL node on my Management node, then I tried a fresh install on a dedicated SQL node.
I was trying cluster 7.5.9-1 originally, then the 7.6 upgrade came out so I started over with that.
I still have this problem. I didn't get any results searching for it on the forums, so I'm thinking I am just doing it wrong and missing something.
Any ideas?
Thanks,
Chuck
The error say, Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
I tried first running SQL node on my Management node, then I tried a fresh install on a dedicated SQL node.
I was trying cluster 7.5.9-1 originally, then the 7.6 upgrade came out so I started over with that.
I still have this problem. I didn't get any results searching for it on the forums, so I'm thinking I am just doing it wrong and missing something.
Any ideas?
Thanks,
Chuck
↧
MySQL NDB Cluster 7.6: mprovements from NDB wakeup threads (no replies)
↧
Mysql Cluster 7.5 to 7.6 upgrade (no replies)
I tried to upgrade my 7.5 cluster to 7.6 yesterday and couldn't get it to work, forcing a rollback. Are there any simple upgrade instructions available?
In my case, none of the components could communicate with each other. I upgrade one manager (I have two) and nothing connected to it except itself. Then I tried to upgrade one data node and it couldn't connect to the manager. There is probably something wrong with my configuration file, but I have no idea what it might be. If anyone has some simple upgrade instructions, I'd appreciate your sharing them.
In my case, none of the components could communicate with each other. I upgrade one manager (I have two) and nothing connected to it except itself. Then I tried to upgrade one data node and it couldn't connect to the manager. There is probably something wrong with my configuration file, but I have no idea what it might be. If anyone has some simple upgrade instructions, I'd appreciate your sharing them.
↧
MySQL NDB Cluster 7.6: Colocated MySQL Server and NDB data nodes (no replies)
↧
↧
Azure Mysql NDB Cluster (no replies)
I've problem with my Mysql NDB Cluster on Azure VM. I have 2 API Server and 1 Management Server on the same server with first API Server, and 2 Node of data. All servers are using Debian 9 and the version of Mysql Cluster is 7.4.7
I've already setup it on azure with same VNet and using E4s_v3 Plans for both API Server (4 Core CPU and 32GB Memory) and E8s_v3 Plans for both Data Server (8 Core CPU and 64GB Memory)
The problem is:
If I only use 1 API and 1 Data, the query takes 3.xx seconds, but if i run with 1 API and 2 Data, it will take 8.xx - 10.xx seconds
If I query small data it's running fast, but if the table has many records the query is too slow.
Can anyone help me solving my problem? I'm confused about what's wrong with my cluster. In general it can run fast.
Thanks
I've already setup it on azure with same VNet and using E4s_v3 Plans for both API Server (4 Core CPU and 32GB Memory) and E8s_v3 Plans for both Data Server (8 Core CPU and 64GB Memory)
The problem is:
If I only use 1 API and 1 Data, the query takes 3.xx seconds, but if i run with 1 API and 2 Data, it will take 8.xx - 10.xx seconds
If I query small data it's running fast, but if the table has many records the query is too slow.
Can anyone help me solving my problem? I'm confused about what's wrong with my cluster. In general it can run fast.
Thanks
↧
ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes (no replies)
According with Known Limitations of NDB Cluster
**
Column width. Attempting to create an index on an NDB table column whose width is greater than 3072 bytes succeeds, but only the first 3072 bytes are actually used for the index. In such cases, a warning Specified key was too long; max key length is 3072 bytes is issued, and a SHOW CREATE TABLE statement shows the length of the index as 3072.
**
So I'm expecting a warning when I try to create a table with a key on a varchar(2000) column,
but I get an error
ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes
and table is not definetively created
Is there any workaround for that ?
**
Column width. Attempting to create an index on an NDB table column whose width is greater than 3072 bytes succeeds, but only the first 3072 bytes are actually used for the index. In such cases, a warning Specified key was too long; max key length is 3072 bytes is issued, and a SHOW CREATE TABLE statement shows the length of the index as 3072.
**
So I'm expecting a warning when I try to create a table with a key on a varchar(2000) column,
but I get an error
ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes
and table is not definetively created
Is there any workaround for that ?
↧
MCMD Agent Trouble (no replies)
After a crash (single cluster test node) mcmd agent doesn0t start anymore.
Seems as something being corrupt.
Tried reinstalling the agent, but still doesn't start.
Is there a way to ripristinate di agent ?
Without agent, could I try to start my cluster ?
****
Error log
root@mymcmmgm:~# /etc/init.d/mcmd status -l
● mcmd.service - LSB: MySQL Cluster Manager
Loaded: loaded (/etc/init.d/mcmd; bad; vendor preset: enabled)
Active: active (exited) since Thu 2018-06-07 17:42:07 CEST; 12min ago
Docs: man:systemd-sysv-generator(8)
Process: 1170 ExecStart=/etc/init.d/mcmd start (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 0B
CPU: 0
Jun 07 17:42:05 mymcmmgm mcmd[1170]: Starting MySQL Cluster Manager service...
Jun 07 17:42:05 mymcmmgm su[1251]: Successful su for mysqladm by root
Jun 07 17:42:05 mymcmmgm su[1251]: + ??? root:mysqladm
Jun 07 17:42:05 mymcmmgm su[1251]: pam_unix(su:session): session opened for user mysqladm by (uid=0)
Jun 07 17:42:07 mymcmmgm mcmd[1170]: cat: /tmp/xfile.1170: No such file or directory
Jun 07 17:42:07 mymcmmgm mcmd[1170]: /etc/init.d/mcmd: 249: test: -eq: unexpected operator
Jun 07 17:42:07 mymcmmgm mcmd[1170]: * MySQL Cluster Manager failed to start.
Jun 07 17:42:07 mymcmmgm systemd[1]: Started LSB: MySQL Cluster Manager.
Jun 07 17:42:07 mymcmmgm mcmd[1170]: **
Jun 07 17:42:07 mymcmmgm mcmd[1170]: ERROR:/export/home/pb2/build/sb_0-26763700-1516206058.81/cluster-manager-1.4.5-release-export-12431048/plugins/manage...d: (s != 0)
Hint: Some lines were ellipsized, use -l to show in full.
***
Seems as something being corrupt.
Tried reinstalling the agent, but still doesn't start.
Is there a way to ripristinate di agent ?
Without agent, could I try to start my cluster ?
****
Error log
root@mymcmmgm:~# /etc/init.d/mcmd status -l
● mcmd.service - LSB: MySQL Cluster Manager
Loaded: loaded (/etc/init.d/mcmd; bad; vendor preset: enabled)
Active: active (exited) since Thu 2018-06-07 17:42:07 CEST; 12min ago
Docs: man:systemd-sysv-generator(8)
Process: 1170 ExecStart=/etc/init.d/mcmd start (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 0B
CPU: 0
Jun 07 17:42:05 mymcmmgm mcmd[1170]: Starting MySQL Cluster Manager service...
Jun 07 17:42:05 mymcmmgm su[1251]: Successful su for mysqladm by root
Jun 07 17:42:05 mymcmmgm su[1251]: + ??? root:mysqladm
Jun 07 17:42:05 mymcmmgm su[1251]: pam_unix(su:session): session opened for user mysqladm by (uid=0)
Jun 07 17:42:07 mymcmmgm mcmd[1170]: cat: /tmp/xfile.1170: No such file or directory
Jun 07 17:42:07 mymcmmgm mcmd[1170]: /etc/init.d/mcmd: 249: test: -eq: unexpected operator
Jun 07 17:42:07 mymcmmgm mcmd[1170]: * MySQL Cluster Manager failed to start.
Jun 07 17:42:07 mymcmmgm systemd[1]: Started LSB: MySQL Cluster Manager.
Jun 07 17:42:07 mymcmmgm mcmd[1170]: **
Jun 07 17:42:07 mymcmmgm mcmd[1170]: ERROR:/export/home/pb2/build/sb_0-26763700-1516206058.81/cluster-manager-1.4.5-release-export-12431048/plugins/manage...d: (s != 0)
Hint: Some lines were ellipsized, use -l to show in full.
***
↧
MySQL NDB Cluster 7.6: Benchmarking Read Backup (no replies)
↧
↧
MySQL NDB Cluster 7.6: Thread Pool (no replies)
↧
MySQL NDB Cluster 7.6: Impact of sharding on query performance (no replies)
↧
MySQL NDB Cluster 7.6: Benchmark of new cloud feature (no replies)
↧
Auto installer stuck at "Starting node 2 (ndbmtd)" with 29% (no replies)
Trying to install Cluster 7.6.6 across (3) RHEL7 servers (1 mgmt/SQL and 2 data nodes). I used "web application" and "low" as the choices.
I started the cluster, but the progress bar has been at 29% for over 3 hours. Do I sit and wait? Or where do I look to get more details?
Here is the output of ndb_mgm:
ndb_mgm> SHOW
Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=1 @10.84.2.11 (mysql-5.7.22 ndb-7.6.6, starting, Nodegroup: 0)
id=2 @10.84.2.13 (mysql-5.7.22 ndb-7.6.6, starting, Nodegroup: 0)
[ndb_mgmd(MGM)] 1 node(s)
id=49 @10.84.2.12 (mysql-5.7.22 ndb-7.6.6)
[mysqld(API)] 5 node(s)
id=53 (not connected, accepting connect from 10.84.2.12)
id=54 (not connected, accepting connect from 10.84.2.12)
id=231 (not connected, accepting connect from 10.84.2.12)
id=232 (not connected, accepting connect from 10.84.2.12)
id=233 (not connected, accepting connect from 10.84.2.12)
Thank you,
Brian
I started the cluster, but the progress bar has been at 29% for over 3 hours. Do I sit and wait? Or where do I look to get more details?
Here is the output of ndb_mgm:
ndb_mgm> SHOW
Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=1 @10.84.2.11 (mysql-5.7.22 ndb-7.6.6, starting, Nodegroup: 0)
id=2 @10.84.2.13 (mysql-5.7.22 ndb-7.6.6, starting, Nodegroup: 0)
[ndb_mgmd(MGM)] 1 node(s)
id=49 @10.84.2.12 (mysql-5.7.22 ndb-7.6.6)
[mysqld(API)] 5 node(s)
id=53 (not connected, accepting connect from 10.84.2.12)
id=54 (not connected, accepting connect from 10.84.2.12)
id=231 (not connected, accepting connect from 10.84.2.12)
id=232 (not connected, accepting connect from 10.84.2.12)
id=233 (not connected, accepting connect from 10.84.2.12)
Thank you,
Brian
↧
↧
MySQL NDB Cluster 7.6: Node restart improvements (no replies)
↧
SQL node 1 not starting - secure-file-priv set to NULL and Fatal error... find out how to run mysqld as root! (no replies)
I'm using MySQL Cluster 7.6.6 with the Auto Installer on RHEL 7. The cluster consists of 1 management node and 2 data nodes. When I start the cluster, the management node starts, followed by the 2 data nodes. But then I get the following error when starting SQL node 1:
Command `nohup /usr/local/mysql/bin/mysqld --defaults-file=/home/administrator/cluster2/53/my.cnf' exited with 1:
nohup: appending output to ‘nohup.out’
2018-06-13T16:19:38.456883Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-06-13T16:19:38.456971Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2018-06-13T16:19:38.456997Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.22-ndb-7.6.6-cluster-gpl) starting as process 16711 ...
2018-06-13T16:19:38.459812Z 0 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
2018-06-13T16:19:38.459841Z 0 [ERROR] Aborting
2018-06-13T16:19:38.459860Z 0 [Note] Binlog end
2018-06-13T16:19:38.459906Z 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
I stopped the cluster, killed any remaining mysqld processes, and got the same error when starting the cluster. Do I need to go back and define parameters?
I feel like I am SO close to getting the cluster started!
Thank you,
Brian
Command `nohup /usr/local/mysql/bin/mysqld --defaults-file=/home/administrator/cluster2/53/my.cnf' exited with 1:
nohup: appending output to ‘nohup.out’
2018-06-13T16:19:38.456883Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-06-13T16:19:38.456971Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2018-06-13T16:19:38.456997Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.22-ndb-7.6.6-cluster-gpl) starting as process 16711 ...
2018-06-13T16:19:38.459812Z 0 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
2018-06-13T16:19:38.459841Z 0 [ERROR] Aborting
2018-06-13T16:19:38.459860Z 0 [Note] Binlog end
2018-06-13T16:19:38.459906Z 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
I stopped the cluster, killed any remaining mysqld processes, and got the same error when starting the cluster. Do I need to go back and define parameters?
I feel like I am SO close to getting the cluster started!
Thank you,
Brian
↧
ndb cluster 7.5 SQL node start failed (no replies)
Hi, due to the disk space full, the redo log files corrupted.
Executed "ndbmt --initial" in the Failed data node, it can solved the issues.
But I cannot start the sql node in the following sql log.
Anyone can help would be appreciate, thanks.
2018-06-19T18:50:16.409943+08:00 0 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mysql/user.frm'
2018-06-19T18:50:16.410153+08:00 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
SQL Node - mysqld.log
---------------------
2018-06-19T18:50:13.976967+08:00 0 [Note] /usr/sbin/mysqld (mysqld 5.7.21-ndb-7.5.9-cluster-gpl-log) starting as process 16106 ...
2018-06-19T18:50:13.990127+08:00 0 [Note] InnoDB: PUNCH HOLE support available
2018-06-19T18:50:13.990408+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-06-19T18:50:13.990470+08:00 0 [Note] InnoDB: Uses event mutexes
2018-06-19T18:50:13.990520+08:00 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-06-19T18:50:13.990564+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-19T18:50:13.990606+08:00 0 [Note] InnoDB: Using Linux native AIO
2018-06-19T18:50:13.994764+08:00 0 [Note] InnoDB: Number of pools: 1
2018-06-19T18:50:13.995568+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2018-06-19T18:50:14.002428+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-06-19T18:50:14.043675+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2018-06-19T18:50:14.051646+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-06-19T18:50:14.068756+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-19T18:50:14.262074+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-06-19T18:50:14.262665+08:00 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-06-19T18:50:14.507610+08:00 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-06-19T18:50:14.515841+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-06-19T18:50:14.516291+08:00 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-06-19T18:50:14.522487+08:00 0 [Note] InnoDB: Waiting for purge to start
2018-06-19T18:50:14.573316+08:00 0 [Note] InnoDB: 5.7.21 started; log sequence number 3054184
2018-06-19T18:50:14.574026+08:00 0 [Note] InnoDB: Loading buffer pool(s) from /data/mysql/ib_buffer_pool
2018-06-19T18:50:14.576979+08:00 0 [Note] Plugin 'FEDERATED' is disabled.
2018-06-19T18:50:14.581606+08:00 0 [Note] InnoDB: Buffer pool(s) load completed at 180619 18:50:14
2018-06-19T18:50:14.829960+08:00 0 [Note] NDB: NodeID is 4, management server '192.168.125.224:1186'
2018-06-19T18:50:15.231490+08:00 0 [Note] NDB[0]: NodeID: 4, all storage nodes connected
2018-06-19T18:50:15.231663+08:00 0 [Warning] NDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by slave mysqlds
2018-06-19T18:50:15.232276+08:00 0 [Note] NDB Binlog: Starting...
2018-06-19T18:50:15.232475+08:00 0 [Note] NDB Util: Starting...
2018-06-19T18:50:15.232502+08:00 1 [Note] NDB Binlog: Started
2018-06-19T18:50:15.232668+08:00 1 [Note] NDB Binlog: Setting up
2018-06-19T18:50:15.232739+08:00 2 [Note] NDB Util: Wait for server start completed
2018-06-19T18:50:15.232958+08:00 0 [Note] NDB Index Stat: Starting...
2018-06-19T18:50:15.233042+08:00 1 [Note] NDB Binlog: Created schema Ndb object, reference: 0x80040004, name: 'Ndb Binlog schema change monitoring'
2018-06-19T18:50:15.233043+08:00 0 [Note] NDB Index Stat: Wait for server start completed
2018-06-19T18:50:15.233620+08:00 1 [Note] NDB Binlog: Created injector Ndb object, reference: 0x80050004, name: 'Ndb Binlog data change monitoring'
2018-06-19T18:50:15.233705+08:00 1 [Note] NDB Binlog: Setup completed
2018-06-19T18:50:15.233741+08:00 1 [Note] NDB Binlog: Wait for server start completed
2018-06-19T18:50:15.480913+08:00 0 [Note] Server hostname (bind-address): '*'; port: 3306
2018-06-19T18:50:15.481078+08:00 0 [Note] IPv6 is available.
2018-06-19T18:50:15.481175+08:00 0 [Note] - '::' resolves to '::';
2018-06-19T18:50:15.481344+08:00 0 [Note] Server socket created on IP: '::'.
2018-06-19T18:50:16.409943+08:00 0 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mysql/user.frm'
2018-06-19T18:50:16.410153+08:00 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
2018-06-19T18:50:16.410683+08:00 0 [ERROR] Aborting
MGM Node - mysqld.log
---------------------
2018-06-19 18:50:14 [MgmtSrvr] INFO -- Alloc node id 4 succeeded
2018-06-19 18:50:14 [MgmtSrvr] INFO -- Nodeid 4 allocated for API at 192.168.125.135
2018-06-19 18:50:14 [MgmtSrvr] INFO -- Node 4: mysqld --server-id=0
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 2: Node 4 Connected
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 3: Node 4 Connected
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 2: Node 4: API mysql-5.7.21 ndb-7.5.9
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 3: Node 4: API mysql-5.7.21 ndb-7.5.9
2018-06-19 18:50:19 [MgmtSrvr] ALERT -- Node 3: Node 4 Disconnected
2018-06-19 18:50:19 [MgmtSrvr] INFO -- Node 2: Communication to Node 4 closed
2018-06-19 18:50:19 [MgmtSrvr] INFO -- Node 3: Communication to Node 4 closed
2018-06-19 18:50:19 [MgmtSrvr] ALERT -- Node 2: Node 4 Disconnected
2018-06-19 18:50:23 [MgmtSrvr] INFO -- Node 2: Communication to Node 4 opened
2018-06-19 18:50:23 [MgmtSrvr] INFO -- Node 3: Communication to Node 4 opened
Executed "ndbmt --initial" in the Failed data node, it can solved the issues.
But I cannot start the sql node in the following sql log.
Anyone can help would be appreciate, thanks.
2018-06-19T18:50:16.409943+08:00 0 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mysql/user.frm'
2018-06-19T18:50:16.410153+08:00 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
SQL Node - mysqld.log
---------------------
2018-06-19T18:50:13.976967+08:00 0 [Note] /usr/sbin/mysqld (mysqld 5.7.21-ndb-7.5.9-cluster-gpl-log) starting as process 16106 ...
2018-06-19T18:50:13.990127+08:00 0 [Note] InnoDB: PUNCH HOLE support available
2018-06-19T18:50:13.990408+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-06-19T18:50:13.990470+08:00 0 [Note] InnoDB: Uses event mutexes
2018-06-19T18:50:13.990520+08:00 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-06-19T18:50:13.990564+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-19T18:50:13.990606+08:00 0 [Note] InnoDB: Using Linux native AIO
2018-06-19T18:50:13.994764+08:00 0 [Note] InnoDB: Number of pools: 1
2018-06-19T18:50:13.995568+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2018-06-19T18:50:14.002428+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-06-19T18:50:14.043675+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2018-06-19T18:50:14.051646+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-06-19T18:50:14.068756+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-19T18:50:14.262074+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-06-19T18:50:14.262665+08:00 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-06-19T18:50:14.507610+08:00 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-06-19T18:50:14.515841+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-06-19T18:50:14.516291+08:00 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-06-19T18:50:14.522487+08:00 0 [Note] InnoDB: Waiting for purge to start
2018-06-19T18:50:14.573316+08:00 0 [Note] InnoDB: 5.7.21 started; log sequence number 3054184
2018-06-19T18:50:14.574026+08:00 0 [Note] InnoDB: Loading buffer pool(s) from /data/mysql/ib_buffer_pool
2018-06-19T18:50:14.576979+08:00 0 [Note] Plugin 'FEDERATED' is disabled.
2018-06-19T18:50:14.581606+08:00 0 [Note] InnoDB: Buffer pool(s) load completed at 180619 18:50:14
2018-06-19T18:50:14.829960+08:00 0 [Note] NDB: NodeID is 4, management server '192.168.125.224:1186'
2018-06-19T18:50:15.231490+08:00 0 [Note] NDB[0]: NodeID: 4, all storage nodes connected
2018-06-19T18:50:15.231663+08:00 0 [Warning] NDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by slave mysqlds
2018-06-19T18:50:15.232276+08:00 0 [Note] NDB Binlog: Starting...
2018-06-19T18:50:15.232475+08:00 0 [Note] NDB Util: Starting...
2018-06-19T18:50:15.232502+08:00 1 [Note] NDB Binlog: Started
2018-06-19T18:50:15.232668+08:00 1 [Note] NDB Binlog: Setting up
2018-06-19T18:50:15.232739+08:00 2 [Note] NDB Util: Wait for server start completed
2018-06-19T18:50:15.232958+08:00 0 [Note] NDB Index Stat: Starting...
2018-06-19T18:50:15.233042+08:00 1 [Note] NDB Binlog: Created schema Ndb object, reference: 0x80040004, name: 'Ndb Binlog schema change monitoring'
2018-06-19T18:50:15.233043+08:00 0 [Note] NDB Index Stat: Wait for server start completed
2018-06-19T18:50:15.233620+08:00 1 [Note] NDB Binlog: Created injector Ndb object, reference: 0x80050004, name: 'Ndb Binlog data change monitoring'
2018-06-19T18:50:15.233705+08:00 1 [Note] NDB Binlog: Setup completed
2018-06-19T18:50:15.233741+08:00 1 [Note] NDB Binlog: Wait for server start completed
2018-06-19T18:50:15.480913+08:00 0 [Note] Server hostname (bind-address): '*'; port: 3306
2018-06-19T18:50:15.481078+08:00 0 [Note] IPv6 is available.
2018-06-19T18:50:15.481175+08:00 0 [Note] - '::' resolves to '::';
2018-06-19T18:50:15.481344+08:00 0 [Note] Server socket created on IP: '::'.
2018-06-19T18:50:16.409943+08:00 0 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mysql/user.frm'
2018-06-19T18:50:16.410153+08:00 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
2018-06-19T18:50:16.410683+08:00 0 [ERROR] Aborting
MGM Node - mysqld.log
---------------------
2018-06-19 18:50:14 [MgmtSrvr] INFO -- Alloc node id 4 succeeded
2018-06-19 18:50:14 [MgmtSrvr] INFO -- Nodeid 4 allocated for API at 192.168.125.135
2018-06-19 18:50:14 [MgmtSrvr] INFO -- Node 4: mysqld --server-id=0
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 2: Node 4 Connected
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 3: Node 4 Connected
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 2: Node 4: API mysql-5.7.21 ndb-7.5.9
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 3: Node 4: API mysql-5.7.21 ndb-7.5.9
2018-06-19 18:50:19 [MgmtSrvr] ALERT -- Node 3: Node 4 Disconnected
2018-06-19 18:50:19 [MgmtSrvr] INFO -- Node 2: Communication to Node 4 closed
2018-06-19 18:50:19 [MgmtSrvr] INFO -- Node 3: Communication to Node 4 closed
2018-06-19 18:50:19 [MgmtSrvr] ALERT -- Node 2: Node 4 Disconnected
2018-06-19 18:50:23 [MgmtSrvr] INFO -- Node 2: Communication to Node 4 opened
2018-06-19 18:50:23 [MgmtSrvr] INFO -- Node 3: Communication to Node 4 opened
↧
Recommendation for running a MySQL cluster on 3 servers (no replies)
I have created a MySQL Cluster across 3 physical servers, but I read a post that leads me to worry that I did not set it up properly... (that a failure of 1 server will cause the cluster to shutdown)
server1:
management node 1
data node 1
server2:
management node 2
sql node 1
server3:
sql node 2
data node 2
This is what I see from server1:
$ ndb_mgm -e SHOW
Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=1 @127.0.0.1 (mysql-5.7.22 ndb-7.6.6, Nodegroup: 0, *)
id=2 @10.84.2.13 (mysql-5.7.22 ndb-7.6.6, Nodegroup: 0)
[ndb_mgmd(MGM)] 2 node(s)
id=101 @127.0.0.1 (mysql-5.7.22 ndb-7.6.6)
id=102 @10.84.2.12 (mysql-5.7.22 ndb-7.6.6)
[mysqld(API)] 5 node(s)
id=53 @10.84.2.12 (mysql-5.7.22 ndb-7.6.6)
id=54 @10.84.2.13 (mysql-5.7.22 ndb-7.6.6)
id=231 (not connected, accepting connect from 10.84.2.11)
id=232 (not connected, accepting connect from 10.84.2.12)
id=233 (not connected, accepting connect from 10.84.2.13)
Thank you,
Brian
server1:
management node 1
data node 1
server2:
management node 2
sql node 1
server3:
sql node 2
data node 2
This is what I see from server1:
$ ndb_mgm -e SHOW
Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=1 @127.0.0.1 (mysql-5.7.22 ndb-7.6.6, Nodegroup: 0, *)
id=2 @10.84.2.13 (mysql-5.7.22 ndb-7.6.6, Nodegroup: 0)
[ndb_mgmd(MGM)] 2 node(s)
id=101 @127.0.0.1 (mysql-5.7.22 ndb-7.6.6)
id=102 @10.84.2.12 (mysql-5.7.22 ndb-7.6.6)
[mysqld(API)] 5 node(s)
id=53 @10.84.2.12 (mysql-5.7.22 ndb-7.6.6)
id=54 @10.84.2.13 (mysql-5.7.22 ndb-7.6.6)
id=231 (not connected, accepting connect from 10.84.2.11)
id=232 (not connected, accepting connect from 10.84.2.12)
id=233 (not connected, accepting connect from 10.84.2.13)
Thank you,
Brian
↧
↧
Ndb cluster hit the row size limit 14000 bytes (no replies)
Hi
Ndb cluster 7.5.9 hit the row size limit 14000 bytes as we wanna to store varchar(2000), any work around solution or store in disk object tablespace can solve?
Anyone can help would be appreciated, many thanks.
Ndb cluster 7.5.9 hit the row size limit 14000 bytes as we wanna to store varchar(2000), any work around solution or store in disk object tablespace can solve?
Anyone can help would be appreciated, many thanks.
↧
How to connect the SQL node to the specified data node (no replies)
4 data nodes, 2 groups, 2 replicas, how does a SQL node connect only the specified two data nodes instead of connecting all the data nodes?
↧
Warning | 1296 | Got error 904 'Out of fragment records (increase MaxNoOfOrderedIndexes)' from NDB (no replies)
when i am going to import tables(after change the engine innodb to ndbcluster) in sql node only 34 tables are importing after that i am facing problem with error like Warning | 1296 | Got error 904 'Out of fragment records (increase MaxNoOfOrderedIndexes)' from NDB
↧
