Project

General

Profile

Actions

Bug #24687

closed

Automatically set expected_num_objects for new pools with >=100 PGs per OSD

Added by Douglas Fuller almost 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Category:
Administration/Usability
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
mimic,luminous
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor, OSD
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Field experience has demonstrated significant performance impact from filestore split and merge activity. The expected_num_objects hint to ceph osd pool create mitigates this impact. Assume that pools created with 50 or more PGs per OSD are expected to store a large number of objects and pre-split their collections automatically.


Related issues 4 (1 open3 closed)

Blocked by RADOS - Bug #24686: change default filestore_merge_threshold to -10ResolvedDouglas Fuller06/28/2018

Actions
Blocks RADOS - Cleanup #25124: Add message to consult pgcalc for expected_num_objectsNew07/26/2018

Actions
Copied to RADOS - Backport #25144: mimic: Automatically set expected_num_objects for new pools with >=100 PGs per OSDResolvedNathan CutlerActions
Copied to RADOS - Backport #25145: luminous: Automatically set expected_num_objects for new pools with >=100 PGs per OSDResolvedNathan CutlerActions
Actions #1

Updated by Douglas Fuller almost 6 years ago

  • Blocked by Bug #24686: change default filestore_merge_threshold to -10 added
Actions #2

Updated by Douglas Fuller almost 6 years ago

  • Subject changed from Automatically set expected_num_objects for new pools with >50 PGs per OSD to Automatically set expected_num_objects for new pools with >=50 PGs per OSD
Actions #3

Updated by Douglas Fuller almost 6 years ago

Also include >1024 PGs overall

Actions #4

Updated by Nathan Cutler almost 6 years ago

  • Backport changed from luminous to mimic,luminous
Actions #5

Updated by Douglas Fuller almost 6 years ago

  • Status changed from In Progress to Fix Under Review

Because a value for expected_num_objects is too difficult to determine automatically, instead we print a suggestion that the user consult pgcalc.

Actions #7

Updated by Neha Ojha almost 6 years ago

  • Subject changed from Automatically set expected_num_objects for new pools with >=50 PGs per OSD to Automatically set expected_num_objects for new pools with >=100 PGs per OSD
  • Status changed from Fix Under Review to 7
Actions #8

Updated by Douglas Fuller over 5 years ago

Removed pgcalc message while pgcalc updates are considered

Actions #9

Updated by Douglas Fuller over 5 years ago

  • Blocks Cleanup #25124: Add message to consult pgcalc for expected_num_objects added
Actions #10

Updated by Douglas Fuller over 5 years ago

  • Status changed from 7 to Pending Backport
Actions #11

Updated by Nathan Cutler over 5 years ago

  • Copied to Backport #25144: mimic: Automatically set expected_num_objects for new pools with >=100 PGs per OSD added
Actions #12

Updated by Nathan Cutler over 5 years ago

  • Copied to Backport #25145: luminous: Automatically set expected_num_objects for new pools with >=100 PGs per OSD added
Actions #13

Updated by Nathan Cutler over 5 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF