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

Not able to change the cluster #924

Open
singhmahendrapal opened this issue May 18, 2021 · 3 comments
Open

Not able to change the cluster #924

singhmahendrapal opened this issue May 18, 2021 · 3 comments

Comments

@singhmahendrapal
Copy link

Currently we are using a Mongodb 3.6 version cluster and to Elasticsearch syncing we are using mongo-connector. I want to upgrade it to 4.0. So we are following the below steps -

  1. Taken a snapshot of 3.6 cluster
  2. Created a new cluster with 4.0 version and restore the 3.6 sanpsot in it successfully.
  3. Updated the new 4.0 replicaset name into existing oplog.ts file (with existing value)

Now my syncing has been stopped. Can someone provide any help on it so that i can start syncing again?

Note: Since we have the same data into new 4.0 cluster so i don't want the syncing since starting. Syning should work when i insert a new record into new cluser 4.0

Thanks in advance. As it's very urgent for me.

@singhmahendrapal
Copy link
Author

Hi @jaraco, @AayushU and @ShaneHarvey,
Since you guys are the most active contributor of mongo-connector.
Actually, I need to change the MongoDB cluster in our application. So I created a new cluster with the updated version and dump all the data into it from old cluster. But after doing this my mongo-connector syncing stopped and if i remove my oplog.ts file it starts the syncing beginging.

Current in our DB we have around 2 CRs data collection so sync them into Elastic Search via mongo-connector since starting it will take time.
So do you guys any suggestion and idea so that we can point out the new cluter and start the syncing where our old cluster left? I have no issue to pay you guys for this efforts. Pleaes let us know so that we can proceed accordinngly.

It's very urgent so please have a look and do the needful.

@ShaneHarvey
Copy link
Contributor

Hi @singhmahendrapal, apologies for the situation. It does sound frustrating. Unfortunately, I do not work on mongo-connector anymore. Taking a look through the open issues shows that mongo-connector only has limited support for MongoDB 3.6 (#767) and does not support MongoDB 4.0 (#865). It seems like you would need to wait for those projects to be completed before using mongo-connector with MongoDB 4.0.

Note that if you're using MongoDB Atlas than you might be interested in using Atlas Search which provides full text search natively in the MongoDB cluster itself. With Atlas Search there's no need to manually sync data to other systems.

@jaraco
Copy link
Collaborator

jaraco commented May 27, 2021

Hello Singh. I unfortunately have little to add. I also have moved to a new role where I spend little time with MongoDB and mongo-connector. I wish I could have help, but I have neither context nor bandwidth to offer. I wish you luck. Feel free to ping me on PRs that would aid in supporting your needs. I'm happy to merge and release contributions.

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