Recently we keep getting this from from our InsightIQ:
Data Retrieval Delayed
The most recent data that InsightIQ has retrieved from the cluster is more than 15 minutes old.
It recovers by itself but once in a while it gets delayed again. We restarted celog on both clusters, it did not help. Has anyone seen this issue before?
Also is there a way to change the delay time alerting to 30 minutes? We are on v3.1.
I'm not sure if your upgrade has finished or not at this point, but in my experience, that update process counts in Microsoft minutes and usually completes much faster. How is your 3.2 experience going so far?
I've seen it before. Best answer I had was to move from a virtual IIQ to a physical one. Sometimes completely rebuilding it is the only way out of this. Make sure you read the docs closely for how to migrate the iiq data.
InsightIQ 3.1.0 and InsightIQ 3.1.1 suffer from a couple different statistic collection issues that Support would be able to help you with.
In IIQ 3.1.0: there was an issue with a debug string being created in the downsampler that cause intermittent delays in other processes (i.e. the factfetcher); we also saw issues with disk statistics and file heat data causing some issues with API connection to your cluster. All of the issues mentioned here are addressed in code changes that can be applied to your machine.
In IIQ 3.1.1: We saw issues with disk statistics and file heat data being too large to process. This would cause other datasets to become temporarily delayed. These issues are also addressed in code changes that can be applied to your machine.
To engage support, please create a service request. To do so you have a few options:
Yes, I had looked at the SR, and I apologize for not replying sooner.
I see we reset the celog databases on December 8th. The Subject Matter Expert currently working on your SR with the assigned TSE is still seeing some errors; what I am seeing is a lack of logging, which is just as concerning. Celog can be quite finicky, and for those of us who have used Isilon for a long while, we know things often get blamed on it. I would give those services one more restart (leave the DB alone, it is fine) just to make sure it's still working properly.
The longest running API calls that I see on your cluster are:
These are going to be on your cluster in /var/log/apache2/webui_httpd_access.log. The times highlighted in red are the time the request took in milliseconds. The default timeout for IIQ is 20 seconds. (I did edit the log lines here as to not reveal anything specific about your cluster.) These stats are for tracking Filesystem Events in performance reporting. These reports (according to the IIQ 3.2 User Guide) do not affect the Data Retrieval Delay condition, so I would consider an upgrade to IIQ 3.2 (if your release version in the SR is correct).
Let me know if there is anything else I can look in to! As for your SR, I can vouch for the fact that it is in good hands with my Subject Matter Expert.
johnsonka
130 Posts
3969
0
Posted January 11th, 2016 11:00
Hello Daniel,
I'm not sure if your upgrade has finished or not at this point, but in my experience, that update process counts in Microsoft minutes and usually completes much faster. How is your 3.2 experience going so far?