Does Mesos support health checks for docker image tasks? Mesos seems to be
ignoring the TaskInfo.HealthCheck field for me.
Example TaskInfo JSON received back from Mesos:
{
>
> "name":"hello-app.web.v3",
>
> "task_id":{
>
> "value":"hello-app_web-v3.fc05a1a5-1e06-4e61-9879-be0d97cd3eec"
ker exec with the command you provided as
> health checks.
>
> It should be in the next release.
>
> Thanks!
>
> Tim
>
>
> On Oct 6, 2015, at 6:49 PM, Jay Taylor wrote:
>
> Does Mesos support health checks for docker image tasks? Mesos seems to
> be ign
Oops- Now I see you already said it's in master. I'll look there :)
Thanks again!
On Tue, Oct 6, 2015 at 6:59 PM, Jay Taylor wrote:
> Great, thanks for the quick reply Tim!
>
> Do you know if there is a branch I can checkout to test it out?
>
> On Tue, Oct 6, 2015
mesos/commit/09e367cd69aa39c156c9326d44f4a7b829ba3db7
> Are you use one of this version?
>
> On Wed, Oct 7, 2015 at 10:26 AM, haosdent wrote:
>
>> I remember 0.23.1 and 0.24.1 contains this backport, let me double check.
>>
>> On Wed, Oct 7, 2015 at 10:01 AM, Jay Taylor wrote:
>>
>>> Oops- No
ou use "exit 1" instead of "sleep 5" to see whether could see
> unhealthy status in your task stdout/stderr.
>
>> On Wed, Oct 7, 2015 at 10:38 AM, Jay Taylor wrote:
>> My current version is 0.24.1.
>>
>>> On Tue, Oct 6, 2015 at 7:30 PM, hao
is in your executor
> stdout
> ```
> Health check process launched at pid xxx
> ```
>
>> On Wed, Oct 7, 2015 at 11:37 AM, Jay Taylor wrote:
>> I'm happy to try this, however wouldn't there be output in the logs with the
>> string "health" or "
h its definition in taskinfo. Do you launch
> your task through Marathon? I could test it in my side.
>
>> On Wed, Oct 7, 2015 at 11:56 AM, Jay Taylor wrote:
>> Precisely, and there are none of those statements. Are you or others
>> confident health-checks are part
S1/frameworks/20150821-214332-1407297728-5050-18973-/executors/app-81-1-hello-app_web-v11.84c0f441-6d2a-11e5-98ba-080027477de0/runs/14335f1f-3774-4862-a55b-e9c76cd0f2da"
> --stop_timeout="0ns"
> --container="mesos-20150924-210922-1608624320-5050-1792-S1.14335f1f-3774-486
, thanks again for your help Haosdent!
Cheers,
Jay
On Wed, Oct 7, 2015 at 12:53 PM, Jay Taylor wrote:
> Hi Haosdent,
>
> Can you share your Marathon POST request that results in Mesos executing
> the health checks?
>
> Since we can reference the Marathon framework, I've be
apperIS6_EEEvEEE6_M_runEv
> @ 0x7f4a38a47e40 (unknown)
> @ 0x7f4a3825d182 start_thread
> @ 0x7f4a37f8a47d (unknown)
Do any of you know which host the path
"/tmp/mesos/slaves/16b49e90-6852-4c91-8e70-d89c54f25668-S1/frameworks/20150821-214332-1407297728-5050-18973-/executors/ap
7, 2015 at 8:11 PM, haosdent wrote:
> >Not sure what was going on with health-checks in 0.24.0.
> 0.24.1 should be works.
>
> >Do any of you know which host the path
> "/tmp/mesos/slaves/16b49e90-6852-4c91-8e70-d89c54f25668-S1/frameworks/20150821-214332-1407297728-5050-189
Using the health-check following parameters:
cmd="exit 1"
delay=5.0
grace-period=10.0
interval=10.0
timeout=10.0
consecutiveFailures=3
Sometimes the tasks are successfully identified as failing and restarted,
however other times the health-check command exits yet the task is left in
a running sta
x dir.
> Is it because MESOS_LAUNCHER_DIR is overrided in your other scripts?
>
>
>> On Fri, Oct 9, 2015 at 1:56 AM, Jay Taylor wrote:
>> I haven't ever changed MESOS_LAUNCHER_DIR/--launcher_dir before.
>>
>> I just tried setting both the env var and flag on the s
AUNCHER_DIR is overrided in your other scripts?
>
>
>> On Fri, Oct 9, 2015 at 1:56 AM, Jay Taylor wrote:
>> I haven't ever changed MESOS_LAUNCHER_DIR/--launcher_dir before.
>>
>> I just tried setting both the env var and flag on the slaves, and have
>
Following up on this:
This problem is reproducible when the command is "exit 1".
Once I set it to a real curl cmd the intermittent failures stopped and health
checks worked as advertised.
> On Oct 8, 2015, at 12:45 PM, Jay Taylor wrote:
>
> Using the health-check f
!
Jay
> On Oct 8, 2015, at 8:29 PM, Jay Taylor wrote:
>
> Maybe tomorrow I will build a fresh cluster from scratch to see if the broken
> behavior experienced today still persists.
>
>> On Oct 8, 2015, at 7:52 PM, haosdent wrote:
>>
>> As far as I kn
ould load as flags
> variables.
> https://github.com/apache/mesos/blob/master/3rdparty/libprocess/3rdparty/stout/include/stout/flags/flags.hpp#L52
>
>> On Fri, Oct 9, 2015 at 11:33 AM, Jay Taylor wrote:
>> One question for you haosdent-
>>
>> You mentioned that th
ur problem in my side. But I guess it maybe related to
>> this ticket. MESOS-1613 HealthCheckTest.ConsecutiveFailures is flaky
>>
>>> On Fri, Oct 9, 2015 at 12:13 PM, haosdent wrote:
>>> I think it maybe because health check exit before executor receive the
>>
problems after repeat tests, I still think it maybe cause
> by your build environment is not clear or have error configurations.
>
>> On Sun, Oct 11, 2015 at 11:02 PM, Jay Taylor wrote:
>> I was testing on a set of VMs on a lan with ideal very low latency.
>>
>>
ds":10,"interval_seconds":1,"timeout_seconds":1}
> --task_id=hello-app_web-v3.33597b73-1943-41b4-a308-76132eebcc91
> Health check process launched at pid: 11253
Any ideas on where to go from here? Is there any additional information I
can provide?
Thanks as always,
Jay
On Thu,
Is this theoretically feasible with Linux checkpoint and restore, perhaps via
CRIU?http://criu.org/Main_Page
> On Feb 18, 2016, at 4:35 AM, Paul Bell wrote:
>
> Hello All,
>
> Has there ever been any consideration of the ability to move in-flight
> containers from one Mesos host node to anoth
I just tried this but it appears my PR was closed without comment.
https://github.com/apache/mesos/pull/119
What am I missing here? :)
On Thu, Jun 30, 2016 at 1:45 PM, Benjamin Mahler wrote:
> Just a reminder. If you're using Mesos and want to be featured in our list
> of users, send a PR to g
n next to the notification it was closed
> you can see that it was pushed back to master on apache/mesos.
>
> On Thu, Jun 30, 2016 at 2:11 PM Jay Taylor wrote:
>
>> I just tried this but it appears my PR was closed without comment.
>>
>> https://github.com/apache/meso
Congratulations Haosdent!
You've frequently helped me out when I found myself in a Mesos-related
bind, so a big THANK YOU and EXTRA BIG CONGRATS is in order!
Glad to hear you're getting even more deeply involved in this project!
On Fri, Dec 16, 2016 at 10:59 AM, Vinod Kone wrote:
> Hi folks,
>
Greetings Mesonians,
What is the procedure for creating debian/ubuntu .deb distribution builds
of Mesos?
I am currently using https://github.com/deric/mesos-deb-packaging, but it
seems to add some dependencies (libunwind* and libcurl4-nss-dev) that the
mesosphere-hosted distributions do not, and
ster,
> mesos-slave, libmesos, java and python binding etc.
>
> Regards,
> Tomas
>
> On 4 August 2015 at 22:36, Jay Taylor wrote:
>
>> Greetings Mesonians,
>>
>> What is the procedure for creating debian/ubuntu .deb distribution builds
>> of Mesos?
&
Hey everyone,
I am writing a scheduler for Mesos and on of my first goals is to get
simple a docker container to run.
The tasks get marked as failed with the failure messages originating from
the slave logs. Now I'm not sure how to determine exactly what is causing
the failure.
The most informa
able by the Mesos UI.
>
> Tim
>
> On Thu, Aug 20, 2015 at 4:01 PM, Jay Taylor wrote:
>
>> Hey everyone,
>>
>> I am writing a scheduler for Mesos and on of my first goals is to get
>> simple a docker container to run.
>>
>> The tasks get marked as f
Eventually I was able to isolate what was going on; in this case the
FrameworkInfo.User was set to an invalid value and setting it to "root" did
the trick.
My scheduler is now working [in a basic form]!!!
Cheers,
Jay
On Thu, Aug 20, 2015 at 4:15 PM, Jay Taylor wrote:
> Hey Tim,
29 matches
Mail list logo
