pt-table-checksum docs don't mention risks posed by inconsistent schemas
Bug #949653 reported by
Fernando Ipar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Toolkit moved to https://jira.percona.com/projects/PT |
Fix Released
|
Wishlist
|
Daniel Nichter | ||
| 2.0 |
Fix Released
|
Wishlist
|
Daniel Nichter | ||
| 2.1 |
Fix Released
|
Wishlist
|
Daniel Nichter | ||
Bug Description
This is either a doc bug or a feature request.
Doc bug:
I think the RISKS section of the manual should warn that pt-table-checksum will break replication if the schema to be checksummed is not consistent. This may sound obvious but on servers with many databases it may be difficult to know in advance which ones should be skipped because they only exist on the master.
OR
Feature request:
Since the tool now accesses slaves to check their lag and throttle itself, couldn't it also check that the tables to checksum exist on all nodes and have the same structure, and refuse to run otherwise?
Related branches
lp:~percona-toolkit-dev/percona-toolkit/fix-risks-docs-bug-949653
- Daniel Nichter: Approve
-
Diff: 14 lines (+5/-0)1 file modifiedbin/pt-table-checksum (+5/-0)
- Daniel Nichter: Approve
-
Diff: 14 lines (+5/-0)1 file modifiedbin/pt-table-checksum (+5/-0)
| Changed in percona-toolkit: | |
| importance: | Undecided → Wishlist |
| Changed in percona-toolkit: | |
| status: | New → Triaged |
| assignee: | nobody → Daniel Nichter (daniel-nichter) |
| milestone: | none → 2.1.1 |
| tags: | added: docs pt-table-checksum risk |
| summary: |
- pt-table-checksum's manual's risks section doesn't warn of problems - caused by schema inconsistencies + pt-table-checksum docs don't mention risks posed by inconsistent schemas |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/