pt-online-schema-change doesn't check PXC flow control

Bug #1413101 reported by Miguel Angel Nieto on 2015-01-21
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Fix Released
Medium
Frank Cizmich

Bug Description

pt-online-schema-change can check regular replication lag to avoid causing any problem. Seems it doesn't do the same with PXC, where it should check flow control on the nodes to see if some pause is needed to avoid causing delays in queries. To make the tool fully reliable with PXC it should be able to understand flow control and monitor it.

tags: added: pt-online-schema-change
tags: added: i50125

Set to confirmed as a wishlist.

Changed in percona-toolkit:
status: New → Confirmed
tags: added: galera pxc
tags: removed: galera
Changed in percona-toolkit:
status: Confirmed → Fix Committed
importance: Undecided → Medium
assignee: nobody → Frank Cizmich (frank-cizmich)
milestone: none → 2.2.15
Frank Cizmich (frank-cizmich) wrote :

Added "--max-flow-ctl" option
This value is a percentage.
When a node is very loaded it sends flow control signals to the other nodes to stop sending transactions in order to catch up.
When the average value of time spent in this state (in percent) exceeds the maximum provided in the option, the tool pauses until it falls below again.
Default is no flow control checking.

Changed in percona-toolkit:
status: Fix Committed → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-671

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers