Project

General

Profile

Actions

Bug #41939

open

Scaling with unfound options might leave PGs in state "unknown"

Added by David Zafman over 4 years ago. Updated over 4 years ago.

Status:
Need More Info
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

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

Description

With osd_pool_default_pg_autoscale_mode="on"

../qa/run-standalone.sh TEST_rep_recovery_unfound

The test failure doesn't matter, but this PG state seen at the end of the test may be a problem. At least with recovery it is halted as indicated with recovery_unfound PG state.

2.1 0 0 0 0 0 0 0 0 0 0 unknown 2019-09-19T18:52:36.610738-0700 0'0 0:0 [] -1 [] -1 0'0 2019-09-19T18:52:36.610738-0700 0'0 2019-09-19T18:52:36.610738-0700 0
2.3 0 0 0 0 0 0 0 0 0 0 unknown 2019-09-19T18:52:36.610738-0700 0'0 0:0 [] -1 [] -1 0'0 2019-09-19T18:52:36.610738-0700 0'0 2019-09-19T18:52:36.610738-0700 0


Related issues 1 (0 open1 closed)

Related to RADOS - Bug #41900: auto-scaler breaks many standalone testsResolvedDavid Zafman09/17/2019

Actions
Actions #1

Updated by David Zafman over 4 years ago

  • Related to Bug #41900: auto-scaler breaks many standalone tests added
Actions #2

Updated by Neha Ojha over 4 years ago

How are we ending up in this state? What the previous states on the those PGs?

Actions #3

Updated by Neha Ojha over 4 years ago

  • Status changed from New to Need More Info
Actions

Also available in: Atom PDF