Skip to content

crimson: Avoid to call try_acquire_throttle_now via budget_available#62006

Closed
mohit84 wants to merge 1 commit intoceph:mainfrom
mohit84:pg_recovery_try_acquire_throttle
Closed

crimson: Avoid to call try_acquire_throttle_now via budget_available#62006
mohit84 wants to merge 1 commit intoceph:mainfrom
mohit84:pg_recovery_try_acquire_throttle

Conversation

@mohit84
Copy link
Contributor

@mohit84 mohit84 commented Feb 26, 2025

Avoid try_acquire_throttle_now via budget_available and return a true due to this the recovery progress is stuck because try_acquire_throttle_now increase the counter(in_progress) but does not release a throttle to decrease the counter.

Fixes: #https://tracker.ceph.com/issues/70180

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

@mohit84 mohit84 requested a review from a team as a code owner February 26, 2025 11:55
@mohit84 mohit84 requested a review from Matan-B February 26, 2025 11:55
@mohit84
Copy link
Contributor Author

mohit84 commented Feb 26, 2025

jenkins test make check

Copy link
Contributor

@Matan-B Matan-B left a comment

Choose a reason for hiding this comment

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

It's not completely "Fixes" the issue described but only avoids it for now.
Can you please add the tracker as a comment above the commented out code? That way it should be easier to understand the context over why it's commented out.

edit: instead of creating a tracker which fixes the issue by avoiding it - I've updated the tracker so that it reflects the required changes - See: https://tracker.ceph.com/issues/70180.

Avoid try_acquire_throttle_now via budget_available and return a true
due to this the recovery progress is stuck because
try_acquire_throttle_now increase the counter(in_progress) but
does not release a throttle to decrease the counter.

Fixes: #https://tracker.ceph.com/issues/70180
Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
@mohit84 mohit84 force-pushed the pg_recovery_try_acquire_throttle branch from 79d3d0a to 2d54369 Compare February 27, 2025 04:08
@mohit84
Copy link
Contributor Author

mohit84 commented Feb 27, 2025

It's not completely "Fixes" the issue described but only avoids it for now. Can you please add the tracker as a comment above the commented out code? That way it should be easier to understand the context over why it's commented out.

edit: instead of creating a tracker which fixes the issue by avoiding it - I've updated the tracker so that it reflects the required changes - See: https://tracker.ceph.com/issues/70180.

done

@mohit84
Copy link
Contributor Author

mohit84 commented Feb 27, 2025

jenkins test make check

@Matan-B Matan-B requested a review from xxhdx1985126 February 27, 2025 08:42
Copy link
Contributor

@Matan-B Matan-B left a comment

Choose a reason for hiding this comment

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

@xxhdx1985126
Copy link
Contributor

Sorry, I forgot to implement the throttler releasing in BackfillState, will fix it.

@Matan-B
Copy link
Contributor

Matan-B commented Mar 6, 2025

@xxhdx1985126 pushed a PR with a full revert of the faulty commit - #62080
Let's either revert the commit here or close this on favor to #62080.
@mohit84, what do you think?

@Matan-B Matan-B moved this from Needs QA to In Progress in Crimson Mar 6, 2025
@mohit84
Copy link
Contributor Author

mohit84 commented Mar 6, 2025

@xxhdx1985126 pushed a PR with a full revert of the faulty commit - #62080 Let's either revert the commit here or close this on favor to #62080. @mohit84, what do you think?

I am ok if #62080 only revert the commit but the pull request has one more change. I think @xxhdx1985126 need to refresh the pull request. for the other change related to introduce per pg push limit we should merge via new tracker bug.

@Matan-B
Copy link
Contributor

Matan-B commented Mar 6, 2025

Let's keep #62080 as is. If this issue blocks you in other work - we can push the revert here and merge it separately. Otherwise, let's wait for the other PR to merge and we could close this PR in this case.

@mohit84
Copy link
Contributor Author

mohit84 commented Mar 6, 2025

I am closing the pull request , the earlier change will revert via #62080

@mohit84 mohit84 closed this Mar 6, 2025
@Matan-B Matan-B removed this from Crimson Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants