Project

General

Profile

Bug #38009

client: session flush does not cause cap release message flush

Added by Patrick Donnelly 6 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Urgent
Category:
Performance/Resource Usage
Target version:
Start date:
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client
Labels (FS):
Pull request ID:

Description

When the client receives CEPH_SESSION_FLUSHMSG, it simply sends an ACK back to the MDS. At least for the cache drop use-case, we expect that cap recall is processed and that cap release messages have been sent. So, flush the cap release message (which releases in batch) prior to sending the CEPH_SESSION_FLUSHMSG_ACK.


Related issues

Copied to fs - Backport #38103: mimic: client: session flush does not cause cap release message flush Resolved
Copied to fs - Backport #38104: luminous: client: session flush does not cause cap release message flush Resolved

History

#1 Updated by Patrick Donnelly 6 months ago

  • Status changed from In Progress to Need Review
  • Pull request ID set to 26082

#2 Updated by Patrick Donnelly 6 months ago

  • Status changed from Need Review to Pending Backport

#3 Updated by Nathan Cutler 6 months ago

  • Copied to Backport #38103: mimic: client: session flush does not cause cap release message flush added

#4 Updated by Nathan Cutler 6 months ago

  • Copied to Backport #38104: luminous: client: session flush does not cause cap release message flush added

#5 Updated by Patrick Donnelly 5 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF