Live data from Hacker News

Cause of YC/HN outage discovered

archub.org

91–100 of 110 posts

Re: Cause of YC/HN outage discovered

#91
post #9

This site was on a shared hosting box? And of course they are going to disable it without warning if it's causing problems for all the other customers on that box...

Not this site, www. There was no sudden spike in traffic. If they'd bothered to check the logs they'd have found that the load, whatever it was, was no higher than it had been.

I'd imagine what happened was one of their other customers finally decided to call support to see why their site was so slow.

Re: Cause of YC/HN outage discovered

#92
post #75

Earlier quoted context omitted.

Any particular reason for Slicehost as opposed to any of the other similar options (Linode, prgmr)? I'm not affiliated with any, though I run my site on VPSes from Linode. I was convinced by a Dec 2009 post by an HNer, uggedal: http://journal.uggedal.com/vps-performance-comparison

Me too. That post was detailed & fair. On slicehost I had a 256MB slice which I upgraded to 512MB slice to host 2 small websites. After the post got a 360MB linode VPS instead and am very happy with it. Edit: Slicehost help articles & resources, well organised & exhaustive is a plus though.

I came to similar conclusions myself:

http://journal.dedasys.com/2008/11/24/slicehost-vs-linode

Re: Cause of YC/HN outage discovered

#93

Earlier quoted context omitted.

So let's see... you're hosting a website that has gotten large; that is, it's grown to the point that it will need higher-cost services in order to meet demand. You have a chance to add a valuable customer to your client base. How best to handle this? a) anything b) except c) killing their service

How best to handle this? Of course, the flip side is that leaving it running adopts an attitude of "screw all our other customers, they can eat crappy service while we kiss up to the popular guys who are chewing up everybody else's server resources". Which isn't what I'd look for in a hosting provider...

False dichotomy. The correct way to handle this would have been to temporarily move the shared server to hardware where it won't impact other customers and notify YC that they need to move their server to a bigger server or the site will have to be shut down. Presumably with an ultimatum of a week or whatever.

Re: Cause of YC/HN outage discovered

#94
post #65
post #37

Earlier quoted context omitted.

Also, just going to point out here that Pair.com has had a great reputation in the hosting industry, and has for the last 10 years. I've been in the industry for 10 years and worked for quite a number of hosting companies, not Pair though, and when you have 150 shared clients on a machine and 1 client is causing the problems you do your best to deliver the warning before it gets out of hand but it is very hard to do.

When I emailed Pair.com to tell them that my site was about to get a writeup in the Wall Street Journal, they moved my site to a dedicated server within an hour, left it there until the spike of traffic was over, then moved my site back to a shared server--all at no charge. If you use Pair.com properly, they are more than excellent.

They could have a small pool of servers where they could move problematic sites until the customer has had a warning and a fair chance to react to it.

Re: Cause of YC/HN outage discovered

#95

Kinda funny and sad that so many people here only see this as some sort of stupid or unfair action against HN, seemingly without even acknowledging that every single other customer on that shared server had as much right individually, and more right collectively, to not have their performance negatively impacted by HN. Yeah, it sucks that one of our favorite tech news sites was impacted by this, but how impacted were…

Strawman. Nobody's saying HN/YC should be allowed to overuse resources (then again, I don't know the terms they had agreed to). But not giving a warning is crappy customer service, no matter how many other folks do likewise, how many years Pair has been doing other stuff well, or however else you want to spin it. In this case, it also happens to be a big sales screwup.

Re: Cause of YC/HN outage discovered

#96
I typically don't tell other people how to run their businesses, but if a similar issue brought my website down and I were to post about the causes, I might focus more on my failures in capacity planning, vendor selection, and monitoring rather than on my vendor's lackluster customer service. User-visible failures are, ultimately, process failures on my part, regardless of the surface cause. A nice side effect of this philosophy is that improvements to my processes help with all sorts of surface causes whereas if I were to address surface causes individually it would be like playing whack-a-mole. Bad vendor whack, hard drive failed whack, traffic spike whack, poor customer service whack, out of memory exception whack whack whack -- why is everyone conspiring to keep me from getting any work done.

Re: Cause of YC/HN outage discovered

#97
post #47

Earlier quoted context omitted.

Ya but if your dad wants to put up his pictures you go tell him to buy a nice scalable hosting product instead of a cheap shared hosting account for $5 to $10 a month?

No. I'd tell him to get a Facebook/Picasa/Flickr/Twitpic account. Dad used to get a shared hosting account for things like that, but now we have services that host content for free. They are much easier for Dad to use as well. In this age of $20/mo VPSs and free content hosting, I'm honestly not sure how shared hosting survives. It's not as flexible as a VPS for hosting sites (and with more than two sites, isn't even…

I'm honestly not sure how shared hosting survives.

John Smith Plumbing's five page brochureware site doesn't need the headaches of having a VPS but also won't accomplish business needs on Flickr.

Re: Cause of YC/HN outage discovered

#98
post #75

Earlier quoted context omitted.

Any particular reason for Slicehost as opposed to any of the other similar options (Linode, prgmr)? I'm not affiliated with any, though I run my site on VPSes from Linode. I was convinced by a Dec 2009 post by an HNer, uggedal: http://journal.uggedal.com/vps-performance-comparison

Me too. That post was detailed & fair. On slicehost I had a 256MB slice which I upgraded to 512MB slice to host 2 small websites. After the post got a 360MB linode VPS instead and am very happy with it. Edit: Slicehost help articles & resources, well organised & exhaustive is a plus though.

Re: Slicehost's help articles... Have you seen the Linode Library http://library.linode.com/ ?

Re: Cause of YC/HN outage discovered

#99
post #96

I typically don't tell other people how to run their businesses, but if a similar issue brought my website down and I were to post about the cause s , I might focus more on my failures in capacity planning, vendor selection, and monitoring rather than on my vendor's lackluster customer service. User-visible failures are, ultimately, process failures on my part, regardless of the surface cause. A nice side effect of t…

One obvious point is that HN is a peripheral part of YC's business, mostly aimed at recruiting, rather than something that's critical.

Re: Cause of YC/HN outage discovered

#100
post #96

I typically don't tell other people how to run their businesses, but if a similar issue brought my website down and I were to post about the cause s , I might focus more on my failures in capacity planning, vendor selection, and monitoring rather than on my vendor's lackluster customer service. User-visible failures are, ultimately, process failures on my part, regardless of the surface cause. A nice side effect of t…

[deleted]
Post reply on HN