Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Stop migration if custom crushmap is detected #975

Closed
jschmid1 opened this issue Mar 1, 2018 · 3 comments
Closed

Stop migration if custom crushmap is detected #975

jschmid1 opened this issue Mar 1, 2018 · 3 comments
Assignees
@jschmid1
Labels
feature

Comments

@jschmid1
Copy link
Contributor

jschmid1 commented Mar 1, 2018 •
edited
Loading

Currently we do not support the migration of filestore to bluestore OSDs when a custom crushmap is used.

Detect it and bail out is the currently the best solution we can offer.
@jschmid1 jschmid1 changed the title Stop migration Stop migration if custom crushmap is detected Mar 1, 2018
@jschmid1 jschmid1 self-assigned this Mar 1, 2018
@Martin-Weiss
Copy link

Hm and how should someone do the filestore -> bluestore migration, then?

Can´t we document where and with which weight an OSD is located in the crushmap and then re-add it to the same place with the same weight?

@jschmid1
Copy link
Contributor Author

jschmid1 commented Mar 1, 2018

that's the plan. We don't have that automated now.

@jschmid1
Copy link
Contributor Author

done with #1216

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jschmid1 jschmid1

Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@swiftgist @jschmid1 @Martin-Weiss