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
Hi,
I was discovering the template and found that there's multiple sizing option for the monitoring node.
pubsubplus-aws-ha-quickstart/templates/solace-master.template
Line 198 in 26cae87
My understanding (I'm still new to Solace), is that the monitoring node load doesn't grow with the load on the broker.
Any reason to have more resources on the monitoring node ?
The text was updated successfully, but these errors were encountered:
Hi @dev-mansonthomas , correct that monitoring node load doesn't grow with the load on the broker. For production, adding 1-2GB extra memory is generally always recommended. Also for upgrades it would be good that there is more RAM and disk space for future use. As you may already know it, the minimum resource requirements are available from https://docs.solace.com/Configuring-and-Managing/SW-Broker-Specific-Config/System-Resource-Requirements.htm?Highlight=resource#res-req-container
Sorry, something went wrong.
Thanks Balázs for the explanation !
No branches or pull requests
Hi,
I was discovering the template and found that there's multiple sizing option for the monitoring node.
pubsubplus-aws-ha-quickstart/templates/solace-master.template
Line 198 in 26cae87
My understanding (I'm still new to Solace), is that the monitoring node load doesn't grow with the load on the broker.
Any reason to have more resources on the monitoring node ?
The text was updated successfully, but these errors were encountered: