hi Jojy,
Unfortunately, I haven't been able to reproduce this issue on demand, it
has just happened spontaneously a few times. So I cannot say for sure if
it would happen on a newer mesos/kernel version. I'm thinking of trying to
force reproduction by creating and destroying a ton of cgroups,
Hi Eric,
Thanks again for the information. The value of 0 for
*/cgroup/cpu/cpu.cfs_* files looks suspicious.
Since you are motivated to look into kernel, here is what I think is
interesting.
- The shed_debug print
Hi Erik
Happy to work on this with you. Thanks for the details.
As you might know, in cfs_rq:/ (from /proc/sched_debug), is the
CPU cgroup hierarchy name. I am curious about the contents and cgroups
hierarchy when this happens. Could you send the “mesos” hierarchy (directory
tree) and
hey Jojy, Thanks for your reply. Response inline.
On Thu, Dec 31, 2015 at 11:31 AM, Jojy Varghese wrote:
> > Are /foo/bar cgroups hierarchical such that /foo missing would prevent
> > /foo/bar tasks from being scheduled? i.e., might that be the root
> cause of
> > why
> Are /foo/bar cgroups hierarchical such that /foo missing would prevent
> /foo/bar tasks from being scheduled? i.e., might that be the root cause of
> why the kernel is ignoring these tasks?
Was curious why you said the above. CPU scheduling shares are a function of
their parent’s CPU