Docker - raising system_scaling_maxconnectioncount

Hello all,

I’ve set up 3 message brokers via docker-compose and am attempting to cluster them.

I’ve run into the problem of having to increase the max connection limit from 100 to 1000.
The suggestions that are out there is to increase the limit by setting the environment variable in the docker container:

docker run … -e system_scaling_maxconnectioncount=1000 … solace/solace-pubsub-standard

which does not seem to have the desired effect. I mean it does set this environment variable within the container to 1000 but… I cannot see any changes with the applications behaviour. Do newer versions of dockerized solace-pubsub-standard ignore this env var?

Please advise!

Thanks!

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

The documentation shows that there are two main ways to increase the connection limit on a software event broker:

  1. Using environment variables when starting the container:
--env system_scaling_maxconnectioncount=1000
  1. Using the Solace CLI after the broker is running:
system > scaling > scale max-connections 1000

Note that changing scaling parameters:

  • Requires a broker restart
  • May require additional system resources (CPU/memory)
  • May require recreating the container with modified resource settings

Here are the relevant documentation links:

For docker-compose specifically, you would need to add the environment variable to your docker-compose.yml file. Please refer to the Solace documentation for the specific resource requirements needed for your desired connection limit.

Never mind, once I removed the persistent volume, it worked.

Hi User29,

Once the broker has been created, you need to use the CLI to scale it up. Not sure if this is an HA group of brokers or 3 singletons that you are trying to incorporate into a DMR Cluster. There are doc procedures for both cases.

Here is the HA procedure.

Scaling Up an Existing HA Group

Best Regards,

Paul