Actions
Bug #38009
closedclient: session flush does not cause cap release message flush
Status:
Resolved
Priority:
Urgent
Assignee:
Category:
Performance/Resource Usage
Target version:
% 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:
Crash signature (v1):
Crash signature (v2):
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.
Updated by Patrick Donnelly about 5 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 26082
Updated by Patrick Donnelly about 5 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #38103: mimic: client: session flush does not cause cap release message flush added
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #38104: luminous: client: session flush does not cause cap release message flush added
Updated by Patrick Donnelly about 5 years ago
- Status changed from Pending Backport to Resolved
Actions