Can anyone give me insight into how the hydra scheduler used by the Splunk App for VMWare caches API requests during a vCenter server reboot? During a reboot the vCenter server is being slammed by requests from the DCN. Do we have any settings around controlling or modifying this?
In hydra_gateway.log and hydra_access.log I am seeing the following:
2017-01-19 09:03:14,624 INFO [HydraWSGI:8464] [CacheBatchProcessor] parsed cache batch of count=30
2017-01-19 09:03:14,630 INFO [HydraWSGI:8464] [HydraCacheManager] current cache_length=30, checking cache for outdated entries...
2017-01-19 09:03:14,633 INFO POST /hydra/cache/batch '200 OK' - - - 1ms
2017-01-19 09:04:55,558 INFO POST /hydra/cache/batch '200 OK' - - - 7ms
... View more