Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could It also clear mesos tmp files? #19

Closed
rafaelcapucho opened this issue Oct 5, 2015 · 1 comment
Closed

Could It also clear mesos tmp files? #19

rafaelcapucho opened this issue Oct 5, 2015 · 1 comment

Comments

@rafaelcapucho
Copy link

Hello,

One of the problems I've is the size of this folder [1] increasing, When some execution fails on Mesos it is restarted by Marathon automatically, in a loop. And all dependency files are downloaded again and again.

I know that Custodian isn't directly related with Mesos/Marathon but if you use it you could offer a flag like --remove-mesos-residues.

[1] - /tmp/slaves//frameworks//executors

The Image attached is an example of restated failed app in a loop, and all those folders have the project resources downloaded again. It isn't an Custodian issue but a Enhancement Proposal.

6

Thank you

@solarkennedy
Copy link
Contributor

Cleaning up after mesos is outside the scope of docker-custodian.

I recommend:

  • taking advantage of Marathon's exponential backoff
  • enabling disk space isolation
  • registering a disk space attribute for your slaves so mesos doesn't fill up your disks
  • and if all else fails, tmpwatch'ing your sandbox directories here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants