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
gh-ost stuck throttling on "value out of range" error #827
Comments
@grantholly Could you please provide the output for this command: show status where variable_name = 'threads_running; At first glance it looks like the internal throttling mechanism is fetching the |
Sorry this has taken me so long to get back to. I am finally able to get back to this. Here is the output from your suggested query
yeah, that's a lot of threads. |
@grantholly So what's happening is I'm not sure there's any value in getting gh-ost to handle this large of a number. I feel like you've hit a bug in mysql somehow causing this astronomical number to return. |
This seems to be an issue with our Aurora database. Even without the gh-ost process running it still reports this comically incorrect value for threads running. We do not see this issue on any of our other mysql databases, including those running with in our Vitess clusters. ¯_(ツ)_/¯ |
Closing this as the issue is with Aurora. Good luck! |
For posterity, AWS claims this is fixed in Aurora versions >= 2.04.7. From the documentation:
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.2047.html |
ghost version:
ghost command:
mysql version:
NOTE: this is an aurora MySQL instance
table definition:
problem:
This gh-ost run will forever be throttled and never copy any rows. Each reported line from the output contains that same error message, however, the reported value changes slightly:
Interestingly, this worked when I excluded the
--execute
flag, and a percona blog post mentioned using gh-ost on aurora MySQL (https://www.percona.com/blog/2018/06/07/using-gh-ost-with-amazon-aurora-for-mysql/) so I was initially very optimistic.The error message seems to be mentioning a column named "Value", but my table does not have that column. However, I did find the
value
column on the_remote_archives_ghc
table.Also of note, this database is not receiving any writes during this migration, and the table only has ~3300 rows in it. Not a big deal right? With the database being so small, I went looking in the
remote_archives
table to find any values that equaled the reported 18446744073709547932 and could not find it in any of the rows on the tableThe gh-ost process doesn't ever crash, but it also never makes any progress copying rows. It looks like this error message is being passed through gh-ost. I couldn't find anything in the code base for "value out of range" for example. It also looks like some sort of parsing problem. Perhaps #681 and #157 could be related. I'm just guessing though.
I should also mention that this same migration worked flawlessly on MySQL 5.7 in our datacenter as well as with our MySQL Vitess cluster.
Right now I am totally blocked on making this migration.
error output with --debug --stack --verbose
The text was updated successfully, but these errors were encountered: