Actions
Feature #3857
closedmds: enforce unique mds names in mdsmap
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:
Description
Currently mds's are uniquely identified by their addr (i.e., a unique instance of the process). The name is useful only as a convenient identifier.
Instead, (optionally) enforce that mds's in the mdsmap have unique names. When an mds boots/joins, any previous mds with the same name is failed and booted.
This makes the names a bit less confusing. It also means that if you restart a daemon, it immediately takes over for its previous instantiation without having to wait for the beacon to time out.
OTOH, if there are two mds's with the same name due to a misconfiguration, they will fight each other.
Actions