# Help in finding large transaction

**URL:** <https://forums.percona.com/t/help-in-finding-large-transaction/3443>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [May 4, 2014, 8:59am UTC](https://forums.percona.com/t/help-in-finding-large-transaction/3443 "2014-05-04T08:59:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![blodan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/blodan/32/1005_2.png) [@blodan](https://forums.percona.com/u/blodan)\
**Post date:** [May 4, 2014, 8:59am UTC](https://forums.percona.com/t/help-in-finding-large-transaction/3443/1 "2014-05-04T08:59:46Z")

</div>

Hi,

We have somewhat of a stall in our PXC setup, once or twice a day there is a query creating a huge transaction which stalls the cluster until the transaction hits the transaction limit, i.e, this is logged:

```auto
140504 12:34:37 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592

```

I’ve tried tracking down the query causing this on my own but I can’t seem to find it. Are there any way i can log querys causing large transactions?

---

<div class="post-metadata">

**Author:** ![mixa](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mixa/32/16881_2.png) [@mixa](https://forums.percona.com/u/mixa)\
**Post date:** [May 13, 2014, 2:51am UTC](https://forums.percona.com/t/help-in-finding-large-transaction/3443/2 "2014-05-13T02:51:09Z")

</div>

Hi blodan,

In case if query/transaction is cslow - you can check the following things:

- entire error log
- show engine innodb status\G
- show global status like ‘ws%’
- you can enable slow query log and check for slow queries

The best is to run pt-stalk (our tool):  
[url][http://www.percona.com/doc/percona-toolkit/2.2/pt-stalk.html[/url]](http://www.percona.com/doc/percona-toolkit/2.2/pt-stalk.html%5B/url%5D)

PTDEST=/tmp/pt/collected/`hostname`/  
mkdir -p $PTDEST;  
cd /tmp/pt;  
wget [percona.com/get/pt-stalk](http://percona.com/get/pt-stalk);  
chmod +x pt\*;  
sudo ./pt-stalk --no-stalk --iterations=2 --sleep=30 --dest=$PTDEST – --user=root --pass=;

Then it will collect a lot of info in $PTDEST folder and you’ll be able to check info there.