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

Cannot run onlineddl migrations with Vitess and pt-osc on AWS Aurora #8039

Closed
aquarapid opened this issue May 4, 2021 · 3 comments · Fixed by #8038
Closed

Cannot run onlineddl migrations with Vitess and pt-osc on AWS Aurora #8039

aquarapid opened this issue May 4, 2021 · 3 comments · Fixed by #8038
Labels
Component: Query Serving Type: Enhancement Logical improvement (somewhere between a bug and feature)

Comments

@aquarapid
Copy link
Contributor

If you use Vitess against an external tablet that is an AWS Aurora instance, and you try to use onlineddl (e.g. vtctlclient ... ApplySchema -ddl_strategy "pt-osc ....."), you will get the following error in the message field of the show vitess_migrations\G output:

Error creating pt-online-schema-change user: Access denied for user 'vt_dba'@'%' (using password: YES) (errno 1045) (sqlstate 28000) during query: GRANT SUPER, REPLICATION SLAVE ON *.* TO 'vt-online-ddl-internal'@'%'"

This is unsurprising, since Aurora does not provide SUPER privs.

@aquarapid
Copy link
Contributor Author

#8038 should fix this.

@aquarapid
Copy link
Contributor Author

Of course, the usual pt-osc requirements on Aurora still apply, e.g. you need to set the MySQL parameter log_bin_trust_function_creators to 1 via a parameter group.

@askdba askdba added Component: Query Serving Severity 3 Type: Enhancement Logical improvement (somewhere between a bug and feature) labels May 6, 2021
@hallaroo
Copy link
Member

#8038 is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Query Serving Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants