Skip to content

os/bluestore: Refactoring reshard_range#62263

Closed
Jayaprakash-ibm wants to merge 1 commit intoceph:mainfrom
Jayaprakash-ibm:wip-refactor-reshard-range
Closed

os/bluestore: Refactoring reshard_range#62263
Jayaprakash-ibm wants to merge 1 commit intoceph:mainfrom
Jayaprakash-ibm:wip-refactor-reshard-range

Conversation

@Jayaprakash-ibm
Copy link
Contributor

@Jayaprakash-ibm Jayaprakash-ibm commented Mar 12, 2025

Refactored ExtentMap::reshard() by splitting it into two distinct functions:

  • reshard_decision(): Determines the resharding plan by analyzing shard distribution, extent sizes, and spanning blob ranges.
  • reshard_action(): Applies the resharding plan, handling faulting, key removals, and shard updates.

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

Copy link
Member

@batrick batrick left a comment

Choose a reason for hiding this comment

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

Please title your commits according to the conventions of this project. This is required for your PR to be merged.

See this article on GitHub on how to amend commits and update your pull request.

@batrick
Copy link
Member

batrick commented Mar 12, 2025

Your commit should also have a rationale for the change.

@aclamk aclamk added the aclamk-testing-nauvoo bluestore testing label Mar 19, 2025
@Jayaprakash-ibm Jayaprakash-ibm force-pushed the wip-refactor-reshard-range branch from f2e0a9f to a74137a Compare March 28, 2025 11:54
@Jayaprakash-ibm Jayaprakash-ibm marked this pull request as ready for review March 28, 2025 11:54
@Jayaprakash-ibm Jayaprakash-ibm requested a review from a team as a code owner March 28, 2025 11:54
…d action phases

Refactored ExtentMap::reshard() by splitting it into two distinct functions:
- reshard_decision(): Determines the resharding plan by analyzing shard distribution, extent sizes, and spanning blob ranges
- reshard_action(): Applies the resharding plan, handling faulting, key removals, and shard updates

Signed-off-by: Jaya Prakash <jayaprakash@ibm.com>
@Jayaprakash-ibm Jayaprakash-ibm force-pushed the wip-refactor-reshard-range branch from a74137a to 44f93a6 Compare April 4, 2025 11:01
@Jayaprakash-ibm Jayaprakash-ibm requested review from aclamk and batrick and removed request for a team April 4, 2025 11:02
@github-actions
Copy link

github-actions bot commented Apr 9, 2025

This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved

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.

3 participants