Hi folks, We have been encountering container stuck issues for quite a long time. Some of these issues are caused by external components such as CNI/CSI plugins, custom Mesos modules, etc. Also, there were cases when a container become stuck due to a Linux kernel bug. All these kinds of issues make it difficult to debug container stuck issues.
We are proposing a container debug endpoint for the Mesos agent [1], which is based on a new mechanism for tracking pending libprocess futures [2]. Please review both of them. [1] Container debug endpoint: https://docs.google.com/document/d/1VtlKD6b8a22HzSdaJUeI7cPGuKd01vLwBJT4XfkeUDI [2] Tracking libprocess futures: https://docs.google.com/document/d/1Unu2pe0dRq3Z6XQ5S8lWZm2cU2REjfkUj0xk2ePQ0MY
