Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding --force-named-panic option #695

Merged
merged 5 commits into from
Mar 11, 2019
Merged

Adding --force-named-panic option #695

merged 5 commits into from
Mar 11, 2019

Conversation

shlomi-noach
Copy link
Contributor

When --force-named-panic is given, a panic command must also indicate the name of migrated table, or else it is ignored.
This can be useful in mass-distributing a panic request to potentially multiple gh-ost migrations, when in fact only seeking to terminate a specific migration.

@shlomi-noach shlomi-noach temporarily deployed to production/mysql_role=ghost_testing March 6, 2019 10:48 Inactive
@shlomi-noach
Copy link
Contributor Author

This PR also supports non-forced named throttle. i.e. you may for example echo throttle table_name | socat - /tmp/gh-ost.sock, and the migration will only throttle on a table name match.

@shlomi-noach shlomi-noach merged commit 2c0aa36 into master Mar 11, 2019
@shlomi-noach shlomi-noach deleted the named-panic branch March 11, 2019 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant