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

mds: release pool allocator memory after exceeding size limit #12443

Merged
merged 2 commits into from Dec 14, 2016

Conversation

jcsp
Copy link
Contributor

@jcsp jcsp commented Dec 12, 2016

John Spray added 2 commits December 12, 2016 12:02
Usually we like keeping the memory in our pools, but in circumstances
where we have violated our self-imposed inode count cap, we should
shrink our usage of system memory afterwards.

Fixes: http://tracker.ceph.com/issues/18225
Signed-off-by: John Spray <john.spray@redhat.com>
...now that it's used more than once place, copying around
the fraction was bad.

Signed-off-by: John Spray <john.spray@redhat.com>
@jcsp jcsp added cephfs Ceph File System feature labels Dec 12, 2016
Copy link
Member

@gregsfortytwo gregsfortytwo left a comment

Choose a reason for hiding this comment

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

Reviewed-by: Greg Farnum gfarnum@redhat.com

@gregsfortytwo
Copy link
Member

Hmm, we should probably add a quick check for this functioning somewhere though. Maybe it can ride along on some of the fill-the-cache teuthology tests?

@david-z
Copy link
Member

david-z commented Dec 14, 2016

Hi guys,

I can help to merge this commit into our internal ceph code base to have a quick check since I threw the question in the email few days ago and we have ready-made cluster at hand. What do you think?

@jcsp jcsp merged commit 8d4a95d into ceph:master Dec 14, 2016
@jcsp jcsp deleted the wip-18225 branch December 14, 2016 12:52
@jcsp
Copy link
Contributor Author

jcsp commented Dec 14, 2016

@david-z I've merged this since it passes our regression tests, but if you could also test that it really behaves as expected that would be great.

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