max-commit-id should persist value in slave
Bug #731293 reported by
Joe Daly
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
Medium
|
David Shrewsbury | ||
| 7.0 |
Fix Released
|
Medium
|
David Shrewsbury | ||
Bug Description
If a user specifies max-commit-id on the slave it should be persisted, its currently just in memory. This avoids the case where a user starts the server with max-commit-id but does not issue a statement on the master and restarts the slave then without the max-commit-id option. The slave would replay everything in this case.
Related branches
lp:~dshrews/drizzle/bug731293_persist_maxcommitid
- Drizzle Developers: Pending requested
-
Diff: 125 lines (+46/-3)5 files modifiedplugin/slave/queue_producer.h (+1/-1)
plugin/slave/replication_schema.cc (+13/-0)
plugin/slave/replication_schema.h (+15/-0)
plugin/slave/replication_slave.cc (+9/-0)
plugin/slave/replication_slave.h (+8/-2)
| Changed in drizzle: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| milestone: | none → 2011-03-14 |
| tags: | added: slave-plugin |
| Changed in drizzle: | |
| assignee: | nobody → David Shrewsbury (dshrews) |
| status: | Confirmed → Triaged |
To post a comment you must log in.
