805 karma · joined August 21, 2012
[ my public key: https://keybase.io/jensrantil; my proof: https://keybase.io/jensrantil/sigs/lxsQ3_wfe5J1Akf75bO42UAhjVdv3TPY0WoT01wbMJA ]
Very few people know about this and it's really scary. I'm happy people are voting this up to increase some awareness of this.
Potential workarounds: You might think disabling `proxy_next_upstream timeout` will do, but that will also disable connection timeout retry which is not what you want!
Increasing `proxy_connect_timeout` is not an option, because then you risk filling up too many connections in the nginx instance if the upstream server swallows SYN packets or whatnot.
The real workaround: Use haproxy. Serioously.
Sure you have Cloudera et al., but I'm still trying to figure out if they really make things easier or worse when it two weeks later comes to figuring out why something is broken, or how to start/install additional Hadoop components.
The solution is simple. Put an infrared camera on the front of the gun. If there's anything warm in front of the gun it simply wont fire. That will make it impossible to shoot other people and only limitting it to cans etc. Possibly you could also use a real camera and do some image analysis to keep the gun from shooting other sensitive objects, such as gas containers etc. Obviously, the firing of the gun will be locked if you take the camera(s) off.
Okay, I admit it. I'm not being serious. A gun is a weapon. The fact that guns are weapons is the problem. There's no technical solution for that.
The only technical solution that will make a gun safe is one that destroys that weapon.
I've heard many smart people recommend having a bunch of small problems to always think of. I think Richard Feynman recommended it.
Some examples of these kind of mental problems that I've been dealing with over the years:
* How long does it take from the time that the planets are aligned to the time that they are aligned once again. This was a problem I thought of in ninth grade and was the reason why I learn programming at that age on my spare time.
* How does one construct a P2P filesharing application that does not have a central single-point of failure. I thought about this for a year or so in high school. Obviously, I also wanted anonyminity for the users if possible.
* Dreaming about the perfect configuration management.
* Mining common log line patterns and automatically extracting useful information for debugging, surveillance etcetera. How I would scale such an application, what it could be used for etcetera. This actually resulted in https://github.com/JensRantil/disco-slct
* Last year or so; How to develop a web application that uses CQRS, event sourcing and a distributed model. This also involves thinking about how this would enable smooth upgrading of subsystems, scaling of such system and security.