Project

General

Profile

Bug #6910

don't query empty osds for unfound

Added by Samuel Just over 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
% Done:

0%

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

Related issues

Duplicated by Ceph - Bug #7872: PG: all_unfound_are_queried_or_lost must skip dne replicas Duplicate 03/26/2014

Associated revisions

Revision 838b6c83 (diff)
Added by Samuel Just over 10 years ago

PG: don't query unfound on empty pgs

When the replica responds, it responds with a notify
rather than a log, which the primary then ignores since
it is already in the peer_info map. Rather than fix that
we'll simply not send queries to peers we already know to
have no unfound objects.

Fixes: #6910
Signed-off-by: Samuel Just <>
Reviewed-by: Sage Weil <>
Reviewed-by: David Zafman <>

Revision c6f754c5 (diff)
Added by Samuel Just about 10 years ago

PG: don't query unfound on empty pgs

When the replica responds, it responds with a notify
rather than a log, which the primary then ignores since
it is already in the peer_info map. Rather than fix that
we'll simply not send queries to peers we already know to
have no unfound objects.

Fixes: #6910
Signed-off-by: Samuel Just <>
Reviewed-by: Sage Weil <>
Reviewed-by: David Zafman <>
(cherry picked from commit 838b6c8387087543ce50837277f7f6b52ae87d00)

Revision 41d5e9ab (diff)
Added by Samuel Just about 10 years ago

PG: don't query unfound on empty pgs

When the replica responds, it responds with a notify
rather than a log, which the primary then ignores since
it is already in the peer_info map. Rather than fix that
we'll simply not send queries to peers we already know to
have no unfound objects.

Fixes: #6910
Signed-off-by: Samuel Just <>
Reviewed-by: Sage Weil <>
Reviewed-by: David Zafman <>
(cherry picked from commit 838b6c8387087543ce50837277f7f6b52ae87d00)

History

#1 Updated by Samuel Just over 10 years ago

  • Status changed from New to Pending Backport

#2 Updated by Samuel Just about 10 years ago

  • Priority changed from Normal to Urgent

#3 Updated by Sage Weil about 10 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF