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.

Sign up for GitHub

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

Jump to bottom

High Availability: Node level replication #74

Open
amemon opened this issue Oct 2, 2012 · 1 comment
Open

High Availability: Node level replication #74

amemon opened this issue Oct 2, 2012 · 1 comment
Labels
Major Priority: Medium Severity: Feature

Comments

@amemon
Copy link
Member

amemon commented Oct 2, 2012

This is a new requirement to make the DSR's highly available by replicating the instances on separate servers.
@szigetigabor
Copy link
Member

The mongodb replication is not a problem (master/slave model). EMIR and the replicated mongo's handling are also not a big problem (we can configured list of mongodbs. and the EMIR will write always to the master and read from the slave mongodb.)
BUT a parent handling and the EMIR handling on client side is a big problem. Who/how can knows which DSR is the given EMIR's replication?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Major Priority: Medium Severity: Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@amemon @szigetigabor