[SERVER-37887] Is it possible to use mongomirror without replicasets? Created: 02/Nov/18 Updated: 02/Nov/18 Resolved: 02/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | venkatesh k | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
I am trying to use mongomirror on docker. I want to make sure if I can run it across two mongo instances without having any replication. Is this possible or is it not available yet? |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 02/Nov/18 ] |
|
Hello Venkatesh, Per our documentation on mongomirror, both the source and destination must be replica sets. This is because mongomirror relies on the oplog and standalone nodes do not contain an oplog. You can convert standalone nodes to single-node replica sets which should accomplish your goal without adding more nodes into the process. If you absolutely must use standalone nodes, you can use mongodump and mongorestore to transfer your information. Please note that this method would require stopping all writes to your cluster until the process completes. As this is not a bug within MongoDB, I will now close this SERVER ticket. Thank you, Danny |