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

osd: WBThrottle::clear_object: signal on cond when we reduce throttle values #5822

Merged
1 commit merged into from Oct 20, 2015

Conversation

Projects
None yet
4 participants
@smithfarm
Contributor

smithfarm commented Sep 5, 2015

WBThrottle::clear_object: signal if we cleared an object
Fixes: #12223
Signed-off-by: Samuel Just <sjust@redhat.com>
(cherry picked from commit 8447b08)

@smithfarm smithfarm self-assigned this Sep 5, 2015

@smithfarm smithfarm added this to the firefly milestone Sep 5, 2015

ghost pushed a commit that referenced this pull request Oct 20, 2015

Merge pull request #5822: WBThrottle::clear_object: signal on cond wh…
…en we reduce throttle values

Reviewed-by: Loic Dachary <ldachary@redhat.com>
@ghost

This comment has been minimized.

ghost commented Oct 20, 2015

@dzafman does this backport look good to merge ? It passed a run of the firefly rados suite ( see http://tracker.ceph.com/issues/11644#note-110 ). Note that there was a valgrind issues but it is unrelated and fixed by #6325.

@dzafman

This comment has been minimized.

Member

dzafman commented Oct 20, 2015

LGTM

ghost pushed a commit that referenced this pull request Oct 20, 2015

Loic Dachary
Merge pull request #5822 from SUSE/wip-12837-firefly
WBThrottle::clear_object: signal on cond when we reduce throttle values

Reviewed-by: David Zafman <dzafman@redhat.com>

@ghost ghost merged commit f48450b into ceph:firefly Oct 20, 2015

@smithfarm smithfarm deleted the SUSE:wip-12837-firefly branch Oct 21, 2015

@ghost ghost changed the title from WBThrottle::clear_object: signal on cond when we reduce throttle values to osd: WBThrottle::clear_object: signal on cond when we reduce throttle values Oct 24, 2015

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment