Project

General

Profile

Bug #41412

multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry

Added by Casey Bodley about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Casey Bodley
Target version:
-
% Done:

0%

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

Description

BucketSyncSingleEntry is supposed to filter out ENOENT (404 Not Found) errors, but there is one case where it accidentally returns that as a fatal error up the stack to DataSyncSingleEntry. DataSyncSingleEntry misinterprets ENOENT to mean that the bucket doesn't exist, so it doesn't schedule the failed bucket sync for retries.

Related issues

Copied to rgw - Backport #41626: luminous: multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry Resolved
Copied to rgw - Backport #41627: nautilus: multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry Resolved
Copied to rgw - Backport #41628: mimic: multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry Resolved

History

#1 Updated by Casey Bodley about 4 years ago

  • Status changed from New to Fix Under Review
  • Assignee set to Casey Bodley
  • Pull request ID set to 29856

#2 Updated by Casey Bodley about 4 years ago

  • Status changed from Fix Under Review to 7

#3 Updated by Casey Bodley about 4 years ago

  • Status changed from 7 to Pending Backport

#4 Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #41626: luminous: multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry added

#5 Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #41627: nautilus: multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry added

#6 Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #41628: mimic: multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry added

#7 Updated by Nathan Cutler almost 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF