Actions
Bug #36396
openmds: handle duplicated uuid in multi-mds cluster
Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
current code can't detect following case:
clientA open mds.0 session with uuid
clientB open mds.1 session with the same uuid
Updated by Zheng Yan over 5 years ago
- Related to Feature #26974: mds: provide mechanism to allow new instance of an application to cancel old MDS session added
Updated by Jeff Layton over 5 years ago
I think we want to kick clientA's session out at this point and let clientB take over (i.e. last one wins).
The question is what should happen to clientA? Ideally I think we'd want to consider it something like a forcible umount and start returning ENOTCONN on most libcephfs calls.
Updated by Patrick Donnelly over 5 years ago
Simple solution to this is to evict both sessions when we detect this and log an error.
Actions