Hello,
In our production env, we noticed that our disk filled up because one framework
had a lot of failed/completed executors folders laying around.
The folders eventually filled up the disk.
228M
/mnt/resource/slaves/c8674097-6e67-4609-b022-3e11de380fe5-S2/frameworks/35e600c2-6f43-402c-856f-9084c0040187-002/executors/52334.1.0
228M
/mnt/resource/slaves/c8674097-6e67-4609-b022-3e11de380fe5-S2/frameworks/35e600c2-6f43-402c-856f-9084c0040187-002/executors/52334.2.0
228M
/mnt/resource/slaves/c8674097-6e67-4609-b022-3e11de380fe5-S2/frameworks/35e600c2-6f43-402c-856f-9084c0040187-002/executors/52335.1.0
228M
/mnt/resource/slaves/c8674097-6e67-4609-b022-3e11de380fe5-S2/frameworks/35e600c2-6f43-402c-856f-9084c0040187-002/executors/52335.2.0
228M
/mnt/resource/slaves/c8674097-6e67-4609-b022-3e11de380fe5-S2/frameworks/35e600c2-6f43-402c-856f-9084c0040187-002/executors/52336.1.0
http://mesos.apache.org/documentation/latest/sandbox/#sandbox-lifecycle
<http://mesos.apache.org/documentation/latest/sandbox/#sandbox-lifecycle>
We have our lifecycle clean up set to the default which is 7days, I believe.
We wanted to know if this is the proper way to clean up the failed/completed
executors folders for a running framework?
OR does the framework need to be Inactive or Completed for the garbage
collection to work?
OR does the framework , itself, need to deal with cleaning up its own executors?
Bonus question: How does “gc_disk_headroom” actually work? This equation will
always return 0 it seems. gc_delay * max(0.0, (1.0 - gc_disk_headroom - disk
usage))
Thanks,
Venkat
