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

David Too Popular (or DDoS) ? #74

Closed
nelsonic opened this issue Jun 24, 2015 · 7 comments
Closed

David Too Popular (or DDoS) ? #74

nelsonic opened this issue Jun 24, 2015 · 7 comments

Comments

@nelsonic
Copy link

Morning @alanshaw hope you are feeling great today!

Really ❤️ David!
The site/service is great and we recommend it to everyone,
but get super sad when the badge goes blank on a repo if its down... 😢

Is David behind CloudFlare? Or can we help with anything...? http://www.isup.me/david-dm.org

david-is-down

Would love to help if there are any tasks you can offload.

@alanshaw
Copy link
Owner

There's an issue that occurs when the site runs out of memory. It causes 100% CPU to be used and causes all traffic to be dropped.

The downtime you noticed was because this happened on the AWS vm. The vm became completely unresponsive (even after power cycles) and I eventually decided to move to a less flakey host. We then had to wait for the TTL on the DNS to expire.

If you can help with the memory issue that would be amazing. David stores all data in memory and should probably be using a DB or something.

@kingcody
Copy link
Contributor

@alanshaw something like mongodb?

@nelsonic
Copy link
Author

@kingcody mongodb is one option.
I would recommend using a mini Node+Redis cluster on DigitalOcean fronted by nginx & CloudFlare.

@alanshaw where did you move the site to from AWS?

@silverwind
Copy link

Is the site having issues currently? curl -v https://david-dm.org gives me

< HTTP/1.1 504 Gateway Time-out
< Server: nginx/1.4.6 (Ubuntu)
< Date: Tue, 08 Sep 2015 14:21:15 GMT
< Content-Type: text/html
< Content-Length: 191
< Connection: keep-alive

@alanshaw
Copy link
Owner

alanshaw commented Sep 8, 2015

I have no idea what the problem is here, but yes something is up.

@alanshaw
Copy link
Owner

alanshaw commented Sep 8, 2015

Upgrade to iojs 3.3 and a reboot seems to have fixed it. Apologies to all inconvenienced.

@alanshaw alanshaw closed this as completed Sep 8, 2015
@silverwind
Copy link

Ah, you probably ran into the memory leak that was there in io.js 3.0 til 3.2 :)

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

4 participants