You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gilbert Song (JIRA)" <ji...@apache.org> on 2019/07/09 00:03:00 UTC
[jira] [Created] (MESOS-9883) Check container timeout counting
should be started when the check command is executed.
Gilbert Song created MESOS-9883:
-----------------------------------
Summary: Check container timeout counting should be started when the check command is executed.
Key: MESOS-9883
URL: https://issues.apache.org/jira/browse/MESOS-9883
Project: Mesos
Issue Type: Improvement
Components: containerization
Reporter: Gilbert Song
Right now the check container timeout counting is started when the checker process sends the request to the agent API. This may not be what users are expecting, and sometimes it may take longer for the agent process to launch a check container if the agent is under a heavy workload. This could lead to the health check being failed if the timeout is small and the agent is slow.
In common sense, users may expect the timeout to be just the timeframe that the command should finish. So that users could better define the health check timeout.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)