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

Multiple mope backends #67

Open
njustus opened this issue May 17, 2019 · 0 comments
Open

Multiple mope backends #67

njustus opened this issue May 17, 2019 · 0 comments
Labels
backend backend related feature a new feature hard complicated -or propabyl impossible- to fix

Comments

@njustus
Copy link
Member

njustus commented May 17, 2019 •
edited
Loading

It should be possible to use multiple mope backend server if we can somehow match the session id x project id to the mope server, that created it...

  • use traefik as load balancer with sticky sessions
  • use zookeeper znodes to store this information
  • use dtab's to map from session_id/compile -> mope-server:port/mope/project/$id/..
  • save it into redis ..
@njustus njustus added backend backend related feature a new feature labels May 17, 2019
@njustus njustus mentioned this issue May 17, 2019
Closed
@njustus njustus added the hard complicated -or propabyl impossible- to fix label Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend backend related feature a new feature hard complicated -or propabyl impossible- to fix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@njustus