PXC triggers that modify MyISAM tables not working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Confirmed
|
Undecided
|
Unassigned | ||
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
To replicate:
1) Load some nodes with wsrep-replicate
2) Load sakila-db (or the attached test case) on one node
3) Check that sakila.film_text has data on that node
At this point, film_text will be empty on the other nodes, and their error logs will have entries like
121008 17:13:41 [ERROR] Slave SQL: Error 'Unknown column 'new.film_id' in 'field list'' on query. Default database: 'sakila'. Query: 'INSERT INTO film_text (film_id, title, description)
VALUES (new.film_id, new.title, new.description)', Error_code: 1054
121008 17:13:41 [Warning] WSREP: RBR event 1 Query apply warning: 1, 35
121008 17:13:41 [Warning] WSREP: Ignoring error for TO isolated action: source: 91dec4df-
Changed in percona-toolkit: | |
status: | New → Confirmed |
tags: | added: percona-xtradb-cluster triggers |
tags: |
added: pxc removed: percona-xtradb-cluster |
tags: | added: myisam |
Changed in percona-toolkit: | |
milestone: | none → 2.2.1 |
importance: | Undecided → High |
Changed in percona-toolkit: | |
milestone: | 2.2.1 → none |
Changed in percona-toolkit: | |
importance: | High → Undecided |
summary: |
- Triggers that modify MyISAM tables not working + PXC triggers that modify MyISAM tables not working |
Changed in codership-mysql: | |
status: | New → Confirmed |
We've had about 8 months of experience with PXC now, and the verdict seems clear: PXC and MyISAM are not a good combination, and afaik there's no big push from users to make it work, i.e. the 99% use-case is PXC with InnoDB. So I'm going to WontFix this bug in Percona Toolkit.