Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
> Have you even read that PDF, it documents just that, a MS setup with MySQL I've read many-many pdfs; htmls; readmes etc. without a real working config. Anyway, which PDF do you mention? > Why not M-M? > You have an obsession, you should see a doctor about that. It is not my theory. I got this advice from #mysql-ndb channel. I think I've written it. TIA, Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
> So I guess there are 2 ways for a MS setup with MySQL. OK. And where is a cookbook for setting up M-S config? Why not M-M? I tried to install MySQL Workbench for SLES11 SP1. There are some broken dependencies. :-( Instead of that fact workbench started. (complained about missin SSH tunnel) I wanted to configure RELOAD and SUPER privs. I was surprised I'm not able to do that with workbench! :-( There are just some predefined role. So I have to learn mysql + GRANT commands. Pacemaker (mysql) wrote some lines in messages file about missing privs, like RELOAD and SUPER. Is that the only problem? I don't think so ... I'll check my DMC for mysql parameters ... TIA, Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
> That's what I said - I didn't see it either. > but if you you check the current RA: What do you think about this: http://www.lathiat.net/files/MySQL%20-%20DRBD%20&%20Pacemaker.pdf I can't see if this is a real M-M or M-S setup. TIA, Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
> That's what I said - I didn't see it either. > but if you you check the current RA: OK, sorry. > # crm ra meta mysql|grep ^replica > replication_user (string): MySQL replication user > replication_passwd (string): MySQL replication user password > replication_port (string, [3306]): MySQL replication port Maybe I found this (or not) those parameters in DMC... Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
> http://lmgtfy.com/?q=linbit+mysql+replication OK. I found that webinar. There isn't any "printed" (readable) doc. :-( TIA, Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
> I am pretty sure Linbit announced mysql RA with replication capabilities. > Haven't seen documentation though. Any URL, or anything? Thanks, Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
> Isn't a Multi-Master and DRBD a big no-no? It implies that two MySQL In this situation there isn't Multi-Master setup. It is just a normal single instance mysql process which will be switched by DRBD to active node. TIA, Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
> The mysql RA controls a single MySQL instance and the rest of the HA setup > is done via DRBD Master-Slave resources. OK. Thank you for your help. Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
Hi, > And now (officially) RHCS can also use Pacemaker > http://theclusterguy.clusterlabs.org/post/1551292286 Nice. > Yeah, like I said, Master-Master and Pacemaker without a proper resource > agent will cause issues. Yes. > big problems. Now let me explain this, a 2-node Multi-Master MySQL setup > means setting up every node as both Master and Slave, node 1's Master > replicates asynchronously to node 2's Slave and node 2's Master replicates > asynchronously to node 1's Slave. The replication channels between the two > are not redundant, nor do they recover from failure automatically and you > have to manually set the auto-increment-increment and auto-increment-offset > so that you don't have primary key collisions. Clear. > each server. Looking at how DRBD handles these kinds of things is one way to > go about it, but ... it's a huge task and there are a lot of things that can > go terribly wrong. :-( > So again, for the third time, the problem is not the Multi-Master setup, nor > it is Pacemaker, it's just a very specific use case for which a resource > agent wasn't written. OK. So now almost the only one possibilities is DRBD+MySQL? TIA, Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
Hi, > A MySQL Multi-Master architecture for a 2 node setup brings a lot of > configuration and administration overhead and has no conflict detection or > resolution. Integrating such a setup with Pacemaker only adds to the Yes, I found it. The real story: I want to learn clustering with a 2 node failover cluster. I configured the cluster by DMC (DRBD Management Console). I used the GUI configuring a MySQL service. It was almost unsuccessfull which wasn't a surprise for me. After that I started to read some HowTo, WEB page, etc. for help. I found someone from #mysql-nbd channel who helped me and adviced me using M-M MySQL config but he doesn't know almost anything about Pacemaker (He uses RH cluster). After we did the working M-M config I started pacemaker and I could see MySQL is working. I could connect to the commonIP and I could create a test DB. Everything seemed all right until I put standby the master node (from pacemaker point of view). In that moment mysqld started to "blinking" between working and not working state because pacemaker always restarted the process. In the messages file I clould see some lines about missing privs. (RELOAD and SUPER). So I'm here now. > server. Even the LSB script doesn't handle a Multi-Master setup. You'd have > to write a custom resource agent, and it would probably fit your setup and > your setup alone, meaning it couldn't be widely used for other setups, I > know I had to make some modifications to the mysql resource agent and those > changes were specific to my setup. No, I don't want to write scripts. I'm not a programmer. I just want to try out a new tech for MySQL clustering except MySQL+DRBD.It is clear for me theoretically. The files of mysqld reside on the common dir. which was switched by DRBD. Is that right? > MySQL Cluster is a choice, it could be integrated with Pacemaker, although I Now I don't want MySQL Cluster. I think it is a bigger task for me. > Anyways, this is just to get a feel for what's involved in the process, and > how Pacemaker would fit the picture, at least from my point of view. OK > I would recommend all questions related to MySQL Cluster, Replication, > Multi-Master be directed to the appropriate mailing lists though, and if you As I mentioned I've got an M-M config from #mysql-nbd. The recent problem is MySQL (M-M) + Pacemaker. > want to write a resource agent for a Multi-Master setup, by all means, do > share :) No, I don't want. I'm a beginner both in clustering and MySQL. > Hope this helps. Yes, of course. BTW. If I want to solve the above problem can you help me? Of course with my strict error messages, config files, etc. I "feel" my M-M config is not rock stable (I was able to brake the IO or SQL "channel" between the two mysqld processes) so I don't know whether I want this type of setup. TIA, Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master replica setup
>You're not making sense, first you say MySQL Master-Master, then you >mention master mysqld on clusterB and slave mysqld on clusterA. So, >which one is it: Yes, it is true. If I stop openais and I start mysql without openais the config is M-M (or Multi-Master). When pacemaker starts mysql processes I can see master and slave mysqld text from crm_mon. >- MySQL Master-Master (or Multi-Master) which can be achieved via MySQL >Replication >- MySQL Master-Slave, which can be achieved via MySQL Replication as well I'd like to implement the above. I don't know which one is right for me. Because of M-M MySQL config I think the 1st one is my choice. >- MySQL Master with a DRBD backend (even MySQL docs recommend this type >of setup for some use cases) in which the MySQL instance runs only where >DRBD is primary I think I know this setup and don't want it now. >- MySQL Cluster (nothing to do with Pacemaker, although they can be put >together in a setup) This would be the next test if I have enough time. TIA, Ruzsi ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
