[bitnami/rabbitmq] Tune parameters to increase performance (#2252)

* Tune parameters to increase performance

* Tune parameters to increase performance

* Update README.md

* Revert changes for the affinity and add a message in README

* [bitnami/rabbitmq] Update components versions

Signed-off-by: Bitnami Containers <containers@bitnami.com>

Co-authored-by: Carlos Rodríguez Hernández <carrodher1179@gmail.com>
Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Rafael Ríos Saavedra
2020-04-15 08:54:13 +02:00
committed by GitHub
parent 44372f6235
commit 4bcde72608
3 changed files with 13 additions and 11 deletions

View File

@@ -205,7 +205,7 @@ Bitnami will release a new chart updating its containers if a new version of the
### Production configuration and horizontal scaling
This chart includes a `values-production.yaml` file where you can find some parameters oriented to production configuration in comparison to the regular `values.yaml`. You can use this file instead of the default one.
This chart includes a `values-production.yaml` file where you can find some parameters oriented to production configuration in comparison to the regular `values.yaml`. You can use this file instead of the default one. In case you want to spread the deployment accross nodes you should configure the affinity parameters.
- Resource needs and limits to apply to the pod:
```diff
@@ -246,7 +246,6 @@ This chart includes a `values-production.yaml` file where you can find some para
- volumePermissions.enabled: false
+ volumePermissions.enabled: true
```
To horizontally scale this chart once it has been deployed you have two options:
- Use `kubectl scale` command

View File

@@ -14,7 +14,7 @@
image:
registry: docker.io
repository: bitnami/rabbitmq
tag: 3.8.3-debian-10-r46
tag: 3.8.3-debian-10-r47
## set to true if you would like to see extra information on logs
## it turns BASH and NAMI debugging in minideb
@@ -97,11 +97,12 @@ rabbitmq:
setUlimitNofiles: true
ulimitNofiles: '65536'
## RabbitMQ maximum available scheduler threads and online scheduler threads
## RabbitMQ maximum available scheduler threads and online scheduler threads. By default it will create a thread per CPU detected, with the following parameters you can tune it manually.
## ref: https://hamidreza-s.github.io/erlang/scheduling/real-time/preemptive/migration/2016/02/09/erlang-scheduler-details.html#scheduler-threads
## ref: https://github.com/bitnami/charts/issues/2189
##
maxAvailableSchedulers: 2
onlineSchedulers: 1
# maxAvailableSchedulers: 2
# onlineSchedulers: 1
## Plugins to enable
plugins: "rabbitmq_management rabbitmq_peer_discovery_k8s rabbitmq_prometheus"
@@ -339,8 +340,9 @@ updateStrategy:
nodeSelector:
beta.kubernetes.io/arch: amd64
tolerations: []
affinity: {}
## Pod AntiAffinity is set to avoid two pods in the same node and increase performance
## ref: https://github.com/bitnami/charts/issues/2189
## affinity: |
## podAntiAffinity:
## requiredDuringSchedulingIgnoredDuringExecution:

View File

@@ -14,7 +14,7 @@
image:
registry: docker.io
repository: bitnami/rabbitmq
tag: 3.8.3-debian-10-r46
tag: 3.8.3-debian-10-r47
## set to true if you would like to see extra information on logs
## it turns BASH and NAMI debugging in minideb
@@ -97,11 +97,12 @@ rabbitmq:
setUlimitNofiles: true
ulimitNofiles: '65536'
## RabbitMQ maximum available scheduler threads and online scheduler threads
## RabbitMQ maximum available scheduler threads and online scheduler threads. By default it will create a thread per CPU detected, with the following parameters you can tune it manually.
## ref: https://hamidreza-s.github.io/erlang/scheduling/real-time/preemptive/migration/2016/02/09/erlang-scheduler-details.html#scheduler-threads
## ref: https://github.com/bitnami/charts/issues/2189
##
maxAvailableSchedulers: 2
onlineSchedulers: 1
# maxAvailableSchedulers: 2
# onlineSchedulers: 1
## Plugins to enable
plugins: "rabbitmq_management rabbitmq_peer_discovery_k8s"