Timeline for I am very frustrated by problems trying to set up mysql-cluster. There are no service files for NDB daemons
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2023 at 17:17 | answer | added | Mikael Ronström | timeline score: 0 | |
| May 23, 2023 at 12:38 | answer | added | Mauritz Sundell | timeline score: 0 | |
| May 22, 2023 at 21:01 | answer | added | elyograg | timeline score: -3 | |
| May 22, 2023 at 20:57 | comment | added | elyograg | I managed to get a 3-node innodb cluster operational in multi-primary mode. Now I just need to reconfigure all my apps to use the new VIP I have set up instead of localhost. | |
| May 21, 2023 at 18:44 | comment | added | elyograg | I found a way to get rid of that ndbinfo database. | |
| May 21, 2023 at 17:14 | comment | added | elyograg | If I am not going to be using ndb cluster, then I will need help with a problem I've encountered: dba.stackexchange.com/questions/326978/… | |
| May 21, 2023 at 17:04 | comment | added | elyograg | I have never heard of innodb cluster. What I am trying to achieve is a database that won't go down if one of my servers dies. | |
| May 21, 2023 at 8:17 | comment | added | dbdemon | Just checking, are you sure NDB cluster is what you want? For whatever reason, NDB cluster doesn't seem to be a very popular solution, although it does have some very unique features. However, MySQL also has InnoDB cluster which I think is much more popular and somewhat more user-friendly. | |
| May 21, 2023 at 5:31 | comment | added | Rick James | NDB has its own clustering. | |
| May 21, 2023 at 4:04 | comment | added | elyograg | I ran into a problem where the ndb daemons would not start if ipv6 is disabled systemwide. So I had to re-enable a protocol that I am not using. | |
| May 21, 2023 at 4:03 | comment | added | elyograg | Also, the ndb cluster log says this: ``` 2023-05-20 22:01:11 [MgmtSrvr] WARNING -- Unable to allocate nodeid for API at 192.168.217.202. Returned error: 'Connection done from wrong host ip 192.168.217.202.' 2023-05-20 22:01:13 [MgmtSrvr] INFO -- Node 2: Initial start, waiting for 3 to connect, nodes [ all: 2 and 3 connected: 2 no-wait: ] ``` Which is highly frustrating as there is no node 3 in config.ini! It ONLY contains info for this one single host, and that ndbd config is node 2. | |
| May 21, 2023 at 4:00 | comment | added | elyograg | This is VERY frustrating! I have ndb_mgmd and ndbd running. But mysql will NOT start. ``` 2023-05-20 21:59:37 [NdbApi] INFO -- Configuration error: Error: Could not alloc node id at gandalf.elyograg.org:1186: Connection done from wrong host ip 192.168.217.202. ``` | |
| May 21, 2023 at 3:20 | review | Close votes | |||
| Jun 5, 2023 at 3:07 | |||||
| May 21, 2023 at 2:59 | comment | added | elyograg | The existing database server is smeagol.elyograg.org at 192.168.217.200. I want to add a third node to the cluster that will NOT have the data, as a tiebreaker. I am beginning on gandalf.elyograg.org at 192.168.217.202. After I get it running woth all data, I will add sauron, and then add the data. Finally I will bring smeagol into the cluster. | |
| May 21, 2023 at 2:57 | comment | added | elyograg | I finally found a page that had the service files. Created those. Now mysql won't start. Configuration error: Error: Could not alloc node id at gandalf.elyograg.org:1186: Connection done from wrong host ip 192.168.217.202. That IS the correct IP address for this host. | |
| S May 21, 2023 at 2:29 | review | First questions | |||
| May 21, 2023 at 10:35 | |||||
| S May 21, 2023 at 2:29 | history | asked | elyograg | CC BY-SA 4.0 |