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

Add support for multiple sniproxy instances #30

Open
Stealthii opened this issue Apr 20, 2018 · 1 comment
Open

Add support for multiple sniproxy instances #30

Stealthii opened this issue Apr 20, 2018 · 1 comment

Comments

@Stealthii
Copy link
Contributor

To prevent blocking of HTTPS connections if the one sniproxy is overloaded, we should look into support for multiple SNIproxy nodes listening on the same port.

Upstream sniproxy added support for reuseport (dlundquist/sniproxy@1cbba1b).

@cmavromichalis
Copy link

Not sure of your setup in terms of machines available to be workers/masters but looks like Docker swarm could do this.

I am interested to hear that sniproxy is being overloaded. Do you have a way to force overloading it/measure the requests until it tips over?

Here is a link if you want to try

https://github.com/cmavromichalis/qcacher/commit/52324229c0990dd870c1b131082ee3d05b4fbdef

docker-compose build
docker stack deploy -c docker-compose.yml qcacher
docker service ls

I threw in visualizer so you can check two instances are running. It's a handy tool, navigate to http://your-local-ip:8080

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

No branches or pull requests

2 participants