 | |
#1
 
| |||
| |||
|
replication and table crash -
10-24-2011
, 08:09 AM
#2
| |||
| |||
|
|
a simple, stupid question: in a replication configuration, when a (single) table crashes on the master DB, what happen on the slave DB? I guess that the slave DB won't receive annymore updates. Is that right? |
this table will succeed on the master. Hence none will be logged to
be replicated to the slave.
XL
#3
| |||
| |||
|
|
DeepBlue<deepblue (AT) spam (DOT) is.lame> wrote: a simple, stupid question: in a replication configuration, when a (single) table crashes on the master DB, what happen on the slave DB? I guess that the slave DB won't receive annymore updates. Is that right? If a table is crashed on the master, then no DML statements against this table will succeed on the master. Hence none will be logged to be replicated to the slave. |
So, is there a way to guarantee the availability of the service in case
of a table crash?
#4
| |||
| |||
|
|
On 10/24/2011 04:05 PM, Axel Schwenke wrote: If a table is crashed on the master, then no DML statements against this table will succeed on the master. Hence none will be logged to be replicated to the slave. So, is there a way to guarantee the availability of the service in case of a table crash? |
crashed tables?
Hint: automatic repair for MyISAM exists. And InnoDB too. RTFM!
XL
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.