HN user

warriormonk5

66 karma
Posts0
Comments30
View on HN
No posts found.

I agree with your take. It was obvious to my VP. It's not obvious to the rest of the enterprise (yet).

But I think it's just a matter of when not if.

My current guess at my slow fortune 500 is ~1-2 years before we see real employment impact.

Startups are happening now at least with my anecdotal conversations. Right now the discussion is more just slower growth than actually doing layoffs. That coin will flip at some point.

> American households, on average, have $41,600 in savings, according to data last collected by the Federal Reserve in 2019.

Average vs Median strikes again.

Median household has 4k. 70% don't break 10k.

It's the high end that weighs on that average pretty hard.

In my experience, a lot of people who live and reside in Los Angeles will take gigs in Georgia. Most people wouldn't actually live there minus their short stints to do the film they are involved in.

The author is incorrect about JSON in mysql. You can in fact index individual columns in your JSON. They end up being generated columns that you then index. Not as slick or mature as postgres, but it does exist.

Edit: audited the rest of the post. Author is otherwise correct. Occasionally ignores some (admittedly ugly) workarounds for some issues. All in all, great post.

So at it's peak we had ~160k Americans in Iraq. At Afghanistan peak, we had ~100k.

Chicago has ~11 times as many Americans. I'll take my chances with Chicago.

It's actually shows how remarkably low we were on the casualty rate in the wars we had. Far cry from the civil war (~25% casualty rate).

https://azure.microsoft.com/en-us/status/history/

Network Infrastructure - North Central US

Summary of impact: Between approximately 19:34 UTC and 21:04 UTC on 06 Nov 2017, customers in North Central US may have experienced degraded performance, network drops, or timeouts when accessing Azure resources hosted in this region. Engineers were aware of additional impact for customers using App Service in South Central US. Engineers determined that this was caused by an underlying Network Infrastructure Event in this region which remains under investigation.

Preliminary root cause: Engineers identified configuration change as the potential root cause.

Mitigation: Engineers performed a change to the service configuration to BGP and mitigate the issue.

Next steps: Engineers will continue to investigate to establish the full root cause in approximately 72 hours.

At some point (roughly around your size, maybe a little larger) you'll want to add dedicated master nodes with no data.

3 small boxes, master eligible, holding no data.

I love the writeup, having a way to reproduce data if your clusters fail is a definite must with ES.

I wonder what size of cluster they are using.

I have two clusters running.

Largest one is an ELK stack. 7 nodes (soon to be 8, we're logging too much :) ), no dedicated master nodes, ~3TBs of data (1.5TB data x 2 for the back up). Need to make sure they are split appropriately into availability zones in case you lose a cloud zone. Need to have the right # of minimum master nodes otherwise you can hit a split brain issue. 500GB SSD, 4vCPUs, 26gigs memory. It eats ~5 gigs an hour peak load without breaking a sweat. Can basically take any heavy query people have thrown at it kibana wise.