Hi, "What are these Async updates anyhow?"
A little history here. Once, the collectors would simply update their whole config every now and then. Say, every 20 minutes. This has some issues when you scale to several thousand devices. The whole configuration can take so long to collect, that you begin missing collect cycles. So... enter ZenHub, which tracks updates to the object database and tries to be smart about changes to devices. It forwards configurations as they are changed. In reality, it does this with a little delay so that 10 changes to a device result in a single update to the collectors. These updates are sent asynchronously to the collectors. That is, the collectors are not requesting the configuration, it just arrives and has to be incorporated with the current configuration while the collector is running. They print a little debug message when updates occur. If a device has no commands, and we know *something* changed, we'll actually try to delete the device in case it *used* to have commands. This shouldn't destroy the scheduled list of commands to run, unless you are actually mucking around in the templates, which affect lots of devices at once. If you want to force a push of the current configuration information, try the "Push Changes" menu option at the root of the device tree. I just did some benchtesting, and I found that zencommand was behaving with respect to asynchronous updates. With this in mind, if you could post a little more about your configuration, and the templates you have created, that would help me focus my testing. Here's the bug to track against: http://dev.zenoss.org/trac/ticket/1681 -Eric ------------------------ Eric Newton -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=7933#7933 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
