| List: | Replication | « Previous MessageNext Message » | |
| From: | Andrei F | Date: | September 23 2009 4:52pm |
| Subject: | Re: borked replication | ||
| View as plain text | |||
Hello, SHOW SLAVE STATUS \G doesn't spit out any errors, replication is running fine at the moment. My concern is that some tables are not synched at all. For example the master server has the following tables: dbname.tablename[1,2,3] Due to the broken replication, the slave doesn't have these tables. SKIP_COUNTER won't help here since I will have to do it numerous times. I'll keep investigating and repost once I get it up and running. Regards,
| Thread | ||
|---|---|---|
| • borked replication | Andrei F | 22 Sep |
| • Re: borked replication | Miguel Angel Nieto | 22 Sep |
| • Re: borked replication | Marcus Bointon | 23 Sep |
| • Re: borked replication | Pankaj Joshi | 23 Sep |
| • Re: borked replication | Ian Simpson | 23 Sep |
| • Re: borked replication | Andrej Pintar | 23 Sep |
| • Re: borked replication | Andrei F | 23 Sep |
| • Re: borked replication | api984 | 24 Sep |
| • Re: borked replication | Mats Kindahl | 25 Sep |
