Lessons from 10 Years of Amazon Web Services

Re:Lessons from 10 Years of Amazon Web Services by bluecmd on Friday March 11, 2016 @04:21PM (#11269641)

So, with No SSH - how do you debug that one-off problem that is only on machine abc12? I'm not talking about mutating, I'm talking about attaching gdb to the process while it's handling requests. I'm talking about collecting CPU profiling information from production. Stuff like that.

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by seanp2k2 on Friday March 11, 2016 @06:37PM (#11270394)

https://speakerdeck.com/niteshkant/distributed-tracing-at-ne...

http://techblog.netflix.com/2012/06/scalable-logging-and-tra...

https://github.com/Netflix/vector

Not terribly easy, but possible. I agree that "never have to SSH" is a bad target because there will always be edge cases, but for the majority of things it's possible to troubleshoot at the cluster level given immutable infrastructure; all the systems will be doing the exact same thing given an input. Reality shows that this is a bit idealistic, but if you start finding that e.g. A certain set of requests cause weird behavior, you can look at what makes those requests different, then set up some routing logic to send them to a debug farm (using something like https://github.com/Netflix/zuul ).

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by mhw on Friday March 11, 2016 @04:32PM (#11269695)

Immutable Infrastructure is the modern day "have you tried turning it off and back on again?"

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by autotune on Friday March 11, 2016 @04:32PM (#11269696)

You could probably have a central logging service like graylog or logstash that automatically collects that information and just sort through the logs that way.

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by api on Friday March 11, 2016 @05:41PM (#11270070)

What if the problem is not diagnosable from logs?

In a perfect world production and development would be identical, all production issues would be easy to reproduce in development, and logging and error handling would be sufficient to diagnose any problem.

But what do you do when you have a problem that doesn't happen in a perfect world -- that you can't diagnose normally, doesn't occur in dev, shows nothing abnormal in logs, etc.? At some point you need the ability to inspect the actual thing. It's like diagnosing a problem with a bridge by doing experiments on a scale model replica. Doesn't always work.

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by autotune on Friday March 11, 2016 @07:38PM (#11270656)

In that case I'd agree with you, and you should still allow for the possibly of logging in via ssh, while aiming to reduce that need and focus on automation as much as possible, or as much as it's appropriate and possible for your environment, rather.

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by AznHisoka on Friday March 11, 2016 @04:57PM (#11269850)

What if that 1 server ran out of file handles and can no longer log to anywhere?

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by xxpor on Friday March 11, 2016 @05:15PM (#11269933)

Take the server out back and shoot it.

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by autotune on Friday March 11, 2016 @05:18PM (#11269951)

Launch a copy of that server with a new image (which I would hope is under a load balancer), update the sysctl.conf file template with a larger fs.file-max limit in whatever config management system you use for that instance, resume logging under freshly cloned instance.

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by dsp1234 on Friday March 11, 2016 @05:38PM (#11270059)

How would you know to do that at all? The proposed issue is that the file handles are exhausted. Thus logging doesn't actually work, and thus you don't know anything about the problem except 'it's not working'. Your solution presupposed that you have figured out the issue, but the question is how do you find out about the problem at all. Without SSH/debugger/whatever, what is the process to inspect the system to find the problem?

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by devonkim on Friday March 11, 2016 @10:28PM (#11271257)

After dealing with different enterprise systems in AWS for a few years now, I'd say that this is what AWS ELB feature to remove a system out of an ASG as part of its lifecycle exists for. If you aren't using similar horizontal scaling strategies, you have a disaster waiting to happen basically and basically deserve an outage you can't diagnose / RCA well. If you can't ssh in afterwards that means your provisioning for automation / instrumentation and you should stay be able to isolate attention to that part of an instance's lifecycle.

[ Parent | on HN ]

Re:Lessons from 10 Years of Amazon Web Services by autotune on Friday March 11, 2016 @07:33PM (#11270630)

Great question. I'd probably look into something like Sysdig Cloud that can collect that information through its own agent, or one of the tools mentioned by seanp2k2. I do also agree with his point on edge cases though, it should be the goal for the majority of your infrastructure while still allowing for edge cases.

[ Parent | on HN ]