# Usage of Percona Toolkit in Production Environment

**URL:** <https://forums.percona.com/t/usage-of-percona-toolkit-in-production-environment/33004>\
**Category:** Percona Toolkit\
**Created:** [September 9, 2024, 6:22am UTC](https://forums.percona.com/t/usage-of-percona-toolkit-in-production-environment/33004 "2024-09-09T06:22:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Omer\_Faruk\_Icen](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/omer_faruk_icen/32/17641_2.png) [@Omer\_Faruk\_Icen](https://forums.percona.com/u/Omer_Faruk_Icen)\
**Post date:** [September 9, 2024, 6:22am UTC](https://forums.percona.com/t/usage-of-percona-toolkit-in-production-environment/33004/1 "2024-09-09T06:22:51Z")

</div>

Dear Percona Team,  
I manage a Percona Cluster (Multi-Master Nodes) running MySQL version 5.7.40. We are experiencing significant slowdowns when adding indexes, in addition to table locking. I’ve been researching Percona Toolkit, particularly the `pt-online-schema-change` tool, and find it very useful.

However, I noticed that the documentation mentions some potential risks:

> “Percona Toolkit is mature, proven in the real world, and well tested, but all database tools can pose a risk to the system and the database server. Before using this tool, please test the tool on a non-production server.”

Given these risks, I would like to know if it’s safe to use the `pt-online-schema-change` tool in a production environment, considering the current performance challenges in our cluster.

Here are the key details of our setup:

- Cluster Version: 57
- MySQL Version: 5.7.40

Could you please provide guidance or best practices for using this tool in a live production system? Any advice on minimizing risks would also be greatly appreciated.

Thank you in advance for your help.

---

<div class="post-metadata">

**Author:** ![Yunus](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yunus/32/6430_2.png) [@Yunus](https://forums.percona.com/u/Yunus)\
**Post date:** [September 9, 2024, 10:13am UTC](https://forums.percona.com/t/usage-of-percona-toolkit-in-production-environment/33004/2 "2024-09-09T10:13:23Z")

</div>

pt-online-schema-change is one of the best tools available for doing schema changes. It is specially built for that.

> [@Omer\_Faruk\_Icen](#):
>
> all database tools can pose a risk to the system and the database server. Before using this tool, please test the tool on a non-production server.”

This is applicable for all the changes you do on your databases not only with pt-online-schema-change.  
You need to test anything that you have to run on your production database

The only thing you need to be stay careful if you have triggers and foreign keys in your table. You should read and understand the document if this is the case and use proper parameters for running pt-online-schema-change. Otherwise it is very straight forward.

> [@Omer\_Faruk\_Icen](#):
>
> Cluster Version: 57

You can use --max-flow-ctl=0 as an additional option if you running Percona Xtradb cluster or Galera cluster.

You can check the documentation for pt-online-schema-change. for tuning it further.

> **[Percona Toolkit Documentation](https://docs.percona.com/percona-toolkit/pt-online-schema-change.html)**
>
> Command-line tools for common MySQL database administration tasks.