Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Right now, Mesos agent enforces size limit of an executor and its tasks(s) on two locations:
- sandbox;
- persistent volume.
It will be great to explore whether we can also limit the size (at least the dynamic part) of a Mesos container, so that a container cannot write unbounded amount of data into its rootfs and use up all disk space w/o proper charged. It will even more awesome if these size change is naturally charged to the limit of disk resource.
One idea is to make the mutable directories involved in a rootfs created in executor's sandbox, which is size controlled.