-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Support block.wal in not-PVC deployment #14142
Comments
Have you tried with the storage:
config:
metadataDevice: nvme01 The storage:
nodes:
- name: node1
config:
metadataDevice: nvme01 This will pass the device to the |
@travisn Yes, https://rook.io/docs/rook/latest-release/CRDs/Cluster/ceph-cluster-crd/#osd-configuration-settings |
@travisn Yes I mean use a separate device for wal, I have checked the code of rook and I confirm that rook support only ONE metadata device for both db and wal for non-PVC disk, but if you use PVC for osd, you can use separate wal device. |
Rook seems support block.wal only if the osd is running under PVC, It would be better if we can use block.wal for high speed devices in host.
Is this a bug report or feature request?
What should the feature do:
What is use case behind this feature:
Environment:
The text was updated successfully, but these errors were encountered: