There's no getting around it, frameworks on Mesos are distributed systems.
Distributed systems must deal with failures, and partitions (the two are indistinguishable from a system's perspective).
Concretely, what does this mean for frameworks? Mesos uses an actor-like message passing programming model, in which messages are delivered at-most-once. (Exceptions to this include task status updates, most of
| $ grep -R ::testing::Types src/tests -A 1 | |
| src/tests/isolator_tests.cpp:typedef ::testing::Types<PosixCpuIsolatorProcess, | |
| src/tests/isolator_tests.cpp- CgroupsCpushareIsolatorProcess> CpuIsolatorTypes; | |
| -- | |
| src/tests/isolator_tests.cpp:typedef ::testing::Types<PosixCpuIsolatorProcess> CpuIsolatorTypes; | |
| src/tests/isolator_tests.cpp-#endif // __linux__ | |
| -- | |
| src/tests/isolator_tests.cpp:typedef ::testing::Types<PosixMemIsolatorProcess, | |
| src/tests/isolator_tests.cpp- CgroupsMemIsolatorProcess> MemIsolatorTypes; | |
| -- |
| $ sudo ./bin/mesos-tests.sh --gtest_list_tests | grep -i cgroups | |
| ROOT_CGROUPS_Cfs | |
| ROOT_CGROUPS_Cfs_Big_Quota | |
| ROOT_CGROUPS_Sample | |
| CGROUPS_ROOT_PerfRollForward | |
| ROOT_CGROUPS_BalloonFramework | |
| CgroupsAnyHierarchyTest. | |
| ROOT_CGROUPS_Enabled | |
| ROOT_CGROUPS_Subsystems | |
| ROOT_CGROUPS_Mounted |
| ------------------------------------------------------------- | |
| Skipping Docker tests because validation failed | |
| [Error] Failed to execute 'docker version': exited with status exited with status 127 | |
| ------------------------------------------------------------- | |
| ------------------------------------------------------------- | |
| Skipping Docker tests because validation failed | |
| [Error] Failed to execute 'docker version': exited with status exited with status 127 | |
| ------------------------------------------------------------- | |
| ------------------------------------------------------------- | |
| Skipping Docker tests because validation failed |