Project

General

Profile

Actions

Bug #13475

closed

PG is always incomple although some replica has all the updates

Added by chuanhong wang over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

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

Description

PG is always incomple although some replica has all the updates, just because the sum of good replicas is less than the min_size of its pool. For example, pg A has 3 replicas, its min replica num is 2, but jus one of its replicas has all the updates, and the others don't have some latest updates, then the pg can't be recovered automatically and can't be tansitioned to be active+clean.
In the ceph source code, if a pg is in GetLog state, it will call choose_acting to compare whether the num of good replicas and the min_size of its pool, if less than, the pg will enter incomple state. Is this process reasonable?

Actions #1

Updated by Samuel Just over 8 years ago

  • Status changed from New to Closed

This behavior is improved in hammer and newer -- the pg will go into a "peered" state where it will perform recovery and backfill a new peer without accepting reads and writes.

Actions

Also available in: Atom PDF