MySQL Forums
Forum List  »  NDB clusters

Re: "Got error 4009 'Cluster Failure' from NDB. Could not acquire global schema lock" and "Could not connect to storage engine"
Posted by: Barnabás Molnár
Date: October 09, 2017 02:25PM

Hello,

I managed to find out the solution.

=========== 1. The ndb_mgm from the MySQL server:

With the MySQL API server repo, I've also installed the "mysql-cluster-community-client" package. So I also installed this to the management node (with the EPEL dependency):

$ rpm -ivh http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-10.noarch.rpm
$ yum install mysql-cluster-community-client

After install I can invoke "ndb-mgm" and also "ndb-mgm -e show" on the management server.

=========== 2. The "Error 4009":

Since it's an Oracle Linux 7.3, I set the Security-Enhanced Linux (SELinux) option to "disabled":

$ vi /etc/selinux/config
SELINUX=disabled

Restarted and started the mysql service:

$ systemctl start mysqld.service

Finally got this:

$ ndb_mgm -e show
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=2 @172.16.1.103 (mysql-5.7.19 ndb-7.5.7, Nodegroup: 0)
id=3 @172.16.1.104 (mysql-5.7.19 ndb-7.5.7, Nodegroup: 0, *)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @172.16.1.101 (mysql-5.7.19 ndb-7.5.7)

[mysqld(API)] 1 node(s)
id=4 @172.16.1.102 (mysql-5.7.19 ndb-7.5.7)

Also managed to create a table with the ndb engine. :)

Options: ReplyQuote




Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.