We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was runnning into an issue where new connections were being refused and tracked it back to the ulimit -n 1024 in the rabbitmq-start script.
ulimit -n 1024
Is there a reason for setting that? Perhaps making it based on an ENV value with default if it's not provided would be a good alternative?
The text was updated successfully, but these errors were encountered:
I tried the following and it seems to work like a charm in my test case:
#!/bin/bash if [[ "${RABBIT_ULIMIT}" ]]; then ulimit -n "${RABBIT_ULIMIT}" else ulimit -n 1024 fi chown -R rabbitmq:rabbitmq /data exec rabbitmq-server $@
Then I just add -e "RABBIT_ULIMIT=unlimited" or some value instead of unlimited and I am able to handle the number of connections I need.
-e "RABBIT_ULIMIT=unlimited"
Sorry, something went wrong.
No branches or pull requests
I was runnning into an issue where new connections were being refused and tracked it back to the
ulimit -n 1024
in the rabbitmq-start script.Is there a reason for setting that? Perhaps making it based on an ENV value with default if it's not provided would be a good alternative?
The text was updated successfully, but these errors were encountered: