Needless to say I opened a new tab, typed "n", and hit enter countless times today before my brain caught up with my muscle memory.
That said, HN does have quality content and the signal/noise is way better than sites designed specifically to keep you addicted.
I'd argue that this site has a good signal/noise ratio by design and specifically to keep you addicted (where "addicted" means using and constantly returning to the site). This site is just designed to attract people who are put off by the kinds of tricks employed elsewhere
Definitely thought the same. Then I realized that I'm browsing trough work VPN and had a second thought: what if our admins decided to fight procrastination?
When I saw hn was down, I double-checked the news to see if a major part of the internet had gone down.
I do this too, and it's because this site is an addictive slot machine just like every other social networking site. I actually really hate this website, but I'm here almost every day, because I can't seem to break the habit. Neat. It's probably because I have a common impulse control / executive functioning disorder, and the way the front page works exploits some bug in my brain.
Reddit does this to me too. I also hate Reddit.
It's a pretty universal issue. Companies are just getting better at using it to their advantage.
My solution: a 3-hour focus mode browser extension.
1. Install the BlockSite chrome extension [1]. 2. In BlockSite settings, add HN, Twitter, and any other distracting sites to the Focus Mode list and set Focus Mode time to 3 hours. 3. Ensure you uninstall all social media apps from your phone 4. When I find myself opening a new tab and typing "n" to get a dopamine hit, I then turn on my 3-hour focus mode.
[1] https://chrome.google.com/webstore/detail/blocksite-block-we...
with that said, the comments are the most addictive part of this site.
Why hate this site? Because it contains interesting/useful content often enough to make you come back? That'd be a weird reason to hate the site. I too have a common impulse control/executive functioning disorder, but I don't hate the things that it makes me vulnerable to. If I were feeling resentful, I'd have to put the blame on my condition.
I don't have to ask why you hate reddit, the valid reasons for hating reddit are myriad
I like wasting time on HN because it's time not actually wasted :)
And don't get me started on Twitter... Sure there are some gems on twitter but I have to wade through 1000s of tweets of pure nonsense to see them. No thanks. If it's something really great someone will post a link on HN anyway :)
... I might have been more productive than usual today.
Double disk failure is improbable but not impossible.
The most impressive thing is that there seems to be no dataloss, almost whatsoever. Whatever the backup system is, it seems rock solid.
It's not even improbable if the disks are the same kind purchased at the same time.
It was not awesome seeing a bunch of servers go dark in just about the order we had originally powered them on. Not a fun day at all.
The lesson I learned is that the three replacements went to different arrays and we never again let drives from the same batch be part of the same array.
e.g. Simultaneous Engine Maintenance Increases Operating Risks, Aviation Mechanics Bulletin, September–October 1999 https://flightsafety.org/amb/amb_sept_oct99.pdf
I guess proper redundancy is having different brands of equipment also in some cases.
Not doing it for this reason but rather financial ones :) But as I have a totally mixed bunch of sizes I have no RAID and a disk loss would be horrible.
Also, you shouldn't wait for disks to fail to replace them. HN's disks were used for 4.5 years, which is greater than the typical disk lifetime, in my experience. They should have replaced them sooner, one by one, in anticipation of failure. This would also allow them to stagger their disk purchases to avoid similar manufacturing dates.
It's actually surprisingly common for failover hardware to fail shortly after the primary hardware. It's normally been exposed to similar conditions to what killed the primary and the strain of failing over pushes it over the edge.
For load balancing I would consider this very likely because both are equally loaded. But "failover" I would usually consider a scenario where a second server is purely in wait for the primary to fail, in which case it would be virtually unused. Like an active/passive scenario as someone mentioned below.
But perhaps I got my terminology mixed up. I'm not working with servers so much anymore.
You know how they say to always test your backups? Always test your failover too.
Those responsible for the sacking have also been sacked.
each server has a pair of mirrored disks, so it seems we're talking about 4 drives failing, not just 2.
On the other hand the primary seems to have gone down 6 hours before the backup server did, so the failures weren't quite simultaneous.
Yes—I'm a bit unclear on what happened there, but that does seem to be the case.
Still, I see no reason for prioritizing that failure mode on a site like HN.
A long time ago we had a Dell server which was pre setup raid from Dell (don't ask, I didn't order it). Eventually one disk on this server died, what sucked was that the second disk in the raid array also failed only a few minutes later. We had to restore from backup which sucked but to our surprise when we opened the Dell server the two disks had sequential serial numbers. They came from the same batch at the same time. Not a good thing to do when you sell people pre configured raid systems at a mark up...
The latter is understandable, the former would be quite a surprise for such a popular site. That means that the machines have no disk redundancy and the server is going down immediately on disk failure. The fallback server would be the only backup.
Primary failure: https://news.ycombinator.com/item?id=32024036 Standby failure: https://twitter.com/HNStatus/status/1545409429113229312
Also I remember the "Why we're going with Rails" story on the front page from before it went down.
Good news for people who were banned, or for posts that didn't get enough momentum :)
edit: Was restored from backup.. so def. dataloss
Were they connected on the same power supply? I had 4 different disks fail at the same time before, but they were all in the same PC... (lightning)
sounds like it is run by one guy
EDIT: My response was based on some edits that are now removed.
I realized how little of this I find elsewhere in my life - whether through Reddit or even my IRL friend circles.
This realization saddens me - I feel like I shouldn’t have to rely on HN so much to scratch this particular itch.
Perhaps I need to get out more.
> Perhaps I need to get out more.
Another way to look at it is that you have a particular set of interests and HN is the online outlet that serves those interests. There's nothing wrong with that, at all and you don't need to have multiple sources for it. No different than someone who likes to ride bikes owning one bike, or someone who likes to read going to the same local library every week for 10 years.
I think I’m just realizing I need to find that in more places, regardless of topic focus.
Whereas, if HN closes, there is no equivalent replacement available.
But I'm too lazy to write the application. I wish there was some SDK I could spin up, like PHPBB back in the days, to have something exactly like HN.
Not that I deserve or expect one from a free service, but because I enjoy reading postmortems from failures where both the primary and backup systems failed, I like to see what holes I might have in my own failover setup.
Tell HN: HN Moved from M5 to AWS - https://news.ycombinator.com/item?id=32030400 - July 2022 (116 comments)
Ask HN: What'd you do while HN was down? - https://news.ycombinator.com/item?id=32026639 - July 2022 (218 comments)
HN is up again - https://news.ycombinator.com/item?id=32026571 - July 2022 (314 comments)
I'd particularly look here: https://news.ycombinator.com/item?id=32026606 and here: https://news.ycombinator.com/item?id=32031025.
If you scroll through my comments from today via https://news.ycombinator.com/comments?id=dang&next=32039936, there are additional details. (Sorry for recommending my own comments.)
If you (or anyone) skim through that stuff and have a question that isn't answered there, I'd be happy to take a crack at it.
https://check-host.net/ip-info?host=https://news.ycombinator...
https://search.arin.net/rdap/?query=50.112.136.166
Note: HN has been on M5 hosting for years and they were still there as of 16-hours ago per Dang:
https://news.ycombinator.com/item?id=32024105
During the outage, listed places to check HN related systems, posted them here:
I definitely spent a non-reasonable amount of time thinking my internet had a problem trying to open HN since it's always just been so constant.
Edit - HN is on AWS now. https://news.ycombinator.com/item?id=32026571
But even comparing the apples to the oranges, this HN status page someone else pointed out https://hn.hund.io/ seems to show that HN has had more than one outage in just the past month. All but today's and last night's being quite short, but still. Sometimes you need some extra complexity if you want to make it to zero downtime overall.
That's not something the HN website needs but I think AWS is doing fine even if that's your point of comparison.
I know old posts indicate it’s running on a low core count but high frequency Intel CPUs on FreeBSD and no database (just flat files).
I wonder if it’s still the same.
HN is running on an old laptop from Viaweb.
Arc is running under the pg user and it's used as the process supervisor.
The actual web server is a VB app running on Linux through Wine.
The flat files have been migrated to an MS Access DB, also running through Wine.
Thank you to everyone who keeps this thing running.
8 hours of downtime in a given year is 99.9%, so only three nines. The major SaaS platforms all are basically at least as resilient as this, and most have more stringent SLAs.
Plus, it's hard to quantify many cases because there is hard-down and soft-down (partial interruptions).
"Did you unplug the router?"
It feels like we've lost a lot of that observability and immediacy with the cloud. It's not as easy to quickly understand the larger picture. You can understand the state of various services with the web console or command line tools but tracing a path through those services is much less obvious and efficient.
I'm kind of nervous to even discuss this as I wonder if it's just my age showing, especially since I see very people mention this as one of the downsides of various cloud solutions. Maybe I'm just jaded?
In all seriousness, at least 2/3rds of the complexity is because of your choice of tools and approach. Terraform alone makes things significantly more complex. If you just want to trigger a deployment, then a Template Spec made from a Bicep file could be banged out in like... an hour.[1]
When in Rome, do as the Romans do. You basically took a Microsoft product and tried to automate it with a bunch of Linux-native tools. Why would you think this would be smooth and efficient?
Have you ever tried automating Linux with VB Script? This is almost the same thing.
[1] Someone had a similar example here using Logic Apps and a Template Spec: https://cloudjourney.medium.com/azure-template-spec-and-logi...
> I normally bill for cloud automation advice, but the gist is
Can you please omit supercilious swipes from your comments here? Everybody knows different things. If you know more than someone else about $thing, that's great—but please don't put them down for it. That's not in the spirit of kindness and curious conversation that we're hoping for here.
https://news.ycombinator.com/newsguidelines.html
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...
And talk is cheap. I dare you to write a blog post or make a public GitHub repo doing the equivalent work (see Goals section) with your own tools. If you can, I'll be super impressed (not that my admiration is worth anything ).
One thing you'll run into is that AD roles and other authn aren't accessible via ARM templates/Bicep
% host news.ycombinator.com
news.ycombinator.com has address 50.112.136.166
and also interesting: DNS TTL is set to 1 (one).
NetRange: 50.112.0.0 - 50.112.255.255
CIDR: 50.112.0.0/16
NetName: AMAZON-EC2-USWESTOR
NetHandle: NET-50-112-0-0-1
Parent: NET50 (NET-50-0-0-0-0)
NetType: Direct Allocation
OriginAS: AS14618
Organization: Amazon.com, Inc. (AMAZO-47)It's great that they were able to spin it up in the cloud for recovery purposes. But it's more legendary on a real server <3
Yes I'm old :P
Anyone been on Slashdot lately? Checked it out too was really nice.
Over a year with no issues. Impressive.
This logs lesser ones: https://hn.hund.io/
Couldn't possibly have been HN that was the problem haha
I reset the router... and HN was still down.
<sniff>
True appreciation to the team who works to keep it up, high-quality, and impactful.
At the early 00's, when Google went offline I wouldn't believe it, and go check my connection (even if I was fetching other sites at the same time). Looks like nowadays HN is in that place.
[1] https://twitter.com/HNStatus
[2] https://www.reuters.com/business/media-telecom/rogers-commun...
Early on /. was amazing! Remember Cmdrtaco it all out, often taking us for the ride?
Good times, frequently good discussion.
HN has been better for years now, was better at inception, for the most part.
/. has improved a bit. Good to see, or I caught it on a good day.
Is it more appropriate to call the strategy in this case fallback, or failover? Since the secondary server wasn't running in production until the first one failed, it sounds like fallback?
Perhaps higher reliability strategies would have been instead of having a secondary server, just have more mirrored disks on the main server, to reduce the likelihood of the array being compromised?
Alternatively, to run both the primary and secondary servers in production all the time. But that would presumably merely move the single point of failure to the proxy?
[0] https://aws.amazon.com/builders-library/avoiding-fallback-in...
https://news.ycombinator.com/item?id=32026565
The ones after it are hours later and usually deleted, until this post (...71).
WELL TODAY WAS VERY INCONVENIENT LET ME TELL YOU! :)
Thanks Dang and company.
I appreciate you all.
@my HN peers:
Have a great weekend and thank you all for being you. I learn a ton here and enjoy the perspectives often found on these pages. It is all high value.
GitHub page for that project: https://github.com/clintonwoo/hackernews-remix-react
I was worried that I may actually have to go out and do things instead of lurking here this weekend..
Visiting a HN is everyday morning ritual to me.
Wasn't cloud flare down for a few hours recently... Cloud providers don't magically fix outages...
127.0.0.1 news.ycombinator.com # REQUIRED for meaningful productivityDoes that mean nothing of value was lost?
Edit: 100 points in 4 minutes
I'm sorry, this kind of thing reeks of point "whoring" to me, and I consider that to be an indefensible thing to do; it's pollution. We can see the site. We know it's up. We don't need to be told. Stop doing things purely to increase your score. This isn't a game. Etc.
I'm not sure I believe you what is your source for this ;)
https://twitter.com/HNStatus/status/1545461511870566400
Disk and fallback server failure. Was definitely a long day for their ops team, on a Friday no less.
Disclaimer: I did not cause it.
Would you please stop spamming your opinion ? You wrote it once, it's enough.
Thank you very much <3
Perfectly acceptable.