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

Timed out waiting on socket read. (Mongo::OperationTimeout) #162

Open
HellBakedMiasma opened this issue Jan 31, 2018 · 3 comments
Open

Timed out waiting on socket read. (Mongo::OperationTimeout) #162

HellBakedMiasma opened this issue Jan 31, 2018 · 3 comments

Comments

@HellBakedMiasma
Copy link

I have two mysql databases, one is relatively small (db1), about 500 000 records, the second contains more than 3.5 million records (db2).

Using mongify to copy the first into mongodb succeeds as intented, while copying the latter yields the following error after having created the tables, copied the records, updated the references, and removed "pre_mongified_id"s from half the collections :

/var/lib/gems/2.3.0/gems/mongo-1.12.5/lib/mongo/networking.rb:336:in `rescue in receive_message_on_socket': Timed out waiting on socket read. (Mongo::OperationTimeout)

i'm on debian stretch using mongodb version 3.2.11.

@anlek
Copy link
Owner

anlek commented Feb 1, 2018

Could be an issue with RAM... maybe manually remove the pre_mongified_id field? or is other data missing?

@Dylan2388
Copy link

I'm facing the same above error. Where can I remove the pre_mongified_id field manually?

@anlek
Copy link
Owner

anlek commented Mar 20, 2020

pre_mongified_id gets removed as the last step of the move process

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

No branches or pull requests

3 participants