- Original Message -
> From: "Martin Gainty"
> Subject: Proxy / connected failover question
> > >> I'm not usually an advocate of MySQL Proxy and the like, but I'm stuck
> > >> with one shitty application that utterly breaks whenever th
> CC: vegiv...@tuxera.be; mysql@lists.mysql.com
> From: wagnerbianch...@gmail.com
> Subject: Re: Proxy / connected failover question
> Date: Wed, 9 Jul 2014 08:31:05 -0300
> To: walterh...@olindata.com
>
> I like HAProxy as well as it simplifies many of the things you seem
anyway; I'll
>> have to see wether or not that's going to be an issue during testing.
>>
>> I have two main questions:
>> * am I remembering right that MySQL Proxy provides transparent failover ?
>> * Are there other contenders in the same field, or alternate
I'll
> have to see wether or not that's going to be an issue during testing.
>
> I have two main questions:
> * am I remembering right that MySQL Proxy provides transparent failover ?
> * Are there other contenders in the same field, or alternate solutions ?
>
> Ideally I&
Hi Johan,
I wanted to love mysql-proxy for so many years, so I understand you :)
> I have two main questions:
> * am I remembering right that MySQL Proxy provides transparent failover ?
>
You need to use/create a lua failover script, I've never seen or tried one.
What kept me
contraption to not notice it's connection
has switched.
I am aware that connection state etc is likely to be lost anyway; I'll have to
see wether or not that's going to be an issue during testing.
I have two main questions:
* am I remembering right that MySQL Proxy provides
:26 pm Johan De Meersman wrote:
> - Original Message -
>
> > From: "Mike Diehl"
> >
> > I'm about to set master-master replication and would like to get
> > recommendations as to the best method for getting my applications to
> > failove
- Original Message -
> From: "Mike Diehl"
>
> I'm about to set master-master replication and would like to get
> recommendations as to the best method for getting my applications to
> failover when needed.
I should already be in bed, but as a very
Hi all,
I'm about to set master-master replication and would like to get
recommendations as to the best method for getting my applications to failover
when needed.
Here are my options, so far:
MySQL Proxy http://forge.mysql.com/wiki/MySQL_Proxy
This seems like the obvious choice, but I&#
On Tue, Oct 19, 2010 at 19:06, John Daisley wrote:
> You may also want to take a look at MySQL MMM which makes use of
> Active/passive masters to makes MySQL failover very simple.
+1 We could not do much of our daily work without MMM. It makes
the whole HA/Failover thing a breeze. We h
:machi...@rdc.co.za]
>Sent: Tuesday, October 19, 2010 5:15 AM
>To: mysql mailing list
>Subject: Failover on master/slave replication
>
>Good day all
>
>I am hoping someone has had some experience in this to assist
>me.
>
>I have been going through lots of foru
You may also want to take a look at MySQL MMM which makes use of
Active/passive masters to makes MySQL failover very simple.
On 19 October 2010 11:45, Johan De Meersman wrote:
> That's pretty much it, indeed. You need to make absolutely sure that no
> more
> connections can be m
That's pretty much it, indeed. You need to make absolutely sure that no more
connections can be made to the old, broken master, though - even if you have
to physically pull the network or power cable. Failover services refer to
this as STONITH: Shoot The Other Node In The Head.
Don't
to do anything (except be
sure that replication is off). That is, tell your apps etc to use the
slave IP/hostname, change the slave server IP to that of the master or
update DNS so that all connections are made to the slave instead of
the master.
To reinstate the master after a failover
Good day all
I am hoping someone has had some experience in this to assist
me.
I have been going through lots of forums and documentation and
can find a lot of information on how to setup a master/slave replication
on MySQL.
The question I have however is how do you fail
Hi Imran,
Have a look at MySQL MMM for Multi-Master Replication failover. The project
is currently in refurbishment when ti comes to having a home, but you can
start by looking at : http://mysql-mmm.org for information.
This project is made for exactly what you want to achieve: Having multiple
I want to fix a replication issue with a 2-node cluster (one active,
one passive) that is using Heartbeat for failover. The nodes are in
Master-Master configuration (that is, each is the slave and master of
the other).
I have several other hosts that are replication slaves from the active
node
n again) Our ES4
> server contains shared data that is not controlled through cvs. Our two
> ES3 servers contain our website which is controlled through cvs. Both
> our ES3 servers have mysql. The mysql dbs have our username/password
> (and other) information.
>
> We are in the pr
rs contain our website which is controlled through cvs. Both
our ES3 servers have mysql. The mysql dbs have our username/password
(and other) information.
We are in the process of setting up ip failover using a dns round-robin.
My concern about keeping the mysql dbs on the ES3 servers is the
poss
Kevin Burton wrote:
Gleb Paharenko wrote:
Hello.
I don't remember solutions with keepalived, but this issue is
discussed in the list from time to time. Search in archives at:
http://lists.mysql.com/mysql
Someone should create a wiki page on this subject... its a commonly
asked question...
Kev
Gleb Paharenko wrote:
Hello.
I don't remember solutions with keepalived, but this issue is
discussed in the list from time to time. Search in archives at:
http://lists.mysql.com/mysql
Someone should create a wiki page on this subject... its a commonly
asked question...
Kevin
--
Use Rojo (RSS/
SQL replication with
> dynamic failover, preferably using keepalived (http://www.keepalived.org)?
>
> What we need is a system so that if the master server dies one of the
> slaves will become the master.
>
> It looks like it should be possible, and merely involves
Hi,
Anybody have any experience with setting up MySQL replication with
dynamic failover, preferably using keepalived (http://www.keepalived.org)?
What we need is a system so that if the master server dies one of the
slaves will become the master.
It looks like it should be possible, and merely
On Thu, 3 Mar 2005, Olivier Kaloudoff wrote:
> Hello,
>
> we're working on a two node setup to achieve high
> availability using 4.1.8;
>
> we first setup both servers with --bin-log, and only
> the slave server (db1) with --log-slave-updates. (binary logfile
> name is "master" on bot
Hello,
we're working on a two node setup to achieve high
availability using 4.1.8;
we first setup both servers with --bin-log, and only
the slave server (db1) with --log-slave-updates. (binary logfile
name is "master" on both server)
replication from db0 to db1 runs smoothly
The way I've found to be the most 100% safe for me is to get my failover
system to completely stop the failed master. The new master will stay master
until I fix the problem on the failed, there's no further interventions from
my failover system. Then I repair, resync etc, then I p
I have been reading and researching ways to create a failover system for
our MySQL databases that require as little intervention as possible.
However I am having trouble coming up with a way to get the system back
into a stable state after a failover has occurred and the main master has
been
I have checked the TODO list and cannot find any mention of an automatic
failover feature. In Jeremy's High Performance MySQL book, he makes mention
of it being some sort of a plan for the future. Also, in a section of the
manual centered on replication, there is also mention of it. I
Matt Sturtz wrote:
Yes, the clients (appearently) read to the end of the previous file, and
then sit there, while the server is writing to a new file.
I was thinking this had to do with the "unclean" shutdown of MySQL--
perhapps it's something else.
It might, but it is a bug anyway. The whole idea
Yes, the clients (appearently) read to the end of the previous file, and
then sit there, while the server is writing to a new file.
I was thinking this had to do with the "unclean" shutdown of MySQL--
perhapps it's something else.
-Matt-
> Matt Sturtz wrote:
>> Hello--
>>
>> We're using Red Hat
Matt Sturtz wrote:
Hello--
We're using Red Hat's cluster manager (RH AS 2.1, MySQL 4.0.16 RPM). Due
to a problem within the cluster software that we're working on with Red
Hat, the cluster fails over from one node to the other sometimes when it
shouldn't (one node will reboot, services will fail
Hello--
We're using Red Hat's cluster manager (RH AS 2.1, MySQL 4.0.16 RPM). Due
to a problem within the cluster software that we're working on with Red
Hat, the cluster fails over from one node to the other sometimes when it
shouldn't (one node will reboot, services will fail over-- at this poin
ata access or update.
- All the data written to the Primary database is
being replicated onto the Secondary database via MySQL
Replication.
FAILOVER SCENARIO:
- Primary becomes unavailable. Primary is DOWN.
- The Heartbeat Mgr on the Secondary becomes aware
and makes the Secondary ACTIVE.
On Wed, Feb 18, 2004 at 02:18:59PM -0800, Gowtham Jayaram wrote:
> Hello all:
>
> I am looking into the Replication issues that surface in a Failover
> scenario (Master goes down and Slave is pressed into service).
>
> I understand that it is critical for the Master and Sl
Hello all:
I am looking into the Replication issues that surface
in a Failover scenario (Master goes down and Slave is
pressed into service).
I understand that it is critical for the Master and
Slave databases to mirror each other for Replication
to work. I am trying to ensure that this
Hi,
I have a question regarding failover in a master/slave replication
enviroment. Any advice/comments/links to materials are very much
appreciated!
Setup: Server A is Master, B is Slave. Upon A's failure, all clients
requests are routed to B.
Question: Upon recovery of A, how do I configu
I'm thinking about doing this:
Setting up 2 mysql servers each replicating to the other (each a slave
of the other).
Code the connect/j connection creation to try one server on connect. If
it fails, connect to the other server.
Both servers are writeable, but my code is never talking to more than
s. What I'd like to do is use
>keepalived to failover to a secondary machine if the first machine dies.
>The question is, if the first machine dies and the second machine were to
>startup mysql server would the database be corrupt? Is this even
>possible?
Try http://linux-ha
Hi,
(mysql 3.23.49, debian linux 2.4.18)
I am looking at running a program called keepalived so I can monitor
the availability of my mysql server. Data is stored on a NetApp filers so
its readily available to multiple machines. What I'd like to do is use
keepalived to failover to a seco
are at the bottom of this mail
as I sent them to the
last person who asked.
Best to all,
Steve Rapaport.
Ronnie Garcia wrote:
Hi Steve,
I just found your post about failover and mysql on google (
http://groups.google.com/groups?hl=fr&threadm=a11dqg%242slq%241%40FreeBSD.csie.NCTU.edu.tw&rnum=
on setup. I don't recommend it yet, because if you use a
circular replication setup, and something goes wrong (which things do
sometimes), it's nearly impossible to be sure you have recovered properly.
Instead I recommend for now keeping the same master, and writing your
own failover scr
;d like to store it in the database.
Unfortunately, this means there has to be a write every time a member
or staff look at a statement.
I've been playing with some ideas on how to have the slaves arbitrate
amongst themselves and take over as master in case the master does go
down. I've al
Steve,
There isn't an automated way, but you can at least semi-script this. To
switch the slave to the master after the old master has failed and then
brought back up do this:
Shut down MySQL on the NEW master
mysqladmin -u root -p shutdown
Snapshot all the data on your NEW master server.
e got replication on 2 machines with a one-way failover setup:
> Master fails, slave takes over.
>
> Now the slave has been recording updates for a day, and I want the
> master to start again. But I don't want to lose the last day's updates.
>
> Since replication is only
Please help, I've read through the manual and this case is suggested but
not really
laid out. I'm using mysql 3.23.37 and can't upgrade to 4.0 yet.
Okay, I've got replication on 2 machines with a one-way failover setup:
Master fails, slave takes over.
Now the slave has be
Please help, I've read through the manual and this case is suggested but
not really
laid out. I'm using mysql 3.23.37 and can't upgrade to 4.0 yet.
Okay, I've got replication on 2 machines with a one-way failover setup:
Master fails, slave takes over.
Now the slave has be
olaris or X86. I hate to implement the failover within the
> > application.
>
> Perhaps you need some tiny piece of middleware that acts as a MySQL
> proxy to do the work, then.
> --
> Jeremy D. Zawodny, <[EMAIL PROTECTED]>
> Technical Yahoo - Yahoo Finance
> Desk:
Sparc Solaris or X86. I hate to implement the failover within the
> > application.
>
> Perhaps you need some tiny piece of middleware that acts as a MySQL
> proxy to do the work, then.
> --
> Jeremy D. Zawodny, <[EMAIL PROTECTED]>
> Technical Yahoo - Yahoo Finance
> D
On Mon, Aug 20, 2001 at 01:21:22PM -0700, David Turner wrote:
>
> It looks like this will only run on Linux and I must either use
> Sparc Solaris or X86. I hate to implement the failover within the
> application.
Perhaps you need some tiny piece of middleware that acts as a MySQL
pro
It looks like this will only run on Linux and I must either use Sparc Solaris
or X86. I hate to implement the failover within the application.
Thanks anyway, Dave
On Mon, Aug 20, 2001 at 01:04:10PM -0700, Jeremy Zawodny wrote:
> On Mon, Aug 20, 2001 at 09:28:20AM -0700, David Turner wr
ble to do is take one
> > down and have all my connections redirected to the second database
> > automatically. I would also like the same auto failover when a
> > database crashes, because of cpu, disk, etc. In oracle I can setup
> > tnsnames failover. Is there a simi
utomatically. I would also like the same auto failover when a
> database crashes, because of cpu, disk, etc. In oracle I can setup
> tnsnames failover. Is there a similar mechanism in MYSQL to redirect
> failed connections to a secondary database?
There is not mechanism built into MySQL curre
I have two identical primarily readonly databases that I want to be able to
upgrade on the fly. What I want to be able to do is take one down and
have all my connections redirected to the second database automatically. I
would also like the same auto failover when a database crashes, because of
failover is to have a load-balancer such as
LVS (http://www.linuxvirtualserver.org). You can have two (again for
failover) 1U rackmounts running LVS - the hardware can be something as low as
486 class. The LVS takes connections and redirects them to each of the MySQL
servers in round-robin fashion. If
Van wrote:
> Simple question:
> Where do I put the my.cnf file? It's nowhere on any of the servers except the
> user directories who use it.
>
Disregard above. I've been using mysqld to start the server since 1998. Hadn't
looked into safe_mysqld since I've only noted that mechanism on RedHat
"Jeremy D. Zawodny" wrote:
>
> On Fri, Mar 16, 2001 at 07:39:01PM -0700, Sasha Pachev wrote:
> >
> > Here is what you can do:
> >
> > server1 -> server2-> server3 -> server4 -> server5 ->
> > ^ |
> > |
cluster for an web cluster for
example
where you can loose a server without any down time in your web cluster.
So it give you all time you need to repair the broken server and bring it
back on line .
It does not provide any failover to the web part for that I recommend if you
have few bucks to by an
Hi Bogomolnyi,
I am really interested in your scripts. I don't have a use for them at this
time, but I am planning to use a fallback system myself in the next few
month.
> 5 pc , and I use it for a web cluster (10 pc) so I use 1 slave
> for 2 httpds
Do you have a similar scheme for the web serv
-
From: "Bryan Coon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 14, 2001 6:10 PM
Subject: Failover and Replication
> Hi,
>
> We are implementing a linux cluster, and rather than get gouged by oracle
> (in performance and licensing) would muuu
On Wed, Mar 14, 2001 at 09:10:42AM -0800, Bryan Coon wrote:
>
> We are implementing a linux cluster, and rather than get gouged by
> oracle (in performance and licensing) would much rather use
> MySQL.
A common solution to a common problem, I suspect.
> If I understand correctly, replicatio
Hi,
We are implementing a linux cluster, and rather than get gouged by oracle
(in performance and licensing) would much rather use MySQL. I searched
through the archives and found several references to failover and
replication but still have some questions.
If I understand correctly
Hi,
We are implementing a linux cluster, and rather than get gouged by oracle
(in performance and licensing) would much rather use MySQL. I searched
through the archives and found several references to failover and
replication but still have some questions.
If I understand correctly
62 matches
Mail list logo
