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.

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

Client storage backend should be removed as a configurable backend #3323

Closed
kostko opened this issue Sep 25, 2020 · 0 comments · Fixed by #3373
Closed

Client storage backend should be removed as a configurable backend #3323

kostko opened this issue Sep 25, 2020 · 0 comments · Fixed by #3373
Assignees
Labels
c:breaking/cfg Category: breaks configuration c:runtime Category: runtime c:storage Category: storage

Comments

@kostko
Copy link
Member

kostko commented Sep 25, 2020

The storage.backend configuration option should only have an effect for storage nodes and should not be needed for client nodes (where it must currently be set to client). The storage backend init should also be moved under go/worker/storage and the configuration options under worker.storage.*.

Note that compute nodes already automatically use the correct storage backend and the client node should do the same automatically.

This would make it easier to run client nodes as there would be one less configuration parameter to misconfigure.

@kostko kostko added c:storage Category: storage c:runtime Category: runtime c:breaking/cfg Category: breaks configuration labels Sep 25, 2020
@jberci jberci self-assigned this Sep 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:breaking/cfg Category: breaks configuration c:runtime Category: runtime c:storage Category: storage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants