Skip to content

osd: bypass messenger for local EC reads#57237

Closed
rzarzynski wants to merge 1 commit intoceph:mainfrom
rzarzynski:wip-osd-ecreads-bypass-msgr
Closed

osd: bypass messenger for local EC reads#57237
rzarzynski wants to merge 1 commit intoceph:mainfrom
rzarzynski:wip-osd-ecreads-bypass-msgr

Conversation

@rzarzynski
Copy link
Contributor

@rzarzynski rzarzynski commented May 2, 2024

In order to fulfill a read request, an OSD needs to fetch chunks from remote shards as well as from its local ObjectStore. Currently, there is no distinction in handling between these sources – even local reads are served through the messenger, using its loopback connection. However, this requires some extra work to be spent on handling buffers, workqueues and executing requests. This commit implements the messenger bypass for reading from local store.

CC: @markhpc, @bill-scales.

(this commit has been dissected from a bigger WIP branch for crimson)

Contribution Guidelines

  • To sign and title your commits, please refer to Submitting Patches to Ceph.

  • If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

  • When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
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 cephadm
  • jenkins test api
  • jenkins test docs
  • jenkins render docs
  • jenkins test ceph-volume all
  • jenkins test ceph-volume tox
  • jenkins test windows
  • jenkins test rook e2e

@github-actions github-actions bot added the core label May 2, 2024
@markhpc markhpc self-requested a review May 2, 2024 14:17
@markhpc
Copy link
Member

markhpc commented May 2, 2024

@rzarzynski Oooh, this is a clever one. I'll try to review later unless @bill-scales gets to it first.

Copy link
Contributor

@bill-scales bill-scales left a comment

Choose a reason for hiding this comment

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

Changes look good, although I don't have authority to sign off the review yet.

The important part of the change is submitting the messages to read other OSDs first, then issuing the local synchronous read (which will block) so all the reads still happen in parallel. The write path already has this optimization for the local write and write reply so no further work is required there.

@rzarzynski rzarzynski marked this pull request as ready for review May 7, 2024 14:42
@rzarzynski rzarzynski requested a review from a team as a code owner May 7, 2024 14:42
Copy link
Contributor

@athanatos athanatos left a comment

Choose a reason for hiding this comment

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

Looks about right.

Signed-off-by: Radoslaw Zarzynski <rzarzyns@redhat.com>
@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days.
If you are a maintainer or core committer, please follow-up on this pull request to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

@github-actions github-actions bot added the stale label Aug 26, 2024
@github-actions
Copy link

This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution!

@github-actions github-actions bot closed this Sep 25, 2024
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.

6 participants