Skip to content
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

Why is there multiple sizing for Monitoring node ? #55

Open
dev-mansonthomas opened this issue May 21, 2021 · 2 comments
Open

Why is there multiple sizing for Monitoring node ? #55

dev-mansonthomas opened this issue May 21, 2021 · 2 comments

Comments

@dev-mansonthomas
Copy link

Hi,

I was discovering the template and found that there's multiple sizing option for the monitoring node.

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 ?

@bczoma
Copy link
Contributor

bczoma commented May 21, 2021

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

@dev-mansonthomas
Copy link
Author

Thanks Balázs for the explanation !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants