-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
StreamEvents encountered unexpected error: Err: runtime error: index out of range #268
Comments
Can you please paste the table definition? Feel free to anonymize column names |
Similar: #179 |
Is it connection to slave or to master? I'm sure that we don't kill any connection manually and we do not have any automatic mechanism for that.
Sorry, I don't understand what does it mean. Please, can you explain? There is table definition:
In the migration, I tried to remove I don't manage slave, it does for me RDS. There is some info from slave:
I tried to migrate again and got the same error after 8 hours on 51%:
|
I just got this exception in the third time (after 2 hours of migration that stoped on 17.5%). But I can't reproduce it on staging with the same configuration but without real load. |
There is an output when run with
|
From your command line I see you connect directly to master, correct? In which case the answer is "to master"
long seconds where there's literally no traffic on the database. I suspect this is not the case, and anyway I see your timeouts are very quick. Question: will you be able to build your own binary given that I publish an experimental branch? You will need to clone the repo and |
Yes. Which branch I should try? |
I will of course let you know once I create it |
I tried to migrate table 10 times and always get the same error This ticket looks similar: go-sql-driver/mysql#467 but I have not found any requests with The are errors from the last 2 attempts:
|
Maybe go-mysql-org/go-mysql#69 can fix it. |
@siddontang that was my intention, thank you! |
@shlomi-noach Thank you. I run migration using gh-ost from |
@shlomi-noach @siddontang migration has failed with error:
I see one similar request in sql.log
but it is valid insert and I' trying to migrate another table |
yes
There 100% reproduce:
Insert crashes migration:
|
Thank you @palexvs I will see it. |
Hi @palexvs |
@palexvs @siddontang I will meanwhile add this to known limitations |
I will try to support 5.7 json and geometry later, maybe this weekend. |
reference: JSON support PR go-mysql-org/go-mysql#88 |
Thank you! Very much. I will try it with next migration in 1-2 weeks. |
Sorry that I am too busy these days. Now I only support not panic for parsing the json field, but I have not supported converting MySQL binary json to readable json string so we can re-insert directly. |
@siddontang take your time and enjoy life |
Meanwhile documenting that |
https://github.com/siddontang/go-mysql (master) and have not got this issue anymore |
See further notes in comment: #275 (comment) |
I tried v1.0.35 and I have not got this issue, so I close it |
@shlomi-noach should docs be updated to express support for json columns? Not sure if that's what I'm gathering here, but seems like it. |
@bbeaudreault sorry for this late response. Unfortunately |
I tried to migrate table with 200M records and I it crashed after 24 hours on 89% with exception
runtime error: index out of range
. I did the same migration on staging successfully.I use MySQL 5.7.11 on AWS RDS
Run gh-ost v1.0.20 on Ubuntu 14.04
The text was updated successfully, but these errors were encountered: