[SERVER-14698] Maintaining mirror database of replset on a single MongoDB instance Created: 26/Jul/14 Updated: 10/Dec/14 Resolved: 28/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Tung Nguyen | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
Hello, We are running production replset and also need a mirror DB of it. This mirror DB is on a single MongoDB instance, not a replset. Please check attachment for the layout. We would like to know if there is a best practice for this use case? Thank you very much, |
| Comments |
| Comment by Tung Nguyen [ 29/Jul/14 ] |
|
Thanks Ramon. |
| Comment by Ramon Fernandez Marina [ 28/Jul/14 ] |
|
Thanks for your report. The SERVER project is for reporting bugs or feature suggestions for the MongoDB server and tools. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. |
| Comment by Tung Nguyen [ 26/Jul/14 ] |
|
More information, we tried running mongooplog on the mirror DB, mirroring the hidden member but it got timed out all the time. Then we added another hidden instance to the replset (it is not drawn out in the attachment), which was a powerful machine so we could touch oplog into its memory. And we could run mongooplog successfully. But he problem is, we do not want the hidden member to be that powerful, we need to keep it as small as the original hidden (in the attachment). Regards, |