Red Hat Bugzilla – Bug 912525
need to add concurrency limit to configuration updates from agent
Last modified: 2013-02-19 15:14:30 EST
Configuration updates from the agent can be expensive, and when you have lots of agents, it ends up clobbering the server and DB. We should add a new concurrency limit to:
We may in the long run try to "unwind" the whole configuration structure on disk, as the recursive structure does a lot of joins on the property table.
Also the endless nesting is a pita in so many places, so that we may want to limit the possible depth (and thus also the number of joins on the table itself).
( the next may not directly apply to our case, the article itself is a good reading anyway )
"queries on queries ("cascades") are often imperformant when not tuned for speed. Like view-on-view cascades, only the deepest query/view can use indexes, while the pendend super-selects always are full table scans (of the result set) inside the database cache! If You cannot escape this, than make sure that Your deepest result sets are as small as possible, and put all the WHERE filters there!"
adding a new concurrency limit requires changes to the docs:
and rhq-server.properties - something like:
master git commit: 3005a262a20961e6c8583e02953d9af1501d8c68
this is a code change - not much to do to test. If you want to see this, turn on debug messages in server. In rhq-server.properties, set "rhq.server.concurrency-limit.configuration-update" to something low, like 1. Then import alot of resources at the same time (those resources must have <resource-configuration> associated with them). If you hit concurrency limits, you'll see this log message:
"Command not permitted - server reached its limit of concurrent invocations ..."