# SST locks donor node for writing after any DDL

**URL:** <https://forums.percona.com/t/sst-locks-donor-node-for-writing-after-any-ddl/35770>\
**Category:** Percona XtraDB Cluster\
**Created:** [December 21, 2024, 8:43pm UTC](https://forums.percona.com/t/sst-locks-donor-node-for-writing-after-any-ddl/35770 "2024-12-21T20:43:03Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [December 23, 2024, 4:02pm UTC](https://forums.percona.com/t/sst-locks-donor-node-for-writing-after-any-ddl/35770/3 "2024-12-23T16:02:02Z")

</div>

Hello @JiriZyka,  
From the docs:

> `LOCK TABLES FOR BACKUP` uses a new MDL lock type to block updates to non-transactional tables and DDL statements for all tables.

What you are experiencing is correct behavior. You should not be running any DDL during an SST. The SST process needs a consistent schema to create a clone of the node, thus any/all DDL are blocked during the SST process.

Because you ran a DDL, it got blocked, and this block also blocks writes to the table. If you do not run a DDL, then writes will not get blocked.

---

_[View the full topic](https://forums.percona.com/t/sst-locks-donor-node-for-writing-after-any-ddl/35770)._