-
Notifications
You must be signed in to change notification settings - Fork 290
An example of a production cluster configuration. #401
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
Merged
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Production Example | ||
|
||
This is an example of a good starting point for a production RabbitMQ deployment. It deploys a 3-node cluster with enough resources to handle reasonable traffic. | ||
|
||
Please keep in mind that: | ||
|
||
1. It may not be suitable for YOUR production deployment. Please go through the [Production Checklist](https://www.rabbitmq.com/production-checklist.html) to learn more about production deployment considerations. | ||
|
||
2. While it is important to correctly deploy RabbitMQ cluster for production deployment, it is even more important to correctly use RabbitMQ from your applications. [Production Checklist](https://www.rabbitmq.com/production-checklist.html) covers some of the common issues such as connection churn and polling cunsumers. Please also consider using [Quorum Queues](https://www.rabbitmq.com/quorum-queues.html) since they provide better data safety. | ||
|
||
You can deploy this example like this: | ||
|
||
```shell | ||
kubectl apply -f rabbitmq.yaml | ||
``` | ||
|
||
Please keep in mind that you need a multi-zone Kubernetes cluster with 6 CPUs, 24Gi RAM, 384Gi disk space available as well as a `storageClass` called `ssd` to deploy this example as-is. Of course you can adjust these values to your environment if needed. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
apiVersion: rabbitmq.com/v1beta1 | ||
kind: RabbitmqCluster | ||
metadata: | ||
name: production | ||
spec: | ||
replicas: 3 | ||
resources: | ||
requests: | ||
cpu: 2 | ||
memory: 8Gi | ||
limits: | ||
cpu: 2 | ||
memory: 8Gi | ||
rabbitmq: | ||
additionalConfig: | | ||
mkuratczyk marked this conversation as resolved.
Show resolved
Hide resolved
|
||
cluster_partition_handling = ignore | ||
vm_memory_high_watermark_paging_ratio = 0.99 | ||
disk_free_limit.relative = 1.0 | ||
persistence: | ||
storageClassName: ssd | ||
storage: "128Gi" | ||
mkuratczyk marked this conversation as resolved.
Show resolved
Hide resolved
|
||
override: | ||
statefulSet: | ||
spec: | ||
template: | ||
spec: | ||
containers: [] | ||
topologySpreadConstraints: | ||
- maxSkew: 1 | ||
topologyKey: "topology.kubernetes.io/zone" | ||
whenUnsatisfiable: DoNotSchedule | ||
labelSelector: | ||
matchLabels: | ||
app.kubernetes.io/component: rabbitmq | ||
ChunyiLyu marked this conversation as resolved.
Show resolved
Hide resolved
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.