mesos task日志的保存时长

[官方文档](Apache Mesos)

Sandbox lifecycle

Sandbox files are scheduled for garbage collection when:

  • An executor is removed or terminated.

  • A framework is removed.

  • An executor is recovered unsuccessfully during agent recovery.

NOTE: During agent recovery, all of the executor’s runs, except for the latest run, are scheduled for garbage collection as well.

Garbage collection is scheduled based on the –gc_delay agent flag. By default, this is one week since the sandbox was last modified. After the delay, the files are deleted.

Additionally, according to the –disk_watch_interval agent flag, files scheduled for garbage collection are pruned based on the available disk and the –gc_disk_headroom agent flag. See the formula here.

–gc_delay=VALUE

Maximum amount of time to wait before cleaning up executor directories (e.g., 3days, 2weeks, etc). Note that this delay may be shorter depending on the available disk usage. (default: 1weeks)

–gc_disk_headroom=VALUE

Adjust disk headroom used to calculate maximum executor directory age. Age is calculated by:

gc_delay * max(0.0, (1.0 - gc_disk_headroom - disk usage))

every –disk_watch_interval duration. gc_disk_headroom must be a value between 0.0 and 1.0 (default: 0.1)

–disk_watch_interval=VALUEPeriodic time interval (e.g., 10secs, 2mins, etc) to check the overall disk usage managed by the agent. This drives the garbage collection of archived information and sandboxes. (default: 1mins)

original refer