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

Support NFS #16686

Open
jonathanlukas opened this issue Mar 4, 2024 · 1 comment
Open

Support NFS #16686

jonathanlukas opened this issue Mar 4, 2024 · 1 comment
Labels
component/zeebe Related to the Zeebe component/team kind/feature Categorizes an issue or PR as a feature, i.e. new behavior

Comments

@jonathanlukas
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Some users are having a hard time finding a proper storage type as they are restricted by several factors, including policies.

I know that NFS will probably not have the best impact on performance, but this is not required anyway if nfs is taken into account.

Describe the solution you'd like
The possibility to use zeebe on nfs. I see 2 options:

  • everything works ootb (might be more complex)
  • a "NFS mode" to enable that will adjust the interaction behaviour with the disk

Describe alternatives you've considered
no

Additional context
Slack thread: https://camunda.slack.com/archives/CSQ2E3BT4/p1708935461926099

@jonathanlukas jonathanlukas added the kind/feature Categorizes an issue or PR as a feature, i.e. new behavior label Mar 4, 2024
@megglos
Copy link
Contributor

megglos commented Mar 5, 2024

@carlo-camunda this would fit this Product Hub epic https://github.com/camunda/product-hub/issues/2030

@romansmirnov romansmirnov added the component/zeebe Related to the Zeebe component/team label Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/zeebe Related to the Zeebe component/team kind/feature Categorizes an issue or PR as a feature, i.e. new behavior
Projects
None yet
Development

No branches or pull requests

3 participants