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

oxd and kong clustering #55

Closed
yuriyz opened this issue Nov 10, 2016 · 2 comments
Closed

oxd and kong clustering #55

yuriyz opened this issue Nov 10, 2016 · 2 comments
Assignees
Milestone

Comments

@yuriyz
Copy link
Contributor

yuriyz commented Nov 10, 2016

This requires additional development. oxd creates so called "site
files" which is actually session. If kong node1 communicates with oxd1
and kong node2 with oxd2 then we have problem if request served by
node1 will go to node2.

For this case I think we need to push oxd "site json" to cassandra in
the same way as kong does it.

See this https://getkong.org/docs/0.6.x/clustering/

In case we keep oxd data in cassandra we are on safe side then:

  1. each kong node can have own oxd or can even share oxd between nodes
  2. all data are replicated among nodes by cassandra.
@yuriyz
Copy link
Contributor Author

yuriyz commented Mar 29, 2017

scheduled for 3.2 future version since it's not urgen cc: @nynymike

@yuriyz yuriyz self-assigned this Mar 29, 2017
@yuriyz yuriyz added this to the 3.2.0 milestone Mar 29, 2017
@yuriyz yuriyz modified the milestones: Future, 3.2.0 Aug 24, 2017
@yuriyz yuriyz modified the milestone: Future Dec 19, 2017
@yuriyz
Copy link
Contributor Author

yuriyz commented Sep 20, 2018

oxd supports redis. Also we can add other persistence if needed. Then we should open ticket which should say what exact persistence we wish to support.

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

1 participant