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

[nEdge] Implement clustering and high-availability #2036

Open
lucaderi opened this issue Sep 17, 2018 · 3 comments
Open

[nEdge] Implement clustering and high-availability #2036

lucaderi opened this issue Sep 17, 2018 · 3 comments

Comments

@lucaderi
Copy link
Member

As nEdge is used inline, a fault can disrupt the whole network. It is requested to implement a way to federate instances in order to implement high-availability so that

  • traffic is distributed across available nEdge instances
  • in case of fault of an instance, the other nEdge instance will handle the load
@lucaderi
Copy link
Member Author

A possible implementation option is to implement hot-standby

@lucaderi lucaderi added this to the 3.8 milestone Nov 17, 2018
@simonemainardi simonemainardi changed the title [nEdge] Implement clustering and high-availability Implement clustering and high-availability Dec 13, 2018
@simonemainardi simonemainardi modified the milestones: 3.8, 4.0 Dec 13, 2018
@simonemainardi simonemainardi modified the milestones: 4.0, 4.1 Nov 14, 2019
@simonemainardi simonemainardi modified the milestones: 4.2, 4.4 Aug 24, 2020
@simonemainardi simonemainardi modified the milestones: 5.0, 5.2 Jun 15, 2021
@sciolto
Copy link

sciolto commented Jan 21, 2022

We have an actual use case for a customer project. They happily use nEdge as traffic shaper, but need to make it high-available in a cluster.

@lucaderi lucaderi removed this from the 5.2 milestone Feb 16, 2022
@cardigliano cardigliano changed the title Implement clustering and high-availability [nEdge] Implement clustering and high-availability Feb 21, 2023
@cory-usap
Copy link

I am working on setting up a HA cluster between two linux instances. Instead of opening up a new thread this seems to fit in this thread.

I have requested a Quota persist feature for nEdge ion #8882

However since this could be some time before it is updated I was wondering if theres a way to sync this to a hot-standby secondary server using corosync+pacemaker [1]?

I understand that it's not persisted however maybe there is a way to sync this over into the running application then we could sync it back when the primary comes back and takes over the HA cluster.

[1] https://www.habibza.in/configuration-ha-cluster-corosync-and-pacemaker-ubuntu-20-04/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants