Project

General

Profile

Actions

Bug #41141

closed

mds: recall capabilities more regularly when under cache pressure

Added by Patrick Donnelly over 4 years ago. Updated almost 4 years ago.

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

0%

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

Description

If a client is doing a large parallel create workload, the MDS may not recall capabilities fast enough and the client capabilities grow without bound.

Two things should happen here: the MDS should more regularly recall client state. The upkeep thread currently operates every 5 seconds. Second, the MDS defaults for client recall are too conservative. A client may obtain significantly more capabilities than can be recalled.

See also: https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/AOYWQSONTFROPB4DXVYADWW7V25C3G6Z/


Related issues 2 (0 open2 closed)

Copied to CephFS - Backport #41467: nautilus: mds: recall capabilities more regularly when under cache pressureResolvedNathan CutlerActions
Copied to CephFS - Backport #41468: mimic: mds: recall capabilities more regularly when under cache pressureRejectedPatrick DonnellyActions
Actions #1

Updated by Patrick Donnelly over 4 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 29542
Actions #2

Updated by Patrick Donnelly over 4 years ago

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

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41467: nautilus: mds: recall capabilities more regularly when under cache pressure added
Actions #4

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41468: mimic: mds: recall capabilities more regularly when under cache pressure added
Actions #5

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".

Actions

Also available in: Atom PDF