Project

General

Profile

Actions

Bug #42108

closed

pg_autoscaler: pool "target_size_bytes" setting doesn't allow for T, G, M values

Added by Craig Gardner over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
OSD
Target version:
% Done:

0%

Source:
other
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

In the documentation [1] for Specifying expected pool size", the example command shows the following syntax and explanatory text:

"""
For example,:

ceph osd pool set mypool target_size_bytes 100T

will tell the system that mypool is expected to consume 100 TiB of space.
"""

However, running the command with "T", "G", or "M" modifiers to the value results in an error:

"Error EINVAL: error parsing integer value '1T': Expected option value to be integer, got '1T' "

[1] https://docs.ceph.com/docs/nautilus/rados/operations/placement-groups/#specifying-expected-pool-size


Related issues 1 (0 open1 closed)

Copied to Ceph - Backport #42885: nautilus: pg_autoscaler: pool "target_size_bytes" setting doesn't allow for T, G, M valuesResolvedNathan CutlerActions
Actions #1

Updated by Prashant D over 4 years ago

  • Status changed from New to In Progress
  • Assignee set to Prashant D
Actions #2

Updated by Prashant D over 4 years ago

  • Status changed from In Progress to Fix Under Review
Actions #3

Updated by Nathan Cutler over 4 years ago

  • Backport set to nautilus
Actions #4

Updated by Nathan Cutler over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #42885: nautilus: pg_autoscaler: pool "target_size_bytes" setting doesn't allow for T, G, M values added
Actions #6

Updated by Nathan Cutler over 4 years ago

  • Pull request ID set to 30701
Actions #7

Updated by Nathan Cutler over 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF