Skip to content

luminous: os/bluestore/BlueFS: compact log even when sync_metadata sees no work #34876

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

Merged
merged 1 commit into from
Jul 13, 2020

Conversation

ifed01
Copy link
Contributor

@ifed01 ifed01 commented May 1, 2020

backport of #17354 to luminous


It's possible that when sync_metadata() is called there won't be any new
log data to flush because it was already flushed for other reasons (e.g.,
because fsync was called). However, the log may still be large and in
need of compaction.

Signed-off-by: Sage Weil sage@redhat.com
(cherry picked from commit dfe5f05)

Checklist

  • References tracker ticket
  • Updates documentation if necessary
  • Includes tests for new functionality or reproducer for bug

Show available Jenkins commands
  • jenkins retest this please
  • jenkins test classic perf
  • jenkins test crimson perf
  • jenkins test signed
  • jenkins test make check
  • jenkins test make check arm64
  • jenkins test submodules
  • jenkins test dashboard
  • jenkins test dashboard backend
  • jenkins test docs
  • jenkins render docs
  • jenkins test ceph-volume all
  • jenkins test ceph-volume tox

Sorry, something went wrong.

@ifed01 ifed01 added this to the luminous milestone May 1, 2020
@ifed01 ifed01 requested a review from smithfarm May 1, 2020 11:34
@ifed01 ifed01 changed the title os/bluestore/BlueFS: compact log even when sync_metadata sees no work luminous: os/bluestore/BlueFS: compact log even when sync_metadata sees no work May 1, 2020
@smithfarm smithfarm requested a review from xiexingguo May 4, 2020 10:16
@smithfarm
Copy link
Contributor

@ifed01 I tried to cherry-pick this and there was a conflict in BlueFS::sync_metadata. Did you see the same? If so, could you add a Conflicts section to the commit message?

@smithfarm smithfarm requested review from jdurgin and neha-ojha May 4, 2020 10:31
It's possible that when sync_metadata() is called there won't be any new
log data to flush because it was already flushed for other reasons (e.g.,
because fsync was called).  However, the log may still be large and in
need of compaction.

Signed-off-by: Sage Weil <sage@redhat.com>
(cherry picked from commit dfe5f05)

 Conflicts:
	src/os/bluestore/BlueFS.cc
 Some pending release stuff that is now absent at both Luminous and
master.
@ifed01 ifed01 force-pushed the wip-ifed-fix-no_compact_bluefs branch from 0975efb to 5eeb70b Compare May 5, 2020 12:35
@ifed01
Copy link
Contributor Author

ifed01 commented May 5, 2020

@ifed01 I tried to cherry-pick this and there was a conflict in BlueFS::sync_metadata. Did you see the same? If so, could you add a Conflicts section to the commit message?

@smithfarm - my bad, there was a conflict. Fixed.

@yuriw
Copy link
Contributor

yuriw commented Jul 8, 2020

@yuriw yuriw merged commit 3b0fd4b into ceph:luminous Jul 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants