# DDL statements

**URL:** <https://forums.percona.com/t/ddl-statements/2463>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [August 10, 2012, 8:13am UTC](https://forums.percona.com/t/ddl-statements/2463 "2012-08-10T08:13:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![azigui](https://avatars.discourse-cdn.com/v4/letter/a/cab0a1/32.png) [@azigui](https://forums.percona.com/u/azigui)\
**Post date:** [August 10, 2012, 8:13am UTC](https://forums.percona.com/t/ddl-statements/2463/1 "2012-08-10T08:13:34Z")

</div>

Hi,

This limitation is again actual ?  
“DDL statements are problematic and may stall cluster. Later, the support of DDL will be improved, but will always require special treatment.”

Or this is fixed with the Percona 5.5.24 ?

I have this error message in my logs :  
[ERROR] Slave SQL: Could not execute Delete\_rows event on table Pa.AreaType; Cannot delete or update a parent row: a foreign key constraint fails (`Pa`.`Area`, CONSTRAINT `fk_Area_AreaType` FOREIGN KEY (`areaTypeId`) REFERENCES `AreaType` (`id`) ON UPDATE CASCADE), Error\_code: 1451; handler error HA\_ERR\_ROW\_IS\_REFERENCED; the event’s master log FIRST, end\_log\_pos 129, Error\_code: 1451  
120808 16:39:29 [Warning] WSREP: RBR event 2 Delete\_rows apply warning: 152, 4075  
120808 16:39:29 [ERROR] WSREP: Failed to apply trx: source: f9cba57e-dc95-11e1-0800-77d8ecca2a9e version: 2 local: 0 state: CERTIFYING flags: 1 conn\_id: 269454 trx\_id: 55717 seqnos (l: 693, g: 4075, s: 4074, d: 4059, ts: 1344436768974245716)  
120808 16:39:29 [ERROR] WSREP: Failed to apply app buffer: z"P, seqno: 4075, status: WSREP\_FATAL  
at galera/src/replicator\_smm.cpp:apply\_wscoll():50  
at galera/src/replicator\_smm.cpp:apply\_trx\_ws():121  
120808 16:39:29 [ERROR] WSREP: Node consistency compromized, aborting…  
120808 16:39:29 [Note] WSREP: Closing send monitor…  
120808 16:39:29 [Note] WSREP: Closed send monitor.  
120808 16:39:29 [Note] WSREP: gcomm: terminating thread  
120808 16:39:29 [Note] WSREP: gcomm: joining thread  
120808 16:39:29 [Note] WSREP: gcomm: closing backend  
120808 16:39:29 [Warning] WSREP: TO isolation failed for: 3, sql: ALTER TABLE `MappingTablesGeoToArea` AUTO\_INCREMENT = 1. Check wsrep connection state and retry the query.  
120808 16:39:29 [Warning] WSREP: ALTER TABLE isolation failure

Best regards

---

<div class="post-metadata">

**Author:** ![lefred](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lefred/32/16885_2.png) [@lefred](https://forums.percona.com/u/lefred)\
**Post date:** [August 14, 2012, 1:35am UTC](https://forums.percona.com/t/ddl-statements/2463/2 "2012-08-14T01:35:09Z")

</div>

Hi,

Yes the limitation is still there, as for example, big alter tables could have some problem. Are you able to reproduce this problem ?