Project

General

Profile

Actions
Copy link

Bug #46830

closed

mds: do not raise "client failing to respond to cap release" when client working set is reasonable

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

Status:
Resolved
Priority:
High
Assignee:
Patrick Donnelly
Category:
-
Target version:
Ceph - v16.0.0
% Done:

0%

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

Description

If a client has more than mds_min_caps_per_client caps pinned due to open files and the MDS is trying to recall caps because the client appears quiescent, we see unnecessary "client failing to respond to cap release" messages from the MDS.

Change Beacon to not send this warning if the client's caps is below some larger threshold (like 10k).

Related issues 2 (0 open — 2 closed)

Copied to CephFS - Backport #46859: octopus: mds: do not raise "client failing to respond to cap release" when client working set is reasonableResolvedNathan CutlerActions
Copied to CephFS - Backport #46860: nautilus: mds: do not raise "client failing to respond to cap release" when client working set is reasonableResolvedPatrick DonnellyActions
Actions
Copy link

Also available in: Atom PDF