Difference between 'Actual Maximum' and 'Configured Maximum' stats in Solace Broker
We have a Solace PubSub+ Event Broker where we would like to configure certain limits, such as max-endpoints in a message VPN, max-egress-flows, etc. However, on changing a value (e.g. changing max-endpoints to 4500) using CLI or SEMP, we see the following output:
Queues and Topic-Endpoints
Maximum Queues and Topic-Endpoints: 100
Configured Max Queues and T-Es: 4500
After configuring, the actual number of queues allowed in the message VPN is still the previous value (100), while a separate item shows the configured max (4500). Similarly for other configs such as max egress/ingress flows, two such maximum values are shown. However, the desired behaviour is not achieved and the VPN still allows only 100 queues.
The max-endpoints-per-client-username and configured-max-endpoints-per-client-username values are different (77) , and the queues are not owned by any client username.
Hence, could you please clarify what is represented by the 'Actual Max' values, as compared with the 'Configured Max' values, and how the actual values can be configured.
Best Answer
-
Hi @soham ,
You are probably bumping into the system limits of your software broker.
All software brokers can be run in different "sizes" or scaling tiers as we call them and will provide different system limits depending on the scaling tier that they are running with.
You can configure higher limits on the VPN level and therefor oversubscribing your broker, but you will only be able to consume as many resources as the broker has available at the system level. That is, until you scale up your broker to a higher tier and make more resoures available at the system/broker level.
Keep in mind that running a broker with a higher scaling tier also requires more system resources like number of CPU cores, memory etc.
You can find more details on scaling tiers here:
https://docs.solace.com/Software-Broker/System-Scaling-Parameters.htm
Also take a look at this handy calculator that helps you figure out how many resources you need for each of the various scaling tiers, here:
https://docs.solace.com/Software-Broker/System-Resource-Calculator.htm
I think in your case, you are probably running a 100 scaling tier broker and are therefore bumping into a maximum of 100 supported endpoints.
You can increase your broker scaling tier to 1000 (for standard edition brokers) or even higher to 10k, 100k, or 200k (for enterprise edition brokers) to get support for more endpoints.
Hope this helps.
Best regards,
Christian
2
Answers
-
Hi @soham ,
You are probably bumping into the system limits of your software broker.
All software brokers can be run in different "sizes" or scaling tiers as we call them and will provide different system limits depending on the scaling tier that they are running with.
You can configure higher limits on the VPN level and therefor oversubscribing your broker, but you will only be able to consume as many resources as the broker has available at the system level. That is, until you scale up your broker to a higher tier and make more resoures available at the system/broker level.
Keep in mind that running a broker with a higher scaling tier also requires more system resources like number of CPU cores, memory etc.
You can find more details on scaling tiers here:
https://docs.solace.com/Software-Broker/System-Scaling-Parameters.htm
Also take a look at this handy calculator that helps you figure out how many resources you need for each of the various scaling tiers, here:
https://docs.solace.com/Software-Broker/System-Resource-Calculator.htm
I think in your case, you are probably running a 100 scaling tier broker and are therefore bumping into a maximum of 100 supported endpoints.
You can increase your broker scaling tier to 1000 (for standard edition brokers) or even higher to 10k, 100k, or 200k (for enterprise edition brokers) to get support for more endpoints.
Hope this helps.
Best regards,
Christian
2
