Project

General

Profile

Actions

Bug #40415

closed

rgw_file: directory expiration should respect nfs_rgw_namespace_expire_secs

Added by Matt Benjamin almost 5 years ago. Updated about 3 years ago.

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

0%

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

Description

Predictably, slow NFS operations like READDIR will overlap mtime
advance, so don't advance faster than the nfs namespace expiration timer.


Related issues 3 (0 open3 closed)

Copied to rgw - Backport #40626: mimic: rgw_file: directory expiration should respect nfs_rgw_namespace_expire_secsResolvedNathan CutlerActions
Copied to rgw - Backport #40627: nautilus: rgw_file: directory expiration should respect nfs_rgw_namespace_expire_secsResolvedPrashant DActions
Copied to rgw - Backport #40628: luminous: rgw_file: directory expiration should respect nfs_rgw_namespace_expire_secsRejectedActions
Actions #1

Updated by Matt Benjamin almost 5 years ago

  • Status changed from In Progress to Fix Under Review
Actions #2

Updated by Matt Benjamin almost 5 years ago

  • Pull request ID set to 28632
Actions #3

Updated by Matt Benjamin almost 5 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40626: mimic: rgw_file: directory expiration should respect nfs_rgw_namespace_expire_secs added
Actions #5

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40627: nautilus: rgw_file: directory expiration should respect nfs_rgw_namespace_expire_secs added
Actions #6

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40628: luminous: rgw_file: directory expiration should respect nfs_rgw_namespace_expire_secs added
Actions #7

Updated by Nathan Cutler about 3 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".

Actions

Also available in: Atom PDF