# Threads stuck in COMMIT phase

**URL:** <https://forums.percona.com/t/threads-stuck-in-commit-phase/3831>\
**Category:** Other MySQL® Questions\
**Created:** [October 17, 2014, 12:57pm UTC](https://forums.percona.com/t/threads-stuck-in-commit-phase/3831 "2014-10-17T12:57:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmollet](https://avatars.discourse-cdn.com/v4/letter/c/7ba0ec/32.png) [@cmollet](https://forums.percona.com/u/cmollet)\
**Post date:** [October 17, 2014, 12:57pm UTC](https://forums.percona.com/t/threads-stuck-in-commit-phase/3831/1 "2014-10-17T12:57:37Z")

</div>

I’m encountering an issue on an Amazon RDS box running mysql 5.6.  
There’s a application process that runs lots of concurrent single-row updates on an innodb table, using the primary key.  
update a set blah=blah … where ID = X;

We’ve been consistently seeing 8-10 threads stuck in a commit state for 2-8 seconds.

This RDS instance is dedicated to this one schema, and this is the only table receiving any significant write activity during this time.  
Table has approx 70k records.

buffer\_pool=2.7gb  
Row\_format=compact  
file\_format=antelope

The table has 3 text columns and one mediumtext column, which seems significant based on what I’ve googled.

We updated the server to run file\_format=barracuda and row\_format=compressed

Still get similar behavior, but now the 8-10 threads are stuck in “query end” state for several seconds at a time.

What should I check for next?

---

<div class="post-metadata">

**Author:** ![cmollet](https://avatars.discourse-cdn.com/v4/letter/c/7ba0ec/32.png) [@cmollet](https://forums.percona.com/u/cmollet)\
**Post date:** [October 27, 2014, 5:17pm UTC](https://forums.percona.com/t/threads-stuck-in-commit-phase/3831/2 "2014-10-27T17:17:41Z")

</div>

We tracked this down last week. It seems to have been due to bumping up against an iops threshold on AWS. Increasing to a higher level of provisioned IOPS sorted us out.