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

Increase sys container usageBytes upper bound #35828

Merged
merged 1 commit into from
Oct 29, 2016

Conversation

timstclair
Copy link

@timstclair timstclair commented Oct 28, 2016

Fix one of flakes in #34990

UsageBytes can grow large since it's only cleaned up under memory pressure.


This change is Reviewable

@timstclair timstclair added the release-note-none Denotes a PR that doesn't merit a release note. label Oct 28, 2016
@yujuhong yujuhong added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 28, 2016
@k8s-github-robot k8s-github-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 28, 2016
@timstclair
Copy link
Author

Labeling p2 to fix flakes.

@timstclair timstclair added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Oct 28, 2016
@foxish foxish added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Oct 29, 2016
@foxish
Copy link
Contributor

foxish commented Oct 29, 2016

Setting to P0 as kubelet-gce-e2e-ci is failing constantly and blocking the submit-queue.

@foxish foxish merged commit 2efdd9e into kubernetes:master Oct 29, 2016
k8s-github-robot pushed a commit that referenced this pull request Oct 31, 2016
Automatic merge from submit-queue

Bump Kubelet workingset upper bound

For #34990

Follow up to #35828, because working memory is too high now too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants