Hi guys,
Thanks for the swift feedback. I can confirm that tweaking
the task_launch_timeout setting in marathon and setting it to a value
bigger that the executor_registration_timeout setting in mesos fixed our
problem.
One sidenote though: the task_launch_timeout setting is in milli-seconds,
so
The case where Mesos loses track about these killed containers is going to
be fixed soon, have a reviewboard up and once it merged we shouldn't have
untracked containers.
Tim
On Fri, Oct 17, 2014 at 3:14 PM, Dick Davies d...@hellooperator.net wrote:
good catch! Sorry, the docs are right I just
Hi,
Environment:
- Clean vagrant install, 1 master, 1 slave (same behaviour on production
cluster with 3 masters, 6 slaves)
- Mesos 0.20.1
- Marathon 0.7.3
- Docker 1.2.0
Slave config:
- containerizers: docker,mesos
- executor_registration_timeout: 5mins
When is start docker container tasks,
Make sure you have --task_launch_timeout in marathon set to same value as
executor_registration_timeout.
https://github.com/mesosphere/marathon/blob/master/docs/docs/native-docker.md#configure-marathon
On 16 October 2014 10:37, Nils De Moor nils.de.m...@gmail.com wrote:
Hi,
Environment:
-
One gotcha - the marathon timeout is in seconds, so pass '300' in your case.
let us know if it works, I spotted this the other day and anecdotally
it addresses
the issue for some users, be good to get more feedback.
On 16 October 2014 09:49, Grzegorz Graczyk gregor...@gmail.com wrote:
Make sure
5 matches
Mail list logo
