jdevinemt

Any update on this? I'm also experiencing this installing in a docker container (Ubuntu 20.04) 

I'm going to try running this again on a brand new database instance just to ensure the issue wasn't caused by starting and stopping the migration multiple times. I'll upload...

Ok, I provisioned a fresh target database instance and tried again with the same results. I've updated my original post with additional logs and MYSQL output.

> Hi [@jdevinemt](https://github.com/jdevinemt) , Can you try with --stream=1 on myloader? Reference: [#1693](https://github.com/mydumper/mydumper/issues/1693) Just tried that and got the same result. This same command was working as expected on v0.19.1-3....

I know it worked on v0.19.1-3 because of [this discussion](https://github.com/mydumper/mydumper/discussions/1211#discussioncomment-13162625) from last month. I had run it successfully several times with the same arguments.

I'll try running this migration again tomorrow with just a single schema defined in the `--database` option to see if this is specific to multi-schema migrations.

> I'll try running this migration again tomorrow with just a single schema defined in the `--database` option to see if this is specific to multi-schema migrations. I tried with...

> Oh! wait, I saw that you were using v0.19.3-1, anyways you should test with `--use-single-column` Please, let me know how it goes. Just ran it again with the `--use-single-column`...

> I will test the full migration on all schema I plan to migrate. Knowing the schema tested here is the largest schema in my migration, I think this should...

> Hi [@jdevinemt](https://github.com/jdevinemt) , just to be clear, `--stream` means `--stream=0` , if you want myloader to start import without waiting mydumper to complete, you must explicitly use `--stream=1` According...