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

pybind/mgr/pg_autoscaler: Add warning message if pool fail to scale to recommended PG_NUM #57467

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pdvian
Copy link

@pdvian pdvian commented May 14, 2024

The pg_autoscaler fails to scale the pool if the recommended PG_NUM value varies from the current value by more than the scaling threshold. There is no way to get to know why pg_autoscaler is failing to scale the pool.

Log a warning message in mgr if pg_autoscaler is failing to implement recommended PG_NUM.

Fixes: https://tracker.ceph.com/issues/66015

Signed-off-by: Prashant D pdhange@redhat.com

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

…o recommended PG_NUM

The pg_autoscaler fails to scale the pool if the recommended PG_NUM
value varies from the current value by more than the scaling threshold.
There is no way to get to know why pg_autoscaler is failing to scale
the pool.

Log a warning message in mgr if pg_autoscaler is failing to implement
recommended PG_NUM.

Fixes: https://tracker.ceph.com/issues/66015

Signed-off-by: Prashant D <pdhange@redhat.com>
@rzarzynski
Copy link
Contributor

jenkins test api

@rzarzynski rzarzynski requested a review from ljflores May 20, 2024 18:10
Copy link
Contributor

@ljflores ljflores left a comment

Choose a reason for hiding this comment

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

@pdvian I would run this against a rados suite and address any tests that fail due to this warning

@ljflores
Copy link
Contributor

@pdvian I would run this against a rados suite and address any tests that fail due to this warning

On second thought, I thought this would cause a cluster warning, but I took a closer look, and it seems like it's just a log message.

Copy link
Contributor

@ljflores ljflores left a comment

Choose a reason for hiding this comment

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

LGTM except for some minor sentence nits. @kamoltat's review is best to have in addition to mine.

adjust = True
else:
if final_pg_target != p['pg_num_target']:
self.log.warning("pool %s won't scale due to recommended PG_NUM target"
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
self.log.warning("pool %s won't scale due to recommended PG_NUM target"
self.log.warning("pool %s won't scale because recommended PG_NUM target"

Comment on lines +621 to +623
self.log.warning("Please adjust threshold to lower multiple to scale"
" pool %s",
pool_name)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
self.log.warning("Please adjust threshold to lower multiple to scale"
" pool %s",
pool_name)
self.log.warning("To scale pool %s, please adjust threshold to a lower multiple",
pool_name)

Copy link
Member

@kamoltat kamoltat left a comment

Choose a reason for hiding this comment

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

LGTM per Laura's suggested changed as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants