Hi Rob, rtirak
So in working with support, this may be attributed to when the discovery_servers "probeDiscovery" queue starts to backup. If you check on your primary hub hub's queue status and check the "probeDiscovery" queue mine from time to time has a backup. I think that's when the remote hubs start getting this backup. Just a guess at this point.
I then noticed that when I have this backup, if I cycle the "qos_processor" probe my "probeDiscovery" queue magically empties out.
So what I did was put a timer on my qos_processor and have it run at 15 min intervals all thru the day. This has prevented so far any discovery_server queue backups. Also I checked today and for the 1st time over this weekend, when I checked the remote hubs I did not have a "discovery" folder filled with GB's of queue files. It was empty.
TLDR:
> Change to the qos_processor's r-click: "EDIT" dialog with the following:
Type: timed
Active [X]
Range From: 00:00
Range To: 23:59
Execution Interval [x] : 15 Min
> This seemed to prevent any discovery_server "probeDiscovery" queue backups
> Which then seems to prevent any vmware or cisco_ucs "discovery" folders from getting filled up as well.