Re: Total number of concurrent checks exceeds 15, aborting!
Posted: Wed Jan 20, 2016 4:23 pm
FYI Troy Lea the creator of the plugin is probably the best person to give you the most correct answer. It's hard to give you an exact answer as it depends of a lot of factors.
For comparison, I have 2 VMA's, one per datacenter, each with 6 CPU's. We have 36 ESX servers on 2 datacenters, 6 clusters, 40 datastores. Our 2 VMA's CPU load is very high. As you can imagine there are too many factors to be able to just say you need this or that. I would say you need at least one more VMA, possibly even two more. You also need to calculate some space for extra load in case of problems, as load tends to get higher caused by shorter retry intervals etc.
I would increase the default concurrent checks to 35 for 6 CPU's in box293_check_vmware.pl
Good luck and let us know how it goes.
For comparison, I have 2 VMA's, one per datacenter, each with 6 CPU's. We have 36 ESX servers on 2 datacenters, 6 clusters, 40 datastores. Our 2 VMA's CPU load is very high. As you can imagine there are too many factors to be able to just say you need this or that. I would say you need at least one more VMA, possibly even two more. You also need to calculate some space for extra load in case of problems, as load tends to get higher caused by shorter retry intervals etc.
I would increase the default concurrent checks to 35 for 6 CPU's in box293_check_vmware.pl
Code: Select all
concurrent_checks => {
type => '=i',
help => 'Maximum amount of concurrent checks that can run at any one time. Default is 15. This option helps prevent the vMA appliance from being overloaded.',
required => 0,
default => 35,
}, # End 'concurrent_checks' => {