Project

General

Profile

Actions
Copy link

Bug #56151

closed

mgr/DaemonServer:: adjust_pgs gap > max_pg_num_change should be gap >= max_pg_num_change

Added by Kamoltat (Junior) Sirivadhna almost 2 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Kamoltat (Junior) Sirivadhna
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
backport_processed
Backport:
quincy,pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
46785
Crash signature (v1):
Crash signature (v2):

Description

output should say that gap >= max_pg_num_change when pg is trying to scale beyond pgpnum in mgr/DaemonServer:: adjust_pgs

https://github.com/ceph/ceph/pull/44155/files#diff-2de410c19e44c5a7ca3ca756e0464f8101e0218002090e36c55b3b68c40040e6R2781

Related issues 2 (0 open — 2 closed)

Copied to RADOS - Backport #56663: pacific: mgr/DaemonServer:: adjust_pgs gap > max_pg_num_change should be gap >= max_pg_num_changeResolvedKamoltat (Junior) SirivadhnaActions
Copied to RADOS - Backport #56664: quincy: mgr/DaemonServer:: adjust_pgs gap > max_pg_num_change should be gap >= max_pg_num_changeResolvedKamoltat (Junior) SirivadhnaActions
Actions
Copy link

Also available in: Atom PDF