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

journal: flush commit position on metadata shutdown #7385

Merged
merged 1 commit into from Jan 27, 2016

Conversation

trociny
Copy link
Contributor

@trociny trociny commented Jan 27, 2016

A crash was observed on JournalTrimmer destroy, which was called
by the Journaler after metadata shutdown. JournalTrimmer destructor
also calls flush_commit_position, but at that time metadata m_timer
is already null and it crushed there.

Signed-off-by: Mykola Golub mgolub@mirantis.com

A crash was observed on JournalTrimmer destroy, which was called
by the Journaler after metadata shutdown. JournalTrimmer destructor
also calls flush_commit_position, but at that time metadata m_timer
is already null and it crushed there.

Signed-off-by: Mykola Golub <mgolub@mirantis.com>
jdurgin added a commit that referenced this pull request Jan 27, 2016
journal: flush commit position on metadata shutdown

Reviewed-by: Josh Durgin <jdurgin@redhat.com>
Reviewed-by: Jason Dillaman <dillaman@redhat.com>
@jdurgin jdurgin merged commit 22e0c8f into ceph:master Jan 27, 2016
vuhuong pushed a commit to vuhuong/ceph-upstream that referenced this pull request Jan 27, 2016
The previous calculation was based upon the image's object size.
Since the cache stores smaller bufferheads, the object size is not
a good indicator of cache usage and was resulting in objects being
evicted from the cache too often.  Instead, base the max number of
objects on the memory load required to store the extra metadata
for the objects.

Fixes: ceph#7385
Backport: firefly, hammer
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit 0b37894)

Conflicts:
	src/librbd/ImageCtx.cc
        because hammer has cct->_conf->rbd_cache_size
        instead of cache_size
@trociny trociny deleted the fix-journal-flush-commit-position branch February 2, 2016 14:59
steveftaylor pushed a commit to steveftaylor/ceph that referenced this pull request May 4, 2016
The previous calculation was based upon the image's object size.
Since the cache stores smaller bufferheads, the object size is not
a good indicator of cache usage and was resulting in objects being
evicted from the cache too often.  Instead, base the max number of
objects on the memory load required to store the extra metadata
for the objects.

Fixes: ceph#7385
Backport: firefly, hammer
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit 0b37894)

Conflicts:
	src/librbd/ImageCtx.cc
        because firefly has cct->_conf->rbd_cache_size
        instead of cache_size
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants