Multiple instances of pt-online-schema-change

Registered by Simon J Mudd on 2011-12-01

When cleaning up a failed run (due to replication delay being too high) notice the following output:

# 2011-12-01T08:47:33 USE `our_db`
# 2011-12-01T08:47:33 Alter table SomeTable using temporary table __tmp_SomeTable
# 2011-12-01T08:47:33 Calling CopyRowsInsertSelect::cleanup()
# 2011-12-01T08:47:33 Calling OSCCaptureSync::cleanup()
# 2011-12-01T08:47:33 DROP TRIGGER IF EXISTS `our_db`.`mk_osc_del`
# 2011-12-01T08:47:33 DROP TRIGGER IF EXISTS `our_db`.`mk_osc_ins`
# 2011-12-01T08:47:33 DROP TRIGGER IF EXISTS `dw`.`mk_osc_upd`
# 2011-12-01T08:47:33 /usr/bin/pt-online-schema-change ending for --cleanup-and-exit

This seems to indicate that the trigger naming is not related to the table name and as a consequence of this it would not be possible to run the pt-online-schema-change script more than once on the same instance. (we tend to do this on a replicated chain which affects the master and 40-50 slaves).

As some OSC changes take perhaps a day or more to run I see there may be a situation when you want to run more than one instance of the script at once and I believe this is not possible now. So if that assumption is correct please adjust the trigger names to be related to the db.table that is being altered so we can have multiple scripts running at once.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.