Actions
Bug #22551
openclient: should flush dirty caps on backgroud
Status:
Need More Info
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
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
the dirty data would have a background thread to do the flush,so we may need to flush dirty caps backgroud too
Updated by Patrick Donnelly over 6 years ago
- Subject changed from client not flush dirty caps on backgroud to client: should flush dirty caps on backgroud
- Component(FS) Client added
Updated by Patrick Donnelly over 6 years ago
- Status changed from New to Need More Info
Dongdong, can you explain more what the problem is? Do you have an issue you've observed?
Updated by dongdong tao over 6 years ago
i'm not sure if i'm right, if there is only one client and opened a file write some data and did not close it. i know the dirty data would be flushed via a background thread every 5 seconds (default?), but i don't see the dirty metedata is flushed. do you think that would be an issue
Updated by Patrick Donnelly over 6 years ago
Dirty metadata should be flushed when the cap is released. It may also happen periodically (I'm not certain).
Updated by dongdong tao over 6 years ago
that's what i'm concerned about, maybe it's not been flushed periodically, it should be easy to verify, will do it
Actions