Replication stops after one hour or so
You are viewing an old version of this question. View
the current version here.
Agenda and notes from day 2 of the MariaDB Developer Meeting in Athens, Greece.
Agenda
| Time | Main Track | Side Track |
|---|---|---|
| 09:00‑10:00 | Email & Hacking time (Public) | |
| 10:00-11:00 | GIS in MariaDB: Current status, upcoming milestones. (Public) | |
| 11:00‑11:15 | Small break | |
| 11:15-12:30 | Replication in MariaDB (Public) | |
| 12:30‑13:30 | Lunch | |
| 13:30‑14:00 | Email and hacking time. | |
| 14:00‑15:15 | Xentio Presentation (Public) | |
| 15:15‑15:45 | Coffee break | |
| 15:45-16:30 | MariaDB 5.3: Technical Status (Public) | |
| 16:30-17:30 | MariaDB 5.5: Planning (features, release theme, release dates, etc...) (Public) |
Printed Schedule (pdf)
Notes
Answer Answered by Martin Trenz in this comment.
The problem stemmed from a table with 390000 records without a primary index that is replicated row-based. InnoDB creates a invisible primary key (six bytes, basically the row-number) but this key is not replicated. Therefor every DELETE leads to a full table scan on the slave. Transaction-Encapsulation lead to the impression of absolute standstill.
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
