mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilbert Song (JIRA)" <>
Subject [jira] [Commented] (MESOS-8489) LinuxCapabilitiesIsolatorFlagsTest.ROOT_IsolatorFlags is flaky
Date Wed, 28 Mar 2018 19:42:00 GMT


Gilbert Song commented on MESOS-8489:

[~abudnik], thanks for the triaging. However, I think we did not understand this issue deep
# The race description seems not accurate enough to me. The race is between the destruction
of the first cluster::slave and the orphan container destroy in the second slave's recovery
path. We should reset the Owned pointer first before we call next StartSlave(). (This would
fix the flakiness in this unit test)
# We need to understand why the nested *test* cgroup is still there when we create the first
slave, since it is just a simple os::rmdir(). This is the trigger of the flakiness. The *test*
cgroup is supposed to be created and removed immediately. There might be a bug in cgroup::remove().
# The nested *test* cgroup may no longer be needed since it was a workaround for old kernel
versions. Could you do some investigations on whether this is supported by kenel version later
than 2.6? We may be able to remove these code and document it (Still need to understand #2

> LinuxCapabilitiesIsolatorFlagsTest.ROOT_IsolatorFlags is flaky
> --------------------------------------------------------------
>                 Key: MESOS-8489
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>            Reporter: Andrei Budnik
>            Assignee: Andrei Budnik
>            Priority: Major
>              Labels: containerizer, flaky-test, mesosphere
>         Attachments: ROOT_IsolatorFlags-badrun3.txt
> Observed this on internal Mesosphere CI.
> {code:java}
> ../../src/tests/cluster.cpp:662: Failure
> Value of: containers->empty()
>   Actual: false
> Expected: true
> Failed to destroy containers: { test }
> {code}
> h2. Steps to reproduce
>  # Add {{::sleep(1);}} before [removing|] "test"
>  # recompile
>  # run `GLOG_v=2 sudo GLOG_v=2 ./src/mesos-tests --gtest_filter=LinuxCapabilitiesIsolatorFlagsTest.ROOT_IsolatorFlags
--gtest_break_on_failure --gtest_repeat=10 --verbose`
> h2. Race description
> While recovery is in progress for [the first slave|],
calling [`StartSlave()`|]
leads to calling [`slave::Containerizer::create()`|]
to create a containerizer. An attempt to create a mesos c'zer, leads to calling [`cgroups::prepare`|].
Finally, we get to the point, where we try to create a ["test" container|]. So,
the recovery process for the first slave [might detect|]
this "test" container as an orphaned container.
> Thus, there is the race between recovery process for the first slave and an attempt to
create a c'zer for the second agent.

This message was sent by Atlassian JIRA

View raw message