mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Rukletsov <>
Subject Re: Review Request 59746: Stopped accounting aborted container launches as failures.
Date Thu, 18 Jan 2018 13:09:00 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Jan. 18, 2018, 1:09 p.m.)

Review request for mesos, Greg Mann, Ian Downes, Jie Yu, Joseph Wu, Jan Schlicht, and Vinod

Bugs: MESOS-7601

Repository: mesos


The container launch future might be failed or discarded (depending
on the containerizer implementation) if the launch has been aborted,
for example, a framework might have stopped while its task are being
started. Such failures should not be accounted as launch errors.


  src/slave/slave.cpp 50d2a10cd68f6611efd4e691e5325e6e0c06f33a 



`make check` on several Linux distros.

Additional manual tests for (1) mesos and (1) docker containerizers. The framework is asked
to exit right after it submits the task to mesos.

(1) With mesos c-zer
m: `./bin/ --work_dir=./m`
a: `GLOG_v=1 sudo ./bin/ --master=<ip>:5050 --work_dir=./a --containerizers=mesos
--image_providers="DOCKER" --isolation=filesystem/linux,docker/runtime`
f: `./src/mesos-execute --master=<ip>:5050 --containerizer=mesos --docker_image=fedora:25
--name=pull-test --command="sleep 1000"`

(2) With docker c-zer
m: `./bin/ --work_dir=./m`
a: `GLOG_v=1 sudo ./bin/ --master=<ip>:5050 --work_dir=./a --containerizers=docker`
f: `./src/mesos-execute --master=<ip>:5050 --containerizer=docker --docker_image=fedora:25
--name=pull-test --command="sleep 1000"`


Alexander Rukletsov

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message