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

Aggressively GC dead containers #13287

Closed
pwittrock opened this issue Aug 28, 2015 · 3 comments
Closed

Aggressively GC dead containers #13287

pwittrock opened this issue Aug 28, 2015 · 3 comments
Labels
sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@pwittrock
Copy link
Member

We currently keep dead containers around for several reasons:

  1. To keep container logs and other data around
  2. To keep a record of the container state
  • It is possible for the container to be GCed before we no longer need this state

We could address these in other ways by:

  1. Storing records for dead containers elsewhere (perhaps the api server?)
  2. Rotating log data to a permanent location (fluentd?)

This would allow us to immediately GC containers once their state and logs had been exported. It would also ensure that we did not lose state or log data due to premature garbage collection.

@dalanlan
Copy link
Contributor

/cc @dalanlan

@dalanlan
Copy link
Contributor

Just to mention, the logs stored elsewhere could be safely removed some time actually (those logs of a container corpse within a deleted pod, for example). The logs could take up space after all.

@bprashanth bprashanth added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Aug 28, 2015
@yujuhong
Copy link
Contributor

Closing this in favor of #26923

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

4 participants