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

updog: Don't source migrations from a downloaded root image #416

Merged
merged 1 commit into from
Oct 16, 2019

Conversation

sam-aws
Copy link
Contributor

@sam-aws sam-aws commented Oct 15, 2019

Issue #, if available:
Fixes #414

Description of changes:
Updog downloads the root image before writing it to disk so that it can
be mounted and searched for existing migrations, in an effort to reduce
network traffic. However this has two problems in the current approach:

  • It doesn't solve the issue of trust for the "other" side when it boots
    and finds these migrations.
  • If run from a container with smaller cgroup limits (eg. dogswatch)
    it can invoke the OOM killer!

Be more conservative with memory and remove this approach. Future
patches will introduce a more trusted and less memory-hungry solution.

Signed-off-by: Samuel Mendoza-Jonas [email protected]

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Updog downloads the root image before writing it to disk so that it can
be mounted and searched for existing migrations, in an effort to reduce
network traffic. However this has two problems in the current approach:
- It doesn't solve the issue of trust for the "other" side when it boots
and finds these migrations.
- If run from a container with smaller cgroup limits (eg. dogswatch)
it can invoke the OOM killer!

Be more conservative with memory and remove this approach. Future
patches will introduce a more trusted and less memory-hungry solution.

Signed-off-by: Samuel Mendoza-Jonas <[email protected]>
@sam-aws
Copy link
Contributor Author

sam-aws commented Oct 15, 2019

Still need to properly test this as my build host is being slow 🐢

@sam-aws
Copy link
Contributor Author

sam-aws commented Oct 16, 2019

Tested updating normally with no other change in behaviour.

Copy link
Member

@jahkeup jahkeup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔭 🌥️ (you can hardly see the memory usage now)

@sam-aws sam-aws merged commit 7fbddfc into develop Oct 16, 2019
@sam-aws sam-aws deleted the deoptimized branch October 16, 2019 17:48
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

Successfully merging this pull request may close these issues.

updog update-image killed by oom-killer
3 participants