Re: Consequences of health-check timeouts?

I'll make sure this gets fixed for 1.0. Apologies for the pain, it looks like there is a significant amount of debt in the docker containerizer / executor. On Wed, May 18, 2016 at 10:51 AM, Steven Schlansker < sschlans...@opentable.com> wrote: > > > On May 18, 2016, at 10:44 AM, haosdent

Re: Consequences of health-check timeouts?

> On May 18, 2016, at 10:44 AM, haosdent wrote: > > >In re executor_shutdown_grace_period: how would this enable the task > >(MongoDB) to terminate gracefully? (BTW: I am fairly certain that the mongo > >STDOUT as captured by Mesos shows that it received signal 15 just

Re: Consequences of health-check timeouts?

>In re executor_shutdown_grace_period: how would this enable the task (MongoDB) to terminate gracefully? (BTW: I am fairly certain that the mongo STDOUT as captured by Mesos shows that it received signal 15 just before it said good-bye). My naive understanding of this grace period is that it

Re: Consequences of health-check timeouts?

Hi Hasodent, Thanks for your reply. In re executor_shutdown_grace_period: how would this enable the task (MongoDB) to terminate gracefully? (BTW: I am fairly certain that the mongo STDOUT as captured by Mesos shows that it received signal 15 just before it said good-bye). My naive understanding

Re: Consequences of health-check timeouts?

>Is there some way to be given control (a callback, or an "exit" routine) so that the container about to be nuked can be given a chance to exit gracefully? The default value of executor_shutdown_grace_period is 5 seconds, you could change it by specify the `--executor_shutdown_grace_period` flag

Consequences of health-check timeouts?

Hi All, I probably have the following account partly wrong, but let me present it just the same and those who know better can correct me as needed. I've an application that runs several MongoDB shards, each a Dockerized container, each on a distinct node (VM); in fact, some of the VMs are on