# "wsrep: write set replicated and certified" while trying to restore a dump

**URL:** <https://forums.percona.com/t/wsrep-write-set-replicated-and-certified-while-trying-to-restore-a-dump/12969>\
**Category:** Percona XtraDB Cluster 8.x\
**Tags:** closed-no-reply\
**Created:** [November 11, 2021, 5:18pm UTC](https://forums.percona.com/t/wsrep-write-set-replicated-and-certified-while-trying-to-restore-a-dump/12969 "2021-11-11T17:18:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gabcicala](https://avatars.discourse-cdn.com/v4/letter/g/6a8cbe/32.png) [@gabcicala](https://forums.percona.com/u/gabcicala)\
**Post date:** [November 11, 2021, 5:18pm UTC](https://forums.percona.com/t/wsrep-write-set-replicated-and-certified-while-trying-to-restore-a-dump/12969/1 "2021-11-11T17:18:46Z")

</div>

Hi Everybody.  
I have a cluster of three Ubuntu node running: percona-xtradb-cluster 1:8.0.21-12-1.bionic

While I try to restore a previous dump of a table I encounter the state above in the processlist.  
It is impossibile to unlock the table even killing the query.  
If I try to kill that query the state is the same but with command “killed”. The table still remain locked and the unique way to let run once again is to restart all the cluster.

Hence I cannot restore that table.

Looking in the error.log file I see some rows like these:  
[Note] [MY-000000] [WSREP] MDL conflict db=XXXX table=xxxxx ticket=9 solved by abort  
but I think this is only a consequence of a conflict solved with that abort.

Did you had the same problems?  
Let me know if you need more information.  
Best regards.  
Gabriele