Re:Under the Hood of Amazon EC2 Container Service
by werner on Tuesday July 21, 2015 @01:09AM
(#9920657)
Nope, we have built a new scheduler for you that will allow placement over multiple AZ's, replace failed containers, allow them to connect to ELB's, etc.
[ Parent
| on HN ]
Re:Under the Hood of Amazon EC2 Container Service
by 2461001642 on Tuesday July 21, 2015 @01:54AM
(#9920739)
Thanks for responding! Can you say how you deal with the significant latencies over multiple AZs?
Also, would you mind answering my other question about whether or not I can run Marathon or Chronos against ECS since it runs Mesos under the hood?
Re:Under the Hood of Amazon EC2 Container Service
by werner on Tuesday July 21, 2015 @02:43AM
(#9920830)
Can you elaborate on the intra- inter-* latencies your are seeing? for AZ independent services this should single digits.
Re:Under the Hood of Amazon EC2 Container Service
by 2461001642 on Tuesday July 21, 2015 @11:01AM
(#9922694)
When I'm balancing a single deployment across multiple AZs (e.g. US-East -> US-West), the latencies between the containers seem far higher than just the 200-300ms predicted by speed of light. Am I doing something wrong?
Re:Under the Hood of Amazon EC2 Container Service
by werner on Tuesday July 21, 2015 @02:40AM
(#9920820)
No mesos under the hood. You can bring mesos as your own scheduler.
Re:Under the Hood of Amazon EC2 Container Service
by 2461001642 on Tuesday July 21, 2015 @10:58AM
(#9922668)
Thanks again - this is really helpful. I had talked to someone who had left Amazon but knew the internal workings who said ECS was Mesos just privately branded like Chef -> OpsWorks, but I guess I must have misunderstood.
Thanks for clarifying!