New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MDS names may not start with a numeric digit. #97
Comments
|
I would slightly prefer a more mnemonic "mds-" prefix, but otherwise, that sounds like a good idea. One thing to note, though, is that metadata servers are not machine-restricted. They are not bound by their data directories and can move around the cluster. As a result, I generally give mine labels like "a", "b", "c". In this case, obviously, we cannot do that, but I wonder if adding and removing arbitrarily-named metadata servers screws with the Ceph database. |
|
I like the "daemon type" prefix and I agree about the statement of volatile MDSs in general. Let's start by fixing this and we can always add a bit of doc later. |
This fixes #97 Signed-off-by: Sébastien Han <seb@redhat.com>
This fixes #97 Signed-off-by: Sébastien Han <seb@redhat.com>
Fix Bug. Got the wrong OSD_ID when verify OSD.
Just spotted this:
deprecation warning: MDS id 'mds.7cf73bf1fd74' is invalid and will be forbidden in a future version. MDS names may not start with a numeric digit.An easy work around could be to do something like this on the
MDS_NAMEvariable:: ${MDS_NAME:=a$(hostname -s)}The text was updated successfully, but these errors were encountered: