-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[bitnami/scylladb] Add --smp and --memory options for ScyllaDB Docker configuration #68051
Comments
I have tried to include
|
Hello everyone,
scylla_io_setup needs to be executed at least once to create the io-properties file and necessary directories. Otherwise, the command won't run. I manually created the files below. SCYLLADB_IGNORE_INITDB_SCRIPTS should be set to 'yes' because a Scylla server dry run command tries to run without the correct flag. Please find below DOCKERFILE to reproduce issue and workarroud. Dockerfile
run.sh
io.conf
io_properties.yaml
|
Hi! Thank you so much for the insight. Would you like to contribute with a PR including these settings? |
I would love to, but I'm a novice when it comes to Bitnami container scripting and related tasks. The Scylla Bitnami container seems to be a duplicate of the Cassandra container, and I'm not fully proficient in how the functions should be orchestrated and implemented. Do you know who created it? Perhaps they can provide assistance and help with testing for the community. |
You can create the PR and the team will guide you on which elements should be changed. It will also perform several verifications as well. |
I do my best :) |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/scylladb:6.0-debian-12
What architecture are you using?
None
What steps will reproduce the bug?
We are planning to deploy ScyllaDB in a production environment using Docker via Bitnami. However, we require the --smp and --memory options to properly configure the Docker environment. Currently, these options are not available in the configuration provided by Bitnami.
According to the official ScyllaDB documentation, these options are crucial for optimizing performance and managing resources in a production Docker environment. You can find detailed information in the Best Practices for ScyllaDB on Docker documentation.
What is the expected behavior?
Bitnami should include the --smp and --memory options in their Docker configuration for ScyllaDB to align with best practices and ensure optimal performance and resource utilization.
What do you see instead?
None
Additional information
No response
The text was updated successfully, but these errors were encountered: