go-sync-mongo

go-sync-mongo copied to clipboard

Hello, **I tried to execute the following** _go-sync-mongo sync --src "src:27018" --src-username mongooplog --src-password pass --src-db db --src-ssl=false --dst "dst:27017" --dst-username mongooplog --dst-password pass --dst-db db --dst-ssl=false_ Result: 2020/05/20 10:13:56...

DonShamsan

I saw in your blog post (https://engineering.checkr.com/mongodb-cluster-migration-with-zero-downtime-f4e294c29bef) that you were syncing local mongo instances to Atlas cloud which was why this tool was created. We are doing the opposite to...

bradjohnsonkink

Can't run at source or destination

1

I am trying to migrate from 192.168.50.10 to 192.168.50.117 but running go-sync-mongo-linux-amd64 in either source or destination produces the following ./go-sync-mongo-linux-amd64 status --src "mongodb://192.168.50.10:27017" --src-username mongooplog --src-password some-password --dst "mongodb://192.168.50.117:27017"...

etemiz

Why Source and Destination both show 0 record for Status?

1

Mu source database collection has 40k records, and destination database collection is empty. But when I ran "go-sync-mongo status", it both showed 0. what could be wrong? Thanks.

gao-jian-zz

I mean standard mongo stuff like --sslPEMKeyFile, --sslCAFile, --sslAllowInvalidHostnames Looks like mgo itself supports X.509: https://www.compose.com/articles/connect-to-mongo-3-2-on-compose-from-golang/

Gugic